CME Caller ID Name PRI

Unanswered Question
May 10th, 2007

Hello --

I have a CME with a new PRI. The Q931 Debug shows all of the caller-id name information; however, the name is not being displayed on the phones, only the number.

Is there anything I can do to bring the name to the phone?

Thanks.

Ohamien

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 3.5 (3 ratings)
Loading.
Paolo Bevilacqua Thu, 05/10/2007 - 12:12

That is strange. What switch type ? In which facility is the name encoded (see debug) ?

ouhakheme Thu, 05/10/2007 - 12:18

Facility i = 0x9F8B0100A10F02010106072A8648CE1500040A0100

Protocol Profile = Networking Extensions

0xA10F02010106072A8648CE1500040A0100

Component = Invoke component

Invoke Id = 1

Operation = InformationFollowing (calling_name)

Name information in subsequent FACILITY message

Progress Ind i = 0x8283 - Origination address is non-ISDN

Calling Party Number i = 0x2183, 'XXXXXXXXXX'

Plan:ISDN, Type:National

Called Party Number i = 0x80, '7515'

Plan:Unknown, Type:Unknown

May 10 2007 16:14:59.858 EDT: ISDN Se0/0/0:23 Q931: RX <- FACILITY pd = 8 callref = 0x004F

Facility i = 0x9F8B0100A117020101020100800F5548414B48454D45204F48414D4945

Protocol Profile = Networking Extensions

0xA117020101020100800F5548414B48454D45204F48414D4945

Component = Invoke component

Invoke Id = 1

Operation = CallingName

Name presentation allowed

Name = UHAKHEME OHAMIE

Switchtype NI

Paolo Bevilacqua Thu, 05/10/2007 - 12:46

Hi,

Please try:

voice service voip

qsig decode

Hope this helps, please rate post if it does!

ouhakheme Fri, 05/11/2007 - 04:14

Isn't that for outbound only? I'm worried about inbound.

Thanks.

Paolo Bevilacqua Fri, 05/11/2007 - 04:33

Hi,

any benefit configuing qsig decode as per above? The switch is using the convoluted method instead of the basic display IE.

ouhakheme Fri, 05/11/2007 - 05:09

No dice.

Bearer Capability i = 0x8090A2

Standard = CCITT

Transfer Capability = Speech

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0xA98381

Exclusive, Channel 1

Facility i = 0x9F8B0100A10F02010106072A8648CE1500040A0100

Protocol Profile = Networking Extensions

0xA10F02010106072A8648CE1500040A0100

Component = Invoke component

Invoke Id = 1

Operation = InformationFollowing (calling_name)

Name information in subsequent FACILITY message

Calling Party Number i = 0x2183, '4078977377'

Plan:ISDN, Type:National

Called Party Number i = 0x80, '4800'

Plan:Unknown, Type:Unknown

May 11 2007 09:09:04.678 EDT: ISDN Se0/0/0:23 Q931: TX -> CALL_PROC pd = 8 callref = 0x806D

Channel ID i = 0xA98381

Exclusive, Channel 1

May 11 2007 09:09:04.710 EDT: ISDN Se0/0/0:23 Q931: TX -> ALERTING pd = 8 callref = 0x806D

Facility i = 0x9FAA068001018201018B0100A1090202024C0201018000

Protocol Profile = Networking Extensions

0x010182

0x01018B

0x0100

0xA1090202024C0201018000

Component = Invoke component, Unsupported operation

May 11 2007 09:09:04.734 EDT: ISDN Se0/0/0:23 Q931: TX -> CONNECT pd = 8 callref = 0x806D

Facility i = 0x9FAA068001018201018B0100A1090202024D0201028000

Protocol Profile = Networking Extensions

0x010182

0x01018B

0x0100

0xA1090202024D0201028000

Component = Invoke component, Unsupported operation

May 11 2007 09:09:04.738 EDT: ISDN Se0/0/0:23 Q931: RX <- STATUS pd = 8 callref = 0x006D

Cause i = 0x80E31C - Information element not implemented

Call State i = 0x07

Paolo Bevilacqua Fri, 05/11/2007 - 06:33

Not sure. With qsig decode, the logic is different. The decoding stops as the "subsequent facility" is never decoded. Other change, the router tries now to supply his own qsig info that the switch refuses. The calling name information on the other hand was easily available in the previous test and should have been copied to call leg attributes.

Would you, for a try, configure switch qsig. Perhaps this would allow the logic to carry on and make the calling name available.

ouhakheme Fri, 05/11/2007 - 06:42

Well for some reason, it wasn't getting the caller id information from my office phone. I know that we are sending caller id name, because they got it with the FXO lines. The following is a debug from my cell phone with the name information if that will make a difference.

Bearer Capability i = 0x8090A2

Standard = CCITT

Transfer Capability = Speech

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0xA98382

Exclusive, Channel 2

Facility i = 0x9F8B0100A10F02010106072A8648CE1500040A0100

Protocol Profile = Networking Extensions

0xA10F02010106072A8648CE1500040A0100

Component = Invoke component

Invoke Id = 1

Operation = InformationFollowing (calling_name)

Name information in subsequent FACILITY message

Progress Ind i = 0x8283 - Origination address is non-ISDN

Calling Party Number i = 0x2183, 'XXXXXXXXXX'

Plan:ISDN, Type:National

Called Party Number i = 0x80, '7515'

Plan:Unknown, Type:Unknown

May 11 2007 10:38:49.785 EDT: ISDN Se0/0/0:23 Q931: RX <- FACILITY pd = 8 callref = 0x0079

Facility i = 0x9F8B0100A117020101020100800F5548414B48454D45204F48414D4945

Protocol Profile = Networking Extensions

0xA117020101020100800F5548414B48454D45204F48414D4945

Component = Invoke component

Invoke Id = 1

Operation = CallingName

Name presentation allowed

Name = UHAKHEME OHAMIE

May 11 2007 10:38:49.801 EDT: ISDN Se0/0/0:23 Q931: TX -> CALL_PROC pd = 8 callref = 0x8079

Channel ID i = 0xA98382

Exclusive, Channel 2

May 11 2007 10:38:49.833 EDT: ISDN Se0/0/0:23 Q931: TX -> ALERTING pd = 8 callref = 0x8079

Facility i = 0x9FAA068001018201018B0100A1090202028E0201018000

Protocol Profile = Networking Extensions

0x010182

0x01018B

0x0100

0xA1090202028E0201018000

Component = Invoke component, Unsupported operation

May 11 2007 10:38:49.861 EDT: ISDN Se0/0/0:23 Q931: TX -> CONNECT pd = 8 callref = 0x8079

Facility i = 0x9FAA068001018201018B0100A1090202028F0201028000

Protocol Profile = Networking Extensions

0x010182

0x01018B

0x0100

0xA1090202028F0201028000

Component = Invoke component, Unsupported operation

May 11 2007 10:38:49.865 EDT: ISDN Se0/0/0:23 Q931: RX <- STATUS pd = 8 callref = 0x0079

Cause i = 0x80E31C - Information element not implemented

Call State i = 0x07

Also, can I set the switch-type to qsig without breaking the circuit? The carrier is set to NI.

Tnanks again,

ouhakheme Fri, 05/11/2007 - 14:30

I changed the type to qsig and it didn't make any difference.

Any other ideas?

Ohamien

Paolo Bevilacqua Fri, 05/11/2007 - 14:39

I would try upgrade to a latest maintenance, then ask the TAC to look at this. The name is available and not copying it to call legs looks like be a plain bug.

ouhakheme Tue, 05/15/2007 - 15:07

I needed the 'isdn supp-service name calling' command from earlier, but the problem lied with the AA. The call was being sent to the AA and forwarded back to the phone. If I called a phone directly using this command, it would have probably been fine.

The problem lied with SIP taking the call for the AA after the first facility message and not waiting for the second message to come though.

I added the following command:

sip-ua

timers buffer-invite 500

That will buffer the invite message for another 500ms before the AA accepts the call; thus solving my problem.

Thanks for all of your help!

Paolo Bevilacqua Tue, 05/15/2007 - 16:15

Good info. Had you said before that there is AA in between, or had timestamps in debug, one could have thought about that before :)

Thanks for letting us know and good luck.

ouhakheme Tue, 05/15/2007 - 16:19

Fair enough. I had to limit the debug text because of the forum limits, and I even forgot about the AA because the phone was ringing during business hours.

No worries, it's all good, just glad that there was such an interest.

Actions

This Discussion