Not allowed

[navin]

Hello guys, Idk why all of a sudden all calls in outbound and inbound is not allowed but when i reboot the server it goes back to normal,
this happens every once in a week.

Dialed: Sir $$$ (+###########) → Via rule: docdx (+###########) → Via trunk: Elevate Calls Employee (+###########) → Not allowed



This is an config of the outbound rules from the old IT I didn't change it yet.

Rule Name	PrefixOutbound	Call from Ext.	Length	Department	Route 1	Route 2	Route 3	Route 4	Route 5
docdx	Any		12	Elevate Calls, Jivana Care	Elevate Calls Employee	Blocked	Blocked	Blocked	Blocked
Go ---- -ecurity	Any		12	Go Safer Security	Go Safer Security	Blocked	Blocked	Blocked	Blocked
Leo ------Only	0	All	11		Elevate Calls Employee	Blocked	Blocked	Blocked	Blocked
12 Digit Rule	Any	All	12		Elevate Calls Employee	Blocked	Blocked	Blocked	Blocked
10 Digit Rule	Any	All	10		Elevate Calls Employee	Blocked	Blocked	Blocked	Blocked
11 Digit Rule	Any	All	11		Elevate Calls Employee	Blocked	Blocked	Blocked	Blocked
Outbound rule for Xentigroupllc	Any	All	Any		Xentigroupllc	Blocked	Blocked	Blocked	Blocked
to onevoip	Any	202	Any	Elevate Calls	one-voip	Blocked	Blocked	Blocked	Blocked

 

[Alphabetic]

You would need to check event / activity logs for further clarification.

set your logging to verbose.

What OS is this on?

 

[Alejandro_3CX]

The system is matching the outbound rule as you describe it is using the rule: docdx

Please check the user is included in one of these departments Elevate Calls, Jivana Care, I also suggest you to check the event log and see if there is any event regarding the voip provider.

 

[navin]

Call or Registration to +########@(Ln.10000@Elevate Calls Employee) has failed. sip:192.76.120.1#:5060;lr replied: Forbidden (403)

 

[Alejandro_3CX]

Call or Registration to +########@(Ln.10000@Elevate Calls Employee) has failed. sip:192.76.120.1#:5060;lr replied: Forbidden (403)

You will need to check this with your voip provider since they are the one rejecting the call with the 403 forbidden.

Is this trunk IP based or uses registration? are you allow to dial the number, for example they may block specific calls...

 

[navin]

this is user registration

 

[Alphabetic]

have you checked the state of your SIP registration at the time of issues?

Try "refresh registration" instead of a restart the next time.

is your WAN IP dynamic?

Is this a supported sip trunk?

 

[navin]

Thanks

 

[navin]

I tried refresh and reregister still wont work

 

[Alphabetic]

So its currently down right now?

 

[navin]

everything is green I green and connected. already send a logs in telnyx and waiting for their response.

 

[Alphabetic]

That doesnt answer my question, and you havent answered any of my others.

it's home time for me today, but good luck.

 

[navin]

Sorry I was responding to someone.

have you checked the state of your SIP registration at the time of issues? yes its registered

Try "refresh registration" instead of a restart the next time. also done

is your WAN IP dynamic? it was static now im suing dynamic

Is this a supported sip trunk? im using telnyx

 

[VoIPTools]

My first thought was that your trunk registration had timed out. But if you say it successfully refreshes, and in my experience Telnyx is a reliable provider, then something else obviously is going on.

I would contact Telnyx support and let them know of your issue (in advance of the issue happening again). Let them know that you will be contacting them again when it happens so they are ready to test as soon as you call.

I would be curious to know is whether Telnyx is receiving your request at all. Also, whether they are logging any issues with registration. It may show green in 3CX, but that does not necessarily mean Telnyx is not having issues on their end.