Webclient over Bridged PBX

[AWS2P]

Hi,
2 PBX bridged one cloud, other on premise, everything is working fine but with webclient only we are not able to let voicemal messages over the bridge, is it a limitation from webclient or a potential misconfiguration ?

it works if i use phone call from here and then on no answer it goes to voicemail (this is ok)

If i try to let voicemail using this menu
then call answer is (voicemail is disabled for this extension) of course it's not. and call is dropped.

have seen this menu is just trying to call local voicemail service on same pbx and not remote side as expected. The dialed number seen on screen from this menu is *43102 and change to 999 which is my VM number on local PBX

 

[paurus]

Yes, and so do I. Version 16.0.910 Pro.

 

[AWS2P]

Other thing i've noticed i use prefix 3 to use bridge both ways it works and in outbound rule i 've set to remove first digit but numbers displayed stay always with prefix , why this is not removed to keep only extensions numbers?

 

[AWS2P]

Hi, @JohnS_3CX

do you have some advice ? is there a bug? am i wrong somewhere?

 

[JohnS_3CX]

This button effectively dials *43102

But your outbound rules do not catch this to strip the 3 in front, so effectively you are dialling an extension number that does not exist.

So for example, if you don't use a prefix and both PBX systems had non-overlapping extension numbers, it would work.

 

[paurus]

So for example, if you don't use a prefix and both PBX systems had non-overlapping extension numbers, it would work.

That's not so. I don't use prefixes and both PBX have non-overlapping numbers. But I have the same problem.

 

[AWS2P]

in my case 2 pbx have same ranges of extensions this is why there's a prefix 3, in this case it's not possible to work ? or this is my bridge rule which is bad?

 

[JohnS_3CX]

That's not so. I don't use prefixes and both PBX have non-overlapping numbers. But I have the same problem.

You are indeed correct, I will explain below

 

[JohnS_3CX]

in my case 2 pbx have same ranges of extensions this is why there's a prefix 3, in this case it's not possible to work ? or this is my bridge rule which is bad?

I think this is just a technical limitation, allow me to explain better:

So *4 is reserved in the PBX to connect to the VM of any local extension.

When you press the webclient button and *43102 is dialled, the system strips the *4 and connects you to the VM server of your own PBX, requesting to speak with extension 3102's mailbox.

This extension 3102 does not exist locally on your side however, so hear the message that the mailbox is not enabled (which is technically true).

You noted that when calling 3102 directly, you do eventually reach their voicemail if they don't answer, but that is the voicemail server that lives on the other PBX. The button in the web client only addresses the VM server that lives on your PBX and responds to *4 locally, hence it will only work for extensions that exist on your own server.

Hope this was concise, let me know if you need any further clarification.

 

[AWS2P]

Thanks John for explainations, So this feature should be unavailable in webclient for remote extensions and stay available only for extensions on local PBX.

i use same 100 range of extensions on both PBX and prefix 3 is in bridge rule both side.
Is it normal numbers stay displayed with prefix3 even the rule ask to strip first digit?

 

[JohnS_3CX]

Yes this is normal because they belong to the other PBX and the users you see there come via presence, not the bridge-trunk itself.

The 3 is stripped during dialling when the rules are processed of course via your outbound rule.