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

IPO Extensions Conflicts with 3rd Party PABX over H323 Trunk

Status
Not open for further replies.

Imran555

Technical User
Aug 4, 2014
90
SA
Hi Guys

We have IPO Installed with different Extension Numbering Plan and and its connected to Remote PABX (Cisco) Over H323 Trunk.
Now The Cisco Have Ext numbering from 1000,1100,1200,1300,1400,1500,1600,1700,1800,1900,2000,
and In Avaya we Config same numbering but for sure unique Extension Numbers,
we use short code in Avaya to send call to cisco example,
Code:1xxx
Feature:Dial
Number:1N
Line Group Id:10 ( 10 is H323 Trunk Line id)
so on for other numberings

Now the calls are going and incoming from both side,
But issue is we seen the error messages like ( This Conflict with 1xxx-Dial The Local Extension will override the Short code)

so any suggestions to avoid this conflict.

Thanks
 
Easy to fix! Don't have conflicting numberING ranges!

Other than that, you cold build smaller ranges of shoetcodes probably even down to the full 4 digits

Or not worry about the error, if the ipo didn't use the dial hierarchy that is does, this whole setup would not work.

Take Care

Matt
I have always wished that my computer would be as easy to use as my telephone.
My wish has come true. I no longer know how to use my telephone.
 
Use access codes to route calla in this access code you define h.323 line through which call will route to other pbx
system a and system b are connected via H.323 so system a dial access code to reach system b extension when system a user dials acces code route it to that H.323 which is connected to system b
 
As said, it's not an error message.
It's a warning message saying that you have extensions matching the shortcode range and if they are dialed it will hit a matching extension before trying the shortcode.

"Trying is the first step to failure..." - Homer
 
Why use the same numbering for both sides? I know you said you keep them unique but as you grow it will become harder to keep from creating conflicts. It is much simpler to have cisco on 1xxx range and IPO on 2xxx range. Then when you work with IPO, you don't have to decide if an extension is use on the Cisco side or vice versa. Every time I work with a system setup like this I find conflicts because it so easy to do.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top