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 gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Cisco - Avaya H.323 QSIG Tunneling
- Thread starter libellis
- Start date
I am also eager to hear a reply/suggestion to this question. I am currently running a hybrid Avaya/Cisco setup, utilizing a voice gateway(2811 with E1 card)connecting to a DS1 circuit pack. It works nicely for internal digit calling to other offices. However we are migrating to Cisco on a permanent level, and would like to utilize the UCM as the primary PBX for inbound digit manipulation(3500 DIDs over 4 exchanges same areacode), to pass to Avaya without the need for additional hardware till migration is complete.
Any input would be greatly appreciated.
Any input would be greatly appreciated.
- Thread starter
- #3
We're in the opposite situation. Avaya is the dominant system, but there remains a Cisco presence. We received a response from Avaya today saying that QSIG tunneling is not supported, but it's difficult to know if the answer is really correct without another source to corroborate.
As an alternative to tunneling QSIG, we're looking at the possibility of just an H.323 trunk, but we don't know all the features that are supported (we know some). We're not sure if such things as inbound Caller ID on the Avaya connected PRI's will be passed to the Cisco.
At this point, it seems more likely that we'll end up with tried and true QSIG over T1 (or E1) and bite the bullet on the extra hardware cost.
As an alternative to tunneling QSIG, we're looking at the possibility of just an H.323 trunk, but we don't know all the features that are supported (we know some). We're not sure if such things as inbound Caller ID on the Avaya connected PRI's will be passed to the Cisco.
At this point, it seems more likely that we'll end up with tried and true QSIG over T1 (or E1) and bite the bullet on the extra hardware cost.
What model of Avaya did you install, and what version. I am on an earlier version S8700, but might be able to do some testing on my side. Also you running pure IP or hybrid IP/Digital service(phones). Might be able to help, if I can.
Also, are Avaya and Cisco talking to each other now, and does Caller ID pass along on internal calls. If so, I can't see why Avaya wouldn't pass it along from the PRI's. Just need to digit manipulate the inbound DNIS to point to the trunk to Cisco via the UDP and AAR table. just need to make sure you add a few digits in the trunk inbound call handling tab(page 3).
As far as hardware goes, if you are over trunked, or can spare a few, and have the old PSTN gateways from Cisco that are not in use, could always recycle.
Just me 2 cents...
Side Question: What caused you to go Avaya from Cisco? I am an Avaya tech, and moving to Cisco cause that is the direction the powers that be want.
Also, are Avaya and Cisco talking to each other now, and does Caller ID pass along on internal calls. If so, I can't see why Avaya wouldn't pass it along from the PRI's. Just need to digit manipulate the inbound DNIS to point to the trunk to Cisco via the UDP and AAR table. just need to make sure you add a few digits in the trunk inbound call handling tab(page 3).
As far as hardware goes, if you are over trunked, or can spare a few, and have the old PSTN gateways from Cisco that are not in use, could always recycle.
Just me 2 cents...
Side Question: What caused you to go Avaya from Cisco? I am an Avaya tech, and moving to Cisco cause that is the direction the powers that be want.
- Thread starter
- #5
Avaya S8720 controllers running CM 4.0.1. Pure IP.
Cisco wasn't the dominant system, and it is installed in a relatively small Trading area. Avaya replaced (transition not yet fully completed) an older NEC system that is still connected to the Cisco via a T1 (all trunking is on the NEC except for some ringdown lines that are directly on the Cisco).
Since the NEC is scheduled to disappear, and to improve reliability and give some breathing space for Trading to decide what they ultimately want to have, the Avaya is to be connected to the Cisco instead, hence the original posting.
We can't run any quick tests at this time, although a test is being discussed. Any changes or experiments with the systems have to go through a vetting process - another story.
H.323 alone may support all the required functions, but if we determine that voice messaging through the Avaya is now needed, then it's likely that QSIG will be required, and without any hard evidence that it can be done between Avaya and Cisco over H.323, then it will end up over a T1.
As for why Avaya and not Cisco, or an upgrade to the NEC - it's a long story. There is no perfect system, and as a time goes by relative strengths and weaknesses change as well, so yesterday's decision can be today's headache.
Cisco wasn't the dominant system, and it is installed in a relatively small Trading area. Avaya replaced (transition not yet fully completed) an older NEC system that is still connected to the Cisco via a T1 (all trunking is on the NEC except for some ringdown lines that are directly on the Cisco).
Since the NEC is scheduled to disappear, and to improve reliability and give some breathing space for Trading to decide what they ultimately want to have, the Avaya is to be connected to the Cisco instead, hence the original posting.
We can't run any quick tests at this time, although a test is being discussed. Any changes or experiments with the systems have to go through a vetting process - another story.
H.323 alone may support all the required functions, but if we determine that voice messaging through the Avaya is now needed, then it's likely that QSIG will be required, and without any hard evidence that it can be done between Avaya and Cisco over H.323, then it will end up over a T1.
As for why Avaya and not Cisco, or an upgrade to the NEC - it's a long story. There is no perfect system, and as a time goes by relative strengths and weaknesses change as well, so yesterday's decision can be today's headache.
- Status
Similar threads
- Locked
- Question
- Locked
- Question