Up to Discussions in OpenSBC

This Question is Not Answered

1 "correct" answer available (5 pts) 2 "helpful" answers available (1 pts)
9 Replies Last post: Mar 9, 2009 6:22 PM by oliverkazaam41  
Click to view oliverkazaam41's profile  
oliverkazaam41
84 posts since
Jan 31, 2009

Mar 4, 2009 4:48 PM

Session Registration Expiration


Hi,

I have this weird problem. I am using opensbc as upper registrar for my asterisk. I have different kinds of SIP phone registered in opensbc. For Polycom phones I have to set the expire to 20 ms for it not to loose registration to opensbc. This works very well. What I am having problem is for SIP phones which you can't set the expiration. Is there a way for opensbc not to loose registration if the phone expiration is set by default to a 3000 sec. Thanks in advance

Tags: registration, expiration, session
Click to view joegen's profile  
joegen
539 posts since
Apr 28, 2007
1. Mar 4, 2009 9:36 PM in response to: oliverkazaam41
Re: Session Registration Expiration
When you say lose registraton, do you mean that the registration disappears from the registration status? Did the user-agent send a registration refresh?
Click to view oliverkazaam41's profile  
oliverkazaam41
84 posts since
Jan 31, 2009
2. Mar 5, 2009 6:21 AM in response to: joegen
Re: Session Registration Expiration
What I mean by loose registration is I can see that the sip phones are still listed in the opensbc registration status but can't receive any incoming calls.What I do is reboot the phone and the phone can start receiving calls but after 3 - 5 minutes it can't receive calls but can do outbound calls. I had this problem with my Polycom phones but what I did was I lowered the expiration to 20 sec and the problem was gone. I have this SIP phone specifically Nokia it registers well with OpenSBC but since I can't specify the expiration it uses the default expiration of 3600 sec. Is there a way I can do in SBC to set the expiration for the phones?
Click to view joegen's profile  
joegen
539 posts since
Apr 28, 2007
3. Mar 5, 2009 10:24 PM in response to: oliverkazaam41
Re: Session Registration Expiration

There is no mechanism in RFC 3261 that allows a registrar to decrease session expiration. It only allows to increase using Interval Too Short response. I have just added ability in OpenSBC to send OPTIONS as NAT keep-alive. This is set in General-Parameters/ Send-OPTIONS-NAT-Keep-Alive. Set this value to TRUE and restart OpenSBC. It should then send OPTIONS instead of CLF/CRLF. This is already in CVS.

Just to warn you though, Nokia might have a very good reason why it did not make expires configurable. I doubt that your phone battery would last a day if its responding to SIP messages every 15 or so seconds.

Joegen

Click to view oliverkazaam41's profile  
oliverkazaam41
84 posts since
Jan 31, 2009
4. Mar 6, 2009 7:42 PM in response to: joegen
Re: Session Registration Expiration

Hi Joegan,

Thanks for the help but the Nat keep alive doesn't work on my nokia phones. Is it possible to do a "persist registration in SBC"? I think that is the only way for me to solve the problem.


Oliver

Click to view joegen's profile  
joegen
539 posts since
Apr 28, 2007
5. Mar 8, 2009 10:36 PM in response to: oliverkazaam41
Re: Session Registration Expiration
Yes, I" understand that your nokia does not send NAT keep alives. That is the reason why I added OPTIONS feature as NAT keep alive in OpenSBC. Did you even try upgrading your OpenSBC as I suggested?
Click to view oliverkazaam41's profile  
oliverkazaam41
84 posts since
Jan 31, 2009
6. Mar 8, 2009 11:39 PM in response to: joegen
Re: Session Registration Expiration
Yes I did do the upgrade. I already checked the nat keep alive and restarted opensbc. My Nokia phones are connecting to opensbc through wifi. Would that matter? I did a test in my polycom phones I set the expiration to 3600 and the keep alive on opensbc works. Maybe its because my nokia phone are connecting through wifi. Maybe that is the case. What do you think?
Click to view joegen's profile  
joegen
539 posts since
Apr 28, 2007
7. Mar 9, 2009 12:23 AM in response to: oliverkazaam41
Re: Session Registration Expiration
Whether its wifi or a wire really shoudn't matter. I would start by looking at the logs of OpenSBC and check whether the nokia phone is responding to OPTIONS. If not, try setting the interval from 15 seconds to a lower value and see if that changes anything.
Click to view oliverkazaam41's profile  
oliverkazaam41
84 posts since
Jan 31, 2009
8. Mar 9, 2009 12:28 AM in response to: joegen
Re: Session Registration Expiration
Thank you very much Joegen for your support. Will check on that.....
Click to view oliverkazaam41's profile  
oliverkazaam41
84 posts since
Jan 31, 2009
9. Mar 9, 2009 6:22 PM in response to: oliverkazaam41
Re: Session Registration Expiration

Hi Joegen,

I already have a snapshot of the logs of my nokia phone. How can I tell that it is correctly responding to the NAT Keep Alive Option. My Nokia Extension is set to register using 8280 id.


2009/03/09 19:05:55.786 DBG: [CID=0xc4affeda] OPTIONS sip:8280@192.168.1.115;transport=UDP SIP/2.0
2009/03/09 19:05:55.786 DBG: [CID=0xc4affeda] From: <sip:8280@6x.1x1xx.1xx>;tag=92fe017f6c0bde119cd9a68c0720d97c
2009/03/09 19:05:55.786 DBG: [CID=0xc4affeda] To: <sip:8280@6x.1x1xx.1xx>
2009/03/09 19:05:55.786 DBG: [CID=0xc4affeda] Via: SIP/2.0/UDP 6x.1x1xx.1xx:5060;branch=z9hG4bKf2f3017f6c0bde119cd9a68c0720d97c;uas-addr=192.168.1.115
2009/03/09 19:05:55.786 DBG: [CID=0xc4affeda] CSeq: 15050 OPTIONS
2009/03/09 19:05:55.786 DBG: [CID=0xc4affeda] Call-ID: 188ac90d-690b-de11-8c26-a68c0720d97c
2009/03/09 19:05:55.786 DBG: [CID=0xc4affeda] Contact: <sip:6x.1x1xx.1xx:5060>
2009/03/09 19:05:55.786 DBG: [CID=0xc4affeda] Subject: NAT Keep Alive
2009/03/09 19:05:55.786 DBG: [CID=0xc4affeda]
2009/03/09 19:05:55.786 DBG: [CID=0xc4affeda]
2009/03/09 19:05:55.794 DBG: [CID=0xc4affeda] NICT(3832579846) Timer E( 1000 ms ) EXPIRED
2009/03/09 19:05:55.794 DBG: [CID=0xc4affeda] NICT(3832579840) Timer E( 2000 ms ) EXPIRED
2009/03/09 19:05:55.794 DTL: [CID=0xc4affeda] NICT(3832579846) Event( Timer-E ) Interval: 1000
2009/03/09 19:05:55.795 DBG: [CID=0xc4affeda] NICT(3832579846) Timer E( 2000 ms ) STARTED
2009/03/09 19:05:55.795 DTL: [CID=0xc4affeda] NICT(3832579840) Event( Timer-E ) Interval: 2000
2009/03/09 19:05:55.796 INF: [CID=0xc4affeda] >>> OPTIONS sip:8280@192.168.1.115;transport=UDP SIP/2.0 Method(OPTIONS) DST: 192.168.1.115:5060:UDP SRC: 6x.1x1xx.1xx:5060 enc=0 bytes=392
2009/03/09 19:05:55.797 DBG: [CID=0xc4affeda]
2009/03/09 19:05:55.797 DBG: [CID=0xc4affeda] OPTIONS sip:8280@192.168.1.115;transport=UDP SIP/2.0
2009/03/09 19:05:55.797 DBG: [CID=0xc4affeda] From: <sip:8280@6x.1x1xx.1xx>;tag=1c0e97826c0bde119cd9a68c0720d97c
2009/03/09 19:05:55.797 DBG: [CID=0xc4affeda] To: <sip:8280@6x.1x1xx.1xx>
2009/03/09 19:05:55.797 DBG: [CID=0xc4affeda] Via: SIP/2.0/UDP 6x.1x1xx.1xx:5060;branch=z9hG4bK540397826c0bde119cd9a68c0720d97c;uas-addr=192.168.1.115
2009/03/09 19:05:55.797 DBG: [CID=0xc4affeda] CSeq: 15053 OPTIONS
2009/03/09 19:05:55.797 DBG: [CID=0xc4affeda] Call-ID: 188ac90d-690b-de11-8c26-a68c0720d97c
2009/03/09 19:05:55.797 DBG: [CID=0xc4affeda] Contact: <sip:6x.1x1xx.1xx:5060>
2009/03/09 19:05:55.797 DBG: [CID=0xc4affeda] Subject: NAT Keep Alive
2009/03/09 19:05:55.797 DBG: [CID=0xc4affeda]
2009/03/09 19:05:55.797 DBG: [CID=0xc4affeda]
2009/03/09 19:05:55.797 DBG: [CID=0xc4affeda] NICT(3832579840) Timer E( 4000 ms ) STARTED
2009/03/09 19:05:55.798 INF: [CID=0xc4affeda] >>> OPTIONS sip:8280@192.168.1.115;transport=UDP SIP/2.0 Method(OPTIONS) DST: 192.168.1.115:5060:UDP SRC: 6x.1x1xx.1xx:5060 enc=0 bytes=392
2009/03/09 19:05:55.799 DBG: [CID=0xc4affeda]
2009/03/09 19:05:55.799 DBG: [CID=0xc4affeda] OPTIONS sip:8280@192.168.1.115;transport=UDP SIP/2.0
2009/03/09 19:05:55.799 DBG: [CID=0xc4affeda] From: <sip:8280@6x.1x1xx.1xx>;tag=8a6e65816c0bde119cd9a68c0720d97c
2009/03/09 19:05:55.799 DBG: [CID=0xc4affeda] To: <sip:8280@6x.1x1xx.1xx>
2009/03/09 19:05:55.799 DBG: [CID=0xc4affeda] Via: SIP/2.0/UDP 6x.1x1xx.1xx:5060;branch=z9hG4bKf46365816c0bde119cd9a68c0720d97c;uas-addr=192.168.1.115
2009/03/09 19:05:55.799 DBG: [CID=0xc4affeda] CSeq: 15052 OPTIONS
2009/03/09 19:05:55.799 DBG: [CID=0xc4affeda] Call-ID: 188ac90d-690b-de11-8c26-a68c0720d97c
2009/03/09 19:05:55.799 DBG: [CID=0xc4affeda] Contact: <sip:6x.1x1xx.1xx:5060>
2009/03/09 19:05:55.799 DBG: [CID=0xc4affeda] Subject: NAT Keep Alive
2009/03/09 19:05:55.799 DBG: [CID=0xc4affeda]
2009/03/09 19:05:55.799 DBG: [CID=0xc4affeda]

Actions

More Like This