Nortel - Cisco integration - called number not displayed (dashes)

[Barbarian7]

Hi.
we have an odd problem.
We have an option 81c on rel 25.30 with a couple of PRIs to Cisco router (2821) for integration with Call Manager (no Q.SIG. It is not an option for us). Locals on the cisco side are CDP'd on the 81c across these PRIs.

Everything works fine, except when a Nortel set calls a local on the Cisco side, it's display of that number (ie: the one I just dialled) gets dashed-out (------) as soon as the far end starts ringing. Funny thing is, the called *name* associated with that local *is* displayed fine... just the called number is blocked.

Called/calling name & number work fine with all other scenarios (nortel to nortel, cisco to nortel, etc)

I have done line-by-line comparisons of configs from other sites which do not have this problem (of DCH, BCH, RDB, etc and Cisco-side configs). Everything seems to be the same, yet...

Can anyone point me in the right direction or suggest other things to check?

Thanks,
Barbarian

 

[johnpoole]

post your rcap?

john poole
bellsouth business
columbia,sc

 

[Barbarian7]

RCAP on both D-channels is: ND2

 

[pacojonezl40]

Why is QSIG not an option?

 

[JcBWF]

What version of Cisco? In 5.1.x there are known issues with displaying e number from a tie trunk. I am at 25.4 and have the same issue. the Cisco VAR said that Cisco is working on the problem.

 

[Barbarian7]

So presumably you would have this same problem if your tie trunk was Cisco -to- Cisco ?

We are at:
System version: 5.1.1.2000-2
The plot thickens: the "known good" site I was comparing my configs to is at 4.1.3 sr5b.

Do you have any bug-IDs or anything I can throw at our local Cisco guys? (ie: the guys who have been "looking into this" for about 8 months now)

thanks,
b

 

[JcBWF]

Try this one for a start and I will keep looking:
CSCsh56063
Garbage characters in DisplayNameFromQ931DisplayIE on ip fone display
<B>Symptom:</B>
Call Terminating IP phone will display call originator's name and appended with random characters.

 

[Barbarian7]

Yes, the garbage characters is a known issue for us (Cisco was up front about that).

But there wasn't any mention that this might be linked to the ------ problem on the *calling* phone, though.

Thanks,
B

 

[johnpoole]

the only way mine works is qsig. if you monitor the d, are you sending names?

john poole
bellsouth business
columbia,sc

 

[Barbarian7]

John:
(D-channel monitoring does not show whether I am sending names or not)

The names are definitely coming across and appear on the Nortel sets OK... it's only the *called* number when a call is placed fron a nortel set to one on the Cisco side.

 

[JcBWF]

I did some checking and mine is doing the same thing. (More work for me - Oh well the users haven't complained yet.) I'll run by my NY rep and see what they say.

 

[Barbarian7]

Ooops -- sorry to be the bearer of bad news, JcBWF !

B

 

[Barbarian7]

JcBWF :
did you learn anything from your rep?

Thanks,
B

 

[JcBWF]

Totally forgot about it till now, but no he hasn't gotten back to me. I'll call and see what he's found out


Perfection is expected, Excellence is Tolerated

 

[phones1]

what protocal are you using? were using Euro Etsi & had similar issues with Call Man, then found a little drop down box on the Call Man regarding message formats for the protocal Cisco was trying as bloody usual to use a non std messaging format on an industry std protocal(Call Man was using advanced mess for cisco clustering) hope it helps!!!!!

Remember if it doesn't work hit it harder

Scott UK