User's Manual
538
Document #: LTRT-65432
MP-11x & MP-124
Parameter
Description
[0]
Disable (default)
[1]
Enable
When this parameter is enabled, if the Request-URI in the received SIP
INVITE includes the 'dtg' parameter, the device routes the call to the
Hunt Group according to its value. This parameter is used instead of the
'tgrp/trunk-context' parameters. The 'dtg' parameter appears in the
INVITE Request-URI (and in the To header).
For example, the received SIP message below routes the call to Hunt
Group ID 56:
INVITE sip:[email protected];dtg=56;user=phone SIP/2.0
Note:
If the Hunt Group is not found based on the 'dtg' parameter, the
IP to Hunt Group Routing Table is used instead for routing the call to
the appropriate Hunt Group.
Web/EMS: Enable GRUU
[EnableGRUU]
Determines whether the Globally Routable User Agent URIs (GRUU)
mechanism is used, according to RFC 5627. This is used for obtaining a
GRUU from a registrar and for communicating a GRUU to a peer within
a dialog.
[0]
Disable (default)
[1]
Enable
A GRUU is a SIP URI that routes to an instance-specific UA and can be
reachable from anywhere. There are a number of contexts in which it is
desirable to have an identifier that addresses a single UA (using GRUU)
rather than the group of UA’s indicated by an Address of Record (AOR).
For example, in call transfer where user A is talking to user B, and user
A wants to transfer the call to user C. User A sends a REFER to user C:
REFER sip:[email protected] SIP/2.0
From: sip:[email protected];tag=99asd
To: sip:[email protected]
Refer-To: (URI that identifies B's UA)
The Refer-To header needs to contain a URI that user C can use to
place a call to user B. This call needs to route to the specific UA
instance that user B is using to talk to user A. User B should provide
user A with a URI that has to be usable by anyone. It needs to be a
GRUU.
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
Summary of Contents for Media Pack MP-11x
Page 2: ......
Page 14: ...User s Manual 14 Document LTRT 65432 MP 11x MP 124 This page is intentionally left blank...
Page 24: ...User s Manual 24 Document LTRT 65432 MP 11x MP 124 This page is intentionally left blank...
Page 25: ...Part I Getting Started with Initial Connectivity...
Page 26: ......
Page 35: ...Part II Management Tools...
Page 36: ......
Page 38: ...User s Manual 38 Document LTRT 65432 MP 11x MP 124 This page is intentionally left blank...
Page 86: ...User s Manual 86 Document LTRT 65432 MP 11x MP 124 This page is intentionally left blank...
Page 94: ...User s Manual 94 Document LTRT 65432 MP 11x MP 124 This page is intentionally left blank...
Page 100: ...User s Manual 100 Document LTRT 65432 MP 11x MP 124 This page is intentionally left blank...
Page 108: ...User s Manual 108 Document LTRT 65432 MP 11x MP 124 This page is intentionally left blank...
Page 109: ...Part III General System Settings...
Page 110: ......
Page 118: ...User s Manual 118 Document LTRT 65432 MP 11x MP 124 This page is intentionally left blank...
Page 121: ...Part IV General VoIP Configuration...
Page 122: ......
Page 152: ...User s Manual 152 Document LTRT 65432 MP 11x MP 124 This page is intentionally left blank...
Page 202: ...User s Manual 202 Document LTRT 65432 MP 11x MP 124 This page is intentionally left blank...
Page 204: ...User s Manual 204 Document LTRT 65432 MP 11x MP 124 This page is intentionally left blank...
Page 230: ...User s Manual 230 Document LTRT 65432 MP 11x MP 124 This page is intentionally left blank...
Page 231: ...Part V Gateway Application...
Page 232: ......
Page 234: ...User s Manual 234 Document LTRT 65432 MP 11x MP 124 This page is intentionally left blank...
Page 274: ...User s Manual 274 Document LTRT 65432 MP 11x MP 124 This page is intentionally left blank...
Page 278: ...User s Manual 278 Document LTRT 65432 MP 11x MP 124 This page is intentionally left blank...
Page 298: ...User s Manual 298 Document LTRT 65432 MP 11x MP 124 This page is intentionally left blank...
Page 326: ...User s Manual 326 Document LTRT 65432 MP 11x MP 124 This page is intentionally left blank...
Page 327: ...Part VI Stand Alone Survivability Application...
Page 328: ......
Page 336: ...User s Manual 336 Document LTRT 65432 MP 11x MP 124 This page is intentionally left blank...
Page 358: ...User s Manual 358 Document LTRT 65432 MP 11x MP 124 This page is intentionally left blank...
Page 361: ...Part VII Maintenance...
Page 362: ......
Page 368: ...User s Manual 368 Document LTRT 65432 MP 11x MP 124 This page is intentionally left blank...
Page 406: ...User s Manual 406 Document LTRT 65432 MP 11x MP 124 This page is intentionally left blank...
Page 409: ...Part VIII Status Performance Monitoring and Reporting...
Page 410: ......
Page 441: ...Part IX Diagnostics...
Page 442: ......
Page 456: ...User s Manual 456 Document LTRT 65432 MP 11x MP 124 This page is intentionally left blank...
Page 458: ...User s Manual 458 Document LTRT 65432 MP 11x MP 124 This page is intentionally left blank...
Page 471: ...Part X Appendix...
Page 472: ......