Avaya Support Forums  

Go Back   Avaya Support Forums > Avaya Aura & Unified Communications

Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old 01-07-2016, 03:13 AM
rkraut rkraut is offline
Member
 
Join Date: Apr 2015
Posts: 3
rkraut has 10 reputation points
Default SIP trunk - Q.850 reason codes

Dear All,

I have a problem with SIP trunk and reason codes (Q.850). I have two SIP trunks on CM5.2.1 via two SMs. First one is from PSTN and second one is to Cisco (Jabber clients).

I am able to call from PSTN to Jabber extension without problem. As well I am able to call from Jabber to PSTN. It looks good. My problem start when Jabber extension is unregistered or doesn't exist or so on. Customer want to differentiate these calls.

Scenario:
I call from mobile phone to ext on Jabber. Call go from PSTN via SM1 (SIP trunk 141 "PSTN-CM") -> CM 5.2.1 -> SM2 (SIP trunk 116 "CM-CISCO") to Jabber.
Jabber send me back to SM2 SIP/2.0 404 Not Found with reason Reason: Q.850;cause=27. It is correct. SM2 forwards it via SIP trunk 116 to CM.
Then CM sends SIP/2.0 404 to SM1 via trunk 141, but without any reason message.

Trace from SM2 to CM (communication SM1 -> Clan):

Jan 7 11:25:52 sesmlyncmanph1 AasSipMgr[3696]: +01:00 2016 092 1 com.avaya.asm | 1 com.avaya.asm SIPMSGT
--------------------
07/01/2016 11:25:52.092 -->
octets: 1469, Body Length: 0
ingress: { L10.254.108.42:48233/R10.254.114.71:5060/TCP/0x20c4 }
egress: [NO TARGET]
SIPMsgContext: [NONE]
--------------------
SIP/2.0 404 Not Found
P-Site: SM;smgr=10.254.114.79;origloc=98306;origsigloc=983 06;origmedialoc=98306;termloc=98309;termsigloc=983 09;termmedialoc=98309;origent=98308;terment=98310
P-Location: SM;origlocname="CM-pro-Webex-Primary";origsiglocname="CM-pro-Webex-Primary";origmedialocname="CM-pro-Webex-Primary";termlocname="Webex-Secondary";termsiglocname="Webex-Secondary";termmedialocname="Webex-Secondary";smaccounting="true"
Server: Cisco-CUCM10.5 AVAYA-SM-6.3.9.0.639011
Av-Global-Session-ID: 06f87160-b529-11e5-877f-6c3be5b2ada0
Allow-Events: presence
Reason: Q.850;cause=27
Warning: 399 10.254.91.201 "No matching outgoing dial-peer"
Date: Thu, 07 Jan 2016 10:22:59 GMT
To:
Jan 7 11:25:52 sesmlyncmanph1 AasSipMgr[3696]: +01:00 2016 092 1 com.avaya.asm | 1 com.avaya.asm SIPMSGT+ <sip:7753@10.254.108.42>;tag=9A418594-22EF
From: <sip:00420731194278@cz.tmo>;tag=020c4398dc2e51eb31 5637528a00
Call-ID: 020c4398dc2e51ec315637528a00
CSeq: 1 INVITE
Via: SIP/2.0/TCP 10.254.108.42;branch=z9hG4bK927038459695413-AP;ft=2
Via: SIP/2.0/TCP 10.254.108.81:15060;rport=39510;ibmsid=local.14176 67674322_51750535_51750532;branch=z9hG4bK927038459 695413
Via: SIP/2.0/TCP 10.254.108.81:15060;rport;ibmsid=local.14176676743 22_51750534_51750531;branch=z9hG4bK877927155883429
Via: SIP/2.0/TCP 10.254.108.42;branch=z9hG4bK020c4398dc2e51ed315637 528a00-AP;ft=1694438;received=10.254.108.42;rport=59890
Via: SIP/2.0/TCP 10.254.108.27;branch=z9hG4bK020c4398dc2e51ed315637 528a00
Via: SIP/2.0/TCP 10.254.114.22:5060;branch=z9hG4bK-s1632-001325105196-1--s1632-
Content-Length: 0



Trace from SM1 to PSTN (communication clan -> SM1)

Jan 7 11:25:52 sesmhivmanph1 AasSipMgr[4356]: +01:00 2016 169 1 com.avaya.asm | 1 com.avaya.asm SIPMSGT
--------------------
07/01/2016 11:25:52.169 -->
octets: 841, Body Length: 0
ingress: { L10.254.114.15:32323/R10.254.114.12:5060/TCP/0x5 }
egress: [NO TARGET]
SIPMsgContext: [NONE]
--------------------
SIP/2.0 404 Not Found
From: <sip:00420731194278@cz.tmo;user=phone>;tag=C95Xi60 4Xj.0gV.Z
To: <sip:226898909;phone-context=ims.mnc001.mcc230.3gppnetwork.org@cz.tmo;u ser=phone>;tag=80c661378dc2e51ea315637528a00
Call-ID: 68E946E2C4D6F1D9057D734E@4642ffffffff
CSeq: 1 INVITE
Via: SIP/2.0/TCP 10.254.114.15;branch=z9hG4bK913440171544121-AP;ft=7
Via: SIP/2.0/TCP 10.254.114.14:15060;rport=41585;ibmsid=local.14497 93821190_1998394_1999644;branch=z9hG4bK91344017154 4121
Via: SIP/2.0/TCP 10.254.114.14:15060;rport;ibmsid=local.14497938211 90_1998393_1999643;branch=z9hG4bK92944039160599
Via: SIP/2.0/TCP 10.254.114.15;branch=z9hG4bK-s1632-001325105196-1--s1632--AP;ft=85;received=10.254.114.15;
Jan 7 11:25:52 sesmhivmanph1 AasSipMgr[4356]: +01:00 2016 169 1 com.avaya.asm | 1 com.avaya.asm SIPMSGT+ rport=49646
Via: SIP/2.0/TCP 10.254.114.22:5060;branch=z9hG4bK-s1632-001325105196-1--s1632-
Server: Avaya CM/R015x.02.1.016.4
Content-Length: 0


Do you have some idea why CM doesn't forward this reason code? Do I have to set some special value on CM for this Q.850 reasons codes?

Thank you very much for your help.

Best Regards

Radek
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -7. The time now is 05:36 AM.

This Forum is provided solely for the use and convenience of Avaya customers and partners. Use of the Forum is subject to the Terms and Use and Privacy Statement found at www.avaya.com. No other use is permitted. The Forum including all content posted is “AS IS” and Avaya expressly disclaims all warranties and/or guarantees as to its accuracy, reliability, usefulness, quality or non-infringement of intellectual property. Avaya reserves the right to remove any content posted on the Forum at any time and for whatever reason.

Avaya will not be liable for any content posted on this Forum, including, without limitation, any errors or omissions or for any losses or damages of any kind incurred as a result of use or reliance on any content, regardless of its origin.

You expressly understand and agree that you assume all risks associated with use or reliance on this content.