web statisticsweb stats

Business Phone Systems

Previous Thread
Next Thread
Print Thread
Rate Thread
#198758 09/02/09 03:45 AM
Joined: Jan 2009
Posts: 62
AndyK Offline OP
Member
OP Offline
Member
Joined: Jan 2009
Posts: 62
Hi all,

I have a campus environment with three buildings. Two are linked to the main building via wireless bridges. At each remote building there are CIX 40's. At the main building there is a CIX 670 and ies32 voice mail. I'm using mostly IP phones.

When a user at this certain remote building leaves a voice mail for someone at the main building, the display on the phone belonging to the person who received it shows that the message is FRM: 0000013300

When it used to display just FRM:300

The automated voice on the iES would say: "new message from (person's name recording) and then the date, followed by the actual message.

Now the automated voice is saying "Phone number 0000013300" followed by the date and then the message. It seems to represent something. There are five zeros for no reason, but the call is coming from node 13, extension 300. That's the last 5 digits of the number.

I've checked all the parameters in Network eManager and in the iES software I know of and nothing seems amiss. This only happens from that one building with the 300 extensions. Voice mail messages from users at the other building with the CIX 40 does not cause this to occur.

Anyone have any ideas?

Atcom VoIP Phones
VoIP Demo

Best VoIP Phones Canada


Visit Atcom to get started with your new business VoIP phone system ASAP
Turn up is quick, painless, and can often be done same day.
Let us show you how to do VoIP right, resulting in crystal clear call quality and easy-to-use features that make everyone happy!
Proudly serving Canada from coast to coast.

#198759 09/11/09 03:16 PM
Joined: Jan 2007
Posts: 154
Member
Offline
Member
Joined: Jan 2007
Posts: 154
Not sure exactly, but I would lean towards program 579, that where you define the SMDI length and integration.

#198760 09/12/09 05:08 AM
Joined: Mar 2009
Posts: 121
Member
Offline
Member
Joined: Mar 2009
Posts: 121
Andy, 0000013300 represents the Caller ID information coming from the CIX. CLID is turned on in Prg 579, this is a option to enable Caller ID to be sent to the VM via the SMDI link. You can disable the feature and No CLID data will be passed through the SMDI link or you can turn this off per Mail Box "Play Date Time" un-check this option.

More Information;
0000013300, is an 10 digit SMDI string, Stratagy only supports up to 5 digit extensions and this includes the Node ID, in you case 13 followed by the extension 300. So an three digit Node ID and an three digit extension number would have integration issues with Stratagy. Just and FYI.


TCTE/CTP Certified
MCP Certified
#198761 09/14/09 08:35 AM
Joined: Jan 2009
Posts: 62
AndyK Offline OP
Member
OP Offline
Member
Joined: Jan 2009
Posts: 62
First of all thanks guys for responding.

I checked program 579 and didn't find anything out of the ordinary between all three sites. Node 13, a CIX 40 is the only one that does this though.

After some testing I did notice something interesting. It appears that when an internal call is made from the remote site in question to any of the other two sites, and a VM is left, it is being shown as a call from an external number when it in fact was obviously not. Normally when we receive calls from the outside and a VM is left, Stratagy will display(and read) what number the call came from at the time the voicemail is retrieved. This is because we have 579-04 enabled on the CIX 670 which has the Stratagy in it. When internal VM's are left, the Stratagy will show it as being from that mailbox number (example: 200) and generally will play the recorded name for the owner of that mailbox.

When I login and manually send a message from the mailbox, things work as they should. When the message is received at the CIX 670 node, it shows up as FRM:302. When I actually dial from extension 302, and leave a voicemail at say, 241 which is on the CIX 670 node, it shows as being FRM:0000013302 when I log in and listen to the message at station 241.

The 10 digit number is 5 zeros followed by the two digit node number followed by the three digit extension.

For some reason it wants to display it as an external call and not an internal call. The software on the systems was updated 4 or 5 months back to AR5.20 MT025.00.

It seems like all the settings in 579 are correct and I'm not sure where to go from here.

#198762 09/14/09 09:00 AM
Joined: Jan 2006
Posts: 2,266
Likes: 1
Member
*****
Offline
Member
*****
Joined: Jan 2006
Posts: 2,266
Likes: 1
Have you talked to tech support ?

#198763 09/14/09 09:07 AM
Joined: Jan 2006
Posts: 340
Member
Offline
Member
Joined: Jan 2006
Posts: 340
Programming doesn't change by itself. First of all, reset both switches and see if it resolves the issue.


Shawn
Absolute Communications, Inc.
#198764 09/14/09 09:43 AM
Joined: Mar 2009
Posts: 121
Member
Offline
Member
Joined: Mar 2009
Posts: 121
What you described is two different call types;
First call from one node to another, when the call is forwarded, the originating Node sent an SMDI packet specific from that Node, N0000013302.

When calling VM and logging into your box 302 and sending a msg to 241, a packet is sent to "light on" to call the VM pilot number, say Frm:850.
When you log in, the box already knows that it is from 302 and plays the name prompt from MB 302.

So this is what I think is going on, you are using the Network DN Table along with Overlap codes in StrataNet.
Remove the Overlap codes and add each NodeID on all nodes to the Flexible access codes.


TCTE/CTP Certified
MCP Certified
#198765 09/15/09 02:56 AM
Joined: Jan 2009
Posts: 62
AndyK Offline OP
Member
OP Offline
Member
Joined: Jan 2009
Posts: 62
Ron- Thanks for your suggestion, that was close enough to get me there and the issue is resolved!

Basically there was no primary overlap code assigned for the node in question. I noticed on the other remote node the programming had the node id (12) in both 656-01 and 656-Primary Overlap Code. I mirrored these settings on node 13 and things are back to normal. This was possibly changed by the tech who was onsite last updating our system software. He was also troubleshooting a one way audio problem at the same site with DID's.

In any case it's back!

Thanks to everyone for their suggestions.


Moderated by  Carlos#1, phonemeister 

Link Copied to Clipboard
Forum Statistics
Forums84
Topics94,294
Posts638,834
Members49,769
Most Online5,661
May 23rd, 2018
Popular Topics(Views)
212,629 Shoretel
189,518 CTX100 install
187,776 1a2 system
Newest Members
Soulece, Robbks, A2A Networks, James D., Nadisale
49,768 Registered Users
Top Posters(30 Days)
Toner 24
teleco 9
dans 5
dexman 4
Who's Online Now
2 members (justbill, Yoda), 120 guests, and 350 robots.
Key: Admin, Global Mod, Mod
Contact Us | Sponsored by Atcom: One of the best VoIP Phone Canada Suppliers for your business telephone system!| Terms of Service

Sundance Communications is not affiliated with any of the above manufacturers. Sundance Phone System Forums - VOIP & Cloud Phone Help
©Copyright Sundance Communications 1998-2024
Powered by UBB.threads™ PHP Forum Software 7.7.5