Random Calls to My Mobile

[Chappo]

Hey Guys,

 

I am having an intermittent issue with inbound calls. There is a few companies that are unable to call through. When this happens I am receiving a call to my mobile phone - These calls are from a Private number (All outbound trunks have CLID enabled). When I answer the call there is no voice/sound. I believe this to the failover that I have configured with my VOIP provider when the 4 VOIP lines are unreachable.

 

2012-05-10T16:25:29 0:00:07 Australia - Mobile Fixed to Mobile 9406156 XXXXXXXX -0.15 Outbound

2012-05-09T13:34:15 0:00:18 Australia - Mobile Fixed to Mobile 9406156 XXXXXXXX -0.15 Outbound

2012-05-07T14:14:06 0:00:04 Australia - Mobile Fixed to Mobile 9406156 XXXXXXXX -0.15 Outbound

2012-05-02T16:44:33 0:00:05 Australia - Mobile Fixed to Mobile 9406156 XXXXXXXX -0.15 Outbound

2012-05-02T12:45:36 0:00:03 Australia - Mobile Fixed to Mobile 9406156 XXXXXXXX -0.15 Outbound

 

 

When checking the logs at these times I have found a common occurrence - The issues seems to be from a lack of available codecs - For what reason this is occurring I am not quite sure? Also I have configured my Snom Installation so that the only SIP server that can connect is as follows: AssociatedAddresses: sip00.mynetfone.com.au. Why am I getting the calls that appear to be coming through from 65.19.131.47?

 

20120510142529: Call port 130: update_codecs for af981122845@65.19.131.47: codec_preference size 4, available codecs list is empty

[5] 20120510142529: Available codec list is empty for af981122845@65.19.131.47

[5] 20120510142529: SIP Tx udp:125.213.160.81:5060:

[1] 20120510142529: Could not allocate new ports!

[5] 20120510142529: SIP Tx tls:172.28.1.68:3150:

[5] 20120510142529: SIP Rx udp:125.213.160.81:5060:

 

[3] 20120509113416: Call port 12: update_codecs for ae1028169497@65.19.131.47: codec_preference size 4, available codecs list is empty

[5] 20120509113416: Available codec list is empty for ae1028169497@65.19.131.47

[5] 20120509113416: SIP Tx udp:125.213.160.81:5060:

[1] 20120509113416: Could not allocate new ports!

[5] 20120509113416: SIP Tx tls:172.28.1.68:3855:

[5] 20120509113416: SIP Rx udp:125.213.160.81:5060:

[5] 20120509113416: SIP Rx udp:125.213.160.81:5060:

[1] 20120509113416: Could not allocate new ports!

 

20120502104536: Call port 218: update_codecs for ae125644798@65.19.131.47: codec_preference size 4, available codecs list is empty

[5] 20120502104536: Available codec list is empty for ae125644798@65.19.131.47

[5] 20120502104536: SIP Tx udp:125.213.160.81:5060:

[1] 20120502104536: Could not allocate new ports!

[5] 20120502104536: SIP Tx tls:172.28.1.68:3887:

[5] 20120502104536: SIP Rx udp:125.213.160.81:5060:

[5] 20120502104536: SIP Tx tls:172.28.1.68:3887:

 

[3] 20120502144433: Call port 345: update_codecs for ac168578346@65.19.131.47: codec_preference size 4, available codecs list is empty

[5] 20120502144433: Available codec list is empty for ac168578346@65.19.131.47

[5] 20120502144433: SIP Tx udp:125.213.160.81:5060:

[1] 20120502144433: Could not allocate new ports!

[5] 20120502144433: SIP Tx tls:172.28.1.68:3887:

[5] 20120502144433: SIP Rx udp:125.213.160.81:5060:

[5] 20120502144433: SIP Tx tls:172.28.1.68:3887:

[Vodia support]

[5] 20120510142529: Available codec list is empty for af981122845@65.19.131.47

 

 

Check if you have any available codecs in the Admin- settings--Ports

You can also populate them in the trunks section as well.

 

 

http://wiki.snomone.com/index.php?title=RTP_Ports

[Chappo]

Thanks - There is a total of 4 available codecs within that section.

 

I've attached a screenshot.

 

 

I am also curious to know why I am getting the unable to allocate port error message too?

 

Edit: Also where is it getting this IP from? 65.19.131.47? It has nothing to do with my SIP provider?

[Vodia PBX]

[1] 20120502104536: Could not allocate new ports!

 

That is definitevely very serious. Seems like you have 600 ports reserved for RTP. That means you can have max 600 / 4 = 150 calls going on at the same time. Maybe the OS also needs a "grace period" for old ports, and the PBX also needs some free space to find a new random port. In short words: Increase the number of RTP ports. 600 is probably somehow on the limit, I would say 1200 should be much more relaxed.

[Chappo]

I had increased the number of ports to 2000 however I was still getting errors.

 

Having a look at the open ports on the server I found that the dns system had about 2500 ports reserved for it. And the range that I selected for the RTP ports was smack bang in the middle.

 

Port errors are now resolved however I am still curious as the origins of 65.19.131.47? It appears to be a Hurricane Electric IP in the US?

 

 

Call port 130: update_codecs for af981122845@65.19.131.47: codec_preference size 4, available codecs list is empty

[pbx support]

Call port 130: update_codecs for af981122845@65.19.131.47: codec_preference size 4, available codecs list is empty

 

That is just the call-id that remote side is sending. Nothing really serious.

[Vodia PBX]

Port errors are now resolved however I am still curious as the origins of 65.19.131.47? It appears to be a Hurricane Electric IP in the US?

 

It is not unusual that someone tries to scan your PBX. If you don't use trivial or even empty passwords the automatic blacklisting should take care about this guy.

[Chappo]

Thanks Guys - I am using the PBX behind NAT with the only IP address allowed through on 5060 is the IP of the SIP provider.

 

That said we have worked out what was causing one of the companies calls to fail - They had a malformed CLID which was two digits short and my provider was rejecting the calls.