Forbidden Error - Specific Area Codes - Gotomeeting

[OS-Milton]

Calls in / Out work fine EXCEPT specific Gotomeeting numbers.
Our Carrier Spectrum
via Soft / yealink / android tested >3CX > Digium G200 > Spectrum (Charter) PRI

8722403212 - fails - forbidden
3127573121 - fails - forbidden
5713173129 - works

--
Call for Mobile phone - Verizon Carrier -
All work no issue
--

01/14/2021 2:03:29 PM - Exception: ParseException ../../rutil/ParseBuffer.hxx:230, Parse failed unexpected eof in context: 8722403212 ^ @ ../../rutil/ParseBuffer.hxx:230



01/14/2021 3:58:11 PM - Call to T:Line:10000>>8722403212@[Dev:sip:10000@SIPPRIGateway] from L:1518.1[Extn:<me>] failed, cause: Cause: 603 Declined/INVITE from SIPPRIGateway:5060


I think its more carrier related - but could definitely be my dial plan - but I can call log distance..

https://community.logmein.com/t5/Go...ial-in-conference-phone-number-on/td-p/171261

is the error tied to the calling restrictions by country?


the numbers are pretty close.. at least 872 one..

Started a ticket with provider -- just thought i post because it seems specifically tied to GotoMeeting and Chicago area

 

[leejor]

It would seem to be an end party issue.

01/14/2021 3:58:11 PM - Call to T:Line:10000>>8722403212@[Dev:sip:10000@SIPPRIGateway] from L:1518.1[Extn:<me>] failed, cause: Cause: 603 Declined/INVITE from SIPPRIGateway:5060

603 Declined means the call went through, but the called party has declined your call, for whatever reason. Perhaps your provider will come up with an answer. Since you are not prefixing the numbers with a +, or international access codes (using 3CX E164), the country codes should not be confused with area codes.

 

[ChrisC_3CX]

@OS-Milton

As you already mentioned, we would of course first recommend that you contact your provider about this since, based on the message you provided, the call left 3CX and therefore out of 3CX's control.

In the event that you are unable to resolve the issue even with the provider's help, you may want to consider having a look at our list of 3CX Supported Provider's which have been tested with 3CX and will therefore offer a more trouble free experience when utilized: https://www.3cx.com/partners/sip-trunks/

If you are utilizing an FXO gateway, please also consider having a look at our list of 3CX Supported Gateways found here: https://www.3cx.com/voip-gateways/

 

[OS-Milton]

Carrier - Noted UpStream Partner routing changes.
More noting error for others searching for similar errors at some later date -
similar to the 2017 Post on LMI forums noted above

# is a GotoMeeting Auto Generated Number - Create a meeting - get a LD Number - odd they don't recognize state local in state might be more logical... oh well.

mainly noting 3CX Error processing -
giving Forbidden MSG would appear to be local PBX issue vs upstream - cleaner error like "UpCallFail" vs "PBXCallFail" or even "RuleFail"

would be more noteworthy to then look specifically at PRI Gateway & Carrier.

just for clarification.
@leejor
THANK YOU for your detailed response

explaining the 603 & country codes -
That is exactly what I was thinking as I wasn't using country codes it should have remained within.
it was the "Forbidden" message with very little detail that was why I was looking there, just to be sure.
(Thank you for ruling out!)