Outbound Rule Stopped Working - International Prefix

cb83

Customer
Joined
Jul 12, 2024
Messages
23
Reaction score
0
I have two on premise (v20) instances that are bridged.

There is a rule on PBX Site A that routes all international calls (starting with 00 prefix) out of the bridge to PBX B.

On Site B, there is a rule that routes these calls to the appropriate SIP trunk.

This 100% used to work. Now I am getting an error prompt from Site B saying "you no longer have permission to use this service"

I know that the call is being routed to PBX Site B as I changed the prompt set language as a test.

There are no entries in the event log and the call log simply says the call was "Unanswered"

Also checked that all country codes are allowed on both sides.

Calls to local extensions on both sites work fine.
 
That prompt doesnt sound like a 3CX prompt.

You can do a capture on the Site B PBX to see what is being returned by the provider when the call is attempted to go through.
 
That is from your sip provider... Maybe you didnt pay the bill ;-)
 
A call to the same number from a local extension on Site B works fine.
 
Than expand your loglevel to at least medium and check again. There must be something in your log to see where the failure is.
 
Are you using the Activity Log (Verbose) to confirm that call is actually reaching your provider, and if so, is there an error message?
 
You would need to check your outbound rules on B. Check your outbound rules are not checking by department or extension, as this would block calls from A going through.
 
  • Like
Reactions: bitn2
"You no longer have permission to utilize the system"

"Destination is not available, not registered, or there are no routes available"

These are the prompts being received.

Department and extension fields on Site B are blank.

This is a very simple rule that has always worked. It is very strange as calling the exact same number from Site B works fine.

The route is there! 00 prefix routing to the SIP provider.
 
There may be another rule that is being matched. I dont recognise the 1st prompt but the 2nd one is a 3CX prompt. That prompt is what you would usually get if there is no matching rule.

3CX always does a 1st matching on its rules, so a rule may need to be moved up to take effect.
 

Forum statistics

Threads
111,969
Messages
590,041
Members
164,880
Latest member
bperry11