03-03-2011 06:59 AM - edited 03-16-2019 03:45 AM
Hi,
I have a deployment where we have Cisco Call Manager connected to a Mitel via a QSIG connection on an voice gateway (MGCP). The same gateway - also has a PSTN E1 connection configured as H323 for inbound and outbound calls.
There are phones configured on both systems currently that happily pass across the Qsig link. I would like to get calls from the Mitel phones to go outbound to PSTN though and get the following error when trying this:
*Mar 3 14:34:11.403: ISDN Se0/1/0:15 Q931: TX -> CALL_PROC pd = 8 callref = 0x8008
Channel ID i = 0xA98388
Exclusive, Channel 8
*Mar 3 14:34:11.435: ISDN Se0/1/0:15 Q931: TX -> ALERTING pd = 8 callref = 0x8008
Progress Ind i = 0x8188 - In-band info or appropriate now available
*Mar 3 14:34:11.711: ISDN Se0/0/0:15 Q931: RX <- SETUP pd = 8 callref = 0x4C4E
Sending Complete
Bearer Capability i = 0x8090A3
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA98381
Exclusive, Channel 1
Facility i = 0x9FAA068001008201008B0100A119020200D406052B0C024E01300C8004303030300A010204015A
Calling Party Number i = 0x4980, '68+84'
Plan:Private, Type:Subscriber(local)
Called Party Number i = 0x80, '9077XXXXXXXX'
Plan:Unknown, Type:Unknown
*Mar 3 14:34:11.715: ISDN Se0/0/0:15 Q931: TX -> RELEASE_COMP pd = 8 callref = 0xCC4E
Cause i = 0x8081 - Unallocated/unassigned number
I have attached the config of the voice gateway for you to have a look at. Any help would be gratefully received.
Cheers
Dave
03-03-2011 07:42 AM
Its probably something with your dial peers. I was trying to figure it out how they are working, you have a 9T dial peer that looks like it should use it, but it may not be hitting it for some reason.
Do a debug dial peers and make the call again... you can then see if the incoming call from the Mitel is using and what dial peers it picks. If it picked the wrong one, simply adjust it or make an explecite pattern to match the calling number and should send it out. Im not sure if 9 is required, or its not stripping the 9 for you or?
03-04-2011 03:00 PM
Unallocated/unassigned number is usually seen when the number is not recognised by the call manager. Is this issue with only outbound calls or inbound calls as well? It might either not have the right CSS or its not finding the right dial peer here to send the call out. Is 9 here the access code? Then it
should strip the 9 in the call manager itself and then send the call out to the gateway. Is predot discard digits enabled?
03-06-2011 02:39 AM
Hi Guys,
Thanks for the feedback. As the gateway is MGCP - the dial-peers are irrelevant. They were just put in to test really. Because of MGCP -the debug dialpeer does not display anything.
One thing I have noticed this weekend whilst working on a similar system with a QSIG connection to a PBX - is that this configuration works fine in Call Manager 4.2 but not in Call Manager 7.1. Therefore I believe that something has changed relating to this between the versions.
Any ideas? Is this a problem with hairpinning calls? What options can I change to affect this within service parameters?
Regards
Dave
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: