[cisco-voip] Calling Name Issue with Nortel 11c and 61c with QSIG
Syed Khalid Ali
syed.khalid.khursheed at gmail.com
Mon Nov 2 13:55:49 EST 2009
Thank you all for the these resources. I will definitely let you know if it
worked or not. Right now I cannot do any testing with this system since it
is already in production and they do not allow until testing is schedule in
advance with approval.
Lastly any one the group know about this **ERROR**: Ux_BadMsg:...... thing.
I did a lot of googling but could not find any thing useful.
--
Regards,
Syed Khalid Ali
On Mon, Nov 2, 2009 at 1:31 PM, Tim Smith <thsglobal at gmail.com> wrote:
> Another good one.
>
> http://www.cisco.com/en/US/solutions/collateral/ns340/ns517/ns477/ns296/white_paper_c11_459092.html
>
>
>
> On Mon, Nov 2, 2009 at 7:30 PM, Tim Smith <thsglobal at gmail.com> wrote:
>
>> Are there other dial peers on the VG's? or are is the connection purely a
>> trunk between the 2 x PBX's?
>>
>> There are H323 and SIP tunnelling features that should pass the Q.SIG
>> between them transparently.
>>
>> See this for example..
>>
>> http://www.cisco.com/en/US/docs/ios/voice/sip/configuration/guide/tunneling_qsig_ps6441_TSD_Products_Configuration_Guide_Chapter.html
>>
>> Cheers,
>>
>> Tim.
>>
>> On Mon, Nov 2, 2009 at 4:42 PM, Syed Khalid Ali <
>> syed.khalid.khursheed at gmail.com> wrote:
>>
>>> There is NO CallManager involved. Just two voice gateways.
>>>
>>> On Sun, Nov 1, 2009 at 11:31 PM, Nate VanMaren <VanMarenNP at ldschurch.org
>>> > wrote:
>>>
>>>> Is there a Cisco Communications Manager controling the voicegateways?
>>>> H.323 support for QSIG is very very limited, you need to run the gateways
>>>> with MGCP, and you'll get much better results with QSIG.
>>>>
>>>> -Nate
>>>> ------------------------------
>>>> *From:* cisco-voip-bounces at puck.nether.net [
>>>> cisco-voip-bounces at puck.nether.net] On Behalf Of Syed Khalid Ali [
>>>> syed.khalid.khursheed at gmail.com]
>>>> *Sent:* Sunday, November 01, 2009 1:39 AM
>>>> *To:* cisco-voip at puck.nether.net
>>>> *Subject:* [cisco-voip] Calling Name Issue with Nortel 11c and 61c with
>>>> QSIG
>>>>
>>>> Greeting:
>>>>
>>>> I have the following scenario. Two PBXes 11c and 61c. Both connected
>>>> with Cisco Voice gateways as following:
>>>>
>>>> 11c----------------E1----------------VG1----------------VG2----------------61c
>>>> Calls are working fine but I could not able to get the Caller Name at
>>>> each site. Both PBXes are acting the ISDN network side but QSIG.
>>>>
>>>> 11c has extension of 12XX and
>>>> 61c has 2XXX, 3XXX, 4XXX
>>>>
>>>> After looking at the command reference, I concluded that following
>>>> commands should work:
>>>> isdn supp-service name calling
>>>> isdn outgoing display-ie
>>>>
>>>> I did the following config on both sides:
>>>> interface Serial0/3/0:15
>>>> no ip address
>>>> no logging event link-status
>>>> isdn switch-type primary-qsig
>>>> isdn incoming-voice voice
>>>> isdn supp-service name calling
>>>> isdn send-alerting
>>>> isdn sending-complete
>>>> isdn outgoing display-ie
>>>> no cdp enable
>>>>
>>>> but I am getting the following error message in Q931 debugs:
>>>> ISDN Se0/3/0:15 Q931: Applying typeplan for sw-type 0x16 is 0x0 0x1,
>>>> Calling num
>>>> 1216
>>>> ISDN Se0/3/0:15 Q931: Applying typeplan for sw-type 0x16 is 0x0 0x9,
>>>> Called num
>>>> 0302
>>>> ISDN Se0/3/0:15 Q931: TX -> SETUP pd = 8 callref = 0x071A
>>>> Sending Complete
>>>> Bearer Capability i = 0x8090A3
>>>> Standard = CCITT
>>>> Transfer Capability = Speech
>>>> Transfer Mode = Circuit
>>>> Transfer Rate = 64 kbit/s
>>>> Channel ID i = 0xA9839F
>>>> Exclusive, Channel 31
>>>> Progress Ind i = 0x8183 - Origination address is non-ISDN
>>>> Calling Party Number i = 0x0180, '1216'
>>>> Plan:ISDN, Type:Unknown
>>>> Called Party Number i = 0x89, '0302'
>>>> Plan:Private, Type:Unknown
>>>> Locking Shift to Codeset 5
>>>> Codeset 5 IE 0x31 i = 0x80
>>>> Codeset 5 IE 0x32 i = 0x81
>>>> ISDN Se0/3/0:15 Q931: RX <- CALL_PROC pd = 8 callref = 0x871A
>>>> Channel ID i = 0xA9839F
>>>> Exclusive, Channel 31
>>>> ISDN Se0/3/0:15 Q931: RX <- ALERTING pd = 8 callref = 0x871A
>>>> Locking Shift to Codeset 5
>>>> Codeset 5 IE 0x32 i = 0x81
>>>>
>>>> ISDN Se0/3/0:15 Q931: TX -> DISCONNECT pd = 8 callref = 0x071A
>>>> Cause i = 0x8090 - Normal call clearing
>>>> ISDN Se0/3/0:15 Q931: RX <- CONNECT pd = 8 callref = 0x871A
>>>> Progress Ind i = 0x8182 - Destination address is non-ISDN
>>>> Connected Number i = 0x0080, '4446'
>>>> Locking Shift to Codeset 5
>>>> Codeset 5 IE 0x32 i = 0x81
>>>> ISDN Se0/3/0:15 **ERROR**: Ux_BadMsg: Invalid Message for call state
>>>> 11, call id
>>>> 0x8E1D, call ref 0x71A, event 0x7
>>>> ISDN Se0/3/0:15 Q931: TX -> STATUS pd = 8 callref = 0x071A
>>>> Cause i = 0x80E507 - Message not compatible with call state
>>>> Call State i = 0x0B
>>>> ISDN Se0/3/0:15 Q931: RX <- RELEASE pd = 8 callref = 0x871A
>>>> ISDN Se0/3/0:15 Q931: TX -> RELEASE_COMP pd = 8 callref = 0x071A
>>>>
>>>> --
>>>> Thanks,
>>>> Syed Khalid Ali
>>>>
>>>>
>>>>
>>>> NOTICE: This email message is for the sole use of the intended
>>>> recipient(s) and may contain confidential and privileged information. Any
>>>> unauthorized review, use, disclosure or distribution is prohibited. If you
>>>> are not the intended recipient, please contact the sender by reply email and
>>>> destroy all copies of the original message.
>>>>
>>>>
>>>
>>>
>>> --
>>> Thanks,
>>> Syed Khalid Ali
>>>
>>>
>>> _______________________________________________
>>> cisco-voip mailing list
>>>
>>> cisco-voip at puck.nether.net
>>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>>
>>>
>>
>>
>> --
>>
>> Cheers,
>>
>> Tim
>>
>>
>> Sent from Sydney, Nsw, Australia
>>
>
>
>
> --
>
> Cheers,
>
> Tim
>
>
> Sent from Sydney, Nsw, Australia
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20091102/eb77a713/attachment.html>
More information about the cisco-voip
mailing list