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!

Avaya CM QSIG T1/PRI Ties to Siemens Hipath 4000 - A second call to the Avaya Station receives busy

Status
Not open for further replies.

exRolman

Technical User
Feb 12, 2007
11
Configuration: Avaya CM Rel 6.0 with QSIG T1/PRI Ties to an Siemens Hipath 4000
Issue: DID calls come in to Siemens and route over to Avaya to a station configured with 3 line appearances. First call shows up showing correct information on display, however if a second call comes into this station, the originating caller hears busy and the call does not ring the 2nd call appearance on the Avaya.
If we were to convert this Tie back to a NI2 Pri between the systems, then I can receive a second call on the Avaya phone ringing the 2nd call appearance.
I would like to have the ability to have a second call come into a available call appearance utilizing QSIG. Has anyone come across the same issue.

Would ultimatly rather have the Ties as QSIG, as I get both Name and Number on internal system Network calls.
 
I remember an Issue I had with QSIG and a Alcatel system. The symptoms are really close. The second call failed. We fixed it by changing the Trunk Hunt: cyclical entry on Page 2. On one system the trunk was changed to ascending and the other system was changed to descending. It can be tested quickly. It worth a test.

Hope this helps
ED

1a2 to ip I seen it all
 
Thank you for the information. I will give it a try. I saw in an earlier thread of yours back on the 6th of December you had an issue where you made a modification in the "Avaya system-parameters coverage-forwarding" where you changed "QSIG VALU Coverage Overrides QSIG Diversion with Rerouting? and set from a "n" to "y" and that fixed a problem for you. Were you having the same issue where you could not get a second call on a station with (3) call appearances in that instance?
 
The coverage-forwarding issue was calls going to voicemail. The calls would not follow coverage to the Voicemail hunt group. The also fixed an issue allowing tie line to tie line calls. Example: City A calls city B. Calls have to route through city c.


Example A <----> C <-----> B

Hope this makes sense?

ED

1a2 to ip I seen it all
 
Thank You, It does make sense.
We will make the modification you suggested earlier and try a few other parameters as well. Thanks again for the time and advise.
When I do get it working, I will post my modifications.
Regards,
 
Solution:
On Hipath 4000 Create your Tie Line as a QSIG type Tie. Same way you would configure it when connecting to a Cisco Call Manager.
On the Avaya Side, Create your Tie Line as a regular ISDN/PRI tie Line. (NI2 Protocol).
If you create your ties this way, then the Avaya Phones will see both the Caller ID Name and Number. As well, If you create it this way, when a 2nd call comes into an Avaya phone with (3) call appearances, then the 2nd call will go to an idle "Call apperarance" when the called phone is busy, then will follow to coverage path if ignored and Ring no answer.
If you were to create the Avaya side as QSIG as well, then your Avaya users will not be able to recieve a 2nd call, as well that 2nd call will not follow coverage.
A total fluke that we found this solution, but works great.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top