Outbound calling issue

[Alan H]

When one of our ext call a number I get this error "Call or Registration to PHONE#@(Ln.10001@Flowroute) has failed. 216.115.69.144 replied: 486 Busy Here; from IP:216.115.69.144:5060" but when I call I get right threw. Any ideas,

 

[Lee Cramman]

The callee is engaged?

https://en.wikipedia.org/wiki/List_of_SIP_response_codes

 

[Alan H]

If I call I get an answer on the other end, if the person with the ext calls she gets nothing, except I get email with that error.

 

[leejor]

That is a "standard" log, from a provider, when the line called is actually busy, or, at least, that's the response they get from the provider that they have passed the call onto. It is strange that your call does go through. Does this happen with only one number, or numbers to a certain destination (mobile carrier)?
You will probably have to contact your provider for an explanation.


If you call...from where? Not from 3CX?

 

[Lee Cramman]

It is strange that your call does go through.

I read it as his call from a different extension went through. Maybe the number was no longer busy?

 

[Alan H]

I get that a standard call does go through log. but what is strange is i'm call the same number from the same system, only difference is we are in 2 different locations and my ext is 3104 her's is 4011

 

[Alan H]

here is the full Activity Log from the call

01/29/2019 10:53:34 AM - Exception: ParseException ../../rutil/ParseBuffer.hxx:230, Parse failed unexpected eof in context: Phone#^ @ ../../rutil/ParseBuffer.hxx:230
01/29/2019 10:53:34 AM - [CM503003]: Call(C:3440): Call to <sip:phone# @sip.flowroute.com:5060> has failed; Cause: 486 Busy Here/INVITE from 216.115.69.144:5060
01/29/2019 10:53:34 AM - Call to T:Line:10001>>Phone#@[Dev:sip:sip.flowroute.com:5060] from L:3440.1[Extn:4011] failed, cause: Cause: 486 Busy Here/INVITE from 216.115.69.144:5060
01/29/2019 10:53:34 AM - [CM503003]: Call(C:3440): Call to <sip:phone#@sip.flowroute.com:5060> has failed; Cause: 486 Busy Here/INVITE from 216.115.69.144:5060
01/29/2019 10:52:23 AM - [CM503003]: Call(C:3439): Call to <sip:[email protected]:5060> has failed; Cause: 487 Request Terminated/INVITE from 127.0.0.1:5063
01/29/2019 10:52:23 AM - Exception: ParseException ../../rutil/ParseBuffer.hxx:230, Parse failed unexpected eof in context: 4011 ^ @ ../../rutil/ParseBuffer.hxx:230

 

[leejor]

Is it just to one particular outside number? Could it be an outgoing caller ID issue, given that , over the same route, one extension does get through?

Have you compared an Activity Log for a call that gets through to the one that fails? Any differences? You might have to used the Verbose setting.

Again, you might want to ask the provider for an explanation.

 

[Alan H]

I think I found the issue on this ext 4011, I have outbound number on it, the same number is on inbound call queue, when I remove the outbound # the call went threw on her ext. Did I do something wrong?

 

[leejor]

You mean that the extension had an outside caller ID assigned, that was removed? If that was the case, then the depending on how your provider interprets, or allows, the caller ID may have prevented that call from completing.

 

[Alan H]

how it was to work was the 555-555-5000 was set to her outbound so when she made a call it showed that #. When some would call into 555-555-5000 it was inbound call queue so incase the person was at lunch or out of the office another person could answer the call. When i remove the number either from her outbound# or the inbound queue, she was able to call the number she couldn't before.

 

[leejor]

You could try putting that number in the settings for a different extension and see if the same thing happens. If it does, then ask you provider why it is happening, if you feel that this outbound caller ID should be used. Do you change the outbound caller ID on other extensions? Perhaps the caller ID is in the wrong field to be utilized correctly by the provider.

 

[YiannisH_3CX]

If the issue occurs when you set the number as an outbound caller ID then that means the provider does not like the number you are sending. If that number is a DID of the system i would recommend reaching out to them and ask them what is it they don't like about the number so you can adjust it. Also if you are using the number 555-555-5000 with the dashes i would recommend removing the dashes and trying again.

 

[Alan H]

If the issue occurs when you set the number as an outbound caller ID then that means the provider does not like the number you are sending. If that number is a DID of the system i would recommend reaching out to them and ask them what is it they don't like about the number so you can adjust it. Also if you are using the number 555-555-5000 with the dashes i would recommend removing the dashes and trying again.

No I was using 15555555000 just like the outgoing DID for others

 

[YiannisH_3CX]

No I was using 15555555000 just like the outgoing DID for others

In this case your best option is to contact your provider and ask them why the call is rejected when using this outbound caller ID.