Solved Outbound calls forbidden

[msardi]

I have a 3CX with a Yeastar TA810 analog VOIP Gateway.
Inbound calls are working, but when I try to do an outbound call I receive a "Forbidden" message in the IP phone display, and the 3cx event log says the following.

• Call or Registration to 113@(Ln.10000@TA810) has failed. 192.168.6.106 replied: 603 Declined; from IP:192.168.6.106:5060

192.168.6.106 is the IP of TA810 gateway.
Surelly there must be a configuration error, but I cannot find where.
If anybody knows which option can be wrong configured, it would be appreciated.

Thanks,

Matias

 

[leejor]

Call or Registration to 113@(Ln.10000@TA810) has failed.

So...are you sending the digits 113 to the gateway? It may be that there is an internal dialplan on the gateway, that is rejecting the digits, or, there is no central office battery, on one or more of the lines plugged into the gateway. Was the gateway used in another installation? How was it configured?

From Wikipedia, here is the definition of the 603 Declined message...

"The destination does not wish to participate in the call, or cannot do so, and additionally the destination knows there are no alternative destinations (such as a voicemail server) willing to accept the call."

 

[msardi]

113 is a number you can dial to listen the official time in Argentina. The error is the same with other external number.

• Call or Registration to 43733864@(Ln.10000@TA810) has failed. 192.168.6.106 replied: 603 Declined; from IP:192.168.6.106:5060

The gateway is new and I am setting it for the first time.
Looking at gatway logs I have found this:

[2018-01-10 10:16:43] NOTICE[1186] chan_sip.c: zzzzccttt 1132579859,4595300
[2018-01-10 10:16:43] NOTICE[1186] chan_sip.c: zzzzccttt username:192.168.6.105, 1, 192.168.6.105:5060
[2018-01-10 10:16:43] NOTICE[1186] chan_sip.c: zzzzccttt
[2018-01-10 10:16:43] NOTICE[1186] chan_sip.c: [YEASTARMAPDNS] Get peer by ip and toexten:43733864
[2018-01-10 10:16:43] NOTICE[1186] chan_sip.c: zzzzccttt 4343803,4595300
[2018-01-10 10:16:43] NOTICE[1186] chan_sip.c: zzzzccttt username:43733864, 1, 192.168.6.105:5060
[2018-01-10 10:16:43] NOTICE[1186] chan_sip.c: zzzzccttt
[2018-01-10 10:16:43] NOTICE[1186] rtp.c: Set RTP to address rtp:4610464 192.168.6.105:7160
[2018-01-10 10:16:43] WARNING[14310] pbx.c: Channel 'SIP/trunk-sps-3CX-00000006' sent into invalid extension 's' in context 'default', but no invalid handler
[2018-01-10 10:16:43] NOTICE[14310] rtp.c: Stop RTP address rtp:4610464 192.168.6.105:7160

IP 192.168.6.105 is the one from 3cx.

Matias

 

[leejor]

I'm not familiar with a Yeastar gateway so I'm not certain what those logs are trying to tell you.
How was the Yeastar gateway provisioned? Looking over the list of 3CX approved gateways https://www.3cx.com/voip-gateways/, I don't see it on the list. There may be one or more settings that are incorrect.

I see some support offered on the Yeastar site, dealing with older 3CX versions.

https://support.yeastar.com/hc/en-us/articles/217756008-How-to-Connect-Yeastar-TA-FXO-Gateway-to-3CX

https://support.yeastar.com/hc/en-u...-How-to-Connect-Yeastar-TA-FXO-Gateway-to-3CX

You may wish to consider contacting Yeastar, for their for support, They should be able to interpret the log you are getting.

Yeastar devices have been mentioned on the 3CX site, in the past https://www.3cx.com/community/threads/support-for-yeastar-gateways.45232/ , so there may be a forum member that has some experience with them, and can offer assistance.

 

[msardi]

I have found the solution:

Go to the 3CX management console, and change the 'From: User Part' in Outbound Parameters of SIP trunk that interconnects to Yeastar gateways. The recommended option is: "OutboundCallerid" Outbound caller Id taken from Extension settings in managament conosle.
If issue persists, please go the Extension settings and fill a proper Outbound Caller ID for the 3CX extensions.

You can read it here:
https://support.yeastar.com/hc/en-u...able-to-Call-from-3CX-v15-to-Yeastar-Gateways

Thanks for your help.

Matias

 

[leejor]

Odd issue, as a PSTN gateway is unable to change/pass caller ID when placing an outgoing call. Perhaps some sort of security/authentication used by the gateway. Glad you were able to resolve.