Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Problems with Mediant 1000B and Avaya Setup

Status
Not open for further replies.

PBXTOM24

IS-IT--Management
Sep 26, 2015
16
US
We are trying to set up a Mediant 1000B Gateway with our PBX that will be used further down the line for IVR.
We have an existing 1-877 number and its DNIS on another trunk that we want to use to get to the Mediant Gateway.
I setup the DS1 that is connected to the Gateway via a T1 Crossover as Signaling ISDN-PRI and QSIG.
I created the Signaling Group for the D Channel and the D Channel Alarm on the Mediant changed to Green.

I also created a Test Agent Login, Station Type DS1FD Tied to the DS1 Port where the Mediant is tied to and Hunt-Group for the IVR

The third party working on the Mediant Gateway Side said they need a DID# to tie down the Mediant Gateway and am not sure how to proceed.
How do we get the DNIS-VDN to that card and to them?



 
Are they just looking for a pilot number to get to the Mediant? Just use a DID with Uniform Dial Plan, that should do the trick to get the call over to the M1K PRI.

 
Thanks.
I guess I am confused on how the number would get to the Mediant though.
Would I tie the DID to one of the ports on the DS1 where the Mediant T1 Crossover is connected?

 
If you have a DID 555-666-1234 terminating on your PRI, and that PRI hits your Avaya, you could create a UDP entry for 666-1234 that just reroutes over AAR to the Mediant 1K PRI. The DNIS would then get passed to the Mediant for routing.



 
Ok, that makes sense, thanks for the help
 
Randy, I had one more question.
Does the DS1 Board where the Mediant is plugged in need to be on the destination trunk group where I am routing the DID Number?

As it is right now, the DS1 Board is not part of any trunk group and only has a signal group attached.
 
yes

uniform dial plan -> aar -> route pattern -> M1K Trunk should be in the route pattern

 
Thanks Randy
Almost there now

I created the trunk group and ran a test call with the dnis and heard the auto operator on the Mediant.
The problem is that I can't get to it when dialing the 1-877-XXX-XXXX number, I get a busy signal.

The dnis 2437 comes in two other trunks and is routed via UDP and AAR to Trunk Group 16 as below.
I have to dial the FAC for AAR to make it work as well.

change uniform-dialplan 2 Page 1 of 2

UNIFORM DIAL PLAN TABLE
Percent Full: 0

Matching Insert Node
Pattern Len Del Digits Net Conv Num
2437 4 0 aar n



change aar analysis 2 Page 1 of 2
AAR DIGIT ANALYSIS TABLE
Location: all Percent Full: 4

Dialed Total Route Call Node ANI
String Min Max Pattern Type Num Reqd
2 7 7 p12 aar n
2437 4 4 16 aar n
3 7 7 p12 aar n
4 7 7 p12 aar n
5 7 7 p12 aar n
5151 4 4 70 unku n
6 7 7 p12 aar n
7 7 7 p12 aar n
8 7 7 p12 aar n
9 7 7 p12 aar n




Any ideas?
Thanks




 
Does your toll free have the same DNIS as the DID that you said worked? If not, then you'll probably want to adjust it on incoming call handling treatment forms. You can identify the DNIS by doing a list tra tac on the trunk.

 
Thanks Randy.

The Trunk Incoming Treatment Table is empty.
I created a station 2437, and dialed the 1-877 number and it rang the phone.
I got around the issue though by creating a vdn and vector pointing to route to the AAR FAC + 2437 and it works now.
The third party on the Mediant side said they are unable to see the caller - unknown name and number shown.

Send Connected Numbers, Send Name and Send Calling number on trunk group type ISDN, Service Type Tie are set to Yes.

The Signal and Trunk Groups have the Supplementary Service Protocol set to A and am doing some digging around to see if it should be set to b.

Any help is much a appreciated
Thanks
 
Do a list trace and see if your trunk is sending the caller ID or not. If it is, then you should probably take a deeper look at the Mediant. Also, you probably need National 2 or QSIG for names (someone correct me if I'm wrong)

 
We have caller ID now and everything is working correctly
Thanks Again
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top