Expiry

[mathias]

Hi,
I'm not sure if that is a bug but I think so

The problem is with the expire between a softphone and your server if i use sip.mysipswitch.com as voip-provider.

If the softphone register with sip.mysipswitch.com it ask the server to use a defined expire (e.g. 1800) but your server don't use the wanted expiry.
Your server set the expire to (fix) 113 in the OK message.

With SJphone that is no problem, it regognize that new expire and use it but with fring (www.fring.com) it don't work
The login expire after that 113 seconds and incoming call will not ring at my fring client.

I use fring at my windows mobile 5 handset because it is the only one that realy works with gprs and 3G.

If you could fix this that your server use the expire time the client requests would very helpfull

And thanks for your service there are very nice features.

Regards, Mathias

[gbonnet]

Hi Mathias,

We must have a look at that.

We will keep you up to date.

Thanks

[Mr-x]

Hey Guys any update on this issue??

[Aaron]

Hi Mr-x,

Guillaume passed on your email as well and I was about to reply but this may be a better place.

The SIP Registrar in the sipswitch does set an expiry value of 113. This is not a bug but a design decision. The reason for having an expiry value of under two minutes is that it has been found to be good at keeping client side NAT connections open.

No matter what sort of NAT keep alives are sent from the server side some NATs will still timeout a connection unless they see a packet come from the private side. By setting the expiry value to 113s there is a good chance the SIP user agent on the private side will be generating requests at a lower frequency than most NAT gateway timeouts.

Regards,

Aaron

[Mr-x]

Hi Aron,

Thanks for the reply can you suggest anything to make this work with fring?

[Aaron]

Hi Mr-x,

It's incorrect behaviour from the fring client, the server is the end that gets to set the expiry time and it's up to it whether it takes any notice of the client requested value or not. However it's not much use to argue about that here so instead I've made a change that allows the sipswitch expiry time to be adjusted based on the user agent. Hopefully that won't cause any problems in the future. My fring client now stays registered with the sipswitch and can be used to receive calls.

Regards,

Aaron

[Mr-x]

That seems to have done the trick cheers Aaron your a legend...

[Mr-x]

Hi Mr-x,

It's incorrect behaviour from the fring client, the server is the end that gets to set the expiry time and it's up to it whether it takes any notice of the client requested value or not. However it's not much use to argue about that here so instead I've made a change that allows the sipswitch expiry time to be adjusted based on the user agent. Hopefully that won't cause any problems in the future. My fring client now stays registered with the sipswitch and can be used to receive calls.

Regards,

Aaron

Hi Aaron,

Could you do something like this for Nokia's user agent in sipsorcery.com fring is working fine for receiving calls, but when I use the native sip client on my Nokia (E51) after a few minutes of leaving it idle I can no longer receive calls similar to the problem you fixed with fring above.

Thanks

[Aaron]

Hi Mr-x,

What's the expiry time on your Nokia?

It sounds like a different issue to the original Fring problem in this case. The solution may be for you to reduce the expiry time in the Nokia SIP client to 60s to get the NAT binding on your router from closing.

Regards,

Aaron

[Mr-x]

There is no option to set the expiry time in the phone?