Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
New Member

Incorrect SIP Route Header modification

Hi,

I am using two Cisco devices (C3845 with Version 15.1(2)T2 and C3945E with Version 15.2(4)M6) to handle SIP calls.
Calls work fine, but I have a problem when call termination side hangs up a call, my Cisco is modifying Route Header with improper data and sends wrong IP to SIP Proxy. Also this is not happening every time, once Route header is properly modified by Cisco, and second time cisco sends wrong Route header (with wrong IP)...
This happens only with one call terminator, with others there is no such problem.

To Summarize, when BYE is coming to Cisco, once Cisco sends BYE with Route Header with own IP (instead of SIP Proxy IP) which is wrong because SIP Proxy sends back such BYE to Cisco and Cisco disconnect it with 481 Call Leg/Transaction Does Not Exist, and second time sends BYE with Route Header with correct SIP Proxy IP. There is no difference between once BYE and second BYE which are coming from call terminator.

On cisco I've enabled debugs:
debug ccsip all
debug voip ccapi all

For improper call in logs I see some errors, but don't no why there are these errors:
 

Sep 23 23:17:18 10.10.10.10 298972: Sep 23 21:17:18: //-1/xxxxxxxxxxxx/SIP/Error/sipUtilPvtVerifyIfRestricted: From header is restricted
Sep 23 23:17:18 10.10.10.10 298973: Sep 23 21:17:18: //-1/xxxxxxxxxxxx/SIP/Error/add_err_resp_hdrs_from_inbound_leg: Error adding header From to container
Sep 23 23:17:18 10.10.10.10 298974: Sep 23 21:17:18: //-1/xxxxxxxxxxxx/SIP/Error/sipUtilPvtVerifyIfRestricted: Content-Length header is restricted
Sep 23 23:17:18 10.10.10.10 298975: Sep 23 21:17:18: //-1/xxxxxxxxxxxx/SIP/Error/add_err_resp_hdrs_from_inbound_leg: Error adding header Content-Length to container
Sep 23 23:17:18 10.10.10.10 298976: Sep 23 21:17:18: //-1/xxxxxxxxxxxx/SIP/Error/sipUtilPvtVerifyIfRestricted: To header is restricted
Sep 23 23:17:18 10.10.10.10 298977: Sep 23 21:17:18: //-1/xxxxxxxxxxxx/SIP/Error/add_err_resp_hdrs_from_inbound_leg: Error adding header To to container
Sep 23 23:17:18 10.10.10.10 298978: Sep 23 21:17:18: //-1/xxxxxxxxxxxx/SIP/Error/sipUtilPvtVerifyIfRestricted: Call-Id header is restricted
Sep 23 23:17:18 10.10.10.10 298979: Sep 23 21:17:18: //-1/xxxxxxxxxxxx/SIP/Error/add_err_resp_hdrs_from_inbound_leg: Error adding header Call-ID to container
Sep 23 23:17:18 10.10.10.10 298980: Sep 23 21:17:18: //-1/xxxxxxxxxxxx/SIP/Error/sipUtilPvtVerifyIfRestricted: Via header is restricted
Sep 23 23:17:18 10.10.10.10 298981: Sep 23 21:17:18: //-1/xxxxxxxxxxxx/SIP/Error/add_err_resp_hdrs_from_inbound_leg: Error adding header Via to container
Sep 23 23:17:18 10.10.10.10 298982: Sep 23 21:17:18: //-1/xxxxxxxxxxxx/SIP/Error/sipUtilPvtVerifyIfRestricted: Cseq header is restricted
Sep 23 23:17:18 10.10.10.10 298983: Sep 23 21:17:18: //-1/xxxxxxxxxxxx/SIP/Error/add_err_resp_hdrs_from_inbound_leg: Error adding header CSeq to container
Sep 23 23:17:18 10.10.10.10 298984: Sep 23 21:17:18: //-1/xxxxxxxxxxxx/SIP/Info/sipGenDestroyContainerContext: Destroying SIP Container=0xC3A72CB4

 

Please see attachments for correct and incorrect behavior of Cisco. As you can see there is no difference in BYE for correct and incorrect behavior of Cisco.
Please help.

1 ACCEPTED SOLUTION

Accepted Solutions
VIP Super Bronze

This is indeed wrong. The UA

This is indeed wrong. The UA/proxy should strip the route header pointing to itself since that route has already been processed and to avoid incorrect routing of calls as seen in this case.This looks like a bug in the software especially since its intermittent. You have two options to resolve this..Oneis to upgrade your ios and see this behaviour changes or use sip profiles to correct this

Please rate all useful posts "The essence of christianity is not the enthronement but the obliteration of self --William Barclay"
3 REPLIES
VIP Super Bronze

This is indeed wrong. The UA

This is indeed wrong. The UA/proxy should strip the route header pointing to itself since that route has already been processed and to avoid incorrect routing of calls as seen in this case.This looks like a bug in the software especially since its intermittent. You have two options to resolve this..Oneis to upgrade your ios and see this behaviour changes or use sip profiles to correct this

Please rate all useful posts "The essence of christianity is not the enthronement but the obliteration of self --William Barclay"
New Member

Hi Ayodeji I will try to use

Hi Ayodeji

 

I will try to use sip profiles to correct this.

Thanks for your reply.

 

Will let know about results.

New Member

Hi, I've used sip profile to

Hi,

 

I've used sip profile to modify a Route header as you advised.

 

 voice class sip-profiles 10
 request BYE sip-header SIP-Req-URI copy "@(.*)" u01
 request BYE sip-header Route modify "@(.*);" "@\u01;"

 

and it works (also on C3845 I need to upgrade IOS to Release 15.1(3)T or a later to be able to use 'copy' in sip profile - but it is not an issue)

 

Thank you Ayodeji.

376
Views
1
Helpful
3
Replies
CreatePlease to create content