Dialogic 1000Series, User Manual

Page: 73 / 326

Dialogic
®
1000 and 2000 Media Gateway Series User’s Guide 73
Parameter Reference
Privacy Header Method
Description: The SIP protocol provides for two methods to keep the ‘Calling Party ID’ data
private. Both methods modify the ‘From’ header by changing the fields to ‘anonymous’. They
differ on how the actual ‘Calling Party ID’ data is presented. The first method is shown in the
preceding example, that is, P-Asserted-Identity’ is used. The second method uses ‘Remote-Party-
ID’. Both methods supply the same data, just in somewhat different formats.
Note: Privacy Header Method is relevant only when Enable Privacy Headers is set to ‘yes’.
Allowed Values:
• P-Asserted-Identification = When a SIP ‘P-Asserted-Identity’ header is received its data is
translated into ISDN privacy fields. When ISDN privacy fields are received they are converted
into a SIP ‘P-Asserted-Identity’ header. If a SIP ‘Remote-Party-ID’ header is received it is
ignored.
• Remote-Party-ID = When a SIP ‘Remote-Party-ID’ header is received its data is translated into
ISDN privacy fields. When ISDN privacy fields are received they are converted into a SIP
‘Remote-Party-ID’ header. If a ‘P-Asserted-Identity’ header is received it is ignored.
• Both = This setting is used when some SIP devices communicating with the gateway use ‘P-
Asserted-Identity’ for privacy and others use ‘Remote-Party-ID’ for privacy. So when either
SIP method is received the gateway converts into ISDN privacy fields. When ISDN privacy
fields are received the gateway creates a SIP message that contains both a ‘P-Asserted-
Identity’ header and a ‘Remote-Party-ID’ header. The receiving party will use the header it
supports.
Default Value = P-Asserted-Identification
INI File Parameter Name = sipPrivacyHdrMethod
3.3.9 User-User Information Group
The User-User Information (UUI) parameters control the translation of information between ISDN
user-user IEs and SIP user-to-user headers. The ISDN user-user IE is specified in Q.931.
The DMG2000 supports sending UUI between called and calling parties. The purpose of UUI is to
pass specific information not pertaining to the call from one user to another. The information is
transferred through the gateway and does not have any effect on the call. The gateway supports
UUI for SIP-SIP calls, SIP-ISDN calls, ISDN-SIP calls, and transfers that use SIP REFER.
SIP-SIP Calls
The UUI header is passed unchanged between calling and called parties. The gateway supports a
single UUI header in the ‘INVITE’, ‘180 Ringing’ and ‘200 OK’ messages.
Figure 8 is an example call flow for SIP-SIP calls: