Skip to main content

Calls are Jumping

Posted by Ulsa on Tue, 03/24/2015

Dear Team,

On MT system one of Tenant experiencing an issues, when someone calls from Internal extension or from remote calls are not landing to desired extensions, randomly It may land the calls to any extension on the tenant, when we checked the record the calls are landed to desired extensions itself, not sure whats going on.!! we have total extensions on this tenant is more than 400 in multiple locations,
System details are
Operating system CentOS Linux 6.0
Webmin version 1.570
Kernel and CPU Linux 2.6.32-71.29.1.el6.x86_64 on x86_64
PBX Manager 6.1.1.11

Eg:- If I tried to reach the extension 308 on the same tenant it may land on 362 extension, like all the extensions its been happening,

Can anyone advise on this ASAP,
Appreciate your time.!!


Submitted by eeman on Tue, 03/24/2015 Permalink

if all the extensions are behind NAT so that all the extensions appear as 1 IP address, its quite possible the firewall is to blame for sending the call to the wrong device. This would explain why CDR shows the correct device instead of the incorrect. There are things you can buy to solve this issue. Hopefully they aren't too married to that flawed software.

Submitted by Ulsa on Wed, 03/25/2015 Permalink

Dear Eeman,

Thank you so much for your reply.!!!

My clients are using SONICWALL FIREWALL , Untangle, Pfsense and Cyber roam etc,
Mainly they have been using SONICWALL firewalls,
Do you have any suggestion for us to make any changes on the firewall ?
Please advise how to overcome from this problem?

Thanks

Submitted by jakevxobee on Fri, 06/12/2015 Permalink

I have seen this on SonicWalls, I refer to it as 'port roving'.

Pretty sure the fix is related to the session timers in the router; try changing it from 30 to 300 seconds and ensure the SIP ALG is off.

Once the timer stops killing the sessions the phones will remain registered on the correct ports and ring properly as asterisk will have the correct port for the extension.

Submitted by raven on Mon, 06/15/2015 Permalink

I have seen stuff like this when the firewall has old firmware with SIP problems or SIP ALG is turned off. Whatever it is its more than likely the firewall.