ERROR LOG SIP TRUNK BUSY

[LuisGonzalez]

HEllo,

im getting this message Call or Registration to 787-xxx-xxxx@(Ln.10000@RocketNet Solutions) has failed. 162.254.144.173 replied: 403 Forbidden; from IP:162.254.144.173:5060
and then the outboundcall sound busy, i need to disable and enable again the trunk

how can i fix it?

 

[leejor]

It all depends on why your provider is sending that reply. You could guess...incorrect number format, incorrect caller ID sent, or, something else. It may also be an issue with the registration/,user or password. You could probably save some time and ask them, for an explanation.

 

[LuisGonzalez]

SIP request (REGISTER) from 64.31.24.94 was rejected. Reason: Block WAN requests is ON. Message: REGISTER sips: PBX_IP:5061 SIP/2.0 Via: SIP/2.0/TLS 64.31.24.94:41902;branch=z9hG4bK68ae715c5bd57e3b3f868ae602745436216ef6410fcea33a9b75e2569372c2 Max-Forwards: 70 Contact: 1001 <sips:[email protected]:41902> To: 1001 <sips:1001@PBX_IP:5061> From: 1001 <sips:1001@PBX_IP:5061>;tag=9aa76878661bc6a1a075ed5a73fb4d2f Call-ID: 3304882224133df2952d05f8c8d3e163 CSeq: 2 REGISTER Expires: 10000 Proxy-Authorization: Digest username="1001",realm="3CXPhoneSystem",nonce="414d535961067c7563:1ca228ad286de2f1b6691b58e05730d5",uri="sips: PBX_IP:5061",response="9b62e9e55637cdb920120c5060a2bdc1",algorithm=MD5 Content-Length: 0

 

[Evolute IT]

SIP request (REGISTER) from 64.31.24.94 was rejected. Reason: Block WAN requests is ON. Message: REGISTER sips: PBX_IP:5061 SIP/2.0 Via: SIP/2.0/TLS 64.31.24.94:41902;branch=z9hG4bK68ae715c5bd57e3b3f868ae602745436216ef6410fcea33a9b75e2569372c2 Max-Forwards: 70 Contact: 1001 <sips:[email protected]:41902> To: 1001 <sips:1001@PBX_IP:5061> From: 1001 <sips:1001@PBX_IP:5061>;tag=9aa76878661bc6a1a075ed5a73fb4d2f Call-ID: 3304882224133df2952d05f8c8d3e163 CSeq: 2 REGISTER Expires: 10000 Proxy-Authorization: Digest username="1001",realm="3CXPhoneSystem",nonce="414d535961067c7563:1ca228ad286de2f1b6691b58e05730d5",uri="sips: PBX_IP:5061",response="9b62e9e55637cdb920120c5060a2bdc1",algorithm=MD5 Content-Length: 0

That's a SIP registration, over TLS apparently. Not related to the trunk but if that's your phone, you'll need to uncheck "Block WAN requests" in the Extensions > 1001 > Options.

As for your trunk, Forbidden is usually because of either: auth failure, CID failure (using a DID that isn't on your account can be blocked) or destination number failure. It could also simply be your provider having blocked the call for any other reasons (billing, fraud, etc.)

If this is a 3CX supported trunk provider, contact your provider as they'll be able to tell you exactly the reason.

 

[LuisGonzalez]

Hey,

But the extension 1001 is a IVR.

0.0

 

[Evolute IT]

Hey,

But the extension 1001 is a IVR.

0.0

If you go to Dashboard > System Extensions (bottom of middle block), is the 1001 IVR registered in there?

If so, it's probably just someone trying to hack. That happens a lot and you don't need to worry about it.

 

[LuisGonzalez]

 

[LuisGonzalez]

The problem is that every time I have this problem all the outgoing calls go busy and I have to restart the trunks.

 

[ChrisC_3CX]

@LuisGonzalez

The problem is that every time I have this problem all the outgoing calls go busy and I have to restart the trunks.

Which provider are you using, is it a 3CX Supported Provider?

Since you've already confirmed that it is the provider that is for some reason causing this, as leejor mentioned, it's probably best that you contact the provider to have them tell you why they are rejecting these calls.

What you might also want to consider is if by any chance this is a Register based provider that you happened to also configure on a different PBX with the same account. If this is the case, you'll most definitely need to delete that SIP Trunk configuration.

 

[LuisGonzalez]

Hey, Im using Voip.ms

 

[ChrisC_3CX]

What you might also want to consider is if by any chance this is a Register based provider that you happened to also configure on a different PBX with the same account. If this is the case, you'll most definitely need to delete that SIP Trunk configuration.

Have you confirmed that this is indeed not the case?

Also, have you contacted the provider at all regarding this?

EDIT: As a test, please check the following: Edit the SIP Trunk and go to "Options", scroll down and check what's selected under "Transport Protocol". Also, change it to "UDP" and apply.