sundance-communications.com/forum Forums Wiring - Telecom Carriers - Trunks & Services Telecom Service & Providers Verizon Call fwd

Are outbound calls being placed from these lines while the forwarding is activated? With some of our local customers being UNABLE to utilize their * button on their instruments for controlling their call forwarding, customer originated traces, etc.,: Our 5ESS will translate the first received digits "12" the same as an entered *, as long as the switch's digit analysis timeout expires after the 4th digit is dialed (no additional digits received). Just a long shot..if someone dials the digits "1272" or "1273" and waits, these digits would be translated in our 5ESS the same as a dialed *72 or *73, thus respectively activating or deactivating the line's call forwarding.

Mike, pm sent

Mike, that's one I forgot, the rotary equivalent of a TT "*".


That might be what's happening, a long shot, for sure, but certainly plausible. Thanks for reminding us.

I'm hopeful that we'll be able to help isolate this down some. I'm just thankful for the opportunity to offer some input that may help point to a possible cause. :thumb:

I thought it was 11, as in 1167 for *67...

Jeff,

It is 11, as in 1167 = *67, etc. here in the New at&t, formerly SBC, formerly Pacific Bell, formerly Pacific Telephone (wait... did I miss five other names??? lol) territory. I thought the "11" = "*" was universal too.

Anyone know differently?

You missed Pacific Telesis

Aside from the name silliness, "11" is interpreted by nearly every brand of switch, used by any service provider, as "*" for rotary-dial users. It is always possible to dial 72 and just wait four seconds for dial tone to return (4 second delay = #), then follow the rest of the activation procedures for all "star" codes.

In Mike's case, the "12" is probably custom due to a military facility with a possible dialing plan conflict where "11" was a legitimate code from a rotary phone.

Mike, I seem to recall that "11" on the 396 exchange was used for commercial long distance access before the 5E went in. It had something to do with the fact that Carolina Tel. still had a toll switch serving the fort that was crossbar. This caused a numbering plan conflict with AutoVON, but it's been a very long time.

You scare me, Ed! :bow: That was the same explanation I received as well! [Sidenote- We've since added three new exchanges, and access to the DSN has also changed. It was decided to leave the " 12 for * " dialing in place, instead of changing to "11".]

Update - I've recently spoken with Don (Rowlettdon), and there is a possiblilty that the type of dialing conflict mentioned in the 3rd paragraph of bf6b5yr's post may be impacting the activation of his customer's CFV feature. Don is currently working with his customer and the local provider to confirm this.

You may be refering to what we call "rex" (routine exerciser and other scheduled audits), which invoke automatic system, individual and ISDN line and trunk, protocol handler, office dependent data and memory, etc, diagnostics and backups during periods of minimal system activity.

Mike -

Do the new COs still do ROTL (Remote Office Trunk & Line?) Testing? This was a big part of our work that we mostly phased out when we went to T-Carrier. I was never really sure it was that good of an idea to get rid of it.

Sam