Caller ID - SIP call to E1/PRI (Q931) - p-preferred-id

richardbuxton · ‎10-17-2007

Hello,

I have a c2800 router running 12.4(13r)T IOS. This router has E1/PRI interfaces and is used as a gateway between a SIP network and the PSTN.

I have a SIP user who is sending his Caller ID using RFC3325. The Caller ID is not being sent to the PSTN. I think the Cisco router is using the description ("MyName") rather than the number ("8543210") and as this is an alphanumeric field this is not valid on the PSTN.

----------------------------------------------------------------

Example SIP message:

INVITE sip:012345678@1.2.3.4

To: sip:012345678@1.2.3.4

From: "MyName" <sip:5.6.7.8>

P-Asserted-Identity: "MyName" <sip:8543210@5.6.7.8;user=phone>

P-Preferred-Identity: "MyName" <sip:8543210@5.6.7.8;user=phone>

End user IP = 5.6.7.8

Cisco2800 = 1.2.3.4

Dialled Number = 012345678

Requested Caller ID = 8543210

----------------------------------------------------------------

The end user is unable to change any settings on his PBX - he cannot send Caller ID in any other format.

I would be very grateful if anyone could suggest how I can configure the C2800 to send the number to the PSTN

Thanks you

Richard

paolo bevilacqua · ‎10-17-2007

Hi,

can you check/send output of "debug isdn q931" ?

Note that on a normal PSTN circuit, any calling number sent that is different from your number/DID, will be replaced by PSTN with the latter. Else you would be able to place calls with an arbitrary caller-ID and this is generally not good.

Exception, some places/telco in the US.

richardbuxton · ‎10-17-2007

Hi,

Thanks for the quick reply.

Output of debug shown below.

We have no restriction on outbound calling numbers (ie. I can send any number to the PSTN).

Regards

Richard

------------------------------------------

Oct 17 17:12:59.118 BST: ISDN Se3/3:15 Q931: Applying typeplan for sw-type 0x12 is 0x0 0x1, Called num 012345678

Oct 17 17:12:59.118 BST: ISDN Se3/3:15 Q931: TX -> SETUP pd = 8 callref = 0x22BD

Bearer Capability i = 0x8090A3

Standard = CCITT

Transfer Capability = Speech

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0xA98381

Exclusive, Channel 1

Called Party Number i = 0x81, '012345678'

Plan:ISDN, Type:Unknown

Oct 17 17:12:59.146 BST: ISDN Se3/3:15 Q931: RX <- SETUP_ACK pd = 8 callref = 0xA2BD

Channel ID i = 0xA98381

Exclusive, Channel 1

Oct 17 17:12:59.822 BST: ISDN Se3/3:15 Q931: RX <- CALL_PROC pd = 8 callref = 0xA2BD

Channel ID i = 0xA98381

Exclusive, Channel 1

Oct 17 17:12:59.826 BST: ISDN Se3/3:15 Q931: RX <- ALERTING pd = 8 callref = 0xA2BD

------------------------------------------

paolo bevilacqua · ‎10-17-2007

Ok, can you try:

voice service voip

sip

header-passing

richardbuxton · ‎10-18-2007

Hi,

I have added this but it is still not working.

The trace is shown below.

Any further ideas?

Thank you

Richard

--------------------------------

Oct 18 15:06:52.557 BST: ISDN Se3/0:15 Q931: Applying typeplan for sw-type 0x12 is 0x0 0x1, Called num 0123456789

Oct 18 15:06:52.557 BST: ISDN Se3/0:15 Q931: TX -> SETUP pd = 8 callref = 0x49EB

Bearer Capability i = 0x8090A3

Standard = CCITT

Transfer Capability = Speech

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0xA98387

Exclusive, Channel 7

Called Party Number i = 0x81, '0123456789'

Plan:ISDN, Type:Unknown

Oct 18 15:06:52.581 BST: ISDN Se3/0:15 Q931: RX <- SETUP_ACK pd = 8 callref = 0xC9EB

Channel ID i = 0xA98387

Exclusive, Channel 7

paolo bevilacqua · ‎10-18-2007

Hi,

In a related thread:

http://forum.cisco.com/eforum/servlet/NetProf?page=netprof&forum=Unified%20Communications%20and%20Video&topic=IP%20Telephony&CommCmd=MB%3Fcmd%3Dpass_through%26location%3Doutline%40%5E1%40%40.1ddfdf6b/12#selected_message

the command was command was required.

I was suggesting that a TCL script should be able to access any SIP header to set any parameter in the call. The example script posted the thread could not successfully access the sip headers, still I think once you can access them, a script would work.

richardbuxton · ‎10-19-2007

Thanks for your help and suggestion. Unfortunatley I do not think a I will be able to create/implement this TCL script.

I am suprised that the voice gateways do not support p-preferred-identity or p-asserted-identity messages. These seem to be commonly used.

Does anyone else have any suggestions?

Thank you

Richard