We recently cut over long distance service from ECCI to AT&T. We connected to ECCI through a T1. We have ISDN from AT&T for local service. AT&T will handle our LD via the ISDN.
I checked AFRS and see that the NPC for long distance numbers is OPR 3, local calls are OPR 2. It was quicker to change AOPR than change all the entries in AFRS, so I set the route for OPR 3 to be the same as OPR 2.
My thought process was that this change would force all long distance number patterns out the same route local calls take. This only partially works. I can complete calls to some exchanges, but not all. Results also vary based on the type of phone used to place the call. I have a Cisco CME attached to the 2400 via a T1. If I dial 9-1-334-xxx-xxxx from the Cisco system, the call is completed. If I dial the same thing from a Dterm (STN) on the 2400 I get a "call cannot be completed" recording. I'm assuming it's got something to do with necessary digits or something in the route class data, but I'm grasping at straws. Any ideas?
I checked AFRS and see that the NPC for long distance numbers is OPR 3, local calls are OPR 2. It was quicker to change AOPR than change all the entries in AFRS, so I set the route for OPR 3 to be the same as OPR 2.
My thought process was that this change would force all long distance number patterns out the same route local calls take. This only partially works. I can complete calls to some exchanges, but not all. Results also vary based on the type of phone used to place the call. I have a Cisco CME attached to the 2400 via a T1. If I dial 9-1-334-xxx-xxxx from the Cisco system, the call is completed. If I dial the same thing from a Dterm (STN) on the 2400 I get a "call cannot be completed" recording. I'm assuming it's got something to do with necessary digits or something in the route class data, but I'm grasping at straws. Any ideas?