Re: Cisco sip-ua sends SIP unregister message(SIP REGISTER MSG with expires field set to 0)

jevgep · ‎05-22-2019

i all,

Basically there is a Cisco 2801 and it is trying to register to SIP service provider.

Below part of the config which relates to SIP registering process:

*****************************************************************************

!
sip-ua
credentials username XXXX password 7 XXXX realm XXX.XXX
no remote-party-id
sip-server dns:XXX.XXX.XXX

registrar dns:XXX.XXX.XXX expires 60
!

********************************************************************************

After registration Cisco 2801 immediately sends SIP REGISTER message with expires field set to 0.

What could be a reason for such behavior ?

You can find SIP trace below:

*May 21 11:00:59.772: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
REGISTER sip:XXX.XXX.XXX:5060 SIP/2.0
Via: SIP/2.0/UDP YYY.YYY.YYY.YYY:5060;branch=z9hG4bK3AD1C5E
From: <sip:sip_user@XXX.XXX.XXX>;tag=48206560-2CE
To: <sip:sip_user@XXX.XXX.XXX>
Date: Tue, 21 May 2019 11:00:59 GMT
Call-ID: 8CFC113F-7AEE11E9-8525B193-993D21B5
User-Agent: Cisco-SIPGateway/IOS-12.x
Max-Forwards: 70
Timestamp: 1558436459
CSeq: 2 REGISTER
Contact: <sip:sip_user@YYY.YYY.YYY.YYY:5060>
Expires:  60
Supported: path
Content-Length: 0


*May 21 11:00:59.820: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 401 Unauthorized 11030230330
Via: SIP/2.0/UDP YYY.YYY.YYY.YYY:5060;branch=z9hG4bK3AD1C5E
To: <sip:sip_user@XXX.XXX.XXX>;tag=h7g4Esbg_5e9c264e01c9f30589634ecc09e5
From: <sip:sip_user@XXX.XXX.XXX>;tag=48206560-2CE
Call-ID: 8CFC113F-7AEE11E9-8525B193-993D21B5
CSeq: 2 REGISTER
Path: <sip:ZZZ.ZZZ.ZZZ.ZZZ;transport=udp;lr>
Service-Route: <sip:ZZZ.ZZZ.ZZZ.ZZZ:5060;transport=udp;lr>
WWW-Authenticate: Digest realm="aaa.aa",nonce="1855BE74C4D2E35C00000000CA42237C",algorithm=MD5,qop="auth"
Content-Length: 0


*May 21 11:00:59.824: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
REGISTER sip:XXX.XXX.XXX:5060 SIP/2.0
Via: SIP/2.0/UDP YYY.YYY.YYY.YYY:5060;branch=z9hG4bK3AE1E79
From: <sip:sip_user@XXX.XXX.XXX>;tag=48206560-2CE
To: <sip:sip_user@XXX.XXX.XXX>
Date: Tue, 21 May 2019 11:00:59 GMT
Call-ID: 8CFC113F-7AEE11E9-8525B193-993D21B5
User-Agent: Cisco-SIPGateway/IOS-12.x
Max-Forwards: 70
Timestamp: 1558436459
CSeq: 3 REGISTER
Contact: <sip:sip_user@YYY.YYY.YYY.YYY:5060>
Expires: 60
Authorization: Digest username="sip_user",realm="aaa.aa",uri="sip:XXX.XXX.XXX:5060",response="038d464cd47521940a8119149104031d",nonce="1855BE74C4D2E35C00000000CA42237C",cnonce="C52C09E1",qop=auth,algorithm=MD5,nc=00000001
Content-Length: 0


*May 21 11:01:00.028: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 200 OK
Via: SIP/2.0/UDP YYY.YYY.YYY.YYY:5060;branch=z9hG4bK3AE1E79
To: <sip:sip_user@XXX.XXX.XXX>;tag=h7g4Esbg_5e9c264e01e5a10589634ecf28e1
From: <sip:sip_user@XXX.XXX.XXX>;tag=48206560-2CE
Call-ID: 8CFC113F-7AEE11E9-8525B193-993D21B5
CSeq: 3 REGISTER
Contact: <sip:sip_user@YYY.YYY.YYY.YYY:5060>;expires=60
P-Associated-Uri: <sip:sip_user@XXX.XXX.XXX>
Service-Route: <sip:ZZZ.ZZZ.ZZZ.ZZZ:5060;transport=udp;lr>
Content-Length: 0
Authentication-Info: qop=auth,rspauth="92084fe725d2c0fb374bfc94c3a16b23",cnonce="C52C09E1",nc=00000001


*May 21 11:01:00.036: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:

REGISTER sip:XXX.XXX.XXX:5060 SIP/2.0
Via: SIP/2.0/UDP YYY.YYY.YYY.YYY:5060;branch=z9hG4bK3AF1E87
From: <sip:sip_user@XXX.XXX.XXX>;tag=48206668-C6C
To: <sip:sip_user@XXX.XXX.XXX>
Date: Tue, 21 May 2019 11:01:00 GMT
Call-ID: 8CFC113F-7AEE11E9-8525B193-993D21B5
User-Agent: Cisco-SIPGateway/IOS-12.x
Max-Forwards: 70
Timestamp: 1558436460
CSeq: 4 REGISTER
Contact: <sip:sip_user@YYY.YYY.YYY.YYY:5060>
Expires:  0
Supported: path
Content-Length: 0


*May 21 11:01:00.128: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:


Via: SIP/2.0/UDP YYY.YYY.YYY.YYY:5060;branch=z9hG4bK3AF1E87
To: <sip:sip_user@XXX.XXX.XXX>;tag=h7g4Esbg_5e9c264e0cb880589634ed0b72c
From: <sip:sip_user@XXX.XXX.XXX>;tag=48206668-C6C
Call-ID: 8CFC113F-7AEE11E9-8525B193-993D21B5
CSeq: 4 REGISTER
Contact: <sip:sip_user@YYY.YYY.YYY.YYY:5060>;expires=0
Service-Route: <sip:ZZZ.ZZZ.ZZZ.ZZZ:5060;transport=udp;lr>
Content-Length: 0



show sip-ua  register  status
Line          peer           expires(sec)  registered   P-Associated-URI
============  =============  ============  ===========  ================
sip_user               -1          50            no

Thank You

Ayodeji Okanlawon · ‎05-22-2019

Typically when a REGISTER message is sent with Expires = 0, this is usually indicative of a keep-alive message sent to the backup registrar. It is possible that when the gateway performed DNS lookup on your registrar more than one hosts were returned and its trying to register to primary and send keep-alive to the secondary. To confirm this, I will need the following:

1. Turn on debug ccsip info, debug ccsip message, debug ccsip feature registration

2. initiate a new register request ( you can do this by doing the following:

sip-ua

no registrar dns:XXX.XXX.XXX expires 60

registrar dns:XXX.XXX.XXX expires 60

Collect the logs and attach here

Please rate all useful posts

pstepanovs · ‎05-22-2019

Probably your are hitting defect:

Symptoms: A Cisco 2921 Gateway that is running Cisco IOS Release 15.1(1)T1 is
unable to register with IMS.

Conditions: The symptom is observed if the P-Associated-URI of the 200 Ok
response contains any special characters (!*.!) in Tel URI Parsing.

https://bst.cloudapps.cisco.com/bugsearch/bug/CSCtl73914

jevgep · ‎05-22-2019

@pstepanovs wrote:
Probably your are hitting defect:
Symptoms: A Cisco 2921 Gateway that is running Cisco IOS Release 15.1(1)T1 is
unable to register with IMS.
Conditions: The symptom is observed if the P-Associated-URI of the 200 Ok
response contains any special characters (!*.!) in Tel URI Parsing.

https://bst.cloudapps.cisco.com/bugsearch/bug/CSCtl73914

Nice observation !

I just looked into ccsip info debug and see:

May 22 11:48:01.036: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 80.235.76.42:5060;branch=z9hG4bK14C5364
To: <sip:sip.A1234567@xxx.xxx.xxx>;tag=h7g4Esbg_49fa64fd0df3405897889958fef
From: <sip:sip.A1234567@xxx.xxx.xxx>;tag=4D8FD7E8-1523
Call-ID: 48DBE551-7BBE11E9-8BAFB193-993D21B5
CSeq: 3 REGISTER
Contact: <sip:sip.A1234567@yyy.yyy.yyy:5060>;expires=60
P-Associated-Uri: <sip:sip.A1234567@xxx.xxx.xxx>
Service-Route: <sip:zzz.zzz.zzz:5060;transport=udp;lr>
Content-Length: 0
Authentication-Info: qop=auth,rspauth="35420b136a118294fd6c907d7e637bf7",cnonce="9516993F",nc=00000001


May 22 11:48:01.036: //7905/000000000000/SIP/Info/sipSPICheckResponseExt: non-INVITE response with no RSEQ - do not disable IS_REL1XX
May 22 11:48:01.040: //7905/000000000000/SIP/Info/ccsip_gw_register_get_response_info: Create new SIP register response info (0x66CB4608)
May 22 11:48:01.040: //7905/000000000000/SIP/Info/ccsip_gw_register_process_response: P-Associated-URI (<sip:sip.A1234567@xxx.xxx.xxx>)
May 22 11:48:01.040: //7905/000000000000/SIP/Info/ccsip_gw_register_process_response: URI (<sip:sip.A1234567@xxx.xxx.xxx>)
May 22 11:48:01.040: //7905/000000000000/SIP/Info/ccsip_gw_register_process_response: user portion of URI (sipA1234567)
May 22 11:48:01.040: //7905/000000000000/SIP/Info/ccsip_gw_register_free_response_info: Free Register Response Info (0x66CB4608)
May 22 11:48:01.040: //7905/000000000000/SIP/Info/ccsip_register_reset_registration: Un-register/Re-register usersname sip.A1234567, passwd 132307225C1B5D3A22, realm aaa.aa

Will try to make an upgrade and see how it goes

Thanks!