07-08-2012 04:12 PM - edited 03-16-2019 12:05 PM
Hello,
I am heaving troubles with cause code transparency on Cisco 3800 working as a IP-to-IP gateway.
Call scenario is as follows: A---> Cisco3845 ---> B, while B is responding with Reason header like following:
Reason: Q.850;cause=19 then Cisco is changing cause code to 18, so as a result it is Reason: Q.850;cause=18.
I have header-passing error-pass through command provided in global configuration mode, but without success.
What is true, 16/31/34 cause codes are forwarded transparently, so i have issues only with some of the cause codes.
Could anybody tell me how to configure cause-code transparency?
My IOS is 12.4(24)T3.
Regards,
Maciej.
Solved! Go to Solution.
07-11-2012 03:01 AM
Hi Maciej,
I have a strong feeling there is something in your IOS or the functionality is not implemented/updated on the CUBE.
I would recommend to have a tac case open and they can have it verified from the BU.
Hope this helps.
Niket
Kindly rate useful posts!!
07-09-2012 01:52 AM
07-09-2012 01:59 AM
Hi Maciej,
Are the parties A and B SIP, if true, this might help
http://www.cisco.com/en/US/docs/ios/voice/cube/configuration/guide/vb-gw-sipsip.html#wp1475564
Regards
Niket
07-09-2012 04:31 PM
Hello,
Here is part of my global config:
voice service voip
cause-code legacy
h323
sip
header-passing error-passthru
so refering to what you've said my config is okay
Here are some ccsip messages debugs:
1)
SIP/2.0 480 No Response
Allow: UPDATE,REFER,INFO
Call-ID: E783FC1D-C94F11E1-B20CA0EA-1CB24DE3@ 10.10.10.2
Contact: < 5060=""> >
CSeq: 101 INVITE
From: <324278129555>;tag=60E389B0-1B3E 324278129555>
Reason: q.850;cause=19
Server: TermGW(gw_sip)
To: <514972111>;tag=00-08181-1a7579d1-063a39312 514972111>
Via: SIP/2.0/UDP 10.10.10.2:5060;received=10.10.10.2;branch=z9hG4bK1136C61BF3
Content-Length: 0
SIP/2.0 480 Temporarily Not Available
Via: SIP/2.0/UDP 10.10.10.50:5060;branch=z9hG4bK-21B5-12274EF4
From: <324278129555>;tag=11064-AS-1a7579d0-6326cf147 324278129555>
To: <514972111>;tag=60E397E8-871 514972111>
Date: Mon, 09 Jul 2012 22:54:42 GMT
Call-ID: 11064-AM-1a7579cf-3abcf4484@termos
CSeq: 333740282 INVITE
Allow-Events: telephone-event
Server: Cisco-SIPGateway/IOS-12.x
Reason: Q.850;cause=18
Content-Length: 0
2)
BYE sip:447570143333@10.10.10.3:5060 SIP/2.0
Call-ID: 7588C644-C93611E1-8FC8C10A-CF29DD8D@10.10.10.3
CSeq: 333719471 BYE
From: <519738444>;tag=00-08038-1a75114b-64a767810 519738444>
Max-Forwards: 29
Reason: q.850;cause=111
To: <447570143333>;tag=603CB0CC-E16 447570143333>
User-Agent: TermGW(gw_sip)
Via: SIP/2.0/UDP 10.10.10.50:5060;branch=z9hG4bK-E5A-12271BDE
Content-Length: 0
BYE sip: 10.10.10.50:5060 SIP/2.0
Via: SIP/2.0/UDP 10.10.10.3:5060;branch=z9hG4bK113AA716E9
From: <519738444>;tag=603CC384-2370 519738444>
To: <447570143333>;tag=13061-RM-1a751149-320844834 447570143333>
Date: Mon, 09 Jul 2012 19:52:45 GMT
Call-ID: 13061-RH-1a751148-07ca41bc7@termos
User-Agent: Cisco-SIPGateway/IOS-12.x
Max-Forwards: 70
Timestamp: 1341863658
CSeq: 101 BYE
Reason: Q.850;cause=16
Content-Length: 0
3)
SIP/2.0 480 Temporarily Not Available
Allow: UPDATE,REFER,INFO
Call-ID: 464FA3EC-C93711E1-A61CA0EA-1CB24DE3@ 10.10.10.2
Contact: < 5060=""> >
CSeq: 101 INVITE
From: <34672969355>;tag=604220E4-2BC 34672969355>
Reason: q.850;cause=31
Server: TermGW(gw_sip)
To: <518855888>;tag=00-07882-1a7520b6-4e2cae385 518855888>
Via: SIP/2.0/UDP 10.10.10.2:5060;received=10.10.10.2;branch=z9hG4bK1132D9151
Content-Length: 0
SIP/2.0 480 Temporarily Not Available
Via: SIP/2.0/UDP 10.10.10.50:5060;branch=z9hG4bK-5A9F-122725A4
From: <34672969355>;tag=16105-JI-1a7520b5-693e47452 34672969355>
To: <518855888>;tag=60422294-E5A 518855888>
Date: Mon, 09 Jul 2012 19:58:23 GMT
Call-ID: 16105-AM-1a7520b4-09de5d2f0@termos
CSeq: 333721732 INVITE
Allow-Events: telephone-event
Server: Cisco-SIPGateway/IOS-12.x
Reason: Q.850;cause=18
Content-Length: 0
so as you may see cause=19 is changes to cause=18, cause=111 to cause=16, cause=31 to cause=18
Any help please...
07-10-2012 07:16 AM
May this misbehaviour be connected with IOS ver?
07-11-2012 03:01 AM
Hi Maciej,
I have a strong feeling there is something in your IOS or the functionality is not implemented/updated on the CUBE.
I would recommend to have a tac case open and they can have it verified from the BU.
Hope this helps.
Niket
Kindly rate useful posts!!
07-12-2012 01:33 AM
Hi,
Thanks for an answer.
At first i need to buy tac support or try with different IOS version.
Important is that i do have correct configuration.
Thanks again.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide