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 strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Collaboration between two standalone Avaya Aura Core PBXs

Status
Not open for further replies.

dianvaguar

Technical User
Mar 28, 2005
10
KW
Dear Fellow Avaya Users,

We have a merger between two companies. Company-A and Coompany-B both has Avaya Core Systems. There is one department in Company-A decided to have sattelite offices in Company-B and they required to get their calls either of the two locations depending where they are at any moment.

The two companies were tied between SIP trunks and currently able to call each other via UDP-AAR routing which works perfectly with gate-opener codes. Company-A dials 1400+CompanyBExtensions while CompanyB dials 65+CompanyAExtensions.

We applying Off Station Mapping for both Company-A and Company-B extensions but it seems that we are getting loop calls because two extensions are pointing to each other. It doesn't work.

We tried coverage after certain rings for both sides but this is not an ideal solution because it takes time to respond to calls if not callers more likely be impatient to eventually disconnect the call. Do you have any other feature option to do solve this requirement? Thanks!
 
dianvaguar,
You are probably not going to want to hear this but in the long run it will make your life and troubleshooting issue much easier. We have two core switches. One in the States and one off shore and we don't use codes so to speak. We went to a 5 digit dial plan. Considering you have sip trunks between them you are already part of the way. Depending on how many DID's you have and yours is way more simpler than ours (all in the US no crazy 6 to 18 digits) you could put everything in company A as 1-4 and company B as 5-8. So extension in company A would start with 1xxxx set your AAR to route any call starting with 5 to a route pattern that points to the sip trunk and on the incoming call handling of that sip trunk on switch B to route the call. You could also add this in SMGR. Do the same for company B to route anything with a 1 to route to sip to company A. Start by building some test stations in both switches and test the back and forth. Then you can lay out the rest of your dialplan and implement over a weekend. You could also centralize your voicemail with the hunt group to a specific pilot number.
 
Dail plans are always fun. I suggest a full E.164 dial plan. For the US this is 1-xxx-xxx-xxxx. You can still dial 4 or 5 digits locally depending on how you configure the dial plan parameters, call type analysis, and UDP/AAR. The use of a prefix code is simple however as you have found out, it leads to loops.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top