Siemens HiPath 8000 Spezifikationen Seite 140

  • Herunterladen
  • Zu meinen Handbüchern hinzufügen
  • Drucken
  • Seite
    / 238
  • Inhaltsverzeichnis
  • LESEZEICHEN
  • Bewertet. / 5. Basierend auf Kundenbewertungen
Seitenansicht 139
Call Admission Control Features
A31003-H8022-F100-2-7618, October 2006
10-4 HiPath 8000 V2.2, Feature Description Guide
call_admission_control_features.fm
CAC Rerouting
10.4 CAC Rerouting
One of the benefits of the integrated CAC solution is the HiPath 8000's ability to provide
rerouting via the PSTN in case there is not enough bandwidth in the bandwidth-limited link from
the branch office to the WAN. The rerouting call scenarios are tightly coupled with the HiPath
8000’s ability to reroute calls based on a provisionable set of SIP response codes. Refer also
to Section 9.8.6, “Rerouting Based on SIP Response Codes”, on page 9-6.
Among other things, this feature provides for the rerouting of calls to SIP gateways or SIP
subscribers if the HiPath 8000 receives a SIP response code indicating a bandwidth restriction
(for example, 606 Not Acceptable).
For the integrated CAC solution, the HiPath 8000 does not actually receive a SIP 606 response
code from the terminating B-side of the call. However, the RM function in the terminating SIP
session manager internally responds with the same error message as if a SIP 606 response
code was received in response to an INVITE message sent to the B-side. No INVITE message
is actually sent to the B-party in case of bandwidth limitation.
10.4.1 Rerouting Calls to SIP Subscribers
Rerouting of calls to SIP subscribers via the PSTN can be performed if the following conditions
are met:
The called SIP subscriber is registered from a survivable branch.
The called SIP subscriber resides in that survivable branch. This means that the called SIP
subscriber is registered with its provisioned survivable SIP endpoint (its SIP proxy). The
administration of the called SIP subscriber to become survivable is enabled by assigning
the Survivable SIP Proxy as the associated SIP Endpoint to the SIP subscriber.
The called subscriber has a valid public E.164 number. Refer also to Section 9.3, “E.164
Compliance”, on page 9-2.
The calling SIP Subscriber is calling from a different survivable branch or is directly
registered with the HiPath 8000.
- or -
The calling device is a SIP endpoint (SIP gateway) that has the rerouting option set, and
there is a last diverting user for the call which is a provisioned SIP subscriber of the HiPath
8000.
For example, assume that a SIP subscriber in the Boca Raton, Florida, branch calls a SIP
subscriber in the San Jose, California, branch. This scenario requires the RTP payload to route
through the bandwidth-limited links that connect the Boca and the San Jose branch offices to
the WAN.
Seitenansicht 139
1 2 ... 135 136 137 138 139 140 141 142 143 144 145 ... 237 238

Kommentare zu diesen Handbüchern

Keine Kommentare