# Configuring Wazo to use E164 Dialing Mode **URL:** \ **Category:** English\ **Created:** [August 29, 2026, 4:45pm UTC](https://wazo-platform.discourse.group/t/configuring-wazo-to-use-e164-dialing-mode/1932 "2026-08-29T16:45:11Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Ramblin](https://yyz2.discourse-cdn.com/free1/user_avatar/wazo-platform.discourse.group/ramblin/32/34_2.png) [@Ramblin](https://wazo-platform.discourse.group/u/Ramblin)\ **Post date:** [August 29, 2026, 4:45pm UTC](https://wazo-platform.discourse.group/t/configuring-wazo-to-use-e164-dialing-mode/1932/1 "2026-08-29T16:45:11Z")
Can someone PLEASE help me configure Wazo to use E164 Dialing Mode configuration? I am on Wazo 26.08 and I use the web gui to configure my system so please provide web gui instructions if possible. If you cannot provide web gui instructions, any help is appreciated. I have just ported my phone to voip.ms and they use the E164 Dialing Mode (NOT the NANPA Dialing Mode). I have been able to successfully register my trunk/DID to voip.ms. The voip.ms portal shows the trunk as registered and “pjsip show registrations” show it registered at the Wazo server. The customer support people at voip.ms (who have been very helpful and professional but are not Wazo experts) have also confirmed that my registration settings are correct. But I cannot get the Outcall or Incall settings to work in Wazo. For Incoming calls: When I dial the number, the portal at voip.ms shows it reaching voip.ms but the person dialing hears an error message (depending on the carrier) something along the lines of “HB1 Your call cannot be completed as dialed” I have edited the settings at /etc/xivo/asterisk/xivo\_in\_callerid.conf to have North American processing be: [northamerican] comment = local number within North America - 10 digits, not including leading 1 - conbert to E164 callerid = \[1\]\d{2}[2-9]\d{2}\d{4}$ strip = add = +1 [northamerican2] comment = local number within North America - 10 digits, with leading 0 or 1 - convert to E164 callerid = \[2\][2-9]\d{2}[2-9]\d{2}\d{4}$ strip = 1 add = +1 [northamerican3] comment = local number within North America - 11 digits with leading +1 - do nothing; this is in E164 format callerid = ^+1[2-9]\d{2}[2-9]\d{2}\d{4}$ strip = add = I tried editing the incoming Extension settings at Call Management → Incalls → From External : +12125555555 (actual number used in my system but edited for security) I used to have just 2125555555 which had worked with the previous trunk provider (Vitelity) but not voip.ms (which I think actually does implement E164 fully) but Wazo would not let me include the + in the definition so I used 12125555555 but that did not work either. I have similar issues with Outgoing call setup but I wanted first to get incoming setup working and then get Outgoing working, so any help on the Incoming setup is GREATLY appreciated and I’ll come back for Outgoing later (unless you really feel generous and can help me with both. * * * 1. 2-9 2. 0-1 ---
**Author:** ![chuckl](https://avatars.discourse-cdn.com/v4/letter/c/0ea827/32.png) [@chuckl](https://wazo-platform.discourse.group/u/chuckl)\ **Post date:** [September 8, 2026, 3:49pm UTC](https://wazo-platform.discourse.group/t/configuring-wazo-to-use-e164-dialing-mode/1932/2 "2026-09-08T15:49:39Z")
I think you would need to provide asterisk logs of the dialplan trace of such an incoming call. You would need to connect (ssh) to the wazo server and look at the `/var/log/asterisk/full` log file. You can run a command such as `tail -f /var/log/asterisk/full > /tmp/incoming-voipms-call.log` before you perform the test call, then cancel the command (control + c on the command line), then extract the file `/tmp/incoming-voipms-call.log` to your machine (e.g. with `scp`) and upload it to your post in this thread. The dialplan generated for incalls does support `+`-prefixed numbers. You can check by running `wazo-confgen asterisk/extensions.conf` on the wazo server and searching for your incall context (look for contexts with suffix `from-extern` or similar). Here’s an example dialplan generated for incalls on a wazo sttack: ```auto [default-key-4wfgx-from-extern] exten = i,1,Playback(no-user-find) same = n,Hangup() exten = s,1,NoOp() same = n,GotoIf($[${CHANNEL(channeltype)} = PJSIP]?:not-pjsip) same = n,GotoIf($["${XIVO_DID_NEXT_EXTEN}" = ""]?:error-loop) same = n,Set(XIVO_DID_NEXT_EXTEN=${CUT(CUT(PJSIP_HEADER(read,To),@,1),:,2)}) same = n,Set(XIVO_FROM_S=1) same = n,Goto(default-key-4wfgx-from-extern,${XIVO_DID_NEXT_EXTEN},1) same = n(not-pjsip),NoOp() same = n,Log(ERROR, This s extension can only be used from a PJSIP channel) same = n,Hangup() same = n(error-loop),NoOp() same = n,Log(ERROR, Dialplan loop detected. Got PJSIP header To: ${PJSIP_HEADER(read,To)}) same = n,Hangup() exten = _+.,1,Goto(${EXTEN:1},1) include = ctx-charlescli-others-438cdb28-0b36-45c2-8b2f-86226e5b2696 include = ctx-charlescli-services-9cdf1412-fe45-4cf4-be34-2b3ce60092ff exten = 0000,1,Set(__WAZO_BASE_CONTEXT=${CONTEXT}) same = n,Set(__XIVO_BASE_EXTEN=${EXTEN}) same = n,GoSub(contextlib,entry-exten-context,1) same = n,Set(__WAZO_TENANT_UUID=54eb71f8-1f4b-4ae4-8730-638062fbe521) same = n,GotoIf(${XIVO_FROM_S}?:action) same = n,CELGenUserEvent(XIVO_FROM_S) same = n(action),GoSub(did,s,1(27,)) ... ``` The `...` indicates other extension blocks for each incall you create. The line `exten = _+.,1,Goto(${EXTEN:1},1)` ensures that the incoming caller id number can be prefixed by `+`, and that prefix is simply stripped to match the digit string you specified for your incall. What you could also try, is to change your in\_callerid config to actually _not_ add any `+` to the number, and strip any `+` present in the incoming number, since it is useless and does not provide any value to the call routing or the user receiving the call. Let’s note for the sake of being pedantic that the `+` in an international telephone number is a convention to indicate to an operator processing that dialstring that the `+` should be replaced by whatever international trunk dialing prefix is appropriate for the caller’s location: [List of international call prefixes - Wikipedia](https://en.wikipedia.org/wiki/List_of_international_call_prefixes) . So sending out a call with a `+` prefix is not “implementing e.164 fully”. e.164 specifies an international numbering plan, and does not specify that `+` should be used to indicate international numbers. That’s a convention that is accidental and only useful for dialing, not receiving a call. ---
**Author:** ![Ramblin](https://yyz2.discourse-cdn.com/free1/user_avatar/wazo-platform.discourse.group/ramblin/32/34_2.png) [@Ramblin](https://wazo-platform.discourse.group/u/Ramblin)\ **Post date:** [September 17, 2026, 8:11pm UTC](https://wazo-platform.discourse.group/t/configuring-wazo-to-use-e164-dialing-mode/1932/3 "2026-09-17T20:11:49Z")
@chuckl Thank you for your reply and, believe it or not, I am not ignoring you. It is just that I am not yet ready to benefit from your suggestions. I am still tryiung to get the trunk with the new provider to be recognized as an endpoint see [Add a trunk but no Endpoint shown](https://wazo-platform.discourse.group/t/add-a-trunk-but-no-endpoint-shown/1934) but so far, in spite of the fact that then new trunk is registered with the new provider and I have created Incall and Outbound routing using the new trunk, I do not see the trunk ahos as an endpoint so I cannot make outbound or take inbound calls using that trunk. Hopefully if I get that resolved, I can then benefit from your feedback above. ---
**Author:** ![chuckl](https://avatars.discourse-cdn.com/v4/letter/c/0ea827/32.png) [@chuckl](https://wazo-platform.discourse.group/u/chuckl)\ **Post date:** [September 22, 2026, 2:36pm UTC](https://wazo-platform.discourse.group/t/configuring-wazo-to-use-e164-dialing-mode/1932/4 "2026-09-22T14:36:14Z")
I responded to your other thread with some investigation advice. ---
**Author:** ![Ramblin](https://yyz2.discourse-cdn.com/free1/user_avatar/wazo-platform.discourse.group/ramblin/32/34_2.png) [@Ramblin](https://wazo-platform.discourse.group/u/Ramblin)\ **Post date:** [September 23, 2026, 10:24pm UTC](https://wazo-platform.discourse.group/t/configuring-wazo-to-use-e164-dialing-mode/1932/5 "2026-09-23T22:24:24Z")
Again, appreciate it Using tail -f /var/log/asterisk/full really helped while I was on the chat line with voip.ms support voip.ms wants to see a specific format for their outbound calls and I finally got that from them so put it into outcall extensions specifier and we are all good.