3cx routes calls to different extensions

[gustavskii]

Hello, I just upgraded from version 9 to new version 15, and now sometimes 3cx routes calls to a different extensions
For example: somebody calls extension 707 and it routs it to extension 706 or 395
It happens randomly and sometimes it works fine, it happens to both external and internal calls, sometimes 3cx just drops the call even when the extension is registered
here logs when it happens:
09/15/2016 11:39:10 AM - PBX has dropped a message with 'User-Agent: friendly-scanner' from IP 104.243.45.140 because it is on blocked UAs list
09/15/2016 11:38:57 AM - STUN servers list is empty, no STUN discovery is possible
09/15/2016 11:38:57 AM - STUN discovery of public IP is disabled
09/15/2016 11:34:54 AM - PBX has dropped a message with 'User-Agent: VaxSIPUserAgent/3.1' from IP 212.83.155.65 because it is on blocked UAs list
Here 3cx routed call from extension 707 to extension 716, call was made from outside

09/15/2016 11:34:37 AM - [CM503003]: Call(C:45): Call to <sip:[email protected]:5060> has failed; Cause: 408 Request Timeout/INVITE from local

Extension 777 was registered at the time of the call, the DND was off, there were no rules that could prevent the call, and it was within office hours

please help, i`m lost

 

[leejor]

I don't see extension 707 or 716 mentioned in the logs you posted, so they really are of no help in diagnosing the cause.

I would check the forwarding options associated with the extension that is NOT getting calls. I would also check the SIP ID of the extensions involved. Check the logs again after one of the misdirected calls. Use the Verbose setting if necessary to provide additional information. You should be able to get some logs that show the incoming call and the final destination, along with why it went there.

I'm assuming that when you went from version 9 to 15, you did it "through" the required, intermediate versions.

 

[gustavskii]

I don't see extension 707 or 716 mentioned in the logs you posted, so they really are of no help in diagnosing the cause.

I would check the forwarding options associated with the extension that is NOT getting calls. I would also check the SIP ID of the extensions involved. Check the logs again after one of the misdirected calls. Use the Verbose setting if necessary to provide additional information. You should be able to get some logs that show the incoming call and the final destination, along with why it went there.

I'm assuming that when you went from version 9 to 15, you did it "through" the required, intermediate versions.

That is the issue there are no logs with extensions that are wrong, but it happens, calls go to different extensions than they intended to go to (707 and 716 are just examples and posted logs are logs that happens at the same time as the call) as of 777 extension, the forwarding rules set up to go to VM and the extension is registered, no additional rules on the phone itself and on calls like that there are no ring, it is just dead air and then VM. and no ring on the extension.

09/15/2016 12:54:28 PM - [CM503025]: Call(C:62): Calling T:Extn:705@[Dev:sip:[email protected]:5060] for L:62.1[Line:10007<<xxx]
09/15/2016 12:54:28 PM - [CM503027]: Call(C:62): From: Line:10007<<xxx ("VMedia " <sip:[email protected]:5060>) to T:Extn:705@[Dev:sip:[email protected]:5060]
09/15/2016 12:54:28 PM - [CM503004]: Call(C:62): Route 1: from L:62.1[Line:10007<<xxx] to T:Extn:705@[Dev:sip:[email protected]:5060]
09/15/2016 12:54:28 PM - [Flow] Call(C:62): has built target endpoint: Extn:705 for call from L:62.1[Line:10007<<xxx]
09/15/2016 12:54:28 PM - [Flow] Target endpoint for 705 is Extn:705
09/15/2016 12:54:28 PM - [CM503010]: Call(C:62): Making route(s) from Line:10007<<xxx to <sip:[email protected]:5060>
09/15/2016 12:54:28 PM - [CM505003]: Provider:[GLT] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [vmediatelecom] PBX contact: [sip:[email protected]:5060]
09/15/2016 12:54:28 PM - [Flow] Refer: RefTo=<sip:[email protected]:5060>; was call from=<sip:[email protected]:5060> to="VMedia " <sip:[email protected]:5060>

here are logs call to extension 705, but extension 712 rang instead, and I checked SIP credentials, and they are correct

 

[leejor]

Ok, you've "hidden" the local IP for Ext 705 for some reason,(showing a local IP is not really a security issue), but you will have to see if the IP in this log...

09/15/2016 12:54:28 PM - [CM503004]: Call(C:62): Route 1: from L:62.1[Line:10007<<xxx] to T:Extn:705@[Dev:sip:705@x.x.x.x:5060]

Is that of Ext 705...and is it the same in the two logs above as well?

Could there be a "feature" in the set that has been invoked to forward calls off to another extension?

Does 705 show as registered?

 

[gustavskii]

Ok, you've "hidden" the local IP for Ext 705 for some reason,(showing a local IP is not really a security issue), but you will have to see if the IP in this log...

09/15/2016 12:54:28 PM - [CM503004]: Call(C:62): Route 1: from L:62.1[Line:10007<<xxx] to T:Extn:705@[Dev:sip:705@x.x.x.x:5060]

Is that of Ext 705...and is it the same in the two logs above as well?

Could there be a "feature" in the set that has been invoked to forward calls off to another extension?

Does 705 show as registered?

Yes it is
I think I found the issue, my G(ra) ndst re@m phones were set for UDP for SIP transport as default, changed it to TCP and now problem not there any more, I`ll write back if it will resume.