Configuring SIP Privacy

 

Overview:

SIP Privacy is configured differently depending on which software version is being used. Select from the two procedures below depending on which software version you are using on the IMG.

10.5.x:

In software 10.5.x SIP Privacy needs to be configured in three separate places in ClientView for SIP Privacy in the IMG to work correctly. Follow procedure below on how to accomplish this.

 

  1. The first object in ClientView that will enable SIP Privacy is under the SIP Signaling Stack. (Physical IMG > Signaling > SIP Signaling). Enabling SIP Privacy in this object pane will enable the SIP Privacy feature on the SIP signaling stack on the IMG. Select one of the options from the drop down menu of the Privacy Support field. All calls will be handled according to this setting regardless of other SIP Privacy settings on an individual External Gateway or ISDN/ISUP Group.

 

 

SC_SIP_Privacy_SIPSIG_10.5.0.png

 

 

 

13:24:20.718 SIP (W)   

                        <--- [10.127.33.123, 5060 <- 10.127.33.127, 5060]

                       INVITE sip:8001234567@10.127.33.123:5060 SIP/2.0

                       Via: SIP/2.0/UDP 10.127.33.127:5060;rport;branch=z9hG4bK

                       -4371-1206033860-19991-132

                       Call-ID: 43ff-406-2202008172420-T1_IMG1-1-10.129.44.240

                       

                       CSeq: 1 INVITE

                       Max-Forwards: 70

                       To: <sip:8001234567@10.127.33.123:5060>

                       From: anonymous<sip:anonymous@anonymous.invalid>;tag=95f

                       fcd055e0f78f7d5d397020e89288d6a8fe84b

                       User-Agent: Cantata-SIP/10.2.4.301 T1_IMG1 1

                       Timestamp: 03202008172420

                       P-Asserted-Identity: 2141234567<sip:2141234567@10.127.33.127>

                       Privacy: id

                       Contact: <sip:anonymous@10.127.33.127:5060>

                       Allow: INVITE, BYE, REGISTER, ACK, OPTIONS, CANCEL, SUBS

                       CRIBE, NOTIFY, INFO, UPDATE

                       Supported: path, timer

                       Session-Expires: 1800

                       Expires: 300

                       Organization: Cantata Technology Inc

                       Remote-Party-ID: 2141234567<sip:2141234567@10.127.33.127

                       ;user=phone>;party=calling;id-type=subscriber;privacy=fu

                       ll;screen=no

                       Content-Type: application/sdp

                       Content-Length: 164

                       

                       v=0

                       o=Cantata_SDP 0 0 IN IP4 10.127.33.127

                       s=Cantata-SIP

                       c=IN IP4 10.127.33.122

                       t=0 0

                       m=audio 8024 RTP/AVP 0

                       a=rtpmap:0 PCMU/8000

                       a=silenceSupp:off - - - -

 

 

From: JohnSmith <sip:5088423501@10.127.33.23>

Remote-Party-ID: JaneSmith <5088423423@10.127.33.14>; party=calling;

id-type=subscriber;

screen=yes

privacy=full

 

 

 

 

  1. The second part of the process is to tell the IMG which gateways in the network are part of the Trusted Domain and whether they accept SIP Privacy settings. This is accomplished by first creating a SIP SGP profile and then inserting that profile into each external gateway pane. The steps are shown below

  2. Under the SIP SGP object in ClientView (Dialogic IMG EMS > Profiles > SIP SGP) select SIP Privacy as either "ON" or "Off" and the Trusted field as either "Yes" or "No".

 

 

 

SC_SIP_Privacy_ProfileSGP_10.5.0.png

 

 

 

  1. Once the SIP profile object is configured, it can be inserted into the external network element pane which is the pane that tells the IMG what the external gateway IP address is etc. (Cantata IMG EMS > External Network Elements > External Gateways > External Gateway).

 

SC_SIP_Privacy_ExtGateway_10.5.0.png

 

  1. The SIP profile can be input into any gateway configured on the GCEMS.

 

Note: To enable Privacy for an ISDN Group or an ISUP Group, set the Discard Privacy Info field in the ISDN Group pane or the ISUP Group pane to Yes.

 

 

 

10.3.x:

In software 10.3.x, SIP Privacy is configured in two separate objects in ClientView.

  1. The first object in ClientView that will enable SIP Privacy is under the SIP Signaling Stack. (Physical IMG > Signaling > SIP Signaling). Enabling SIP Privacy in this object pane will enable the SIP Privacy feature on the SIP signaling stack on the IMG. Select one of the options from the drop down menu of the Privacy Support field. All calls will be handled according to this setting regardless of other SIP Privacy settings on an individual External Gateway or ISDN/ISUP Group.

 

SC_SIP_Privacy_SIPSIG_10.5.0.png

 

 

 

  1. In order to configure SIP Privacy on the individual gateways the next few steps must be followed. This will allow configuring SIP Privacy on some gateways and not others.

  2. In ClientView create an external gateway pane as shown below (Cantata IMG EMS > External Network Elements > External Gateways > External Gateways. See screen capture below

  3. Select from drop down menu whether SIP Privacy is "Off" or "On" (Default = Off). SIP Privacy is now set on the SIP stack on the IMG and the IMG knows which gateways/servers SIP Privacy is configured on.

  4. Select from drop down menu whether this gateway is part of the trusted domain (Yes or No, Default=No). See above explanation on trusted domain

 

 

SC_SIP_Privacy_ProfileSGP_10.5.0.png

 

 

 

 

 

 

Related Topics

SIP Privacy

SIP Signaling

External Gateway

ISDN Group

ISUP Group

 

 

DG_SIP_Privacy.png