Jump to content

Messages in logfile


olecoot
 Share

Recommended Posts

I'm seeing this in several of our servers and I'm not quite sure why the address change. Version 2.1.6.2450 (Win32).

 

[3] 2008/04/18 12:02:52: Source address for sip:1206@domain.com has changed to udp:xx.xxx.xx.xxx:23943

[3] 2008/04/18 12:04:01: Source address for sip:1207@domain.com has changed to udp:xx.xxx.xx.xxx:23953

[3] 2008/04/18 12:04:22: Source address for sip:1206@domain.com has changed to udp:xx.xxx.xx.xxx:23955

[3] 2008/04/18 12:05:31: Source address for sip:1207@domain.com has changed to udp:xx.xxx.xx.xxx:23963

[3] 2008/04/18 12:05:48: Source address for sip:1206@domain.com has changed to udp:xx.xxx.xx.xxx:23965

Link to comment
Share on other sites

This is a serious message because the NAT router is not really ready for VoIP. There are some routers on the market that change the port during re-registration, leaving a blind spot for the reachability for the registered device. In the above case, the registration changes every 90 seconds - don't be surprised if calling that phone will result in random call drops.

Link to comment
Share on other sites

This is a serious message because the NAT router is not really ready for VoIP. There are some routers on the market that change the port during re-registration, leaving a blind spot for the reachability for the registered device. In the above case, the registration changes every 90 seconds - don't be surprised if calling that phone will result in random call drops.

 

 

Can you define what "not ready for VoIP" means? We have not seen this message in previous versions of pbxnsip.

Link to comment
Share on other sites

Can you define what "not ready for VoIP" means? We have not seen this message in previous versions of pbxnsip.

 

Well if the router creates a NAT binding, it is supposed to keep that binding when there is traffic on that binding. When it drops the binding, and during that time the PBX sends a request to the old binding port, the request will not be forwarded to the phone. This creates a blind spot.

 

We have seen routers that have exactly 32 entries for NAT. If you open the binding 33, then it just drops binding 1. This especially happens when a PC behind that router does some kind of activity, practically kicking out SIP during that time. If you see the log message in the PBX, you should check if the router is responsible for that. If you have several routers in operation, it should be easy to check the model and maybe easy to isolate the router that is causing this kind of problem.

 

The ugly thing is that is works fine most of the time and it is extremly difficult to find out why devices are offline from time to time. That is why we put that log in.

 

BTW The same applies to changing IP addresses. Service providers in Asia now start to change/recycle IP addresses every 4 (four!) hours because if the address shortages there. I think everybody understands that this is not increasing the registration stability.

 

Bye bye, NAT. Here you go, IPv6!

Link to comment
Share on other sites

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.

 Share

×
×
  • Create New...