Dialing Account Codes Manually is Failing

[jsjungle]

Here's my setup (north America, USA):

IP412 at main location on 2.1.27 firmware, connected to standard T1 with DID service.

IP403 at remote site on 3.0 firmware, connected to IP412 at the main location for trunking over an IP connection (point to point T1, using Cisco routers to connect and provide QoS). Enable Fast Start, Out of Band DTMF, Allow Direct Media Path, and Voice Networking are all checked in the VoIP line settings, and the others are not (recommended by Avaya).

IP412 has local carrier for voice traffic and LD carrier with account codes for dialing long distance.

When users at the remote 403 location attempt to place a long distance call, they dial the appropriate number (91xxxxxxxxxx) and get a dialtone (prompting them to enter their access code). Once the code is entered, they get an error message that says "sorry, your call cannot be completed as dialed." The LD dialing with codes was working fine prior to the upgrade, but now does not work. The LD carrier and codes are unchanged, as is the local carrier.

We can't understand why the 403 will not allow us to enter the LD codes. The main location is able to dial LD using the LD codes as always.



Please help!!!

 

[Morrack]

It might help to upgrade the 412 as well, so both sites are on the same firmware.

To analyze this I would suggest you run monitor after hours, turn off most of the items (ensure both Call items are ticked under the Call tab as well as Error and Print under the system tab), but tick all the items under the ISDN tab (I'm assuming here that you are using a PRI on the 412). Start monitor logging, place a test call from the 403, and post the results.



Peter Sherwood

Morrack Consulting

http://www.morrack.com