Snom 320 Oddity

Hi

I have a Snom 320 which has been working on a Asterisk based system. I
am now trying to get it to work on a OpenSER fronted system and it is
showing a bizzare behaviour.

Lets say I set the register expiry time to 60 seconds this is what happens.

1. It registers with a expiry of 60 seconds
2. 30 seconds later it reregisters for 30 seconds.
3. 15 seconds later it reregisters for 15 seconds.
4. 7 seconds later it reregister for 7 seconds.

It then wait about 5 minutes and repeats the pattern.

The same pattern happens if I set the initial registry value to a
greater value with each subsequent registration expiry half that of the
previous.


Anyone got any ideas what is going on? No other SIP client on this
system has shown this same behaviour.

Regards

jon

Jon Farmer wrote:
> Hi
>
> I have a Snom 320 which has been working on a Asterisk based system. I
> am now trying to get it to work on a OpenSER fronted system and it is
> showing a bizzare behaviour.
>
> Lets say I set the register expiry time to 60 seconds this is what happens.
>
> 1. It registers with a expiry of 60 seconds
> 2. 30 seconds later it reregisters for 30 seconds.
> 3. 15 seconds later it reregisters for 15 seconds.
> 4. 7 seconds later it reregister for 7 seconds.
>

This is nuts.

Which firmware version are you on?

Can you post up the SIP trace from the Snom phone?

Loads of people use Snom with OpenSER and SER so think it should be
easily fixed.

*****

Also, in general using a 60 second registration expiry time is a bad
idea. It will result in the phone not showing not registered in case
of an iffy network.

You should use a long registration time (like 1 hour) and use keepalives
to keep the NAT open.


Tim

Tim wrote:

> Also, in general using a 60 second registration expiry time is a bad
> idea. It will result in the phone not showing not registered in case
> of an iffy network.
>
> You should use a long registration time (like 1 hour) and use keepalives
> to keep the NAT open.

Yep I know this but i turned it down to 60 secs while trying to debug
this problem.

Regards

Jon

Tim wrote:

> This is nuts.
>
> Which firmware version are you on?
>
> Can you post up the SIP trace from the Snom phone?
>
> Loads of people use Snom with OpenSER and SER so think it should be

The firmware is

Kernel Version: snom320 linux 3.25
Application-Version: snom320-SIP 6.2.3
Rootfs-Version: snom320 jffs2 v3.36

I cant get a SIP trace right now.

Regards

Jon

Jon Farmer wrote:
> Yep I know this but i turned it down to 60 secs while trying to debug
> this problem.

ok.

I just sent you an email.

Tim

Jon Farmer wrote:
> Kernel Version: snom320 linux 3.25
> Application-Version: snom320-SIP 6.2.3
> Rootfs-Version: snom320 jffs2 v3.36

6.2.3 is good. Old and had some niggles, but very widely used.

My current favourite firmware is 6.5.14

http://snom.provu.co.uk/sw/snom320-6.5.14-SIP-j.bin

Technically a beta - and it is very recently, so YMMV.

Maybe worth a go.


Tim