3CXPhone not ringing IP Phones

[jholcombe]

Hello,

I have a 3CXPhone with extension 765. I have a Yealink T46G with extension 281. If I call 765 from 281, 765 will ring. If I call 281 from 765, it will stay quiet for a while (no rings) and then I'll hear a brief ring and get forwarded to the voicemail for 281. Extension 281 never rings.

I have another Yealink T64G with extension 333. I can call 333 from 281 and 281 from 333 with no problems. Both will ring.

I can place outside calls with 3CXphone. I can receive inbound calls with 3CXphone. The only thing I can't seem to do is ring an internal extension with 3CXphone, even from the same LAN. Does anyone have any suggestions?

Thanks,

--John

 

[lneblett]

A verbose log of the issue may help. I have no problem using the 3CX phone with 504G or Yealinks or others. Did you provision the 504Gs using 3CX? Does the 504G physically ring? You indicated you will hear a brief ring but was not certain if you meant you heard same on the 3CX phone as a ring back or that the 504G actually rang physically.

 

[craigreilly]

The 504 must be in your head... its not in the OP's question.

 

[craigreilly]

Have you tried resending the config file from the 3cx console and reapplying to it?
Maybe firewall on the computer hosting the softphone?

 

[lneblett]

Thanks Craig....wish I had a head on this one.

I had just answered another post and this one was a 504.....In any event, I also have the Yealinks (as I fortunately noted) and still no issue. :mrgreen:

 

[jholcombe]

Below is a log of 3CXPhone (ext 765) calling Yealink (ext 281). The Yealink never rang (but the screen did light up), and the call eventually forwarded to voicemail. Also I could not hear ringing on 3CXphone until the call forwarded to voicemail, then there was a brief ring on 3CXphone and the call went to voicemail.

06-Jul-2015 11:06:03.298 Leg L:53.3[VMail] is terminated: Cause: BYE from PBX
06-Jul-2015 11:06:03.297 [CM503008]: Call(C:53): Call is terminated
06-Jul-2015 11:06:03.293 Leg L:53.1[Extn] is terminated: Cause: BYE from 10.101.100.23:55136
06-Jul-2015 11:05:58.450 [CM503007]: Call(C:53): VMail:999 has joined, contact <sip:[email protected]:40600>
06-Jul-2015 11:05:58.450 [CM503007]: Call(C:53): Extn:765 has joined, contact <sip:[email protected]:55136>
06-Jul-2015 11:05:58.442 L:53.3[VMail] has joined to L:53.1[Extn]
06-Jul-2015 11:05:58.242 [CM503025]: Call(C:53): Calling T:VMail:999@[Dev:sip:[email protected]:40600;rinstance=66ef7bca6217aa4f] for L:53.1[Extn]
06-Jul-2015 11:05:58.237 [CM503005]: Call(C:53): Forwarding: T:VMail:999@[Dev:sip:[email protected]:40600;rinstance=66ef7bca6217aa4f]
06-Jul-2015 11:05:58.237 L:53.1[Extn] forwards call from Extn:281 to VMail:999 based on rule Fwd[Available/NoAnsw]
06-Jul-2015 11:05:58.237 L:53.1[Extn] failed to reach Extn:281, reason No Answer
06-Jul-2015 11:05:43.161 Currently active calls - 1: [53]
06-Jul-2015 11:05:38.191 [CM503025]: Call(C:53): Calling T:Extn:281@[Dev:sip:[email protected]:5062] for L:53.1[Extn]
06-Jul-2015 11:05:38.143 [CM503027]: Call(C:53): From: Extn:765 ("removed" <sip:[email protected]:5060>) to T:Extn:281@[Dev:sip:[email protected]:5062]
06-Jul-2015 11:05:38.143 [CM503004]: Call(C:53): Route 1: from L:53.1[Extn] to T:Extn:281@[Dev:sip:[email protected]:5062]
06-Jul-2015 11:05:38.141 [CM503001]: Call(C:53): Incoming call from Extn:765 to <sip:[email protected]:5060>

Here's a call from my cell phone inbound on a SIP line to Yealink extension 281. In this case, the Yealink phone rang and the call connected just fine. Phone numbers and names redacted.

06-Jul-2015 11:14:10.800 Leg L:54.1[Line:10000<<+1xxxxxxxxx] is terminated: Cause: BYE from PBX
06-Jul-2015 11:14:10.800 [CM503008]: Call(C:54): Call is terminated
06-Jul-2015 11:14:10.797 Leg L:54.3[Extn] is terminated: Cause: BYE from 10.102.100.10:5062
06-Jul-2015 11:14:07.179 Leg L:54.2[Ivr] is terminated: Cause: BYE from 127.0.0.1:40600
06-Jul-2015 11:14:06.969 [CM503007]: Call(C:54): Extn:281 has joined, contact <sip:[email protected]:5062>
06-Jul-2015 11:14:06.967 L:54.3[Extn] has joined to L:54.1[Line:10000<<+1xxxxxxxxxx]
06-Jul-2015 11:14:05.232 Currently active calls - 1: [54]
06-Jul-2015 11:14:04.735 [CM503025]: Call(C:54): Calling T:Extn:281@[Dev:sip:[email protected]:5062] for L:54.1[Line:10000<<+1removed]
06-Jul-2015 11:14:04.683 [CM503027]: Call(C:54): From: Line:10000<<+1removed ("name removed " <sip:[email protected]:5060>) to T:Extn:281@[Dev:sip:[email protected]:5062]
06-Jul-2015 11:14:04.683 [CM503004]: Call(C:54): Route 1: from L:54.1[Line:10000<<+1removed] to T:Extn:281@[Dev:sip:[email protected]:5062]
06-Jul-2015 11:14:04.682 [CM505003]: Provider:[Flowroute] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [] PBX contact: [sip:[email protected]:5060]
06-Jul-2015 11:13:47.632 [CM503007]: Call(C:54): Ivr:800 has joined, contact <sip:[email protected]:40600>
06-Jul-2015 11:13:47.632 [CM503007]: Call(C:54): Line:10000<<+1removed has joined, contact <sip:[email protected]:5060>
06-Jul-2015 11:13:47.628 L:54.2[Ivr] has joined to L:54.1[Line:10000<<+1xxxxxxxxx]
06-Jul-2015 11:13:47.427 [CM503025]: Call(C:54): Calling T:Ivr:800@[Dev:sip:[email protected]:40600;rinstance=cf3cef1da329531e] for L:54.1[Line:10000<<+1xxxxxxxxxx]
06-Jul-2015 11:13:47.410 [CM503027]: Call(C:54): From: Line:10000<<+1xxxxxxxxxx ("name removed " <sip:[email protected]:5060>) to T:Ivr:800@[Dev:sip:[email protected]:40600;rinstance=cf3cef1da329531e]
06-Jul-2015 11:13:47.410 [CM503004]: Call(C:54): Route 1: from L:54.1[Line:10000<<+1xxxxxxxxxx] to T:Ivr:800@[Dev:sip:[email protected]:40600;rinstance=cf3cef1da329531e]
06-Jul-2015 11:13:47.409 [CM505003]: Provider:[Flowroute] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [] PBX contact: [sip:[email protected]:5060]
06-Jul-2015 11:13:47.408 [CM503001]: Call(C:54): Incoming call from Line:10000<<+1xxxxxxxxxx to <sip:[email protected]:5060>
06-Jul-2015 11:13:47.408 Line limit check: Current # of calls for line Lc:10000(@Flowroute[<sip:[email protected]:5060>]) is 1; limit is 25
06-Jul-2015 11:13:47.324 [CM503012]: Inbound office hours rule (unnamed) for 10000 forwards to DN:800

Below is a call from the Yealink at xt 281 to the 3CXPhone at xt 765. The call went through with no problems:

06-Jul-2015 11:22:15.064 Leg L:55.2[Extn] is terminated: Cause: BYE from PBX
06-Jul-2015 11:22:15.063 [CM503008]: Call(C:55): Call is terminated
06-Jul-2015 11:22:15.059 Leg L:55.1[Extn] is terminated: Cause: BYE from 10.102.100.10:5062
06-Jul-2015 11:22:10.815 [CM503007]: Call(C:55): Extn:765 has joined, contact <sip:[email protected]:55136>
06-Jul-2015 11:22:10.814 [CM503007]: Call(C:55): Extn:281 has joined, contact <sip:[email protected]:5062>
06-Jul-2015 11:22:10.811 L:55.2[Extn] has joined to L:55.1[Extn]
06-Jul-2015 11:22:01.874 [CM503025]: Call(C:55): Calling T:Extn:765@[Dev:sip:[email protected]:55136;ob] for L:55.1[Extn]
06-Jul-2015 11:22:01.825 [CM503027]: Call(C:55): From: Extn:281 ("MDF" <sip:[email protected]:5060>) to T:Extn:765@[Dev:sip:[email protected]:55136;ob]
06-Jul-2015 11:22:01.825 [CM503004]: Call(C:55): Route 1: from L:55.1[Extn] to T:Extn:765@[Dev:sip:[email protected]:55136;ob]
06-Jul-2015 11:22:01.823 [CM503001]: Call(C:55): Incoming call from Extn:281 to <sip:[email protected]:5060>

Any help is much appreciated. Thank you!

--John

 

[jholcombe]

Craigreilly: Yes, I have re-sent and re-applied the config file to 3CXPhone and am still experiencing this issue. I will try again with Windows firewall completely disabled.

Ineblett: Yes, I provisioned the T46Gs using 3CX. The T46G does ring only if I call it from either another extension that is not 3CXPhone or from outside via a SIP provider. If I call it from 3CXPhone it will not ring. The ring was heard on 3CXPhone (I suspect it was the call ringing to voicemail). When I call the T46G from 3CXPhone I don't hear ringing on 3CXPhone or the T46G -- There's just a delay. Then after a short delay (about 5 rings worth) it transfers to voicemail.

 

[lneblett]

I will test the same config today. You indicated that the T46, while not ringing, did light up. If you were to pick up during this time, will the connection be made?

Ok, so the t46 was configured using 3CX, and I see that you provisioned the 3CX phone as well. Are there any set-ups that are not vanilla - codecs, ports, security, etc. You indicated that the issue is from the 3CX phone to an internal extension.......what about from an internal extension to the 3CX phone?

 

[jholcombe]

Ineblett: If I answer the T46G while calling it from 3CXPhone, I'll get a dial tone. The connection is not made.

If I call from an extension to 3CXPhone, the connection is fine. 3CXPhone will ring and the call will be established with no problems.

I checked the CODECs as you suggested. The extension for the 3CXPhone also at one time had a T46G associated with it. That T46G is still listed in the phone provisioning. I noticed that the preferred order of CODECs was reversed on extension 765 from the other extensions. Previously I had been adjusting the CODECs because I was trying to find a lower-bandwidth CODEC.

I just did a test call from 3CXPhone xt 765 from my home to extension 281 and the call went through with no problems. It sounds like you solved it. It was likely a problem with the order of the CODECs on the 3CXPhone extension.

Thank you all for your help. I'll do some more testing later today but I think the problem is solved.

Take care,

--John

 

[lneblett]

Great.....glad to know that it seems to work.

I had just tested my T46 with 3CX phone and no issues.

 

[jholcombe]

The problem started up again when I checked it locally. I noticed that there was a firmware upgrade available, so I upgraded the Yealink SIP-T46G phone from 28.72.0.26 to 28.73.0.48. Now it appears to be working again, and the phones are ringing when I call them from 3CXPhone. I'll try again tomorrow and let y'all know how it goes. Thank you everyone for your help.

--John

 

[jholcombe]

I installed the 28.73.0.48 firmware update to all of our Yealink T46G phones. This seems to have corrected the problem as it hasn't been an issue all day. Thank you!