Odd routing thing

[usa2k]

In outbound routing, a bunch of bogus names seem to describe some shortcuts.
LVE-600855

Its been a while since I've set a route ... so I have not looked in a while.

[usa2k]

Its being looked at, just wondered if others saw such things?
I have 8 outbound routes, the most recent I just added.
255 (Or CLK for clock) routed to 6137451576
Its an NRC time clock in Ottawa Ontario - just seemed like a cool thing

[usa2k]

Looks like they cleaned up the bogus names in outbound routing.
One now ther that was not there before at least matches the number

1-800-555 TELL 611 8005558355 Forward

[patoka]

I tried setting my mom's number to 7 digits (we had an area code split and my fingers still don't want to dial her new code...) but all I got was a fast busy. I set 500 to forward and it works fine.

[usa2k]

7 digits likely conflicts with the normal 7 digit dial plan.
Glad you got a working compromise.

I actually believe 7 digit should work if you have the same first 3 digits of the 10.

[usa2k]

Now that I read the "area code split" part again, I wonder if VOIPo could designate the 7 digit dialing to the more popular side of the split?

[fisamo]

IMO, the ideal solutions would be either of the following:
1. Have the user's area code prepended to a 7-digit dial string (current behavior)
2. Allow the user to choose which area code is prepended (IIRC, Voicepulse offers this)

Option 2 should be enabled through vPanel, not solely via submission of a ticket. (Perhaps support could make the change to a provisioning file--only way to know is to ask.)

Obviously, the first option is by far the easiest to implement, but some people may appreciate being able to set the option.

[usa2k]

Settable is handy if you have a vacation place, and take the ATA there. Each location you end up at, you could update for 7 digit dialing prefix. I've not personally cared about 7 digit dialing, but Average Family may care, and assume things.