When the Calling Party Information Retrieval feature is enabled, if the IAM received from the SS7 side does not contain a Calling Party Number -or- the Calling Party Category is set to unknown, the IMG 2020 will send an INR (Information Request) back to the SS7 network requesting the Calling Party Number and/or the Calling Party Category. Once the SS7 side receives the INR, it will send back an INF (Information Message) with the requested parameters. The IMG 2020 then receives the parameters and uses this information along with the information in the original IAM to generate an INVITE message to the SIP or H.323 network which includes the additional parameters. Refer to the information below.
Call Flow
When the feature is enabled, the IMG 2020 will send back an INR (Information Request) message if the IAM does not contain the Calling Party Number (CPN) or the Calling Party Category (CPC) = unknown. Once the information is retrieved from the SS7 side, the IMG 2020 will add the CPN and CPC information into the outgoing INVITE message on the SIP side. Refer to the Call Flow below.
Call Trace (SS7 to SIP)
21:37:06.747 CALL(SS7) (00:00002:00)
RCVD: STK: 0 PRI: 00
DPC: 0-0-1 OPC: 7-7-7
SLS: 0x04 CIC: 00500 (0x01f4)
IAM [0048000003020a08031095363303099900]
21:37:06.747 CALL(SS7) (00:00002:00) RCVD IAM from (0x383f:0x1:500)
21:37:06.747 CALL(SS7) (00:00002:00) Leg 0 associated with LTS(161)(span 1 chan 1)
21:37:06.747 CALL(SS7) (00:00002:00) SENT Setup Ind w/info (0x383f:0x1:500) to L4
21:37:06.747 CALL(L4) (00:00002:00) RCVD Setup Ind from SS7
21:37:06.747 CALL(L4) (00:00002:00) SENT RFS to GCL
21:37:06.747 CALL(GCL) (00:00002:00) RCVD RFS DN=[596333309099] ANI=[] from L4
21:37:06.747 CALL(GCL) (00:00002:00) ANI APRI=[15],SI=[15],Category=[0]
21:37:06.747 CALL(GCL) (00:00002:00) DN NOA=[3]
21:37:06.747 CALL(GCL) (00:00002:00) Incoming Channel Group = 2 [ss7_51_out]
21:37:06.747 CALL(GCL) (00:00002:00) SENT Make Call Request to GCL
21:37:06.747 CALL(GCL) (00:00002:01) SENT Route Control to L4
21:37:06.747 CALL(L4) (00:00002:00) RCVD RFS response from GCL
21:37:06.747 CALL(L4) (00:00002:00) RCVD Route Control from GCL
21:37:06.747 CALL(L4) (00:00002:00) Accessing Route Table 15
21:37:06.747 CALL(GCL) (00:00002:01) RCVD Route Control Ack (Mid Stream Router) from L4
21:37:06.747 CALL(GCL) (00:00002:01) Outgoing Channel Group = 3 [sipp]
21:37:06.747 CALL(GCL) (00:00002:01) SENT Route Control to L4
21:37:06.747 CALL(L4) (00:00002:01) RCVD Route Control from GCL
21:37:06.747 CALL(L4) (00:00002:01) Accessing Resource Table 1
21:37:06.747 CALL(L4) (00:00002:01) Resource Group ID is 1
21:37:06.747 CALL(L4) (00:00002:01) Hunting Algorithm is Round Robin
21:37:06.757 CALL(L4) (00:00002:01) SENT Ppl Ev. Ind to GCL
21:37:06.757 CALL(GCL) (00:00002:01) RCVD CPE of ADDRESS INFO from L4
21:37:06.757 CALL(GCL) (00:00002:01) Leg 1 associated with LTS(1025)(span 4096 chan 1)
21:37:06.757 CALL(GCL) (00:00002:00) SENT Ppl Ev. Req to L4
21:37:06.757 CALL(L4) (00:00002:00) SENT Ppl Ev. Req to SS7
21:37:06.757 CALL(SS7) (00:00002:00) RCVD PPL Event Request (0x1:0x383f:500) from L4
21:37:06.757 CALL(SS7) (00:00002:00)
SENT: STK: 0 PRI: 00
DPC: 7-7-7 OPC: 0-0-1
SLS: 0x1f4 CIC: 00500 (0x01f4)
INR [090000]
21:37:06.757 CALL(SS7) (00:00002:00) SENT INR to (0x1:0x383f:500)
21:37:08.807 CALL(SS7) (00:00002:00)
RCVD: STK: 0 PRI: 00
DPC: 0-0-1 OPC: 7-7-7
SLS: 0x00 CIC: 00500 (0x01f4)
INF [2300010a070311055869032209010d00]
21:37:08.807 CALL(SS7) (00:00002:00) RCVD INF from (0x383f:0x1:500)
21:37:08.807 CALL(L4) (00:00002:00) SENT Ppl Ev. Ind to GCL
21:37:08.807 CALL(GCL) (00:00002:01) SENT Ppl Ev. Req to L4
21:37:08.807 CALL(L4) (00:00002:01) SENT Outseize Ctrl to SIP
21:37:08.817 CALL(SIP) (00:00002:01) RCVD Outseize Ctrl from L4
21:37:08.817 CALL(SIP) (00:00002:01) SENT Route Control to L4
21:37:08.817 CALL(L4) (00:00002:01) RCVD Route Control from SIP
21:37:08.817 CALL(L4) (00:00002:01) Accessing GatewayId to IP Tables
21:37:08.817 CALL(L4) (00:00002:01) Gateway ID is 1026
21:37:08.817 CALL(L4) (00:00002:01) SENT Route Control Ack to SIP
21:37:08.817 CALL(SIP) (00:00002:01) RCVD Route Control Ack from L4
21:37:08.817 CALL(SIP) (00:00002:01) Session Group Profile ID is 8
21:37:08.817 CALL(SIP) (00:00002:01) SENT Route Control to L4
21:37:08.817 CALL(L4) (00:00002:01) RCVD Route Control from SIP
21:37:08.817 CALL(L4) (00:00002:01) Accessing IP Bearer Profiles
21:37:08.817 CALL(L4) (00:00002:01) Profile Id 1 (RG 769)
21:37:08.817 CALL(L4) (00:00002:01) SENT Route Control Ack to SIP
21:37:08.817 CALL(SIP) (00:00002:01) RCVD Route Control Ack from L4
21:37:08.817 CALL(SIP) (00:00002:01) REM TP port=5060 transport:0
21:37:08.817 CALL(SIP) (00:00002:01) SENT INVITE W/SDP to 10.129.39.101:5060 Cseq:1
21:37:08.817 CALL(SIP) (00:00002:01) with R-URI: 10.129.39.101:5060 UDP
21:37:08.817 CALL(SIP) (00:00002:01) and Call-id: 7712-401-612201121378-img51-0-10.129.39.51
21:37:08.817 CALL(SIP) (00:00002:01)
<--- [10.129.39.101, 5060 <- 10.129.39.51, 5060]
INVITE sip:596333309099@10.129.39.101:5060 SIP/2.0\r\n
Via: SIP/2.0/UDP 10.129.39.51:5060;rport;branch=z9hG4bK-
32d8-1310506628-4998-501\r\n
Call-ID: 7712-401-612201121378-img51-0-10.129.39.51\r\n
CSeq: 1 INVITE\r\n
Max-Forwards: 70\r\n
To: <sip:596333309099@10.129.39.101:5060>\r\n
From: "5085963022"<sip:5085963022;cpc=test@10.129.39.51>
;tag=95ffcd055e0f78f7d5d397020e89288d5b8d86a9\r\n
User-Agent: Dialogic-SIP/10.5.3.223 img51 0\r\n
Contact: <sip:5085963022@10.129.39.51:5060>\r\n
Allow: INVITE, BYE, REGISTER, ACK, OPTIONS, CANCEL, SUBS
CRIBE, NOTIFY, INFO, REFER, UPDATE\r\n
Supported: path, replaces, timer, tdialog\r\n
Session-Expires: 1800\r\n
Expires: 300\r\n
Organization: Dialogic\r\n
Content-Type: application/sdp\r\n
Content-Length: 164\r\n
\r\n
v=0\r\n
o=Dialogic_SDP 1 0 IN IP4 10.129.39.51\r\n
s=Dialogic-SIP\r\n
c=IN IP4 10.129.39.52\r\n
t=0 0\r\n
m=audio 8004 RTP/AVP 0\r\n
a=rtpmap:0 PCMU/8000\r\n
a=silenceSupp:off - - - -\r\n
21:37:08.937 CALL(SIP) (00:00002:01) RCVD 100 Trying from 10.129.39.101:5060 udp CSeq:1 Msg Size:394
21:37:08.937 CALL(SIP) (00:00002:01)
---> [10.129.39.101, 5060 -> 10.129.39.51, 5060]
SIP/2.0 100 Trying\r\n
Via: SIP/2.0/UDP 10.129.39.51:5060;rport;branch=z9hG4bK-
32d8-1310506628-4998-501\r\n
From: "5085963022"<sip:5085963022;cpc=test@10.129.39.51>
;tag=95ffcd055e0f78f7d5d397020e89288d5b8d86a9\r\n
To: <sip:596333309099@10.129.39.101:5060>;tag=41\r\n
Call-ID: 7712-401-612201121378-img51-0-10.129.39.51\r\n
CSeq: 1 INVITE\r\n
Contact: <sip:10.129.39.101:5060;transport=UDP>\r\n
Content-Length: 0\r\n
\r\n
21:37:09.437 CALL(SIP) (00:00002:01) RCVD 180 Ringing WO/SDP from 10.129.39.101:5060 udp CSeq:1 Msg Size:395
21:37:09.437 CALL(SIP) (00:00002:01)
---> [10.129.39.101, 5060 -> 10.129.39.51, 5060]
SIP/2.0 180 Ringing\r\n
Via: SIP/2.0/UDP 10.129.39.51:5060;rport;branch=z9hG4bK-
32d8-1310506628-4998-501\r\n
From: "5085963022"<sip:5085963022;cpc=test@10.129.39.51>
;tag=95ffcd055e0f78f7d5d397020e89288d5b8d86a9\r\n
To: <sip:596333309099@10.129.39.101:5060>;tag=41\r\n
Call-ID: 7712-401-612201121378-img51-0-10.129.39.51\r\n
CSeq: 1 INVITE\r\n
Contact: <sip:10.129.39.101:5060;transport=UDP>\r\n
Content-Length: 0\r\n
\r\n
21:37:09.437 CALL(SIP) (00:00002:01) SENT Outseize Ack to L4
21:37:09.437 CALL(SIP) (00:00002:01) SENT Alerting to L4
21:37:09.437 CALL(L4) (00:00002:01) RCVD Outseize ACK from SIP
21:37:09.437 CALL(L4) (00:00002:01) RVCD Alerting from SIP
21:37:09.437 CALL(GCL) (00:00002:00) SENT Connect Tone to L4
21:37:09.437 CALL(L4) (00:00002:00) RCVD Connect Tone from GCL
21:37:09.437 CALL(L4) (00:00002:00) SENT Request DSP Service to SYSRM
21:37:09.437 CALL(MED) (00:00002:00) Transmitting tone 0x2 on (0x0,0x3,0x0)
21:37:09.437 CALL(MED) (00:00002:00) RCVD OUTPULSE CP from L4
21:37:09.437 CALL(GCL) (00:00002:00) SENT Connect w/Pad Response to L4
21:37:09.437 CALL(L4) (00:00002:01) SENT Alerting to L4
21:37:09.437 CALL(L4) (00:00002:00) SENT Alerting to SS7
21:37:09.437 CALL(SIP) (00:00002:01) RCVD Host Connect from L4
21:37:09.437 CALL(SS7) (00:00002:00) RCVD Alerting (0x1:0x383f:500) from L4
21:37:09.437 CALL(SS7) (00:00002:00)
SENT: STK: 0 PRI: 00
DPC: 7-7-7 OPC: 0-0-1
SLS: 0x1f4 CIC: 00500 (0x01f4)
ACM [040100]
21:37:09.437 CALL(SS7) (00:00002:00) SENT ACM to (0x1:0x383f:500)
21:37:09.937 CALL(SIP) (00:00002:01) RCVD 200 OK INVITE W/SDP from 10.129.39.101:5060 udp CSeq:1 Msg Size:595
21:37:09.937 CALL(SIP) (00:00002:01)
---> [10.129.39.101, 5060 -> 10.129.39.51, 5060]
SIP/2.0 200 OK\r\n
Via: SIP/2.0/UDP 10.129.39.51:5060;rport;branch=z9hG4bK-
32d8-1310506628-4998-501\r\n
From: "5085963022"<sip:5085963022;cpc=test@10.129.39.51>
;tag=95ffcd055e0f78f7d5d397020e89288d5b8d86a9\r\n
To: <sip:596333309099@10.129.39.101:5060>;tag=41\r\n
Call-ID: 7712-401-612201121378-img51-0-10.129.39.51\r\n
CSeq: 1 INVITE\r\n
Contact: <sip:10.129.39.101:5060;transport=UDP>\r\n
Content-Type: application/sdp\r\n
Content-Length: 170\r\n
\r\n
v=0\r\n
o=Excel_SDP 0 0 IN IP4 10.129.39.101\r\n
s=Excel-Open-SIP\r\n
c=IN IP4 10.129.39.101\r\n
t=0 0\r\n
m=audio 6000 RTP/AVP 0 101\r\n
a=fmtp:101 0-15\r\n
a=rtpmap:101 telephone-event/8000
21:37:09.937 CALL(SIP) (00:00002:01) Session Refresh is not Needed
21:37:09.937 CALL(SIP) (00:00002:01) SENT ACK WO/SDP to 10.129.39.101:5060 Cseq:1
21:37:09.937 CALL(SIP) (00:00002:01) with R-URI: 10.129.39.101:5060 UDP
21:37:09.937 CALL(SIP) (00:00002:01)
<--- [10.129.39.101, 5060 <- 10.129.39.51, 5060]
ACK sip:10.129.39.101:5060 SIP/2.0\r\n
Via: SIP/2.0/UDP 10.129.39.51:5060;rport;branch=z9hG4bK-
80-1310506629-4998-501\r\n
Call-ID: 7712-401-612201121378-img51-0-10.129.39.51\r\n
CSeq: 1 ACK\r\n
Max-Forwards: 70\r\n
To: <sip:596333309099@10.129.39.101:5060>;tag=41\r\n
From: <sip:5085963022;cpc=test@10.129.39.51>;tag=95ffcd0
55e0f78f7d5d397020e89288d5b8d86a9\r\n
User-Agent: Dialogic-SIP/10.5.3.223 img51 0\r\n
Content-Length: 0\r\n
\r\n
21:37:09.937 CALL(SIP) (00:00002:01) m line (audio) codec list: 0 101
21:37:09.937 CALL(SIP) (00:00002:01) RTP Type: 101, name: telephone-event, clk: 8000
21:37:09.937 CALL(SIP) (00:00002:01) SENT CDR Msg Event to L4
21:37:09.937 CALL(SIP) (00:00002:01) Set media src IP 10.129.39.52:8004
21:37:09.937 CALL(SIP) (00:00002:01) Set media dst IP 10.129.39.101:6000
21:37:09.937 CALL(SIP) (00:00002:01) CODEC Negotiation Priority LOCAL
21:37:09.937 CALL(SIP) (00:00002:01) Set media PLD ID 2
21:37:09.937 CALL(SIP) (00:00002:01) Set media PLD Size 20, Multiplier:4
21:37:09.937 CALL(SIP) (00:00002:01) RFC 2833 DTMF Relay Enabled, pld type 101
21:37:09.937 CALL(SIP) (00:00002:01) Set Fax Type to Bypass
21:37:09.937 CALL(SIP) (00:00002:01) Source Port Validation : Enabled
21:37:09.937 CALL(SIP) (00:00002:01) SENT L3-L3 Outseize Ctrl to VPPL
21:37:09.937 CALL(L4) (00:00002:01) SENT CDR Msg Event to GCL
21:37:09.937 CALL(IP) (00:00002:01) RCVD Outseize ([vts 1] [m0.1.1]) from L3P (span 4096 chan 1)
21:37:09.937 CALL(IP) (00:00002:01) RTP: (Src) 10.129.39.52:8004
21:37:09.937 CALL(IP) (00:00002:01) RTP: (Dst) 10.129.39.101:6000
21:37:09.937 CALL(GCL) (00:00002:01) RCVD CDR Msg Event from L4
21:37:09.937 CALL(IP) (00:00002:01) VoIP Codec is G711Mulaw; Payload Size is 20 ms
21:37:09.937 CALL(IP) (00:00002:01) Fax Mode is Bypass, Modem Mode is Bypass
21:37:09.957 CALL(IP) (00:00002:01) SENT Outseize ACK (toPvid: x66) to L3P
21:37:09.957 CALL(SIP) (00:00002:01) RCVD Outseize Ack from VPPL
21:37:09.957 CALL(SIP) (00:00002:01) SENT Connect to L4
21:37:09.957 CALL(SIP) (00:00002:01) RCVD Cut Thru from VPPL
21:37:09.957 CALL(SIP) (00:00002:01) RCVD Connect from VPPL
21:37:09.957 CALL(L4) (00:00002:01) RCVD Connect from SIP
21:37:09.957 CALL(L4) (00:00002:01) SENT CPE of ANSWER to GCL
21:37:09.957 CALL(L4) (00:00002:01) SENT connect_1way: r_ts=0xa1 l_ts=0x401 to TSI
21:37:09.957 CALL(L4) (00:00002:00) SENT connect_1way: r_ts=0x401 l_ts=0xa1 to TSI
Configuration
Below are instructions on how to configure the IMG 2020 to request Calling Party information from the SS7 side and then interwork the requested information into the SIP side. Before configuring, the IMG 2020 must have an initial configuration created on it. Refer to the Basic Configurations procedure and verify the basic functionality has been configured. In the procedure, the incoming side is SS7 and the outgoing side is SIP. Refer to the Configure SS7 and Configure SIP (Single SIP IP) or Configure SIP (Multiple SIP IP) for information on configuring these signaling protocols.
Create SIP SGP
Configure a SIP SGP object. The profile being created will be added to the drop down list in the SIP Profile field of the external gateway that will be created.
Right click on the Profiles object and select New SIP SGP. Once SIP SGP pane is created, change the SIP Profile Id field to something other than 0 by selecting a different ID from the drop down menu. This will allow user to edit the SIP Profile (SGP) object.
Enter a name in the SIP Profile Name field that identifies the SIP Profile (SGP) being created. In this procedure, the SIP Profile (SGP) object was labeled SIP_Profile_CPR. Refer to SIP Profile - SGP topic for more information on configuring this object.
Create SIP Gateway
Create an External Network Element and configure an external gateway under it. This gateway will be the gateway that the IMG 2020 will communicate with for the Calling Party Retrieval Interworking feature.
Right click on IMG EMS and select New External Network Elements. No configuration is needed here. The External Network Element pane is a container object to multiple external entities in the network. Refer to External Network Elements topic for more information.
Right click on the External Network Elements object and select New External Gateways. Again, no configuration is accomplished here. Refer to External Gateways object for more information.
Right click on External Gateways object and select New External Gateway. Enter a name to identify this gateway, modify the Gateway Signaling Protocol field to display SIP. In this procedure the External Gateway was labeled CPR_GW.
Enter the IP address of the Gateway in the Gateway IP Address field. In the SIP Profile field, select from drop down menu a SIP Profile (SGP) created earlier. Refer to screen capture below.
Refer to the External Gateway topic for more information.
Create SIP or H.323 Channel Group
Right click on the Routing Configuration object and select New Channel Groups. The Channel Groups object is a container or parent object. No configuration is needed within this object. For more information, refer to the Channel Groups topic.
Right click on Channel Groups object and select New Channel Group. Set theSignaling Type field to either SIP or H.323. and enter a name for this channel group.
Select Enabled from the drop down menu in the CPN/CPC retrieval via INR/INF field. Refer to screen capture below. The capture displays the last few fields of the Channel Group object.
SIP and H323 Channel Group
Refer to Channel Group topic for more information on configuring a SIP Channel Group.
Right click on the SIP or H.323 channel group created and select New IP Network Element. Select the H.323 or SIP gateway created earlier from the drop down menu in the IP Network Element field.
Create SS7 Channel Group
Right click on Channel Groups object again and select New Channel Group. Set the Signaling Type field to SS7 and enter a name for this channel group. For more information on configuring this object, refer to the Channel Group topic.
Under the SS7 Channel Group, the ISUP Group and CICs will need to be configured. Refer top the ISUP Group and IMG 1010 - Circuit Group topics for information on configuring these objects.
At this point the feature has been configured. Routing and translations can now be configured.
Additional Information
The call flows supported are from SS7 to SIP or from SS7 to H.323 only.
The feature is by default set to Disabled. The feature is enabled through ClientView in either the SIP or H.323 Channel Group object. Within this object is a field labeled CPN/CPC retrieval via INR/INF. The feature is enabled and disabled through this field.
If the field SIP ISUP CPC Mapping in the SIP Profiles (SGP) object is set to Disable, CPC information will not be sent to the SIP side. (From Header)
When feature is enabled and the IMG 2020 receives an IAM that contains a Calling Party's Number, the IMG 2020 will NOT send INR message back to SS7 network.
When the feature is enabled, on receipt of IAM that does NOT contain the Calling Party’s Number and the Calling Party’s category is “unknown” (0000 0000), the IMG 2020 will send an INR message back to the SS7 network requesting the Calling party number and Calling party’s category information.
If the INF comes back from the SS7 side with a Calling party number and/or the Calling party’s category, the IMG 2020 will add the CPN and/or update CPC to the already-received IAM and use all this information to create the INVITE on the SIP leg.
If the INF comes back from the SS7 side with a Calling party number and/or the Calling party’s category, the IMG 2020 will add the CPN and/or update CPC to the already-received IAM and use all this information to create the SETUP message on the H.323 leg.
If the INF comes back from the SS7 side without the Calling party number and/or the Calling party’s category, the IMG 2020 will send an INVITE or SETUP message without a Calling party number.
In the case where SIP Privacy is enabled, the mapping of the received Calling party number in the INF to the SIP side will follow the normal privacy rules as if the Calling party number was received in the IAM.