bandwidth.com ENUM (E.164)

[m***@mattkeys.net]

I can't seem to get sipxecs to pass along a "+" as a ENUM prefix. I've entered "e164.org" in the base domain, and + in the add prefix, when I click Apply, OK, then restart the SIP Registrar and double check the setting afterwards the + is removed. Bandwidth.com sets this by default, as they describe in the provisioning email :

* Inbound and Outbound Numbers can be formatted in the following formats:

**E.164 format
Local / Long Distance calls (+1 then 10 digits)
Example: [phone]

**10 digit dialing
Local/Long Distance calls (10 digits)
Example: 2125551212
*******************************************************************
PLEASE NOTE: E.164 is the default format; you must notify your Installation Specialist if you wish to use a different format.
*******************************************************************
International calls (+ country code - city code - numbers)
Example: [phone]
**Note: If set for 10 digit outbound then can send 011 instead of just the + for international dialing

Any suggestions on that? On a related note, the default "ot.bandwidth.com" in the bandwidth.com template is invalid :

$ nslookup
> server 8.8.8.8
Default server: 8.8.8.8
Address: 8.8.8.8#53
> ot.bandwidth.com
Server: 8.8.8.8
Address: 8.8.8.8#53

Non-authoritative answer:
*** Can't find ot.bandwidth.com: No answer

I had to use their primary and secondary IPs provided as two separate gateways, and also entered the port number and protocol.

[Tony Graziano]

You would do this in the dial plan. I've always been able to send a + using
a basic dial plan entry.
On Jun 27, 2012 7:06 AM, "***@mattkeys.net" <***@mattkeys.net> wrote:

> I can't seem to get sipxecs to pass along a "+" as a ENUM prefix. I've
> entered "e164.org" in the base domain, and + in the add prefix, when I
> click Apply, OK, then restart the SIP Registrar and double check the
> setting afterwards the + is removed. Bandwidth.com sets this by default, as
> they describe in the provisioning email :****
>
> ** **
>
> *• Inbound and Outbound Numbers can be formatted in the following
> formats: **
>
> **E.164 format
> Local / Long Distance calls (+1 then 10 digits)
> Example: [phone]
>
> **10 digit dialing
> Local/Long Distance calls (10 digits)
> Example: 2125551212
> *******************************************************************
> PLEASE NOTE: E.164 is the default format; you must notify your
> Installation Specialist if you wish to use a different format.
> *******************************************************************
> International calls (+ country code - city code - numbers)
> Example: [phone]
> **Note: If set for 10 digit outbound then can send 011 instead of just the
> + for international dialing *
>
> ** **
>
> Any suggestions on that? On a related note, the default "ot.bandwidth.com"
> in the bandwidth.com template is invalid :****
>
> ** **
>
> $ nslookup****
>
> > server 8.8.8.8****
>
> Default server: 8.8.8.8****
>
> Address: 8.8.8.8#53****
>
> > ot.bandwidth.com****
>
> Server: 8.8.8.8****
>
> Address: 8.8.8.8#53****
>
> ** **
>
> Non-authoritative answer:****
>
> *** Can't find ot.bandwidth.com: No answer****
>
> ** **
>
> I had to use their primary and secondary IPs provided as two separate
> gateways, and also entered the port number and protocol.****
>
> ** **
>
> _______________________________________________
> sipx-users mailing list
> sipx-***@list.sipfoundry.org
> List Archive: http://list.sipfoundry.org/archive/sipx-users/
>

--
LAN/Telephony/Security and Control Systems Helpdesk:
Telephone: [phone]
sip: ***@voice.myitdepartment.net

Helpdesk Customers: http://myhelp.myitdepartment.net
Blog: http://blog.myitdepartment.net

[m***@mattkeys.net]

Thanks Tony. I'm working with a nice tech at bandwidth.com. He disabled the E.164 requirement for 10 digit dialing and I tested this morning. On a 10 digit test call trace and using 9 as the pstn prefix (e.g. 91234567890), it was passing along the 9 prefix to the itsp. Once I changed the prefix to optional, it's passing along 1234567890 and then changing it at the sipXbridge to a long distance (1 prefix, e.g. 11234567890), which gets rejected because it's not E.164 format. My question is, how does the dial plan under Systems -> Dial Plan interact with the prefix requirement in Devices -> Gateways -> <provider> -> Dial Plans? Also, can you give an example of how you would emulate the E.164 inside a dial plan?

Thanks,
Matt

________________________________
From: sipx-users-***@list.sipfoundry.org [sipx-users-***@list.sipfoundry.org] On Behalf Of Tony Graziano [***@myitdepartment.net]
Sent: Wednesday, June 27, 2012 7:59 AM
To: Discussion list for users of sipXecs software
Subject: Re: [sipx-users] bandwidth.com ENUM (E.164)


You would do this in the dial plan. I've always been able to send a + using a basic dial plan entry.

On Jun 27, 2012 7:06 AM, "***@mattkeys.net<mailto:***@mattkeys.net>" <***@mattkeys.net<mailto:***@mattkeys.net>> wrote:
I can't seem to get sipxecs to pass along a "+" as a ENUM prefix. I've entered "e164.org<http://e164.org>" in the base domain, and + in the add prefix, when I click Apply, OK, then restart the SIP Registrar and double check the setting afterwards the + is removed. Bandwidth.com sets this by default, as they describe in the provisioning email :

• Inbound and Outbound Numbers can be formatted in the following formats:

**E.164 format
Local / Long Distance calls (+1 then 10 digits)
Example: [phone]

**10 digit dialing
Local/Long Distance calls (10 digits)
Example: 2125551212
*******************************************************************
PLEASE NOTE: E.164 is the default format; you must notify your Installation Specialist if you wish to use a different format.
*******************************************************************
International calls (+ country code - city code - numbers)
Example: [phone]
**Note: If set for 10 digit outbound then can send 011 instead of just the + for international dialing

Any suggestions on that? On a related note, the default "ot.bandwidth.com<http://ot.bandwidth.com>" in the bandwidth.com<http://bandwidth.com> template is invalid :

$ nslookup
> server 8.8.8.8
Default server: 8.8.8.8
Address: 8.8.8.8#53
> ot.bandwidth.com<http://ot.bandwidth.com>
Server: 8.8.8.8
Address: 8.8.8.8#53

Non-authoritative answer:
*** Can't find ot.bandwidth.com<http://ot.bandwidth.com>: No answer

I had to use their primary and secondary IPs provided as two separate gateways, and also entered the port number and protocol.


_______________________________________________
sipx-users mailing list
sipx-***@list.sipfoundry.org<mailto:sipx-***@list.sipfoundry.org>
List Archive: http://list.sipfoundry.org/archive/sipx-users/

LAN/Telephony/Security and Control Systems Helpdesk:
Telephone: [phone]
sip: ***@voice.myitdepartment.net<mailto:***@voice.myitdepartment.net>

Helpdesk Customers: http://myhelp.myitdepartment.net
Blog: http://blog.myitdepartment.net

[Tony Graziano]

I use 3 dialplan entires on the system. I dont use the default plans.


Local
Long distance
911

Dial seven digits and prepend +1 and the local area code
Dial 10 and prepend +1
etc.
On 6/28/12, ***@mattkeys.net <***@mattkeys.net> wrote:
> Thanks Tony. I'm working with a nice tech at bandwidth.com. He disabled the
> E.164 requirement for 10 digit dialing and I tested this morning. On a 10
> digit test call trace and using 9 as the pstn prefix (e.g. 91234567890), it
> was passing along the 9 prefix to the itsp. Once I changed the prefix to
> optional, it's passing along 1234567890 and then changing it at the
> sipXbridge to a long distance (1 prefix, e.g. 11234567890), which gets
> rejected because it's not E.164 format. My question is, how does the dial
> plan under Systems -> Dial Plan interact with the prefix requirement in
> Devices -> Gateways -> <provider> -> Dial Plans? Also, can you give an
> example of how you would emulate the E.164 inside a dial plan?
>
> Thanks,
> Matt
>
> ________________________________
> From: sipx-users-***@list.sipfoundry.org
> [sipx-users-***@list.sipfoundry.org] On Behalf Of Tony Graziano
> [***@myitdepartment.net]
> Sent: Wednesday, June 27, 2012 7:59 AM
> To: Discussion list for users of sipXecs software
> Subject: Re: [sipx-users] bandwidth.com ENUM (E.164)
>
>
> You would do this in the dial plan. I've always been able to send a + using
> a basic dial plan entry.
>
> On Jun 27, 2012 7:06 AM, "***@mattkeys.net<mailto:***@mattkeys.net>"
> <***@mattkeys.net<mailto:***@mattkeys.net>> wrote:
> I can't seem to get sipxecs to pass along a "+" as a ENUM prefix. I've
> entered "e164.org<http://e164.org>" in the base domain, and + in the add
> prefix, when I click Apply, OK, then restart the SIP Registrar and double
> check the setting afterwards the + is removed. Bandwidth.com sets this by
> default, as they describe in the provisioning email :
>
> • Inbound and Outbound Numbers can be formatted in the following formats:
>
> **E.164 format
> Local / Long Distance calls (+1 then 10 digits)
> Example: [phone]
>
> **10 digit dialing
> Local/Long Distance calls (10 digits)
> Example: 2125551212
> *******************************************************************
> PLEASE NOTE: E.164 is the default format; you must notify your Installation
> Specialist if you wish to use a different format.
> *******************************************************************
> International calls (+ country code - city code - numbers)
> Example: [phone]
> **Note: If set for 10 digit outbound then can send 011 instead of just the +
> for international dialing
>
> Any suggestions on that? On a related note, the default
> "ot.bandwidth.com<http://ot.bandwidth.com>" in the
> bandwidth.com<http://bandwidth.com> template is invalid :
>
> $ nslookup
>> server 8.8.8.8
> Default server: 8.8.8.8
> Address: 8.8.8.8#53
>> ot.bandwidth.com<http://ot.bandwidth.com>
> Server: 8.8.8.8
> Address: 8.8.8.8#53
>
> Non-authoritative answer:
> *** Can't find ot.bandwidth.com<http://ot.bandwidth.com>: No answer
>
> I had to use their primary and secondary IPs provided as two separate
> gateways, and also entered the port number and protocol.
>
>
> _______________________________________________
> sipx-users mailing list
> sipx-***@list.sipfoundry.org<mailto:sipx-***@list.sipfoundry.org>
> List Archive: http://list.sipfoundry.org/archive/sipx-users/
>
> LAN/Telephony/Security and Control Systems Helpdesk:
> Telephone: [phone]
> sip:
> ***@voice.myitdepartment.net<mailto:***@voice.myitdepartment.net>
>
> Helpdesk Customers: http://myhelp.myitdepartment.net
> Blog: http://blog.myitdepartment.net
>


--
~~~~~~~~~~~~~~~~~~
Tony Graziano, Manager
Telephone: [phone]
sip: ***@voice.myitdepartment.net
Fax: [phone]
~~~~~~~~~~~~~~~~~~
Linked-In Profile:
http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4
Ask about our Internet Fax services!
~~~~~~~~~~~~~~~~~~

Using or developing for sipXecs from SIPFoundry? Ask me about sipX-CoLab
2013! <http://sipxcolab2013.eventbrite.com/?discount=tony2013%22>

--
LAN/Telephony/Security and Control Systems Helpdesk:
Telephone: [phone]
sip: ***@voice.myitdepartment.net

Helpdesk Customers: http://myhelp.myitdepartment.net
Blog: http://blog.myitdepartment.net

[m***@mattkeys.net]

Thanks again Tony, that works much better!

________________________________________
From: sipx-users-***@list.sipfoundry.org [sipx-users-***@list.sipfoundry.org] On Behalf Of Tony Graziano [***@myitdepartment.net]
Sent: Thursday, June 28, 2012 8:23 AM
To: Discussion list for users of sipXecs software
Subject: Re: [sipx-users] bandwidth.com ENUM (E.164)

I use 3 dialplan entires on the system. I dont use the default plans.


Local
Long distance
911

Dial seven digits and prepend +1 and the local area code
Dial 10 and prepend +1
etc.
On 6/28/12, ***@mattkeys.net <***@mattkeys.net> wrote:
> Thanks Tony. I'm working with a nice tech at bandwidth.com. He disabled the
> E.164 requirement for 10 digit dialing and I tested this morning. On a 10
> digit test call trace and using 9 as the pstn prefix (e.g. 91234567890), it
> was passing along the 9 prefix to the itsp. Once I changed the prefix to
> optional, it's passing along 1234567890 and then changing it at the
> sipXbridge to a long distance (1 prefix, e.g. 11234567890), which gets
> rejected because it's not E.164 format. My question is, how does the dial
> plan under Systems -> Dial Plan interact with the prefix requirement in
> Devices -> Gateways -> <provider> -> Dial Plans? Also, can you give an
> example of how you would emulate the E.164 inside a dial plan?
>
> Thanks,
> Matt
>
> ________________________________
> From: sipx-users-***@list.sipfoundry.org
> [sipx-users-***@list.sipfoundry.org] On Behalf Of Tony Graziano
> [***@myitdepartment.net]
> Sent: Wednesday, June 27, 2012 7:59 AM
> To: Discussion list for users of sipXecs software
> Subject: Re: [sipx-users] bandwidth.com ENUM (E.164)
>
>
> You would do this in the dial plan. I've always been able to send a + using
> a basic dial plan entry.
>
> On Jun 27, 2012 7:06 AM, "***@mattkeys.net<mailto:***@mattkeys.net>"
> <***@mattkeys.net<mailto:***@mattkeys.net>> wrote:
> I can't seem to get sipxecs to pass along a "+" as a ENUM prefix. I've
> entered "e164.org<http://e164.org>" in the base domain, and + in the add
> prefix, when I click Apply, OK, then restart the SIP Registrar and double
> check the setting afterwards the + is removed. Bandwidth.com sets this by
> default, as they describe in the provisioning email :
>
> • Inbound and Outbound Numbers can be formatted in the following formats:
>
> **E.164 format
> Local / Long Distance calls (+1 then 10 digits)
> Example: [phone]
>
> **10 digit dialing
> Local/Long Distance calls (10 digits)
> Example: 2125551212
> *******************************************************************
> PLEASE NOTE: E.164 is the default format; you must notify your Installation
> Specialist if you wish to use a different format.
> *******************************************************************
> International calls (+ country code - city code - numbers)
> Example: [phone]
> **Note: If set for 10 digit outbound then can send 011 instead of just the +
> for international dialing
>
> Any suggestions on that? On a related note, the default
> "ot.bandwidth.com<http://ot.bandwidth.com>" in the
> bandwidth.com<http://bandwidth.com> template is invalid :
>
> $ nslookup
>> server 8.8.8.8
> Default server: 8.8.8.8
> Address: 8.8.8.8#53
>> ot.bandwidth.com<http://ot.bandwidth.com>
> Server: 8.8.8.8
> Address: 8.8.8.8#53
>
> Non-authoritative answer:
> *** Can't find ot.bandwidth.com<http://ot.bandwidth.com>: No answer
>
> I had to use their primary and secondary IPs provided as two separate
> gateways, and also entered the port number and protocol.
>
>
> _______________________________________________
> sipx-users mailing list
> sipx-***@list.sipfoundry.org<mailto:sipx-***@list.sipfoundry.org>
> List Archive: http://list.sipfoundry.org/archive/sipx-users/
>
> LAN/Telephony/Security and Control Systems Helpdesk:
> Telephone: [phone]
> sip:
> ***@voice.myitdepartment.net<mailto:***@voice.myitdepartment.net>
>
> Helpdesk Customers: http://myhelp.myitdepartment.net
> Blog: http://blog.myitdepartment.net
>


--
~~~~~~~~~~~~~~~~~~
Tony Graziano, Manager
Telephone: [phone]
sip: ***@voice.myitdepartment.net
Fax: [phone]
~~~~~~~~~~~~~~~~~~
Linked-In Profile:
http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4
Ask about our Internet Fax services!
~~~~~~~~~~~~~~~~~~

Using or developing for sipXecs from SIPFoundry? Ask me about sipX-CoLab
2013! <http://sipxcolab2013.eventbrite.com/?discount=tony2013%22>

--
LAN/Telephony/Security and Control Systems Helpdesk:
Telephone: [phone]
sip: ***@voice.myitdepartment.net

Helpdesk Customers: http://myhelp.myitdepartment.net
Blog: http://blog.myitdepartment.net