Can't make outbound calls

[Mike Watts]

Setting up a Yealink T29G and after provisioning getting error in 3cx activity logs "04/06/2018 3:00:18 PM - Exception: ParseException ../../rutil/ParseBuffer.hxx:230, Parse failed unexpected eof in context: 2145555555 ^ @ ../../rutil/ParseBuffer.hxx:230"

Phone can receive calls but can't make outgoing calls or even call an internal extension, other ip phones of a different brand do not have this issue.
Any ideas?

 

[craigreilly]

The ParseBuffer error seems common - but for different reasons:

https://www.3cx.com/community/threads/call-to-twillio-fails.55534/#post-229909

https://www.3cx.com/community/threa...rd-party-declines-the-call.54413/#post-223947

https://www.3cx.com/community/threa...ough-to-3cx-windows-client.53337/#post-218538

have you tried setting up a new extension - or is this already new?

 

[Mike Watts]

Thanks for the reply, yeah it was already a new extension.

 

[leejor]

Is the extension local to the PBX? Is this the only Yealink with this issue? Current set firmware? "Factory reset" and re-provision have any affect?

 

[Mike Watts]

It's not local to the pbx, we're using 3cx on the cloud. We have 2 new Yealink's and both have the same issue, one is a T29G and the other one is a W60B with 5 W56H handsets. All have the latest 3cx "approved" firmware and were factory reset before provisioning. I've reset both several times and reprovisioned and still get the same error. As a test I setup a Htek uc924 on one of the extensions entered the auto provision link using STUN, rebooted and it works perfect.

 

[eddv123]

I think your best bet is to take a trace with the Verbose logs and look at it with the binary log viewer: https://www.3cx.com/docs/collecting-logs-for-3cx-support/

https://www.3cx.com/docs/3cx-log-viewer/

I've never known such issues where one brand phone works and another not and Yealinks are pretty solid devices with 3CX.

One very simple check could be checking the outbound rule, you may have it configured to all calls outbound for the Htek but not the Yealink.

 

[Faserm]

Thanks for the reply, yeah it was already a new extension.

Why do you say that ?

 

[craigreilly]

Cause I asked him ... I’ve seen issues thru an upgrade where things get corrupt and creating a new extension helps.