User's Manual
420
Document #: LTRT-89729
Mediant 3000
with an Authorization header (containing the user name and password).
3.
The device validates the SIP message according to the settings of the parameters,
AuthNonceDuration, AuthChallengeMethod and AuthQOP.
•
If validation fails, the message is rejected and the device sends a 403
"Forbidden" response.
•
If validation succeeds, the device verifies identification of the SBC user. This is
done by checking that the user name and password received from the user is the
same username and password that appears in the device's database. The SBC
users in the database are obtained from the User Information file. If the SIP SBC
user is not successfully authenticated after three attempts, the device sends a
403 "Forbidden" response.
4.
If the user is successfully identified, the SIP message request is processed.
Note:
This feature is applicable only to Mediant 3000 in Simplex mode.
28.8 Interworking SIP Signaling
The device supports interworking of SIP signaling messages to ensure interoperability
between communicating SIP UAs or entities. This is critical in network environments where
the UAs on opposing SBC legs have different SIP signaling support. For example, some
UAs may support different versions of a SIP method while others may not event support a
specific SIP method. The configuration method for assigning specific SIP message
handling modes to UAs, includes configuring an IP Profile with the required interworking
mode, and then assigning the IP Profile to the relevant IP Group.
This section describes some of the device's support for handling SIP methods to ensure
interoperability.
28.8.1 Interworking SIP 3xx Redirect Responses
The device supports interworking of SIP 3xx redirect responses. By default, the device's
handling of SIP 3xx responses is to send the Contact header unchanged. However, some
SIP UAs may support different versions of the SIP 3xx standard while others may not even
support SIP 3xx.
The handling of SIP 3xx can be configured for all calls, using the global parameter
SBC3xxBehavior. For configuring different SIP 3xx handling options for different UAs (i.e.,
per IP Group), use the IP Profile table parameter, 'SBC Remote 3xx Behavior'.
28.8.1.1 Resultant INVITE Traversing Device
The device can handle SIP 3xx responses so that the new INVITE message sent as a
result of the 3xx traverses the device. The reasons for enforcing resultant INVITEs to
traverse the device may vary:
The user that receives the 3xx is unable to route to the 3xx contact (i.e., the user is on
the LAN and the new contact is on the WAN). In such a scenario, the device enables
the user to reach the WAN contact and overcome NAT problems.
Enforce certain SBC policies (e.g., call admission control, header manipulation, and
transcoding) on the resultant INVITE.
The device enforces this by modifying each Contact in the 3xx response as follows:
Changes the host part to the device's IP address – this change causes the remote
Summary of Contents for Mediant 3000
Page 2: ......
Page 26: ...User s Manual 26 Document LTRT 89729 Mediant 3000 Reader s Note...
Page 27: ...Part I Getting Started with Initial Connectivity...
Page 28: ......
Page 40: ...User s Manual 40 Document LTRT 89729 Mediant 3000 Reader s Notes...
Page 41: ...Part II Management Tools...
Page 42: ......
Page 44: ...User s Manual 44 Document LTRT 89729 Mediant 3000 Reader s Notes...
Page 80: ...User s Manual 80 Document LTRT 89729 Mediant 3000 Reader s Notes...
Page 98: ...User s Manual 98 Document LTRT 89729 Mediant 3000 Reader s Notes...
Page 103: ...Part III General System Settings...
Page 104: ......
Page 113: ...Part IV General VoIP Configuration...
Page 114: ......
Page 144: ...User s Manual 144 Document LTRT 89729 Mediant 3000 Reader s Notes...
Page 164: ...User s Manual 164 Document LTRT 89729 Mediant 3000 Reader s Notes...
Page 222: ...User s Manual 222 Document LTRT 89729 Mediant 3000 Reader s Notes...
Page 224: ...User s Manual 224 Document LTRT 89729 Mediant 3000 Reader s Notes...
Page 275: ...Part V Gateway and IP to IP Application...
Page 276: ......
Page 278: ...User s Manual 278 Document LTRT 89729 Mediant 3000 Reader s Notes...
Page 399: ...Part VI Session Border Controller Application...
Page 400: ......
Page 402: ...User s Manual 402 Document LTRT 89729 Mediant 3000 Reader s Notes...
Page 464: ...User s Manual 464 Document LTRT 89729 Mediant 3000 Reader s Notes...
Page 465: ...Part VII Stand Alone Survivability Application...
Page 466: ......
Page 474: ...User s Manual 474 Document LTRT 89729 Mediant 3000 Reader s Notes...
Page 494: ...User s Manual 494 Document LTRT 89729 Mediant 3000 Reader s Notes...
Page 497: ...Part VIII IP Media Capabilities...
Page 498: ......
Page 501: ...Part IX High Availability System...
Page 502: ......
Page 515: ...Part X Maintenance...
Page 516: ......
Page 522: ...User s Manual 522 Document LTRT 89729 Mediant 3000 Reader s Notes...
Page 524: ...User s Manual 524 Document LTRT 89729 Mediant 3000 Reader s Notes...
Page 552: ...User s Manual 552 Document LTRT 89729 Mediant 3000 Reader s Notes...
Page 562: ...User s Manual 562 Document LTRT 89729 Mediant 3000 Reader s Notes...
Page 565: ...Part XI Status Performance Monitoring and Reporting...
Page 566: ......
Page 578: ...User s Manual 578 Document LTRT 89729 Mediant 3000 Reader s Notes...
Page 609: ...Part XII Diagnostics...
Page 610: ......
Page 624: ...User s Manual 624 Document LTRT 89729 Mediant 3000 Reader s Notes...
Page 626: ...User s Manual 626 Document LTRT 89729 Mediant 3000 Reader s Notes...
Page 638: ...User s Manual 638 Document LTRT 89729 Mediant 3000 Reader s Notes...
Page 639: ...Part XIII Appendix...
Page 640: ......
Page 864: ...User s Manual 864 Document LTRT 89729 Mediant 3000 Reader s Notes...
Page 871: ...Version 6 6 871 Mediant 3000 User s Manual 55 Selected Technical Specifications Reader s Notes...