In this section:
SBC SIP-to-SIP Basic Call Processing Flow
The following instructions lists the
Unable to show "metadata-from": No such page "_space_variables"
basic SIP-to-SIP call processing.- The call is received by the SBC. The Source IP addresses is matched against the Federated IP addresses contained in all the Signaling Groups (SG).
- The SG with the closest matching Federated IP is selected to process the incoming call.
- In the case above, the Federated IP, host1.vx.net/32, exactly matches the sending host's source IP as resolved via DNS (host1.vx.net).
- Of course, the transport type and incoming port must also match.
- The Signaling Group defines the Call Routing Table to use for processing the call, sba: SIP to ISDN in this case.
- The Call Routing Table contains a list of call routing entries.
- Those call route entries define which Transformation Table (sba:Lync to SIP Reg) to use in manipulating the call's numbers, names, etc.
- If the transformation is valid, the call is passed to the Destination Signaling Group (10.1.1.91 SG) defined in the call route entry.
- The Egress Signaling Group contains the configuration for the (egress) SIP Server Table (10.1.1.91)
The call is then sent to destination based upon the configuration of the SIP Server Table entry.
Overview
Content Tools