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

ISDN E1 ETSI - No Caller ID Name showing?

Status
Not open for further replies.

ahorner

Programmer
Sep 5, 2023
28
GB
Hi there,

I have an IPO500 set up with a PRI line. I control both ends of this line, with the network end being a Cisco 2811 ISR.

Calls incoming and outgoing are working perfectly fine and as expected, however incoming calls do not display the upstream Caller ID Name, only the caller's number.

I have monitored the incoming call with the System Monitor and I can see that indeed, the Caller ID Name (DECT Test Line) is being passed down the line to the Avaya system, however it is being completely ignored, as can be seen on this truncated log:

[tt]
4422241mS ISDNL3Evt: v=13 stacknum=13 State, new=Present, old=NullState id=10
4422242mS CMLineRx: v=13
CMSetup
Line: type=Q931Line 13 Call: lid=13 id=10 in=1
Called[2565121] Type=Unknown (0) Reason=CMDRdirect Calling[2565125] Type=Unknown Plan=ISDN Pres=Allowed (0)
BC: CMTC=Speech CMTM=Circuit CMTR=64 CMST=Default CMU1=ALaw
BChan: slot=0 chan=1
Display [DECT Test Line]

...

4422251mS CD: CALL: 13.10.1 BState=Ringing Cut=1 Music=2.0 Aend="Line 13" (7.2) Bend="Deskphones(9000)" [] (0.0) CalledNum=9000 (Deskphones) CallingNum=2565125 () Internal=0 Time=8 AState=Ringing
[/tt]

Configuring both ends for QSIG fixes the issue, but is a major change with unwanted implications (the fact Incoming Call Routes do not work so I'd have to use Shortcodes instead). SIP trunks also work perfectly fine.

Is there anything I can configure on either end of this line to allow the Avaya to correctly interpret the caller as 2565125 DECT Test Line instead of just the numeric representation?

Many thanks in advance!
 
E1 as ETSI does not transport any NAME but just the caller ID number so is correct that the IPO ignore that information, viceversa Qsig does but you need networking licenses and define if Qsig A or Qsig B
 
Thanks for the reply IamaSherpa,

Seems to annoying that we're so close to having that information on phone displays, showing up in monitor logs, but unable to use it. I suppose there's no fancy tricks I can do to retrieve that data and place it into the caller ID name field at all?

Thanks!
 
All credit goes to Shaun_E for this one. Been talking to him and we have worked out a solution. This does not work with E1 ETSI though, so sadly if you need E1 you'll still need to go QSIG.

We switched the Cisco ISR side to T1, with [tt]isdn switch-type primary-dms100[/tt] and switched the PRI trunk line to T1 too. This does mean we have to use u-law for incoming and outgoing calls on this trunk, but luckily despite this being an a-law system, it does u-law perfectly fine on the trunk. Caller ID Name comes in fine!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top