Send cisco-voip mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://puck.nether.net/mailman/listinfo/cisco-voip
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of cisco-voip digest..."
Today's Topics:
1. SIP CUBE Caller ID (Heim, Dennis)
2. Re: SIP CUBE Caller ID (Kenneth Hayes)
3. Re: SIP CUBE Caller ID (Mark Holloway)
4. Re: SIP CUBE Caller ID (Heim, Dennis)
5. Re: SIP CUBE Caller ID (Heim, Dennis)
6. Re: SIP CUBE Caller ID (Christian Kratzer)
7. Re: SIP CUBE Caller ID (Mark Holloway)
8. Re: SIP CUBE Caller ID (Heim, Dennis)
9. Re: SIP CUBE Caller ID (Mark Holloway)
10. Re: SIP CUBE Caller ID (Joel Perez)
11. Simulate SIP error code 408 and 603 from CUBE (Me)
12. Re: Simulate SIP error code 408 and 603 from CUBE (Mark Holloway)
13. Cisco Unified IP Phone Local Kernel System Call Input
Validation Vulnerability (Ahmed Elnagar)
----------------------------------------------------------------------
Message: 1
Date: Thu, 10 Jan 2013 12:26:23 -0600
From: "Heim, Dennis" <[email protected]>
To: "[email protected]" <[email protected]>
Subject: [cisco-voip] SIP CUBE Caller ID
Message-ID:
<[email protected]>
Content-Type: text/plain; charset="us-ascii"
I am doing a sip integration to a pbx. We are not getting the caller id
name/number when a call is placed form cisco to the pbx via the cube. We do see
the caller id name in the debugs, but not on the phone display.
Received:
SIP/2.0 200 OK
Call-ID:
[email protected]<mailto:[email protected]>
CSeq: 101 INVITE
From: <sip:[email protected]>;tag=7FA30F9C-154B
To: <sip:[email protected]>;tag=SEC21-a58620a-1e58d20a-2-1e9kU4nFr1Kp
Via: SIP/2.0/UDP 10.98.254.51:5060;branch=z9hG4bK456B7
Contact: <sip:[email protected]:5060;maddr=10.210.88.39>
Content-Type: application/sdp
Content-Length: 367
X-Siemens-Call-Type: ST-insecure
Accept-Language: en;q=0.0
Allow: REGISTER, INVITE, ACK, BYE, CANCEL, NOTIFY, REFER, INFO
Date: Thu, 10 Jan 2013 17:20:27 GMT
P-Asserted-Identity: "My Name" <sip:[email protected]>
What am I missing?
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130110/87f6ca6f/attachment-0001.html>
------------------------------
Message: 2
Date: Thu, 10 Jan 2013 13:32:10 -0500
From: Kenneth Hayes <[email protected]>
To: "Heim, Dennis" <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [cisco-voip] SIP CUBE Caller ID
Message-ID: <3410625381745969557@unknownmsgid>
Content-Type: text/plain; charset="iso-8859-1"
Do you have privacy ID enabled on your voice service voip also on your SIP
trunk to CUBE to UCM under inbound and outbound make sure you have the
header boxes checked.
Sent from my iPad
On Jan 10, 2013, at 1:28 PM, "Heim, Dennis" <[email protected]> wrote:
I am doing a sip integration to a pbx. We are not getting the caller id
name/number when a call is placed form cisco to the pbx via the cube. We do
see the caller id name in the debugs, but not on the phone display.
Received:
SIP/2.0 200 OK
Call-ID: [email protected]
CSeq: 101 INVITE
From: <sip:[email protected]>;tag=7FA30F9C-154B
To: <sip:[email protected]>;tag=SEC21-a58620a-1e58d20a-2-1e9kU4nFr1Kp
Via: SIP/2.0/UDP 10.98.254.51:5060;branch=z9hG4bK456B7
Contact: <sip:[email protected]:5060;maddr=10.210.88.39>
Content-Type: application/sdp
Content-Length: 367
X-Siemens-Call-Type: ST-insecure
Accept-Language: en;q=0.0
Allow: REGISTER, INVITE, ACK, BYE, CANCEL, NOTIFY, REFER, INFO
Date: Thu, 10 Jan 2013 17:20:27 GMT
P-Asserted-Identity: "My Name" <sip:[email protected]>
What am I missing?
_______________________________________________
cisco-voip mailing list
[email protected]
https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130110/86279608/attachment-0001.html>
------------------------------
Message: 3
Date: Thu, 10 Jan 2013 13:50:31 -0500
From: Mark Holloway <[email protected]>
To: "Heim, Dennis" <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [cisco-voip] SIP CUBE Caller ID
Message-ID: <[email protected]>
Content-Type: text/plain; charset="us-ascii"
The FROM field should have a name in front of the phone number. (Like the
bottom line of text in this capture). Can you send the SIP INVITE from CUCM >
CUBE, and from CUBE to the PBX?
On Jan 10, 2013, at 1:26 PM, "Heim, Dennis" <[email protected]> wrote:
> I am doing a sip integration to a pbx. We are not getting the caller id
> name/number when a call is placed form cisco to the pbx via the cube. We do
> see the caller id name in the debugs, but not on the phone display.
>
> Received:
> SIP/2.0 200 OK
> Call-ID: [email protected]
> CSeq: 101 INVITE
> From: <sip:[email protected]>;tag=7FA30F9C-154B
> To: <sip:[email protected]>;tag=SEC21-a58620a-1e58d20a-2-1e9kU4nFr1Kp
> Via: SIP/2.0/UDP 10.98.254.51:5060;branch=z9hG4bK456B7
> Contact: <sip:[email protected]:5060;maddr=10.210.88.39>
> Content-Type: application/sdp
> Content-Length: 367
> X-Siemens-Call-Type: ST-insecure
> Accept-Language: en;q=0.0
> Allow: REGISTER, INVITE, ACK, BYE, CANCEL, NOTIFY, REFER, INFO
> Date: Thu, 10 Jan 2013 17:20:27 GMT
> P-Asserted-Identity: "My Name" <sip:[email protected]>
>
> What am I missing?
> _______________________________________________
> cisco-voip mailing list
> [email protected]
> https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130110/fcffa909/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: PastedGraphic-1.png
Type: image/png
Size: 123121 bytes
Desc: not available
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130110/fcffa909/attachment-0001.png>
------------------------------
Message: 4
Date: Thu, 10 Jan 2013 13:55:08 -0600
From: "Heim, Dennis" <[email protected]>
To: Mark Holloway <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [cisco-voip] SIP CUBE Caller ID
Message-ID:
<[email protected]>
Content-Type: text/plain; charset="us-ascii"
It is showing in the PAI, but not the from field.
Call-ID: [email protected]
CSeq: 101 INVITE
Timestamp: 1357847526
Content-Length: 0
Jan 10 19:52:06.991: //184752/427582000000/SIP/Info/sipSPICheckResponseExt:
INVITE response with no RSEQ - disable IS_REL1XX
Jan 10 19:52:06.991: //184752/427582000000/SIP/State/sipSPIChangeState:
0x2472CB8 : State change from (STATE_SENT_INVITE, SUBSTATE_NONE) to
(STATE_RECD_PROCEEDING, SUBSTATE_PROCEEDING_PROCEEDING)
Jan 10 19:52:07.119: //-1/xxxxxxxxxxxx/SIP/Info/HandleUdpIPv4SocketReads: Msg
enqueued for SPI with IP addr: [10.98.88.38]:5060, local_address:[10.98.254.51]
Jan 10 19:52:07.119:
//-1/xxxxxxxxxxxx/SIP/Info/ccsip_process_sipspi_queue_event:
ccsip_spi_get_msg_type returned: 2 for event 1
Jan 10 19:52:07.119:
//-1/xxxxxxxxxxxx/SIP/Transport/sipTransportProcessNWNewConnMsg: context=0x0
Jan 10 19:52:07.119: //-1/xxxxxxxxxxxx/SIP/Info/ccsip_new_msg_preprocessor:
Checking Invite Dialog
Jan 10 19:52:07.119: //184752/427582000000/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 180 Ringing
Call-ID: [email protected]
CSeq: 101 INVITE
From: sip:[email protected];tag=802E4C74-179B
To: <sip:[email protected]>;tag=SEC11-a58620a-1e58d20a-1-zvE1E7A74E0q
Via: SIP/2.0/UDP 10.98.254.51:5060;branch=z9hG4bK5C1C8C
Contact: <sip:[email protected]:5060;maddr=10.98.88.38>
Date: Thu, 10 Jan 2013 19:52:29 GMT
P-Asserted-Identity: "My Name" <sip:[email protected]>
Content-Length: 0
From: Mark Holloway [mailto:[email protected]]
Sent: Thursday, January 10, 2013 1:51 PM
To: Heim, Dennis
Cc: [email protected]
Subject: Re: [cisco-voip] SIP CUBE Caller ID
The FROM field should have a name in front of the phone number. (Like the
bottom line of text in this capture). Can you send the SIP INVITE from CUCM >
CUBE, and from CUBE to the PBX?
[cid:[email protected]]
On Jan 10, 2013, at 1:26 PM, "Heim, Dennis"
<[email protected]<mailto:[email protected]>> wrote:
I am doing a sip integration to a pbx. We are not getting the caller id
name/number when a call is placed form cisco to the pbx via the cube. We do see
the caller id name in the debugs, but not on the phone display.
Received:
SIP/2.0 200 OK
Call-ID:
[email protected]<mailto:[email protected]>
CSeq: 101 INVITE
From: <sip:[email protected]>;tag=7FA30F9C-154B
To: <sip:[email protected]>;tag=SEC21-a58620a-1e58d20a-2-1e9kU4nFr1Kp
Via: SIP/2.0/UDP 10.98.254.51:5060;branch=z9hG4bK456B7
Contact: <sip:[email protected]:5060;maddr=10.210.88.39>
Content-Type: application/sdp
Content-Length: 367
X-Siemens-Call-Type: ST-insecure
Accept-Language: en;q=0.0
Allow: REGISTER, INVITE, ACK, BYE, CANCEL, NOTIFY, REFER, INFO
Date: Thu, 10 Jan 2013 17:20:27 GMT
P-Asserted-Identity: "My Name" <sip:[email protected]>
What am I missing?
_______________________________________________
cisco-voip mailing list
[email protected]<mailto:[email protected]>
https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130110/78702056/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 123121 bytes
Desc: image001.png
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130110/78702056/attachment-0001.png>
------------------------------
Message: 5
Date: Thu, 10 Jan 2013 14:56:41 -0600
From: "Heim, Dennis" <[email protected]>
To: Kenneth Hayes <[email protected]>,
"[email protected]" <[email protected]>
Subject: Re: [cisco-voip] SIP CUBE Caller ID
Message-ID:
<[email protected]>
Content-Type: text/plain; charset="us-ascii"
This is outbound from CUCM. I dial the number it connects and the display just
shows the dialed number, without the name. I did not have a display name on my
phone, when I fixed that, the caller id name is visible to the siemens pbx.
The problem still is that I dial a number and it does not put in the name
The Cisco-Siemens direction, we see Cisco set the From with the name (From:
"Cisco Phone" sip:5987800@ip. We also see the P-Asserted-Identity set to "Cisco
Phone" sip:5987800@ip.
On the invite coming back from the siemens we see it set the From, only contain
the number. However, the P-Asserted-Identity, contains the caller id name.
From: Heim, Dennis
Sent: Thursday, January 10, 2013 3:46 PM
To: 'Kenneth Hayes'; Voice_VT
Subject: RE: [cisco-voip] SIP CUBE Caller ID
This is outbound from CUCM. I dial the number it connects and the display just
shows the dialed number, with the name. I did not have a display name on my
phone, when I fixed that, the caller id name is visible to the siemens pbx.
The problem still is that I dial a number and it does not put in the name.
From: Kenneth Hayes
[mailto:[email protected]]<mailto:[mailto:[email protected]]>
Sent: Thursday, January 10, 2013 3:29 PM
To: Heim, Dennis
Subject: Re: [cisco-voip] SIP CUBE Caller ID
This is inbound correct?
On Thu, Jan 10, 2013 at 2:55 PM, Heim, Dennis
<[email protected]<mailto:[email protected]>> wrote:
It is showing in the PAI, but not the from field.
Call-ID:
[email protected]<mailto:[email protected]>
CSeq: 101 INVITE
Timestamp: 1357847526
Content-Length: 0
Jan 10 19:52:06.991: //184752/427582000000/SIP/Info/sipSPICheckResponseExt:
INVITE response with no RSEQ - disable IS_REL1XX
Jan 10 19:52:06.991: //184752/427582000000/SIP/State/sipSPIChangeState:
0x2472CB8 : State change from (STATE_SENT_INVITE, SUBSTATE_NONE) to
(STATE_RECD_PROCEEDING, SUBSTATE_PROCEEDING_PROCEEDING)
Jan 10 19:52:07.119: //-1/xxxxxxxxxxxx/SIP/Info/HandleUdpIPv4SocketReads: Msg
enqueued for SPI with IP addr: [10.98.88.38]:5060, local_address:[10.98.254.51]
Jan 10 19:52:07.119:
//-1/xxxxxxxxxxxx/SIP/Info/ccsip_process_sipspi_queue_event:
ccsip_spi_get_msg_type returned: 2 for event 1
Jan 10 19:52:07.119:
//-1/xxxxxxxxxxxx/SIP/Transport/sipTransportProcessNWNewConnMsg: context=0x0
Jan 10 19:52:07.119: //-1/xxxxxxxxxxxx/SIP/Info/ccsip_new_msg_preprocessor:
Checking Invite Dialog
Jan 10 19:52:07.119: //184752/427582000000/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 180 Ringing
Call-ID:
[email protected]<mailto:[email protected]>
CSeq: 101 INVITE
From:
sip:[email protected]<mailto:sip%[email protected]>;tag=802E4C74-179B
To:
<sip:[email protected]<mailto:sip%[email protected]>>;tag=SEC11-a58620a-1e58d20a-1-zvE1E7A74E0q
Via: SIP/2.0/UDP 10.98.254.51:5060;branch=z9hG4bK5C1C8C
Contact: <sip:[email protected]:5060;maddr=10.98.88.38>
Date: Thu, 10 Jan 2013 19:52:29 GMT
P-Asserted-Identity: "My Name"
<sip:[email protected]<mailto:sip%[email protected]>>
Content-Length: 0
From: Mark Holloway [mailto:[email protected]<mailto:[email protected]>]
Sent: Thursday, January 10, 2013 1:51 PM
To: Heim, Dennis
Cc: [email protected]<mailto:[email protected]>
Subject: Re: [cisco-voip] SIP CUBE Caller ID
The FROM field should have a name in front of the phone number. (Like the
bottom line of text in this capture). Can you send the SIP INVITE from CUCM >
CUBE, and from CUBE to the PBX?
[cid:[email protected]]
On Jan 10, 2013, at 1:26 PM, "Heim, Dennis"
<[email protected]<mailto:[email protected]>> wrote:
I am doing a sip integration to a pbx. We are not getting the caller id
name/number when a call is placed form cisco to the pbx via the cube. We do see
the caller id name in the debugs, but not on the phone display.
Received:
SIP/2.0 200 OK
Call-ID:
[email protected]<mailto:[email protected]>
CSeq: 101 INVITE
From: <sip:[email protected]>;tag=7FA30F9C-154B
To: <sip:[email protected]>;tag=SEC21-a58620a-1e58d20a-2-1e9kU4nFr1Kp
Via: SIP/2.0/UDP 10.98.254.51:5060;branch=z9hG4bK456B7
Contact: <sip:[email protected]:5060;maddr=10.210.88.39>
Content-Type: application/sdp
Content-Length: 367
X-Siemens-Call-Type: ST-insecure
Accept-Language: en;q=0.0
Allow: REGISTER, INVITE, ACK, BYE, CANCEL, NOTIFY, REFER, INFO
Date: Thu, 10 Jan 2013 17:20:27 GMT
P-Asserted-Identity: "My Name" <sip:[email protected]>
What am I missing?
_______________________________________________
cisco-voip mailing list
[email protected]<mailto:[email protected]>
https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________
cisco-voip mailing list
[email protected]<mailto:[email protected]>
https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130110/3c21a24c/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 123121 bytes
Desc: image001.png
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130110/3c21a24c/attachment-0001.png>
------------------------------
Message: 6
Date: Thu, 10 Jan 2013 21:38:30 +0100 (CET)
From: Christian Kratzer <[email protected]>
To: "Heim, Dennis" <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [cisco-voip] SIP CUBE Caller ID
Message-ID: <[email protected]>
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Hi,
On Thu, 10 Jan 2013, Heim, Dennis wrote:
> I am doing a sip integration to a pbx. We are not getting the caller id
> name/number when a call is placed form cisco to the pbx via the cube. We do
> see the caller id name in the debugs, but not on the phone display.
try
clid strip name
in the incoming sip dial-peer.
If sip gives the cube a usable although empty name for the incoming call
then your phones won't bother to lookup the number.
If you strip the name the phones will look it up again.
Greetings
Christian
>
> Received:
> SIP/2.0 200 OK
> Call-ID:
> [email protected]<mailto:[email protected]>
> CSeq: 101 INVITE
> From: <sip:[email protected]>;tag=7FA30F9C-154B
> To: <sip:[email protected]>;tag=SEC21-a58620a-1e58d20a-2-1e9kU4nFr1Kp
> Via: SIP/2.0/UDP 10.98.254.51:5060;branch=z9hG4bK456B7
> Contact: <sip:[email protected]:5060;maddr=10.210.88.39>
> Content-Type: application/sdp
> Content-Length: 367
> X-Siemens-Call-Type: ST-insecure
> Accept-Language: en;q=0.0
> Allow: REGISTER, INVITE, ACK, BYE, CANCEL, NOTIFY, REFER, INFO
> Date: Thu, 10 Jan 2013 17:20:27 GMT
> P-Asserted-Identity: "My Name" <sip:[email protected]>
>
> What am I missing?
>
--
Christian Kratzer CK Software GmbH
Email: [email protected] Wildberger Weg 24/2
Phone: +49 7032 893 997 - 0 D-71126 Gaeufelden
Fax: +49 7032 893 997 - 9 HRB 245288, Amtsgericht Stuttgart
Web: http://www.cksoft.de/ Geschaeftsfuehrer: Christian Kratzer
------------------------------
Message: 7
Date: Thu, 10 Jan 2013 16:23:12 -0500
From: Mark Holloway <[email protected]>
To: "Heim, Dennis" <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [cisco-voip] SIP CUBE Caller ID
Message-ID: <[email protected]>
Content-Type: text/plain; charset="windows-1252"
What I was looking for, but didn't see in your TXT file, is the SIP INVITE from
CUCM includes the calling party name in the FROM field to CUBE, and CUBE
includes the same FROM name to Siemens. Assuming that is true, Siemens appears
to be disregarding the name portion of the FROM field by not only failing to
display it, but completely removing it in 1XX responses. It would be nice if it
processed PAI but I think the name is being stripped and then Siemens just
assumes there is no name for the call, as if PAI didn't exist.
On Jan 10, 2013, at 3:56 PM, "Heim, Dennis" <[email protected]> wrote:
> This is outbound from CUCM. I dial the number it connects and the display
> just shows the dialed number, without the name. I did not have a display name
> on my phone, when I fixed that, the caller id name is visible to the siemens
> pbx.
>
> The problem still is that I dial a number and it does not put in the name
>
> The Cisco-Siemens direction, we see Cisco set the From with the name (From:
> ?Cisco Phone? sip:5987800@ip. We also see the P-Asserted-Identity set to
> ?Cisco Phone? sip:5987800@ip.
>
> On the invite coming back from the siemens we see it set the From, only
> contain the number. However, the P-Asserted-Identity, contains the caller id
> name.
>
> From: Heim, Dennis
> Sent: Thursday, January 10, 2013 3:46 PM
> To: 'Kenneth Hayes'; Voice_VT
> Subject: RE: [cisco-voip] SIP CUBE Caller ID
>
> This is outbound from CUCM. I dial the number it connects and the display
> just shows the dialed number, with the name. I did not have a display name on
> my phone, when I fixed that, the caller id name is visible to the siemens pbx.
>
> The problem still is that I dial a number and it does not put in the name.
>
> From: Kenneth Hayes [mailto:[email protected]]
> Sent: Thursday, January 10, 2013 3:29 PM
> To: Heim, Dennis
> Subject: Re: [cisco-voip] SIP CUBE Caller ID
>
> This is inbound correct?
>
> On Thu, Jan 10, 2013 at 2:55 PM, Heim, Dennis <[email protected]> wrote:
> It is showing in the PAI, but not the from field.
>
> Call-ID: [email protected]
> CSeq: 101 INVITE
> Timestamp: 1357847526
> Content-Length: 0
>
>
> Jan 10 19:52:06.991: //184752/427582000000/SIP/Info/sipSPICheckResponseExt:
> INVITE response with no RSEQ - disable IS_REL1XX
> Jan 10 19:52:06.991: //184752/427582000000/SIP/State/sipSPIChangeState:
> 0x2472CB8 : State change from (STATE_SENT_INVITE, SUBSTATE_NONE) to
> (STATE_RECD_PROCEEDING, SUBSTATE_PROCEEDING_PROCEEDING)
> Jan 10 19:52:07.119: //-1/xxxxxxxxxxxx/SIP/Info/HandleUdpIPv4SocketReads: Msg
> enqueued for SPI with IP addr: [10.98.88.38]:5060,
> local_address:[10.98.254.51]
> Jan 10 19:52:07.119:
> //-1/xxxxxxxxxxxx/SIP/Info/ccsip_process_sipspi_queue_event:
> ccsip_spi_get_msg_type returned: 2 for event 1
> Jan 10 19:52:07.119:
> //-1/xxxxxxxxxxxx/SIP/Transport/sipTransportProcessNWNewConnMsg: context=0x0
> Jan 10 19:52:07.119: //-1/xxxxxxxxxxxx/SIP/Info/ccsip_new_msg_preprocessor:
> Checking Invite Dialog
> Jan 10 19:52:07.119: //184752/427582000000/SIP/Msg/ccsipDisplayMsg:
> Received:
> SIP/2.0 180 Ringing
> Call-ID: [email protected]
> CSeq: 101 INVITE
> From: sip:[email protected];tag=802E4C74-179B
> To: <sip:[email protected]>;tag=SEC11-a58620a-1e58d20a-1-zvE1E7A74E0q
> Via: SIP/2.0/UDP 10.98.254.51:5060;branch=z9hG4bK5C1C8C
> Contact: <sip:[email protected]:5060;maddr=10.98.88.38>
> Date: Thu, 10 Jan 2013 19:52:29 GMT
> P-Asserted-Identity: "My Name" <sip:[email protected]>
> Content-Length: 0
>
> From: Mark Holloway [mailto:[email protected]]
> Sent: Thursday, January 10, 2013 1:51 PM
> To: Heim, Dennis
> Cc: [email protected]
> Subject: Re: [cisco-voip] SIP CUBE Caller ID
>
> The FROM field should have a name in front of the phone number. (Like the
> bottom line of text in this capture). Can you send the SIP INVITE from CUCM
> > CUBE, and from CUBE to the PBX?
>
> <image001.png>
>
>
>
> On Jan 10, 2013, at 1:26 PM, "Heim, Dennis" <[email protected]> wrote:
>
>
> I am doing a sip integration to a pbx. We are not getting the caller id
> name/number when a call is placed form cisco to the pbx via the cube. We do
> see the caller id name in the debugs, but not on the phone display.
>
> Received:
> SIP/2.0 200 OK
> Call-ID: [email protected]
> CSeq: 101 INVITE
> From: <sip:[email protected]>;tag=7FA30F9C-154B
> To: <sip:[email protected]>;tag=SEC21-a58620a-1e58d20a-2-1e9kU4nFr1Kp
> Via: SIP/2.0/UDP 10.98.254.51:5060;branch=z9hG4bK456B7
> Contact: <sip:[email protected]:5060;maddr=10.210.88.39>
> Content-Type: application/sdp
> Content-Length: 367
> X-Siemens-Call-Type: ST-insecure
> Accept-Language: en;q=0.0
> Allow: REGISTER, INVITE, ACK, BYE, CANCEL, NOTIFY, REFER, INFO
> Date: Thu, 10 Jan 2013 17:20:27 GMT
> P-Asserted-Identity: "My Name" <sip:[email protected]>
>
> What am I missing?
> _______________________________________________
> cisco-voip mailing list
> [email protected]
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
> _______________________________________________
> cisco-voip mailing list
> [email protected]
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
> _______________________________________________
> cisco-voip mailing list
> [email protected]
> https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130110/d980a68e/attachment-0001.html>
------------------------------
Message: 8
Date: Thu, 10 Jan 2013 15:58:23 -0600
From: "Heim, Dennis" <[email protected]>
To: Mark Holloway <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [cisco-voip] SIP CUBE Caller ID
Message-ID:
<[email protected]>
Content-Type: text/plain; charset="us-ascii"
Is it possible with cube to take the PAI and copy it into the from field?
Call setup
INVITE sip:18077014@CUBE:5060 SIP/2.0
Via: SIP/2.0/TCP CUCM:5060;branch=z9hG4bK1eda32bbab882
From: "Cisco Phone"
<sip:5987800@CUCM>;tag=2004325~37777082-f7ba-4cb2-8467-e286cea21f2e-88710674
To: <sip:18077014@CUBE>
Date: Thu, 10 Jan 2013 21:47:24 GMT
Call-ID: 50330380-ef136ec-1a038-2b3dd20a@CUCM
Supported: timer,resource-priority,replaces
Min-SE: 1800
User-Agent: Cisco-CUCM8.6
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER,
SUBSCRIBE, NOTIFY
CSeq: 101 INVITE
Expires: 180
Allow-Events: presence, kpml
Supported: X-cisco-srtp-fallback
Supported: Geolocation
Cisco-Guid: 1345520512-0000065536-0000033495-0725471754
Session-Expires: 1800
P-Asserted-Identity: "Cisco Phone" <sip:5987800@CUCM>
Remote-Party-ID: "Cisco Phone"
<sip:5987800@CUCM>;party=calling;screen=yes;privacy=off
Contact: <sip:5987800@CUCM:5060;transport=tcp>
Max-Forwards: 69
Content-Type: application/sdp
Content-Length: 214
When ringing
Received:
SIP/2.0 180 Ringing
Call-ID: 1A53E43D-5AA611E2-A21DF143-739C4300@CUBE
CSeq: 101 INVITE
From: sip:5987800@CUCM;tag=809784F8-1B9F
To: <sip:18077014@SiemensOSV>;tag=SEC11-a58620a-1e58d20a-1-4197U1P1AG4o
Via: SIP/2.0/UDP CUBE:5060;branch=z9hG4bK7B1AD5
Contact: <sip:18077014@SiemensOSV:5060;maddr=SiemensOSV>
Content-Type: application/sdp
Content-Length: 320
Allow: REGISTER, INVITE, ACK, BYE, CANCEL, NOTIFY, REFER, INFO
Allow-Events: CCNR
Date: Thu, 10 Jan 2013 21:47:24 GMT
P-Asserted-Identity: "Siemens User" <sip:18077014@SiemensOSV>
From: Mark Holloway [mailto:[email protected]]
Sent: Thursday, January 10, 2013 4:23 PM
To: Heim, Dennis
Cc: Kenneth Hayes; [email protected]
Subject: Re: [cisco-voip] SIP CUBE Caller ID
What I was looking for, but didn't see in your TXT file, is the SIP INVITE from
CUCM includes the calling party name in the FROM field to CUBE, and CUBE
includes the same FROM name to Siemens. Assuming that is true, Siemens appears
to be disregarding the name portion of the FROM field by not only failing to
display it, but completely removing it in 1XX responses. It would be nice if it
processed PAI but I think the name is being stripped and then Siemens just
assumes there is no name for the call, as if PAI didn't exist.
On Jan 10, 2013, at 3:56 PM, "Heim, Dennis"
<[email protected]<mailto:[email protected]>> wrote:
This is outbound from CUCM. I dial the number it connects and the display just
shows the dialed number, without the name. I did not have a display name on my
phone, when I fixed that, the caller id name is visible to the siemens pbx.
The problem still is that I dial a number and it does not put in the name
The Cisco-Siemens direction, we see Cisco set the From with the name (From:
"Cisco Phone" sip:5987800@ip. We also see the P-Asserted-Identity set to "Cisco
Phone" sip:5987800@ip.
On the invite coming back from the siemens we see it set the From, only contain
the number. However, the P-Asserted-Identity, contains the caller id name.
From: Heim, Dennis
Sent: Thursday, January 10, 2013 3:46 PM
To: 'Kenneth Hayes'; Voice_VT
Subject: RE: [cisco-voip] SIP CUBE Caller ID
This is outbound from CUCM. I dial the number it connects and the display just
shows the dialed number, with the name. I did not have a display name on my
phone, when I fixed that, the caller id name is visible to the siemens pbx.
The problem still is that I dial a number and it does not put in the name.
From: Kenneth Hayes
[mailto:[email protected]]<mailto:[mailto:[email protected]]>
Sent: Thursday, January 10, 2013 3:29 PM
To: Heim, Dennis
Subject: Re: [cisco-voip] SIP CUBE Caller ID
This is inbound correct?
On Thu, Jan 10, 2013 at 2:55 PM, Heim, Dennis
<[email protected]<mailto:[email protected]>> wrote:
It is showing in the PAI, but not the from field.
Call-ID:
[email protected]<mailto:[email protected]>
CSeq: 101 INVITE
Timestamp: 1357847526
Content-Length: 0
Jan 10 19:52:06.991: //184752/427582000000/SIP/Info/sipSPICheckResponseExt:
INVITE response with no RSEQ - disable IS_REL1XX
Jan 10 19:52:06.991: //184752/427582000000/SIP/State/sipSPIChangeState:
0x2472CB8 : State change from (STATE_SENT_INVITE, SUBSTATE_NONE) to
(STATE_RECD_PROCEEDING, SUBSTATE_PROCEEDING_PROCEEDING)
Jan 10 19:52:07.119: //-1/xxxxxxxxxxxx/SIP/Info/HandleUdpIPv4SocketReads: Msg
enqueued for SPI with IP addr: [10.98.88.38]:5060, local_address:[10.98.254.51]
Jan 10 19:52:07.119:
//-1/xxxxxxxxxxxx/SIP/Info/ccsip_process_sipspi_queue_event:
ccsip_spi_get_msg_type returned: 2 for event 1
Jan 10 19:52:07.119:
//-1/xxxxxxxxxxxx/SIP/Transport/sipTransportProcessNWNewConnMsg: context=0x0
Jan 10 19:52:07.119: //-1/xxxxxxxxxxxx/SIP/Info/ccsip_new_msg_preprocessor:
Checking Invite Dialog
Jan 10 19:52:07.119: //184752/427582000000/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 180 Ringing
Call-ID:
[email protected]<mailto:[email protected]>
CSeq: 101 INVITE
From:
sip:[email protected]<mailto:sip%[email protected]>;tag=802E4C74-179B
To:
<sip:[email protected]<mailto:sip%[email protected]>>;tag=SEC11-a58620a-1e58d20a-1-zvE1E7A74E0q
Via: SIP/2.0/UDP 10.98.254.51:5060;branch=z9hG4bK5C1C8C
Contact: <sip:[email protected]:5060;maddr=10.98.88.38>
Date: Thu, 10 Jan 2013 19:52:29 GMT
P-Asserted-Identity: "My Name"
<sip:[email protected]<mailto:sip%[email protected]>>
Content-Length: 0
From: Mark Holloway [mailto:[email protected]<mailto:[email protected]>]
Sent: Thursday, January 10, 2013 1:51 PM
To: Heim, Dennis
Cc: [email protected]<mailto:[email protected]>
Subject: Re: [cisco-voip] SIP CUBE Caller ID
The FROM field should have a name in front of the phone number. (Like the
bottom line of text in this capture). Can you send the SIP INVITE from CUCM >
CUBE, and from CUBE to the PBX?
<image001.png>
On Jan 10, 2013, at 1:26 PM, "Heim, Dennis"
<[email protected]<mailto:[email protected]>> wrote:
I am doing a sip integration to a pbx. We are not getting the caller id
name/number when a call is placed form cisco to the pbx via the cube. We do see
the caller id name in the debugs, but not on the phone display.
Received:
SIP/2.0 200 OK
Call-ID:
[email protected]<mailto:[email protected]>
CSeq: 101 INVITE
From: <sip:[email protected]>;tag=7FA30F9C-154B
To: <sip:[email protected]>;tag=SEC21-a58620a-1e58d20a-2-1e9kU4nFr1Kp
Via: SIP/2.0/UDP 10.98.254.51:5060;branch=z9hG4bK456B7
Contact: <sip:[email protected]:5060;maddr=10.210.88.39>
Content-Type: application/sdp
Content-Length: 367
X-Siemens-Call-Type: ST-insecure
Accept-Language: en;q=0.0
Allow: REGISTER, INVITE, ACK, BYE, CANCEL, NOTIFY, REFER, INFO
Date: Thu, 10 Jan 2013 17:20:27 GMT
P-Asserted-Identity: "My Name" <sip:[email protected]>
What am I missing?
_______________________________________________
cisco-voip mailing list
[email protected]<mailto:[email protected]>
https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________
cisco-voip mailing list
[email protected]<mailto:[email protected]>
https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________
cisco-voip mailing list
[email protected]<mailto:[email protected]>
https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130110/37b92d3e/attachment-0001.html>
------------------------------
Message: 9
Date: Thu, 10 Jan 2013 17:15:24 -0500
From: Mark Holloway <[email protected]>
To: "Heim, Dennis" <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [cisco-voip] SIP CUBE Caller ID
Message-ID: <[email protected]>
Content-Type: text/plain; charset="windows-1252"
Maybe with SIP Profiles, but I think the real issue is Siemens isn't honoring
the From name, RPID, or PAI. Even if you add it back in after a 1XX response
it may not solve your problem.
On Jan 10, 2013, at 4:58 PM, "Heim, Dennis" <[email protected]> wrote:
> Is it possible with cube to take the PAI and copy it into the from field?
>
> Call setup
>
> INVITE sip:18077014@CUBE:5060 SIP/2.0
> Via: SIP/2.0/TCP CUCM:5060;branch=z9hG4bK1eda32bbab882
> From: "Cisco Phone"
> <sip:5987800@CUCM>;tag=2004325~37777082-f7ba-4cb2-8467-e286cea21f2e-88710674
> To: <sip:18077014@CUBE>
> Date: Thu, 10 Jan 2013 21:47:24 GMT
> Call-ID: 50330380-ef136ec-1a038-2b3dd20a@CUCM
> Supported: timer,resource-priority,replaces
> Min-SE: 1800
> User-Agent: Cisco-CUCM8.6
> Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER,
> SUBSCRIBE, NOTIFY
> CSeq: 101 INVITE
> Expires: 180
> Allow-Events: presence, kpml
> Supported: X-cisco-srtp-fallback
> Supported: Geolocation
> Cisco-Guid: 1345520512-0000065536-0000033495-0725471754
> Session-Expires: 1800
> P-Asserted-Identity: "Cisco Phone" <sip:5987800@CUCM>
> Remote-Party-ID: "Cisco Phone"
> <sip:5987800@CUCM>;party=calling;screen=yes;privacy=off
> Contact: <sip:5987800@CUCM:5060;transport=tcp>
> Max-Forwards: 69
> Content-Type: application/sdp
> Content-Length: 214
>
> When ringing
>
> Received:
> SIP/2.0 180 Ringing
> Call-ID: 1A53E43D-5AA611E2-A21DF143-739C4300@CUBE
> CSeq: 101 INVITE
> From: sip:5987800@CUCM;tag=809784F8-1B9F
> To: <sip:18077014@SiemensOSV>;tag=SEC11-a58620a-1e58d20a-1-4197U1P1AG4o
> Via: SIP/2.0/UDP CUBE:5060;branch=z9hG4bK7B1AD5
> Contact: <sip:18077014@SiemensOSV:5060;maddr=SiemensOSV>
> Content-Type: application/sdp
> Content-Length: 320
> Allow: REGISTER, INVITE, ACK, BYE, CANCEL, NOTIFY, REFER, INFO
> Allow-Events: CCNR
> Date: Thu, 10 Jan 2013 21:47:24 GMT
> P-Asserted-Identity: "Siemens User" <sip:18077014@SiemensOSV>
> From: Mark Holloway [mailto:[email protected]]
> Sent: Thursday, January 10, 2013 4:23 PM
> To: Heim, Dennis
> Cc: Kenneth Hayes; [email protected]
> Subject: Re: [cisco-voip] SIP CUBE Caller ID
>
> What I was looking for, but didn't see in your TXT file, is the SIP INVITE
> from CUCM includes the calling party name in the FROM field to CUBE, and CUBE
> includes the same FROM name to Siemens. Assuming that is true, Siemens
> appears to be disregarding the name portion of the FROM field by not only
> failing to display it, but completely removing it in 1XX responses. It would
> be nice if it processed PAI but I think the name is being stripped and then
> Siemens just assumes there is no name for the call, as if PAI didn't exist.
>
> On Jan 10, 2013, at 3:56 PM, "Heim, Dennis" <[email protected]> wrote:
>
>
> This is outbound from CUCM. I dial the number it connects and the display
> just shows the dialed number, without the name. I did not have a display name
> on my phone, when I fixed that, the caller id name is visible to the siemens
> pbx.
>
> The problem still is that I dial a number and it does not put in the name
>
> The Cisco-Siemens direction, we see Cisco set the From with the name (From:
> ?Cisco Phone? sip:5987800@ip. We also see the P-Asserted-Identity set to
> ?Cisco Phone? sip:5987800@ip.
>
> On the invite coming back from the siemens we see it set the From, only
> contain the number. However, the P-Asserted-Identity, contains the caller id
> name.
>
> From: Heim, Dennis
> Sent: Thursday, January 10, 2013 3:46 PM
> To: 'Kenneth Hayes'; Voice_VT
> Subject: RE: [cisco-voip] SIP CUBE Caller ID
>
> This is outbound from CUCM. I dial the number it connects and the display
> just shows the dialed number, with the name. I did not have a display name on
> my phone, when I fixed that, the caller id name is visible to the siemens pbx.
>
> The problem still is that I dial a number and it does not put in the name.
>
> From: Kenneth Hayes [mailto:[email protected]]
> Sent: Thursday, January 10, 2013 3:29 PM
> To: Heim, Dennis
> Subject: Re: [cisco-voip] SIP CUBE Caller ID
>
> This is inbound correct?
>
> On Thu, Jan 10, 2013 at 2:55 PM, Heim, Dennis <[email protected]> wrote:
> It is showing in the PAI, but not the from field.
>
> Call-ID: [email protected]
> CSeq: 101 INVITE
> Timestamp: 1357847526
> Content-Length: 0
>
>
> Jan 10 19:52:06.991: //184752/427582000000/SIP/Info/sipSPICheckResponseExt:
> INVITE response with no RSEQ - disable IS_REL1XX
> Jan 10 19:52:06.991: //184752/427582000000/SIP/State/sipSPIChangeState:
> 0x2472CB8 : State change from (STATE_SENT_INVITE, SUBSTATE_NONE) to
> (STATE_RECD_PROCEEDING, SUBSTATE_PROCEEDING_PROCEEDING)
> Jan 10 19:52:07.119: //-1/xxxxxxxxxxxx/SIP/Info/HandleUdpIPv4SocketReads: Msg
> enqueued for SPI with IP addr: [10.98.88.38]:5060,
> local_address:[10.98.254.51]
> Jan 10 19:52:07.119:
> //-1/xxxxxxxxxxxx/SIP/Info/ccsip_process_sipspi_queue_event:
> ccsip_spi_get_msg_type returned: 2 for event 1
> Jan 10 19:52:07.119:
> //-1/xxxxxxxxxxxx/SIP/Transport/sipTransportProcessNWNewConnMsg: context=0x0
> Jan 10 19:52:07.119: //-1/xxxxxxxxxxxx/SIP/Info/ccsip_new_msg_preprocessor:
> Checking Invite Dialog
> Jan 10 19:52:07.119: //184752/427582000000/SIP/Msg/ccsipDisplayMsg:
> Received:
> SIP/2.0 180 Ringing
> Call-ID: [email protected]
> CSeq: 101 INVITE
> From: sip:[email protected];tag=802E4C74-179B
> To: <sip:[email protected]>;tag=SEC11-a58620a-1e58d20a-1-zvE1E7A74E0q
> Via: SIP/2.0/UDP 10.98.254.51:5060;branch=z9hG4bK5C1C8C
> Contact: <sip:[email protected]:5060;maddr=10.98.88.38>
> Date: Thu, 10 Jan 2013 19:52:29 GMT
> P-Asserted-Identity: "My Name" <sip:[email protected]>
> Content-Length: 0
>
> From: Mark Holloway [mailto:[email protected]]
> Sent: Thursday, January 10, 2013 1:51 PM
> To: Heim, Dennis
> Cc: [email protected]
> Subject: Re: [cisco-voip] SIP CUBE Caller ID
>
> The FROM field should have a name in front of the phone number. (Like the
> bottom line of text in this capture). Can you send the SIP INVITE from CUCM
> > CUBE, and from CUBE to the PBX?
>
> <image001.png>
>
>
>
> On Jan 10, 2013, at 1:26 PM, "Heim, Dennis" <[email protected]> wrote:
>
>
> I am doing a sip integration to a pbx. We are not getting the caller id
> name/number when a call is placed form cisco to the pbx via the cube. We do
> see the caller id name in the debugs, but not on the phone display.
>
> Received:
> SIP/2.0 200 OK
> Call-ID: [email protected]
> CSeq: 101 INVITE
> From: <sip:[email protected]>;tag=7FA30F9C-154B
> To: <sip:[email protected]>;tag=SEC21-a58620a-1e58d20a-2-1e9kU4nFr1Kp
> Via: SIP/2.0/UDP 10.98.254.51:5060;branch=z9hG4bK456B7
> Contact: <sip:[email protected]:5060;maddr=10.210.88.39>
> Content-Type: application/sdp
> Content-Length: 367
> X-Siemens-Call-Type: ST-insecure
> Accept-Language: en;q=0.0
> Allow: REGISTER, INVITE, ACK, BYE, CANCEL, NOTIFY, REFER, INFO
> Date: Thu, 10 Jan 2013 17:20:27 GMT
> P-Asserted-Identity: "My Name" <sip:[email protected]>
>
> What am I missing?
> _______________________________________________
> cisco-voip mailing list
> [email protected]
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
> _______________________________________________
> cisco-voip mailing list
> [email protected]
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
> _______________________________________________
> cisco-voip mailing list
> [email protected]
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130110/16fd96f6/attachment-0001.html>
------------------------------
Message: 10
Date: Thu, 10 Jan 2013 17:19:26 -0500
From: Joel Perez <[email protected]>
To: "Heim, Dennis" <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [cisco-voip] SIP CUBE Caller ID
Message-ID:
<cabdwouhtfgdqdfo9jpxkjtukaoj_l-eug1e7bzxwzqutnxl...@mail.gmail.com>
Content-Type: text/plain; charset="windows-1252"
You should be able to but it depends on the version of IOS.
http://www.cisco.com/en/US/products/sw/voicesw/ps5640/products_configuration_example09186a0080982499.shtml
I havent tried it with CUBE, only with ACME but it should be the same or
similar.
Joel P.
On Thu, Jan 10, 2013 at 4:58 PM, Heim, Dennis <[email protected]> wrote:
> Is it possible with cube to take the PAI and copy it into the from field?*
> ***
>
> ** **
>
> *Call setup*
>
> * *
>
> INVITE sip:18077014@CUBE:5060 SIP/2.0****
>
> Via: SIP/2.0/TCP CUCM:5060;branch=z9hG4bK1eda32bbab882****
>
> From: "Cisco Phone" <sip:5987800@CUCM
> >;tag=2004325~37777082-f7ba-4cb2-8467-e286cea21f2e-88710674****
>
> To: <sip:18077014@CUBE>****
>
> Date: Thu, 10 Jan 2013 21:47:24 GMT****
>
> Call-ID: 50330380-ef136ec-1a038-2b3dd20a@CUCM****
>
> Supported: timer,resource-priority,replaces****
>
> Min-SE: 1800****
>
> User-Agent: Cisco-CUCM8.6****
>
> Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER,
> SUBSCRIBE, NOTIFY****
>
> CSeq: 101 INVITE****
>
> Expires: 180****
>
> Allow-Events: presence, kpml****
>
> Supported: X-cisco-srtp-fallback****
>
> Supported: Geolocation****
>
> Cisco-Guid: 1345520512-0000065536-0000033495-0725471754****
>
> Session-Expires: 1800****
>
> P-Asserted-Identity: "Cisco Phone" <sip:5987800@CUCM>****
>
> Remote-Party-ID: "Cisco Phone" <sip:5987800@CUCM
> >;party=calling;screen=yes;privacy=off****
>
> Contact: <sip:5987800@CUCM:5060;transport=tcp>****
>
> Max-Forwards: 69****
>
> Content-Type: application/sdp****
>
> Content-Length: 214****
>
> ** **
>
> *When ringing*
>
> ** **
>
> Received: ****
>
> SIP/2.0 180 Ringing****
>
> Call-ID: 1A53E43D-5AA611E2-A21DF143-739C4300@CUBE****
>
> CSeq: 101 INVITE****
>
> From: sip:5987800@CUCM;tag=809784F8-1B9F****
>
> To: <sip:18077014@SiemensOSV>;tag=SEC11-a58620a-1e58d20a-1-4197U1P1AG4o***
> *
>
> Via: SIP/2.0/UDP CUBE:5060;branch=z9hG4bK7B1AD5****
>
> Contact: <sip:18077014@SiemensOSV:5060;maddr=SiemensOSV>****
>
> Content-Type: application/sdp****
>
> Content-Length: 320****
>
> Allow: REGISTER, INVITE, ACK, BYE, CANCEL, NOTIFY, REFER, INFO****
>
> Allow-Events: CCNR****
>
> Date: Thu, 10 Jan 2013 21:47:24 GMT****
>
> P-Asserted-Identity: "Siemens User" <sip:18077014@SiemensOSV>****
>
> *From:* Mark Holloway [mailto:[email protected]]
> *Sent:* Thursday, January 10, 2013 4:23 PM
> *To:* Heim, Dennis
> *Cc:* Kenneth Hayes; [email protected]
>
> *Subject:* Re: [cisco-voip] SIP CUBE Caller ID****
>
> ** **
>
> What I was looking for, but didn't see in your TXT file, is the SIP INVITE
> from CUCM includes the calling party name in the FROM field to CUBE, and
> CUBE includes the same FROM name to Siemens. Assuming that is true, Siemens
> appears to be disregarding the name portion of the FROM field by not only
> failing to display it, but completely removing it in 1XX responses. It
> would be nice if it processed PAI but I think the name is being stripped
> and then Siemens just assumes there is no name for the call, as if PAI
> didn't exist.****
>
> ** **
>
> On Jan 10, 2013, at 3:56 PM, "Heim, Dennis" <[email protected]> wrote:**
> **
>
>
>
> ****
>
> This is outbound from CUCM. I dial the number it connects and the display
> just shows the dialed number, without the name. I did not have a display
> name on my phone, when I fixed that, the caller id name is visible to the
> siemens pbx.****
>
> ****
>
> The problem still is that I dial a number and it does not put in the name*
> ***
>
> ****
>
> The Cisco-Siemens direction, we see Cisco set the From with the name
> (From: ?Cisco Phone? sip:5987800@ip. We also see the P-Asserted-Identity
> set to ?Cisco Phone? sip:5987800@ip.****
>
> ****
>
> On the invite coming back from the siemens we see it set the From, only
> contain the number. However, the P-Asserted-Identity, contains the caller
> id name.****
>
> ****
>
> *From:* Heim, Dennis
> *Sent:* Thursday, January 10, 2013 3:46 PM
> *To:* 'Kenneth Hayes'; Voice_VT
> *Subject:* RE: [cisco-voip] SIP CUBE Caller ID****
>
> ****
>
> This is outbound from CUCM. I dial the number it connects and the display
> just shows the dialed number, with the name. I did not have a display name
> on my phone, when I fixed that, the caller id name is visible to the
> siemens pbx.****
>
> ****
>
> The problem still is that I dial a number and it does not put in the name.
> ****
>
> ****
>
> *From:* Kenneth Hayes [mailto:[email protected]]
> *Sent:* Thursday, January 10, 2013 3:29 PM
> *To:* Heim, Dennis
> *Subject:* Re: [cisco-voip] SIP CUBE Caller ID****
>
> ****
>
> This is inbound correct?****
>
> On Thu, Jan 10, 2013 at 2:55 PM, Heim, Dennis <[email protected]> wrote:
> ****
>
> It is showing in the PAI, but not the from field.****
>
> ****
>
> Call-ID: [email protected]****
>
> CSeq: 101 INVITE****
>
> Timestamp: 1357847526****
>
> Content-Length: 0****
>
> ****
>
> ****
>
> Jan 10 19:52:06.991:
> //184752/427582000000/SIP/Info/sipSPICheckResponseExt: INVITE response with
> no RSEQ - disable IS_REL1XX****
>
> Jan 10 19:52:06.991: //184752/427582000000/SIP/State/sipSPIChangeState:
> 0x2472CB8 : State change from (STATE_SENT_INVITE, SUBSTATE_NONE) to
> (STATE_RECD_PROCEEDING, SUBSTATE_PROCEEDING_PROCEEDING)****
>
> Jan 10 19:52:07.119: //-1/xxxxxxxxxxxx/SIP/Info/HandleUdpIPv4SocketReads:
> Msg enqueued for SPI with IP addr: [10.98.88.38]:5060,
> local_address:[10.98.254.51]****
>
> Jan 10 19:52:07.119:
> //-1/xxxxxxxxxxxx/SIP/Info/ccsip_process_sipspi_queue_event:
> ccsip_spi_get_msg_type returned: 2 for event 1****
>
> Jan 10 19:52:07.119:
> //-1/xxxxxxxxxxxx/SIP/Transport/sipTransportProcessNWNewConnMsg: context=0x0
> ****
>
> Jan 10 19:52:07.119:
> //-1/xxxxxxxxxxxx/SIP/Info/ccsip_new_msg_preprocessor: Checking Invite
> Dialog****
>
> Jan 10 19:52:07.119: //184752/427582000000/SIP/Msg/ccsipDisplayMsg:****
>
> Received:****
>
> SIP/2.0 180 Ringing****
>
> Call-ID: [email protected]****
>
> CSeq: 101 INVITE****
>
> From: sip:[email protected];tag=802E4C74-179B****
>
> To: <sip:[email protected]>;tag=SEC11-a58620a-1e58d20a-1-zvE1E7A74E0q**
> **
>
> Via: SIP/2.0/UDP 10.98.254.51:5060;branch=z9hG4bK5C1C8C****
>
> Contact: <sip:[email protected]:5060;maddr=10.98.88.38>****
>
> Date: Thu, 10 Jan 2013 19:52:29 GMT****
>
> P-Asserted-Identity: "My Name" <sip:[email protected]>****
>
> Content-Length: 0****
>
> ****
>
> *From:* Mark Holloway [mailto:[email protected]]
> *Sent:* Thursday, January 10, 2013 1:51 PM
> *To:* Heim, Dennis
> *Cc:* [email protected]
> *Subject:* Re: [cisco-voip] SIP CUBE Caller ID****
>
> ****
>
> The FROM field should have a name in front of the phone number. (Like the
> bottom line of text in this capture). Can you send the SIP INVITE from
> CUCM > CUBE, and from CUBE to the PBX? ****
>
> ****
>
> <image001.png>****
>
> ****
>
> ****
>
> ****
>
> On Jan 10, 2013, at 1:26 PM, "Heim, Dennis" <[email protected]> wrote:**
> **
>
> ****
>
> I am doing a sip integration to a pbx. We are not getting the caller id
> name/number when a call is placed form cisco to the pbx via the cube. We do
> see the caller id name in the debugs, but not on the phone display.****
>
> ****
>
> Received:****
>
> SIP/2.0 200 OK****
>
> Call-ID: [email protected]****
>
> CSeq: 101 INVITE****
>
> From: <sip:[email protected]>;tag=7FA30F9C-154B****
>
> To: <sip:[email protected]>;tag=SEC21-a58620a-1e58d20a-2-1e9kU4nFr1Kp*
> ***
>
> Via: SIP/2.0/UDP 10.98.254.51:5060;branch=z9hG4bK456B7****
>
> Contact: <sip:[email protected]:5060;maddr=10.210.88.39>****
>
> Content-Type: application/sdp****
>
> Content-Length: 367****
>
> X-Siemens-Call-Type: ST-insecure****
>
> Accept-Language: en;q=0.0****
>
> Allow: REGISTER, INVITE, ACK, BYE, CANCEL, NOTIFY, REFER, INFO****
>
> Date: Thu, 10 Jan 2013 17:20:27 GMT****
>
> P-Asserted-Identity: "My Name" <sip:[email protected]>****
>
> ****
>
> What am I missing?****
>
> _______________________________________________
> cisco-voip mailing list
> [email protected]
> https://puck.nether.net/mailman/listinfo/cisco-voip****
>
> ****
>
>
> _______________________________________________
> cisco-voip mailing list
> [email protected]
> https://puck.nether.net/mailman/listinfo/cisco-voip****
>
> ****
>
> _______________________________________________
> cisco-voip mailing list
> [email protected]
> https://puck.nether.net/mailman/listinfo/cisco-voip****
>
> ** **
>
> _______________________________________________
> cisco-voip mailing list
> [email protected]
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130110/53da0d8b/attachment-0001.html>
------------------------------
Message: 11
Date: Thu, 10 Jan 2013 18:08:02 -0800
From: Me <[email protected]>
To: [email protected]
Subject: [cisco-voip] Simulate SIP error code 408 and 603 from CUBE
Message-ID:
<CAGBqMBjocfDmaMijThnXFWXCtF=_qsbxfuh+eyvyntpcopz...@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
Is there a way to simulate SIP error code 408 (Not Available) and 603
(Reject) from a Cisco CUBE? Such as making a call to a number router
returns the SIP errors.
Regards,
Dave
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130110/5ebd8f05/attachment-0001.html>
------------------------------
Message: 12
Date: Thu, 10 Jan 2013 22:30:41 -0500
From: Mark Holloway <[email protected]>
To: Me <[email protected]>
Cc: [email protected]
Subject: Re: [cisco-voip] Simulate SIP error code 408 and 603 from
CUBE
Message-ID: <[email protected]>
Content-Type: text/plain; charset="iso-8859-1"
You need a SIP device to originate the call to CUBE and something on the "other
side" of CUBE to generate the 603 message. For SIP 408, this usually occurs
when a SIP INVITE Timeout occurs. You could configure CUBE to forward to some
null device to the INVITE will timeout and CUBE will send 408 back to the
originating party.
SIPp and X-Lite work well for this sort of thing.
On Jan 10, 2013, at 9:08 PM, Me <[email protected]> wrote:
> Is there a way to simulate SIP error code 408 (Not Available) and 603
> (Reject) from a Cisco CUBE? Such as making a call to a number router
> returns the SIP errors.
>
> Regards,
> Dave
> _______________________________________________
> cisco-voip mailing list
> [email protected]
> https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130110/5de09708/attachment-0001.html>
------------------------------
Message: 13
Date: Fri, 11 Jan 2013 16:10:37 +0200
From: Ahmed Elnagar <[email protected]>
To: "'VOIP Group '" <[email protected]>
Subject: [cisco-voip] Cisco Unified IP Phone Local Kernel System Call
Input Validation Vulnerability
Message-ID: <[email protected]>
Content-Type: text/plain; charset="us-ascii"
I think someone was asking about the below a couple of days
Regards,
Ahmed Elnagar | Unified Communication Team Leader | CCIE #24697, Voice
Description: Description: Description: MS Green
From: [email protected]
[mailto:[email protected]]
Sent: Thursday, January 10, 2013 3:33 PM
To: Ahmed Elnagar
Subject: Cisco Notification Alert -UC-Products-01/10/2013 13:32 GMT
Cisco Notification Service Alert:
____________________________________________________________________________
____
Security Advisories & Responses for All Voice and Unified Communications
Title
Cisco Unified IP Phone Local Kernel System Call Input Validation
Vulnerability
<http://www.cisco.com/en/US/products/csa/cisco-sa-20130109-uipphone.html>
Description
Cisco Unified IP Phones 7900 Series versions 9.3(1)SR1 and prior contain an
arbitrary code execution vulnerability that could allow a local attacker to
execute code or modify arbitrary memory with elevated privileges. This
vulnerability is due to a failure to properly validate input passed to
kernel system calls from applications running in userspace. An attacker
could exploit this issue by gaining local access to the device using
physical access or authenticated access using SSH and executing an
attacker-controlled binary that is designed to exploit the issue. Such an
attack would originate from an unprivileged context. Ang Cui initially
reported the issue to the Cisco Product Security Incident Response Team
(PSIRT). On November 6, 2012, the Cisco PSIRT disclosed this issue in Cisco
bug ID CSCuc83860 (registered customers only) Release Note Enclosure.
Subsequently, Mr. Cui has spoken at several public conferences and has
performed public demonstrations of a device being compromised and used as a
listening device. Mitigations are available to help reduce the attack
surface of affected devices. See the &quo;Details&quo; section of this
security advisory and the accompanying Cisco Applied Mitigation Bulletin
(AMB) for additional information. This advisory is available at the
following link:
http://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-s
a-20130109-uipphone
Date
09-JAN-2013
For more information; you can visit Cisco Security Advisories
<http://www.cisco.com/en/US/products/products_security_advisories_listing.ht
ml> & Responses index.
____________________________________________________________________________
____
To unsubscribe this notification click here
<http://www.cisco.com/cisco/support/notifications/addedit.html?notiId=186498
>
Help us improve this facility. To give feedback click here
<http://www.cisco.com/cisco/support/notifications.html#feedback>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130111/bb4a8717/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 2768 bytes
Desc: not available
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130111/bb4a8717/attachment-0001.jpg>
------------------------------
_______________________________________________
cisco-voip mailing list
[email protected]
https://puck.nether.net/mailman/listinfo/cisco-voip
End of cisco-voip Digest, Vol 111, Issue 10
*******************************************
