Filter
Top Products
SIP Release Notes 34 Document #: LTRT-26901
CPE SIP Products
• Obtaining a GRUU: The mechanism for obtaining a GRUU is through
registrations. A UA can obtain a GRUU by generating a REGISTER request
containing a Supported header field with the value “gruu”. The UA includes a
“+sip.instance” Contact header parameter of each contact for which the GRUU is
desired. This Contact parameter contains a globally unique ID that identifies the
UA instance. The global unique ID is created from one of the following:
♦ If the REGISTER is per the device’s client (endpoint), it is the MAC address
concatenated with the phone number of the client.
♦ If the REGISTER is per device, it is the MAC address only.
♦ When using TP, “User Info” can be used for registering per endpoint. Thus,
each endpoint can get a unique id – its phone number. The globally unique
ID in TP is the MAC address concatenated with the phone number of the
endpoint.
If the remote server doesn’t support GRUU, it ignores the parameters of the
GRUU. Otherwise, if the remote side also supports GRUU, the REGISTER
responses contain the “gruu” parameter in each Contact header. This parameter
contains a SIP or SIPS URI that represents a GRUU corresponding to the UA
instance that registered the contact. The server provides the same GRUU for the
same AOR and instance-id when sending REGISTER again after registration
expiration. RFC 5627 specifies that the remote target is a GRUU target if its’
Contact URL has the "gr" parameter with or without a value.
• Using GRUU: The UA can place the GRUU in any header field that can contain a
URI. It must use the GRUU in the following messages: INVITE request, its 2xx
response, SUBSCRIBE request, its 2xx response, NOTIFY request, REFER
request and its 2xx response.
14. Sending/Receiving IP Calls to/from Trusted IP Addresses:
Product
MP-11x MP-124
Mediant 600 Mediant 1000
Mediant 800 MSBG Mediant 1000 MSBG
Mediant 2000
Mediant 3000/TP-6310 Mediant 3000 HA/TP-6310
Mediant 3000/TP-8410 Mediant 3000 HA/TP-8410
Management Protocol
Web INI
SNMP
EMS
CLI
This feature provides support for sending and receiving IP calls only to and from
“trusted” IP addresses respectively. Trusted IP addresses are those that appear in the
Outbound IP Routing/Tel to IP Routing table (routing table) or Proxy Set table. In
addition, if a fully-qualified domain name (FQDN) is defined in the routing table or
Proxy Set table, the call is allowed only if the resolved DNS IP address appears in one
of these tables. Calls with IP addresses or resolved IP addresses (in case of DNS
queries) that do not appear in the routing table or Proxy Set table are rejected.
This feature is configured using the new option, “Secure All Calls” (2) for the existing
SecureCallsfromIP parameter.