Long time listener, first time caller in the free edition. Having dealt exhaustively with v16/v18 the free Edition I set up for a single user is confusing me,
I set up a SIP trunk between Twilio and the 3CX Free for under 10 users.
The inbound number from Twilio rings the extension properly and voice is fine in both directions, however since many things changed in v20
Firstly I configured USA based outbound rules which I though made sense based on my prior experience.
Where
Calls to numbers starting with prefix "1" _ from extensions "Greyed out" with Calls to numbers with length of 9 Digits
Would satisfy 1212NPANXX pattern, I've assigned it to the Twillo SIP trunk and asked it to prepend + so the outbound number would look like +1212NPANXX
Upon dialing from the 3CX iPhone client I the outbound call from 3CX would not even get sent to twillo - Instead it would 3CX would tell me it's not a valid number or extension, seen in basic logs
as
There was no user or outbound rule found for the number 17188NPANXX that Ext.12345 dialed.
I added another rule to bypass this mechanism and have it respond to digits 123 - where the number would be re-written using outbound rules directly to my cellphone, and got the following error.
Device +123 dialed on (AnyLine@TWIL_IN) has reached max amount of calls - Call(from "Persons Name"<sip:[email protected]>;tag=REDACTED to +123)
Where TWIL_IN is the name of the sip trunk.
As this "free" edition is nothing I had experienced before logs did not tell me anything beyond that, as well as looking on Twilio's side it looks like this 3CX free instance did not even attempt to reach
Twillo, as the logs are blank on their side, even though both sides IP's are whitelisted, and incoming calls from for 1718NPANXX from Twilio arrive at the PBX perfectly and ring the 3CX Web Client as well as the 3CX iPhone client provisioned.
Am I missing something, I've never seen a message saying Max Amount of Calls had been reached, nor had trouble matching outbound rules in 3CX v16 and v18 prior.
I set up a SIP trunk between Twilio and the 3CX Free for under 10 users.
The inbound number from Twilio rings the extension properly and voice is fine in both directions, however since many things changed in v20
Firstly I configured USA based outbound rules which I though made sense based on my prior experience.
Where
Calls to numbers starting with prefix "1" _ from extensions "Greyed out" with Calls to numbers with length of 9 Digits
Would satisfy 1212NPANXX pattern, I've assigned it to the Twillo SIP trunk and asked it to prepend + so the outbound number would look like +1212NPANXX
Upon dialing from the 3CX iPhone client I the outbound call from 3CX would not even get sent to twillo - Instead it would 3CX would tell me it's not a valid number or extension, seen in basic logs
as
There was no user or outbound rule found for the number 17188NPANXX that Ext.12345 dialed.
I added another rule to bypass this mechanism and have it respond to digits 123 - where the number would be re-written using outbound rules directly to my cellphone, and got the following error.
Device +123 dialed on (AnyLine@TWIL_IN) has reached max amount of calls - Call(from "Persons Name"<sip:[email protected]>;tag=REDACTED to +123)
Where TWIL_IN is the name of the sip trunk.
As this "free" edition is nothing I had experienced before logs did not tell me anything beyond that, as well as looking on Twilio's side it looks like this 3CX free instance did not even attempt to reach
Twillo, as the logs are blank on their side, even though both sides IP's are whitelisted, and incoming calls from for 1718NPANXX from Twilio arrive at the PBX perfectly and ring the 3CX Web Client as well as the 3CX iPhone client provisioned.
Am I missing something, I've never seen a message saying Max Amount of Calls had been reached, nor had trouble matching outbound rules in 3CX v16 and v18 prior.
