Internal Caller ID Issue Bridge

[Rhys Haskell]

Hi,

We have an issue with caller ID on internal calls over a bridge on mobile apps.

If we have system A and system B that both have extentions 201 on them, using 9 as the bridge prefix for example.

If a user on system A dials 7201 to dial system B it will intermitantily show the caller name of 201 on system A.

We have tried to add the extentions into the local phone book with the prefix on both system, and all users have presence sharing enabled.

Has anyone come across this before?

 

[JohnS_3CX]

Hi Rhys,

You mention 9 as a prefix example but then you dial 7 in the next sentence.

Try the following:

1. Edit both bridges and set the rule prefix there to 9


2. Make sure you haven't modified the Advanced tab



2. Edit the Outbound Rule for the bridge on both PBXs and set the prefix, then strip that digit


Double check the rules to make sure there are no duplicates.

There is no need to add them in the phonebook, those can be removed now.

 

[Rhys Haskell]

Hi Rhys,

You mention 9 as a prefix example but then you dial 7 in the next sentence.

Try the following:

1. Edit both bridges and set the rule prefix there to 9
View attachment 36645

2. Make sure you haven't modified the Advanced tab
View attachment 36647


2. Edit the Outbound Rule for the bridge on both PBXs and set the prefix, then strip that digit
View attachment 36646

Double check the rules to make sure there are no duplicates.

There is no need to add them in the phonebook, those can be removed now.

Hi, Sorry they are both using a 7 that was a typo. The customer has a few bridges setup and it is happening to all of them but not all the time and with no real pattern. The outbound rules are setup as per the below.

 

[JohnS_3CX]

Hi Rhys,

Can you please tell us the exact version number their PBXs are running?

And also whether this is noticed on Android, iOS or both apps when it happens?

 

[Rhys Haskell]

Hi Rhys,

Can you please tell us the exact version number their PBXs are running?

And also whether this is noticed on Android, iOS or both apps when it happens?

Hi,

All PBX's are running 18.0 (Build 312).

It has only been noticed on iPhones but that is what all users use, I will do some more testing on Android to confirm this.

 

[Rhys Haskell]

Hi Rhys,

Can you please tell us the exact version number their PBXs are running?

And also whether this is noticed on Android, iOS or both apps when it happens?

Hi John,

I have been unable to replicate on Android although it does only happen intermittently so not 100% sure the issue isn't there on Android.

 

[JohnS_3CX]

Thank you Rhys, we are also able to replicate this under certain conditions, I think we have what we need now.

This will probably get fixed in a later release of the app.