We're doing some pilot testing that involves integrating Nortel PBXs with CCM via QSIG. We just tried to bring up a site into production and discovered that calls that rolled to voice mail were not passing the original called info to the voice mail system.
Here's what the network looks like:
That's a Nortel Option 81C with Meridian Mail. The 81C is connected via QSIG PRI to a 3825. At the remote site, we have a 2811 connected to an Option 11C, also connected via QSIG.
My first thought was to go to the gateway configuration page and check the boxes for Redirecting Number IE Delivery - Outbound and Redirecting Number IE Delivery - Inbound. I did that at both sites and restarted the gateways, but that didn't help.
The path replacement settings are correct, as are the forwarding parameters. For some reason, the original called party info is either not being included by the transferring PBX or is not being recognized by the PBX where Meridian Mail resides.
I've adjusted a couple of QSIG-related parameters and will do more testing when our PBX guru returns from lunch.
Yeah, it should work. That's why it's frustrating. We have a couple of IP phones at our main site that we're using for testing. The IP phones have mailboxes built on the 81C, which resides over a QSIG trunk. Calls to those phones roll to voice mail with no problem. There must be something misconfigured at our remote sites but I have no idea what it could be. This is a fairly straightforward configuration.
I think we're running into a QSIG bug. We just tried a test with an identical configuration on Succession 4.0 and it worked perfectly. It appears that we may need to apply a patch to our Succession 3.0 systems. I've heard that there are a number of QSIG bug fixes available. I have a suspicion that one is available for this problem.
IntroductionCUCM Routing RulesDial String implementation PolicyCUCM Routing LogicSIP URI Call Routing Analysis+++ Case Study: 1 ++++++ Case Study: 2 +++Conclusion
Over the last few months, I have had the privilege of working on SI...
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...