SIP Register interval problem

[nmdc.kzstan]

Hi,

I have Cisco 2921 ISR (c2900-universalk9-mz.SPA.154-2.T1.bin) and Grandstream voice gateway registered to the same ITSP. 

ITSP's SIP register interval is 300 seconds. Grandstream registers every 300 seconds (no problem),  ISR - 480 seconds so

some incoming calls are not working. 

 Where does ISR take 480 sec value and how to change it? 

sip
  min-se 180 session-expires 240

sip-ua
 credentials username a password 7 a realm sip.k
 authentication username a password 7 a
 no remote-party-id
 max-forwards 10
 retry invite 3
 retry response 3
 retry bye 3
 retry cancel 3
 timers trying 100
 registrar dns:sip.k:5060 expires 1800 auth-realm sip.k
 sip-server dns:sip.k
 no suspend-resume

[Manish Prasad]

Are you sure that register time interval is causing the inbound call to fail ?

SIP register message and call setup (INVITE) message are sent separately and there is no relation between them but yes in some cases when user agent remain unregistered (due to lack of response from ITSP) and call came in at the same time then you have an inbound call failure . In that case you need to point at ITSP 

Can you share debug ccsip message for a failing inbound call ?

[nmdc.kzstan]

Hi Manish,

When call fails there is not any traffic from ITSP at all so debug ccsip messages shows nothing.

As far as I understand SIP registrar "forgets" about ISR SIP account after some time if there is no Register message so it does not know where to send Invite message. If incoming call is for example  at 400 second it fails, if it is in first 10 seconds after Register message, call is successful.

ITSP denies any problems because Grandstream is working, and the difference between Grandstream and ISR is that GS registers every 5 min, ISR - every 8 min.

[Manish Prasad]

That means there is timeout setup at ITSP registrar , can you lower sip-ua registrar server expire seconds to 300.

[nmdc.kzstan]

 registrar dns:sip.k:5060 expires 300 auth-realm sip.k
 

HUB2#sh sip-ua register status
Line                             peer       expires(sec) reg survival P-Associ-URI
================================ ========== ============ === ======== ============
389388                     -1         0            yes normal
HUB2#sh sip-ua register status
Line                             peer       expires(sec) reg survival P-Associ-URI
================================ ========== ============ === ======== ============
389388                        -1         479          yes normal

What I see in Wireshark:

ISR sends Expires 300 in Message header of Register message

ITSP sends Contact Parameter : expires = 600\r\n in 200 OK message.

[Manish Prasad]

Did you mean when ITSP send OK message for REGISTER it send expire header value as 600 sec?

Do you see within 5 mins the ISR router send REGISTER message again ?

[nmdc.kzstan]

Yes, in reply OK message expire value is 600.

No, ISR sends Register messages every 8 min. Checked it with Wireshark. 

[Manish Prasad]

Does the ITSP send same value in OK expire header for other ISR router and Grandstream router ?

[nmdc.kzstan]

Yes, Grandstream sends Expires 3600, gets Contact parameter: expires 600.

But registration is every 5 min.

Grandstream config:

Register Expiration 60 min.

SIP port 5062

Session expiration 180 seconds.

5 min is not configured anywhere.

[Manish Prasad · Accepted solution]

Sorry for late reply. When you run sh sip-ua register status command between 300 to 480 second , did you see the registration status dropped in between that time ? And can you make an outbound call in between that time ?

See inbound is always been routed by Telco and if our ITSP pointing IP is reachable then that's their headache to route inbound call.

Do you have proper interface binding in place ? Can you share voice relevant config from your router ?

[nmdc.kzstan]

sh sip-ua register status always shows reg status "yes" and there is no problem with outbound calls anytime.

I think there is a problem with ITSP too. What I don't get is where does cisco take 480 sec value, it is not configured anywhere, ITSP does not send it. And if

there is a way to force register.

Current config:

voice service voip
 allow-connections h323 to h323
 allow-connections h323 to sip
 allow-connections sip to h323
 allow-connections sip to sip
 no supplementary-service sip moved-temporarily
 no supplementary-service sip refer
 redirect ip2ip
 fax protocol pass-through g711alaw
 sip
  early-offer forced

dial-peer voice 110 voip
 translation-profile outgoing SIP_OUT
 destination-pattern 9[23]......
 session protocol sipv2
 session target ipv4:a.b.c.d
 session transport udp
 voice-class sip localhost dns:sip.k preferred
 voice-class sip dtmf-relay force rtp-nte
 voice-class sip early-offer forced
 dtmf-relay rtp-nte sip-notify
 codec g711alaw
 fax protocol pass-through g711alaw
 no vad

dial-peer voice 210 voip
 translation-profile incoming SIP_IN
 session protocol sipv2
 session target ipv4:a.b.c.d
 incoming called-number 389388
 dtmf-relay rtp-nte
 codec g711alaw
 no vad

sip-ua
 credentials username 389388 password 7 a realm sip.k
 authentication username 389388 password 7 a realm sip.k
 no remote-party-id
 max-forwards 10
 retry invite 3
 retry response 3
 retry bye 3
 retry cancel 3
 timers trying 100
 registrar dns:sip.k:5060 expires 180 auth-realm sip.k
 sip-server dns:sip.k
 no suspend-resume

[Manish Prasad · Accepted solution]

On expire timer value the final call always from the registrar server , so in this case ITSP registrar send 600 sec as an expire time and that is maximum time to expire but cisco set threshold time as 480 sec so that it wont hit the maximum time before re-registration is done. So after 480 second it start sending re-registration message.

I cant see any interface binding in your config , please check this link do the necessary configuration.

Lets do not assume anything , get in a call with ITSP and asked them what they see in their system about your account status  when registration timer hit 480 seconds and also when you do an inbound call after 480 second , how they transport that call , do they get some sip 4XX error or what ?

I am sure this is something to do with telco , so you need to press them hard and asked to share logs if they feel its an issue with us.

[nmdc.kzstan]

It seems it is a weird L2 problem. ITSP was sending Invite messages but ISR

is not getting them. Before ISR was connected over HP switch to ITSP CPE.

Now it is connected directly to CPE and for 2 days problem did not repeat.

It will take some troubleshooting to say exactly if switch was blocking.

Thank you for your help and time.

[nmdc.kzstan]

Checked another ISR (c2951-universalk9-mz.SPA.152-3.T2.bin) that is working fine for a long time connected to the same ITSP, it registers every 120 sec.