- Joined
- Dec 14, 2017
- Messages
- 54
- Reaction score
- 1
Hello,
Since a few weeks, or actually since we configured E164 Processing (we did this to be able to call our phone contacts through the 3CX iPhone client), we noticed that incoming calls would have a 0 appended. This is also the problem with missed calls.
When we go to 'Missed' on our SNOM devices and recall them, it will call to (Belgium): 0011 12 34 56 instead of 011 12 34 56.
This issue is on every client; Windows client, iPhone client, SNOM devices.
When we dial 0032 or +32 (Belgium, our location) the calls will pass through. The E164 works as intended.
I configured following settings at E164 Processing:
Outbound rules are not configured:
To give an example, this is what our call log looks like: *360525:unknown (0011360525)
I'm lost in space..


I tried stripping a digit but then it only dials 11 12 34 56, unless it's prefixed with +32 or 0032
It looks like it's some kind of incoming formatting? Not sure...
If anyone has any clue where to find this issue?
Thanks in advance!
Since a few weeks, or actually since we configured E164 Processing (we did this to be able to call our phone contacts through the 3CX iPhone client), we noticed that incoming calls would have a 0 appended. This is also the problem with missed calls.
When we go to 'Missed' on our SNOM devices and recall them, it will call to (Belgium): 0011 12 34 56 instead of 011 12 34 56.
This issue is on every client; Windows client, iPhone client, SNOM devices.
When we dial 0032 or +32 (Belgium, our location) the calls will pass through. The E164 works as intended.
I configured following settings at E164 Processing:
Outbound rules are not configured:
To give an example, this is what our call log looks like: *360525:unknown (0011360525)
I'm lost in space..
I tried stripping a digit but then it only dials 11 12 34 56, unless it's prefixed with +32 or 0032
It looks like it's some kind of incoming formatting? Not sure...
If anyone has any clue where to find this issue?
Thanks in advance!