Extension mobile number calling via bridge ends up in bridge prefix + mobile and fails

[Darkon91]

Hi guys,

is it normal that if you call a mobile number that is defined in an extension that it dials the bridge prefix + mobile number and fails as it does not find the number with the prefix in front?

Regards,
Christian

 

[craigreilly]

Check the E164 processing.
This was a very long time ago - but numbers from the bridge were being affected by this for one reason or another. I can not remember all the details.

maybe I read this wrong... do any of the outbound rules match calls to extension mobile numbers? Does it affect any mobile number - or only those in the extension setup?

 

[Darkon91]

Hi,
thanks for the reply.

I attached our outbound rules for the 3CX system I use personally at the moment.

We made a test with one bridge prefix so the prefix will be removed with the outbound rule but this is way to much work as we have about 10 3CX servers + several different combinations for mobile numbers like + or 00 or only 0 ...

The "Process E164 Numbers" does not sound like this has to do with the bridge prefix as it is for the +XX and not for the number in front of the + or do I mix up things?

Example:

I am at location 100 and try to call a number at location 180.
The person I'd like to call is listed in the Presence Information list in the 3CX client with his extension number 180xxx and with his mobile number 1800172xxx
Once I click on the mobile number it calls with the prefix in front.

If I search the contact in the presence list with the "Enter text to search" it lists the contact. After clicking on the right arrow it shows me the details of the contact and lists the nubmers as below:

You see? In there it lists the number as 0172xxxxx only, which can be called normally.

Most users use the search field above instead of the details, which of course is much easier than always clicking on details and then the detail number.

Creating 14x14x2 rules (or maybe more) is for sure no option I think ...

Do I have to tell all users to use the details and call the number that way?

Kind regards,
Christian

 

[craigreilly]

That just sounds like a bug then if you are selecting the number from a list and it’s calling via bridge. Unless 3CX assumes place the call over the bridge because it will be the cheapest route to use.
I haven’t had to deal with bridges in about 5 years. My apologies.
check outbound rules. Ensure bridge calls have a number of digits set.
(Edit- Oh I see now the bridge info is listed before the mobile number - It might be by design - cheapest route or a bug... I am not qualified to say)