Skip to main content
Accessibility Resource Center Skip to main content
Have a phone you love? Get up to $500 when you bring your phone.
end of navigation menu
***Announcement: Welcome to the new Verizon Community! We have merged our Wireless and Fios Communities to bring you the best place to discuss any Verizon product or service, along with all things tech! We have many new features to discuss with you in the coming weeks, but first we want to make sure that all of you who have been active on either of our communities before are able to log in!

Please see the Announcement in the Announcement section under Information Hub.

Network Extender fails with E.164 "+1" in dialed number
cprail1
Newbie

As I travel extensively my contact list uses the E.164 prefix "+1" for my north American numbers. eg +1 xxx yyy zzzz  . Numbers dialed this way work fine on the Verizon network itself however when the same number is dialed from behind the Network Extender, i receive the error "sorry your number cannot be completed as dialed, switch number 30900-250 ."

 

However, when i manually enter the number as simply xxx yyy zzzz , it goes through fine.

 

This tells me that the Network Extender is not dealing with the +1 correctly, which means it is not following the E.164 standard.

 

Can anyone suggest a correction for this ?

 

I cannot simply remove the +1 as this is required when dialing back to the USA when traveling internationally.

 

Thank you, Peter

0 Likes
Re: Network Extender fails with E.164 "+1" in dialed number
AyaniB_VZW
Verizon Employee

Hi cprail1,

 

 

I apologize for the inconvenience.  Please PM your wireless number to ensure the correct features on the account.  I look forward to hearing from you soon.

 

 

Thank you for your contribution to our community forums,

0 Likes
Re: Network Extender fails with E.164 "+1" in dialed number
howieco
Newbie

I am also having the same issues.

0 Likes
Re: Network Extender fails with E.164 "+1" in dialed number
gentscji
Newbie

I was also having this issue but a reboot of my network extender appears to have resolved the problem for now.

0 Likes