The
is integrated with Juniper Session Resource Controller (JSRC) using SOAP interface to perform enhanced call processing such as bandwidth reservation and Gateway client process creation.
For example, when a call comes in, the
acting acting as a Gateway client contacts the SRC and reserves bandwidth for the session. Once the call completes, the bandwidth reservation is released. Currently, each business partner can have three users (user1, user 2, user3). Each of these users has a 6M (6000000) link to the DSLAM.
...
- End-to-end session establishment starts Sonus SBC #1 #1.
- Sonus #1 examines the global configuration to determine if the SRC bandwidth reservation feature is enabled (for the example above, SRC bandwidth reservation is enabled).
- Sonus #1 examines the offered session attributes, determines worst case bandwidth requirements and performs three Subscriber_activateService API calls to reserve bandwidth:
- SIP trunk #1 (reservation is optional, depending on network topology)
- Ingress trunk #1
- Egress trunk #1
- Sonus #1 forwards session establishment signaling to Sonus SBC #2 #2.
- Sonus #2 examines global configuration to determine if SRC bandwidth reservation is enabled (for example above, SRC bandwidth reservation is enabled).
- Sonus #2 examines the offered session attributes, determines worst case bandwidth requirements and performs three Subscriber_activateService API calls to reserve bandwidth:
- SIP trunk #2 (reservation is optional, depending on network topology)
- Ingress trunk #2
- Egress trunk #2
- Once the session attributes are negotiated end-to-end, both Sonus s have knowledge of the actual bandwidth used by the session on each trunk.
- At this point both of the Sonus s perform Subscriber_modifyService API calls to adjust down the bandwidth as needed.
...