Solved Busy Line 486

[Bhav Panesar]

Hi all,

I've come across a few points about people raising an issue when users make calls from their Yealink handsets that are on the 3CX system and unable to make outbound external calls. Internal are fine. We have 2 extensions affected here in this office, meanwhile our Luxembourg office has no issues at all.

The errors we have had are:

10/11/2018 10:06:50 AM - Exception: ParseException ../../rutil/ParseBuffer.hxx:230, Parse failed unexpected eof in context: 0032xxxxxx ^ @ ../../rutil/ParseBuffer.hxx:230
10/11/2018 10:06:50 AM - Call to T:Line:10000>>032xxxxxx@[Dev:sip:[email protected]:5060] from L:485.1[Extn:38] failed, cause: Cause: 486 Busy Here/INVITE from 85.93.219.252:5060
10/11/2018 10:06:50 AM - [CM503003]: Call(C:485): Call to <sip:[email protected]:5060> has failed; Cause: 486 Busy Here/INVITE from 85.93.219.252:5060
10/11/2018 10:00:03 AM - Exception: ParseException ../../rutil/ParseBuffer.hxx:230, Parse failed unexpected eof in context: 0032xxxxxxxxx ^ @ ../../rutil/ParseBuffer.hxx:230
10/11/2018 10:00:03 AM - Call to T:Line:10000>>032xxxxxxx@[Dev:sip:[email protected]:5060] from L:481.1[Extn:38] failed, cause: Cause: 486 Busy Here/INVITE from 85.93.219.232:5060
10/11/2018 10:00:03 AM - [CM503003]: Call(C:481): Call to <sip:[email protected]:5060> has failed; Cause: 486 Busy Here/INVITE from 85.93.219.232:5060

Could someone point me out what the obvious issue is here? Note, only 2 extensions are affected, all others are working fine and nothing has been changed, the issue has come up today.

 

[YiannisH_3CX]

Hello @Bhav Panesar

From the provided logs i can see that you get a Busy message from the provider so i believe you should first ask the provider why you are getting a busy message.
Yealink phones can produce the ParseException error when a call cannot be completed or no outgoing routed exist so i believe the error can be safely ignored.

 

[Bhav Panesar]

I figured as much, but I thought let me try steps on my side to fix the issue before resulting to contacting the provider. Fingers crossed will see how this goes down! Thanks Yiannis!

 

[YiannisH_3CX]

Keep us updated

 

[Bhav Panesar]

Resolved @YiannisH_3CX - User error... At least I had time to diagnose and try bits and bobs and get familiarised with the system. Thanks your time, buddy!

 

[YiannisH_3CX]

Glad to see the issue has been resolved and thank you for updating the thread.