cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
3448
Views
3
Helpful
7
Replies

Connected Party Name Pass Through via PAI on CUBE

daniel.bloom
Level 1
Level 1

I have a CUBE setup between Cisco CUCM (v9.1) and an Avaya PBX to allow extension dialling between both systems. Calls are established ok, however the connected party information is not being passed from CUCM to the Avaya by the CUBE. CUCM sends the connected party information in the PAI header on the ringing and 200OK messages however CUBE is stripping this header off when forwarding the ringing or 200OK messages onto the Avaya PBX.

 

An example of the ringing messages are below (names have been modified). The first message is from CUCM to CUBE and the second is sent from CUBE to remote PBX

 

Aug 20 02:19:44.817: //956/C1B6C9DE841B/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 180 Ringing
Via: SIP/2.0/TCP 10.140.128.2:5060;branch=z9hG4bK3A926EA
From: <sip:anonymous@anonymous.invalid>;tag=8807E4-1A48
To: <sip:7403@10.100.131.11>;tag=3704627~bf4527d6-3b32-4834-b6ec-60bc65e4cbf9-44960986
Date: Thu, 20 Aug 2015 02:19:44 GMT
Call-ID: C1B7B41A-461811E5-8421F107-51381D77@10.140.128.2
CSeq: 101 INVITE
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
Allow-Events: presence
Supported: X-cisco-srtp-fallback
Supported: Geolocation
P-Asserted-Identity: "Called Party Name" <sip:7403@10.100.131.11>
Contact: <sip:7403@10.100.131.11:5060;transport=tcp>
Content-Length: 0


Aug 20 02:19:44.818: //955/C1B6C9DE841B/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 180 Ringing
Via: SIP/2.0/TCP 10.216.35.221;branch=z9hG4bK0AD823DCFFFFFFFFDC2B65820438864863-AP
From: "Anonymous" <sip:anonymous@anonymous.invalid>;tag=0d6aa38484ee5180985564d29500
To: sip:7403@customer.com;tag=880803-FBA
Date: Thu, 20 Aug 2015 02:19:44 GMT
Call-ID: 0d6aa38484ee5181985564d29500
CSeq: 1 INVITE
Require: 100rel
RSeq: 8103
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
Contact: <sip:7403@10.140.128.2:5060;transport=tcp>
Record-Route: <sip:2a061603@10.216.35.221;transport=tcp;lr>
Server: Cisco-SIPGateway/IOS-15.2.2.S1
History-Info: <sip:77403@customer.com>;index=1,"77403" <sip:77403@customer.com>;index=1.1
Content-Length: 0

 

The relevant CUBE config is below.

 

voice service voip
 allow-connections sip to sip
 sip
  session transport tcp
  min-se 1200 session-expires 1200
  asserted-id pai
  history-info
  midcall-signaling passthru
  privacy-policy passthru
  pass-thru headers unsupp

 

sip-ua
 no remote-party-id
 retry invite 2
 timers trying 250
 connection-reuse


Does anyone know how to configure CUBE to pass the connected party information onto the outgoing SIP messages?

 

1 Accepted Solution

Accepted Solutions

daniel.bloom
Level 1
Level 1

Turns out this is caused by a bug in IOS. CUBE needs to be running IOS 15.5(3)M or later to correctly handle the PAI header for connected party information.

View solution in original post

7 Replies 7

Jonathan Schulenberg
Hall of Fame
Hall of Fame

Have you tried removing 'asserted-id pai' under voice service voip, sip? The documentation indicates that command is used to translate FROM P-Preferred Identity (PPID) TO the P-Asserted Identity (PAID) header. My guess is that since PPID is blank, that command is forcing CUBE to clear the PAID header on the other side.

http://www.cisco.com/c/en/us/td/docs/ios/voice/cube/configuration/guide/vb_book/vb_book/vb_9397.html

Hi Jonathan,

 

I will test this and let you know.

Unfortunately this didn't have an effect. I have opened this with Cisco TAC so will see what they discover.

Hi,

 

The PAI should be sent from CUCM to CUBE in INVITE message. Based on your config, CUBE will pass PAI in INVITE message to Avaya if received from CUCM

 

Did you enable "Asserted-Identity" in CUCM SIP Trunk? If not please enable it and share the full debug from the CUBE.

Hi Mohammed,

 

We are talking about connected party information for calls originated from the Avaya PBX not calling party information. The issue is not on CUCM as the connected party information is seen on the Ringing and 200 OK messages from CUCM however CUBE is stripping it when sending to the Avaya. The scenario you describe works as expected, by this I mean the calling party information contained in the PAI of an Invite is being passed through successfully.

 

Daniel

daniel.bloom
Level 1
Level 1

Turns out this is caused by a bug in IOS. CUBE needs to be running IOS 15.5(3)M or later to correctly handle the PAI header for connected party information.

Hey Daniel,

Long time. Hope you are well. Thanks for updating this..Great stuff..

Please rate all useful posts
Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: