Call is not allowed by system

[nml]

What does it mean when 3CX tells me call is not allowed by system when i dial inbound?

For example...

I dial in to my GXW from the PSTN. Occassionally, for no reason, 3cx will tell me "call is not allowed by system" and hang up on me, instead of going to the DR. What does this mean? What could cause it?

 

[mfm]

The pbx is rejecting it, can be for multiple reasons. The best place to start would be to look at the the server logs, if you could paste the logs of a failing call we might be able to identify where the problem is originating from,

 

[nml]

I havent been able to catch it in the act yet, but here is a good incoming call. Is there anything in here out of place?

This call comes in, then goes back out to the PSTN (this particular extension is designed to do that).

successful call (does this look OK?):

09:53:50.601 [CM503008]: Call(689): Call is terminated
09:53:49.882 [CM503007]: Call(689): Device joined: sip:[email protected]:5060;transport=udp
09:53:49.866 [CM505002]: Gateway:[The GXW] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Grandstream GXW4108 (HW 1.1, Ch:8) 1.3.1.6] PBX contact: [sip:[email protected]:5060;transport=udp]
09:53:48.257 [CM503008]: Call(688): Call is terminated
09:53:47.726 [CM503025]: Call(689): Calling PSTNline:2514578@(Ln.10008@The GXW)@[Dev:sip:[email protected]:5060;transport=udp]
09:53:47.679 [CM503004]: Call(689): Route 2: PSTNline:2514578@(Ln.10008@The GXW)@[Dev:sip:[email protected]:5060;transport=udp,Dev:sip:[email protected]:5064;transport=udp,Dev:sip:[email protected]:5068;transport=udp,Dev:sip:[email protected]:5070;transport=udp]
09:53:47.679 [CM503004]: Call(689): Route 1: PSTNline:2518304@(Ln.10008@The GXW)@[Dev:sip:[email protected]:5060;transport=udp,Dev:sip:[email protected]:5064;transport=udp,Dev:sip:[email protected]:5068;transport=udp,Dev:sip:[email protected]:5070;transport=udp]
09:53:47.663 [CM505002]: Gateway:[The GXW] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Grandstream GXW4108 (HW 1.1, Ch:1) 1.3.1.6] PBX contact: [sip:[email protected]:5060;transport=udp]
09:53:39.523 [CM503007]: Call(689): Device joined: sip:[email protected]:40600;rinstance=24ec46bc115de2f2
09:53:39.523 [CM503007]: Call(689): Device joined: sip:[email protected]:5062;transport=udp
09:53:39.304 [CM503025]: Call(689): Calling Ext:Ext.801@[Dev:sip:[email protected]:40600;rinstance=24ec46bc115de2f2]
09:53:39.288 [CM503004]: Call(689): Route 1: Ext:Ext.801@[Dev:sip:[email protected]:40600;rinstance=24ec46bc115de2f2]
09:53:39.273 [CM505002]: Gateway:[The GXW] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Grandstream GXW4108 (HW 1.1, Ch:1) 1.3.1.6] PBX contact: [sip:[email protected]:5060;transport=udp]
09:53:39.273 [CM503001]: Call(689): Incoming call from 2124721773@(Ln.10009@The GXW) to <sip:[email protected]:5060>

 

[tehama]

I have the same problem but I can replicate. If the system makes 2 outgoing call all incoming call get "call not allowed by system" and are dropped. on the Port/Trunk Status the inbound call pops up as an OUT call.
here is log:
16:28:58.859 [CM503019]: Call(887): Rejected! Line is 'Busy' because number of simultaneous calls per line 5305261234@(Ln.10021@GXW-4108 192.168.XXX.XXX) is limited by Administrator

 

[leejor]

I would think that this is either a licence restriction (number of concurrent calls), or, there is no outbound route for the call, all trunks busy?

 

[tehama]

Re: Call is not allowed by system (solved)

Figured it out. In 3cx set Maximum Simultaneous calls on each port to 4 or 8 depending on the Grandstream model. The grandstream is sending the next call sometimes on an already open channel. This is causing 3cx to error cause the max simultaneous call was set to 1. So far problem has gone away.

 

[sigma1]

Get ready for another problem...

All outbound calls using a GXW4104-4108 no matter what port you use to send it out (10000-10003), the GXW will use it's own port not the one that 3CX pre-selected. Result 3CX send a call out on 10000, GXW instead uses FXO port 4 (would be 10003), now while on the call, a real call comes in on FXO1 and 3CX received an invite for 10000, because you specified 1 call, it will ignore it.
The 4 concurrent calls is a temporary workaround to alleviate that issue. For now only Patton FXO work well. Known issue currently worked on.