gkludt

I recently moved an IP403 to a new location. It had two of the 4 port analog trunk cards and a digital 30 expansion unit. As part of the move, they upgraded to PRI T1 while still using one of the analog trunk cards. They also added DID numbers for all of their extensions (this was planned from the beginning and even matched up their 4 digit extensions to match their future DIDs during the initial install a year ago.)

Upon plugging in the PRI card, the DIDs were up and working in minutes... BUT, after much frustration and unsuccessful troubleshooting, we determined that configuring the incoming call routes for the DID numbers stopped the OUTGOING long distance calls from working. They would busy out instead. Removing the incoming call route clears the problem, but that defeats the purpose of DID for each user of course. We tried with just 4 digits in the incoming number, we tried specifying the entire 10 digits, all to no avail. Provider is sending us 4 digits. How this matters to OUTGOING calls is a mystery to me.

A call trace from monitor, a call/email of the config to Avaya , and some strange discussions with the T1 provider have not yet shed any light on this problem.

The user names were created with the extension number as follows: 1989 Cindy, 1949 Mark, etc.
Could those digits on the usernames be somehow messing up the outgoing calls? I will try renaming a user and see if it works, but other systems I programmed like this had no issues.

Has anyone else run into this issue? We are on 2.1.27 firmware now. The analog trunks work great no matter the incoming call route status. PRI is in slot B, analog trunk card in slot A. Thought about putting PRI in slot A but was unsure if I was just wasting energy by ripping the system apart (may provide needed relief from the H-E-L-L this particular system has provided me and the client. ) But I digress.

thanks for any help!

corhavelaar

Looks like the users sends their extension number out on the PRI as their CLI number wich may not be accepted by your provider.

By default if a incoming DID matches the targets extension number then IPO uses the DID number as this users personal CLI to outgoing calls, there you have your link between incoming and outgoing numbers.

Change your outgoing shortcode to surpress your outgoing CLI and see what happens.

Add a "W" at the end of the telephonenumber of the shortcode.

PBXtech.info

 

sjered

I tried entering the W after all of my dial short codes and the only result I got was that the Caller ID was reduced from 10 to 4 digits. Any idea why this block of Caller ID isn't working? Which short codes do I need to apply the W to? Please help