Avaya IP Office 500 connected to Meridian Option 11C over T1 trunk with incoming call issues

[johnkerr16]

Hello, I currently have an Ayava IP office 500 (Essentials) that communicates over a typical T1 trunk line (E&M Tie) to a Meridian Option 11C which is then connected out to the PSTN. Originally there was a Nortel BCM400 in place that has failed which was replaced by the Avaya IP Office 500 PBX. Have TCM8 cards in the Avaya PBX for the existing Nortel and another analog card for the Analog phones along with a PRI/T1 Daughter card. I have outgoing calls working fine over the T1 trunk line however incoming calls don't work. Any incoming calls for the Avaya PBX extensions get stopped right away and just go right to a dead tone (no ringing happens). All of the incoming call routes, extensions, users, etc. are set up for the extensions available on the Avaya PBX. Anything special required for the T1 trunk settings? Any large differences between the BCM400 and Avaya PBX in terms of how the Meridian trunk line should be set up to sent all of the calls for the Avaya PBX extensions over the T1 trunk? Does the meridian need something sent to it to know what extensions are available on the Avaya PBX? Any advice would be great, thanks.

 

[edayalfa]

Check your incoming call route?

E

 

[mforrence]

Use Monitor to determine what digits (if any) that the far end is sending. Also, you may not have the inbound signaling correct - the most common is wink-start. You could also configure a default incoming call route for the trunk, just to see if you can create any type of inbound call.

 

[johnkerr16]

It is a wink-wink type for the E&M TIE trunk. I did have the monitor software running and I wasn't seeing anything coming up when I got a co-worker to call me right back. I did do a "catch all" for the incoming call routes to have any calls come in to go right to the extension I was using and still didn't see anything on the monitor. There is easily a 500ms latency in calls due to the remote location. I did update some of the timers to match the meridian timers in the route data block that the trunk uses although due to the different brands they are not directly named the same so a bit of guess work went into it. I will start tweaking the timers on the trunk and see if that is the issue. Not easily to find information on what exactly each of the timers are for the Avaya IP Office to help correlate to the meridian timers. The couple Avaya IP Office manuals I have don't see to mention much about them.