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

Send CLID from 9006.6 HICOM 300E with T1 PRI Tie Line (NI2) Protocol to An Avaya CM.

Status
Not open for further replies.

exRolman

Technical User
Feb 12, 2007
11
We have a Hicom 300E 9006.6 with a PRI (NI2) T1 Tie to an Avaya CM.
Issue: Can not seem to get the Caller ID (4 - digit extension number) from a 9006.6 user to pass over the PRI Tie and show on the Avaya called parties phone.
I know that this span will pass Caller ID to the Avaya, as when outside callers call a DID number on the Avaya, the DID trunks terminate in the 9006 and calls are routed to the Avaya over PRI Tie. It then shows the Nxx-xxx-xxxx caller ID on the Avaya display.
My Avaya extensions are set up in the DPLN of the 9006 Hicom PBX as a Route Number. (I am not utilizing any LDPLN entries)
My LROUT is defined with a LODR of Echo All / End, sending the callers to the trunk group via LROUT.

QSIG is not an option for me.
Is there some specific options in the LODR possibly that I may add to push the Caller ID (4-Digit extension number is fine) to the other phone system?
I have the same issue when I provide PRI Ties to "Mitel", Cisco as well..

Any Ideas would be appreciated. Thank You
 
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.
 
In the first post you said the PBX in question was a 9006.6 version Hicom. In the solution post you state it's a Hipath 4K. I am a bit confused?
 
You are correct Kevin906.
When I first posted this thread. I was trying to find a solution to Pass Caller ID from a Telco DID call that initiates from the 9006.6 Hicom and then sent via a Route to the Avaya G450 CM across a Regular ISDN PRI (NI2 Protocol). I neved did find a solution for this. so......

Fortunatly in this network I have (2) Cornet Spans between the Hicom 9006 and a Hipath 4000 as well. so......

I installed a DIU2-M T1 card in the Hipath 4000 and a T1 Card in my Avaya G450 as well. I decided to force all Telco incoming DID calls that come into my 9006.6 Hicom across Cornet, thus forcing the Caller ID and Name due to the Cornet Protocol over to the Hipath, then following a Route to the Avaya and passing the Caller ID and Name once more.

Result: Incoming calls from Telco I now force through the Hipath 4000 and then across my new QSIG / Non-QSIG Pri Span to the Avaya as described above. For all "Outbound" calls from the Avaya, I continue to utilize my original PRI (NI2) span that connects directly to the Hicom 9006 system and then out to the PSTN Provider "Century Link" in this case.

Ends up being a good work around for us. The 9006.6 has limitations on sending Caller ID and Name across a ISDN Pri. Yet, when sent across Cornet it performs the magic of retaining the Name and Number to the next system as Cornet was designed to make Siemens Networked systems transparant.
 
Thanks for the clarification. This may come in handy at some point.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top