3cx can not call a mobile phone

Status
Not open for further replies.

uniscanadmin

Customer
Joined
Mar 18, 2019
Messages
48
Reaction score
6
Good day.

Our LDAP uses mobile numbers like + 7-123-456-78-90.
So, after unloading this data from LDAP to 3cx and configuring the Forwarding Rules for mobile transfer as the "Forward to mobile" ... the function is not work

Those. 3cx does not understand the "-" sign, the PBX does not understand how to bypass this sign and just call the number +71234567890

What to do?
 
You need to add an outbound rule to strip + 7- and then prepend +7. It would also be worth checking with your VoIP provider if you need the + as most do not. If this was the case you would just prepend a 7.
 
Firs:
3CX for some reason cuts +7 without any rules
example
Outgoing number with 3cx PBX type +71234567890
converted to
1234567890
without any of my rules

Secondary:
I tried to test the outgoing number of the form
+71234567890 it works.

I tried to test the outgoing number of the form
+ 7-1234567890 it did not work.

I tried to test the outgoing number of the form
+ 7123-456-78-90 it work.

How can I make 3сx see number +7 in the rules?
How does 3cx handle the "-" sign?
 
Hi,

If you check your PBX logs you should be able to see whether your PBX sends it to the provider with the "-" signs and whether they reject the call, or if the call is not sent at all due to your outbound rules.

As for the +7 being removed, you can check your E164 Processing under settings.

To send the number to your provider without the dashes you can also use the Outbound Caller ID reformatting https://www.3cx.com/docs/cid-reformatting/
 
Ok I understood about E164 and Yes my provider support the "-" sign for a callerId parameter;
As for the "+ 7-", how to write outgoing rules for the first "-" sign?
 
If that is the case then you should be able to strip 1 digit and it should remove the - and allow the call to be reformatted as 1234567890. Ideally you would check with your SIP provider for a document of support number formats.

If they do support -1234567890 then you will need to look at your outbound rules and allow calls that start with a - and add an extra digit to the number length.

If the first scenario works it will defiantly be the simplest.
 
The problem is that 3cx doesn't work. Those. 3cx doesn't even try to call through the provider. This is a 3cx error, it does not understand the "-" sign and therefore the call is immediately disconnected without trying to connect to the provider PBX.

those. In the processing of 3cx gets the number of the form:
-123-456-78-90 and this number is not work
therefore for 3cx need to be a number of the form at least
123-456-78-90
 
how to write outgoing rules for the first "-" sign?
 
The PBX will send to the provider the number as long as it matches the outbound rule. If your provider supports dashes it will work. Below is a screenshot from a wireshark capture showing the PBX sending the number to the provider.
9898

So you need to either edit your numbers and delete dashes and spaces or create a more general outbound rule to handle these calls. You could only set the extension group as a criteria.

9899
 
Hi,
I have 3cx of 15.5 version.
The 3cx software does not send an INVITE to my provider because 3cx can not process number form -12345678.

Once again, this matter is not in the provider, 3cx does not even form an INVITE message.
 
Status
Not open for further replies.

Forum statistics

Threads
111,916
Messages
589,722
Members
164,787
Latest member
IWalter