Outbound rule "prepend" shows up in Windows client call history

[tdtech]

I found another thread reporting this issue a few years ago, but there was never any resolution. I have an outbound rule that prepends "1" to our 10 digit calls in the US, because our SIP provider needs it.

But that "1" shows up in the call history! So if the user dials 210-555-1212, it shows up in call history as 12105551212. The problem there is if they then try to double-click to call that number, there isn't an 11 digit rule so the call fails.

Obviously, this can be handled by setting up an 11 digit rule to just pass the call, but this really seems like a bad design choice...an outbound rule is a backend admin thing, so it shouldn't impact what shows up in history! That should only show what the user actually dialed!

Am I missing something, or is this still truly the way this operates?

 

[JohnS_3CX]

Hi @tdtech

1. What version is your PBX exactly
2. Where do you see the history? (management console, phone, webclient?)

 

[tdtech]

3CX version 16.0.3.676

The call history with the "1" prepended shows up in the web client and the windows client. The phone shows correctly (without the "1" prepended" because it is maintaining its own call history I assume.

 

[JohnS_3CX]

Thanks @tdtech

I was able to replicate this behavior and this is what happens:

1.) If the call is not answered by the other side, the logs will show what the user dialled

2.) If the call is answered, the logs will update and show the reformatted number (as sent to the provider)

We are aware of this issue and will plan to correct it in a future release, but I have no ETA as to when this will happen.