Can't connect with Nextiva SIP carrier

[dhijrwn]

Cluster setup
ViciBox v.8.1.2 ISO
VERSION: 2.14-733a
BUILD: 200115-1702
Asterisk 13.29.2-vici

Im trying to configure our backup carrier. So we choose nextiva voice and analytics service. SO they gave us the cred and we are connected with each other.
when im executing the sip show peers the status is ok 164ms. So when im doing a call. Im having sip 403 forbidden error.

{phonenumber} the phone number is a placeholder

[Mar 24 14:06:07] == Using SIP RTP CoS mark 5
[Mar 24 14:06:07] > 0x7fa33400ca30 -- Strict RTP learning after remote address set to: xx.xx.xx.xx:6176
[Mar 24 14:06:07] -- Executing [{phonenumber}@default:1] AGI("SIP/6000-00000000", "agi://127.0.0.1:4577/call_log") in new stack
[Mar 24 14:06:07] -- <SIP/6000-00000000>AGI Script agi://127.0.0.1:4577/call_log completed, returning 0
[Mar 24 14:06:07] -- Executing [{phonenumber}@default:2] Dial("SIP/6000-00000000", "SIP/nextiva/{phonenumber},,To") in new stack
[Mar 24 14:06:08] == Using SIP RTP CoS mark 5
[Mar 24 14:06:08] -- Called SIP/nextiva/{phonenumber}
[Mar 24 14:06:08] WARNING[10950][C-00000001]: chan_sip.c:24088 handle_response_invite: Received response: "Forbidden" from '"me" <sip:6000@210.4.112.133>;tag=as554a60e9'
[Mar 24 14:06:08] == Everyone is busy/congested at this time (1:0/0/1)
[Mar 24 14:06:08] -- Executing [{phonenumber}@default:3] Hangup("SIP/6000-00000000", "") in new stack
[Mar 24 14:06:08] == Spawn extension (default, {phonenumber}, 3) exited non-zero on 'SIP/6000-00000000'
[Mar 24 14:06:08] -- Executing [h@default:1] AGI("SIP/6000-00000000", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----21-----CHANUNAVAIL---------------SIP 403 Forbidden)") in new stack
[Mar 24 14:06:08] -- <SIP/6000-00000000>AGI Script agi://127.0.0.1:4577/call_log--HVcauses ... -------SIP 403 Forbidden) completed, returning 0


Any idea how to debug this or fix??

[williamconley]

Forbidden is NOT something you can cure on your side. They must tell you what is wrong with the call based on their logs. It could be that they require a country code, or don't allow the country code, or require a special digit or digits in front of the call other than a country code, or a Plus sign. It could also be that they don't like your caller id number or caller id name. There are no rules here aside from what the carrier makes up for their own nefarious purposes. No standard.

All forbidden tells you is that YOU are not allowed to dial That Number. Nothing else.

You *could* try to enable SIP debugging, which may give you an error code which may provide a bit more insight. But that's only about a 25% chance that it'll even be helpful.

They should be able to tell you why they rejected a call on your account to the number you called at that precise time (and time zone). That should be enough to pull it up in their log to find the reject reason.