Jump to content

Recommended Posts

Posted

Hello,

 

One to many times in a day, the snom 360 and snom 320 will have a registration fail.

 

Of course we have to reboot the phone. This is very anying because we never know when the fail will happen.

 

PBX version 1.5.2.10a and snom FW 6.5.12 and 6.5.10 are used.

 

we have many phones and we cannot get this to happen all the times.

 

Any solution welcomed.

 

Digisoft VOIP

Posted

I would suggest to use the logging feature in the PBX. You can set per extension on what log level registration events should be logged. For example, if you set it to log level 1 and set the general log level to 2, you should be able to see when the phone looses it's registration and when it comes back.

 

This feature helped in other situations to figure out what was wrong. In that case there was a router that was changing the NAT binding from time to time and during that switch-over the registration got lost. A replacement of the router solved the problem.

Posted
I would suggest to use the logging feature in the PBX. You can set per extension on what log level registration events should be logged. For example, if you set it to log level 1 and set the general log level to 2, you should be able to see when the phone looses it's registration and when it comes back.

 

This feature helped in other situations to figure out what was wrong. In that case there was a router that was changing the NAT binding from time to time and during that switch-over the registration got lost. A replacement of the router solved the problem.

 

For your info : the phone never register back after a fail. Absolute need to reboot... :angry:

 

Case 1 : the phone snom 360 has many numbers, only one of them fail.

 

Case 2 : the network has many phone snom 360 and snom 320 only one fail at a given time.

 

Case 3 : the network and the phone have many different type of registration UDP and TLS. Still same issues some will fail some will continue to work.

 

We need a solution how to keep the phone working at all time.

 

regards,

 

Digisoft VOIP

Posted

If the phone does not register any more, I would recommend to set the transport layer to UDP and use IP addresses (no DNS addresses). If that is not stable, there is something really strange going on. If the DNS does the trick, check out the availability of the DNS server. If the UDP does make a difference, there msut be something with the stability of the TCP connections in this setup.

Posted
If the phone does not register any more, I would recommend to set the transport layer to UDP and use IP addresses (no DNS addresses). If that is not stable, there is something really strange going on. If the DNS does the trick, check out the availability of the DNS server. If the UDP does make a difference, there msut be something with the stability of the TCP connections in this setup.

 

In snom phone UDP is default no TCP used. When you do not write anything transport is udp (similar to transport=udp)

IP address of the proxy is used and no DNS are involve.

 

will have to think about something else.

 

regards,

Posted

Well, what you can do is run a PCAP trace on the phone and see if it is really sending REGISTER packets. Or if you can have Wireshark in the network you will get a "objective" view on where it is failing. If you filter by IP address the actual PCAP trace will not become too big, so that you can run it for several hours.

 

If you are running the phones behind NAT, it would also be very interesting if the packets arrive at the PBX unmodified. There is some equipment out there that tries to behave smart and patches SIP packets in a bad way or randomly changes ports. Just want to make sure we are not burning time on such bad equipment!

Posted
Well, what you can do is run a PCAP trace on the phone and see if it is really sending REGISTER packets. Or if you can have Wireshark in the network you will get a "objective" view on where it is failing. If you filter by IP address the actual PCAP trace will not become too big, so that you can run it for several hours.

 

If you are running the phones behind NAT, it would also be very interesting if the packets arrive at the PBX unmodified. There is some equipment out there that tries to behave smart and patches SIP packets in a bad way or randomly changes ports. Just want to make sure we are not burning time on such bad equipment!

 

We will try to capture the traffic.

The equipment seems to be find we have many installations unsing these ZyXEL router. Not all in voip solution!

Also use the NetGear FSM7326P POE switch.

 

We have found that if there is more number to register in the same phone, it would create more problems.

 

Is there any auto reboot when registration fail?

 

DigiVoip

Posted

Just wild guessing here... Many routers have relatively short tables for NAT, for example I have seen devices with just 32 entries. If the number of phones changes the behavior, that could be a point. Keep in mind that DNS and RTP require additional ports. If you can, reduce the number of phones and see if that at least improves the stability. Or if you have another router, maybe try swapping the router out just to see if that changes something.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...