SIP PBX Access _ i-SBC Scenario

benjamin.omeke
benjamin.omeke  Diamond  (1)
7 years 10 months ago  View: 1933  Reply: 2
1F

SIP Private Branch eXchange (PBX) access is a feature that enables SIP PBXs to access the NGN.


SIP PBX Access (in the I-SBC Scenario)

In this scenario, the SE2600 is configured to act as an interworking gateway between the SIP PBX and the core network. This networking is applicable to the NGN. Based on the number analysis result, the SE2600 forwards packets to the corresponding SIP PBX.

In the I-SBC scenario, the SE2600 supports the following functions:

  • SIP PBX number analysis

    After receiving an INVITE message from the core network, the SE2600 analyzes the callee number carried in the INVITE message. Based on the callee number, the SE2600 locates the SIP PBX to which the UE (callee) is attached. Then the SE2600 forwards the INVITE message to the SIP PBX to which the UE (callee) is attached.

  • Media release

    The SIP PBX access feature supports the automatic media release function. By default, the automatic media release function is enabled. Media release enables media streams to be transmitted between the caller and the callee attached to a SIP PBX without passing through the SE2600. This function can be configured by running media-bypass. For other information, see SBCS0FMEDR00 Media Bypass.

  • Call admission control (CAC)

    The maximum number of concurrent calls, maximum bandwidth for all concurrent calls, and maximum bandwidth for individual calls can be configured in the iptrunk-intercom view of the SE2600. Currently, policies in which the maximum number of concurrent calls and maximum bandwidth for all concurrent calls are set cannot be shared. For the CAC configuration, see Configuring the Local CAC Feature.

  • HMR

    After receiving a SIP message, the SE2600 searches for the SIP PBX based on the source IP address + port in the SIP message. If the SIP PBX is found, the SE2600 will enforce an HMR rule, which is configured in the iptrunk-intercom view, for the SIP PBX. If there are HMR rules in maggroup, these rules will be enforced first. You can configure HMR rules for each SIP PBX. For details, see SBCS0SIPHM00 SIP Header Manipulation.

  • Traffic measurement for the SIP PBX

    You can view SIP PBX measurement statistics on the SE2600 by running display sbc iptrunk statistic. You can view some traffic measurement indicators on the NMS. For details, see IPTrunk.

  • IP address match

    The SE2600 discards messages originating from incorrect source IP addresses. By default, this function is disabled. You can run sbc sip iptrunk match ip enable to enable this function.

  • Call number check

    The SE2600 discards the INVITE messages carrying unauthorized caller numbers destined for the core network. By default, this function is enabled. You can run undo match userinfo to disable this function.

  • IP-trunk-domain-based routing

    After the SE2600 receives an INVITE message originating from the core network, it matches the domain name in the Request-URI header of the message with the IP trunk domain names configured on the SE2600 to locate the IP trunk on which the UE (callee) resides. The SE2600 then forwards the INVITE message to the IP trunk on which the UE (callee) resides. You can run domain and call-routing via iptrunk-domain to configure IP trunk domain names.

  • IP trunk backup

    The ID of the backup IP trunk can be set in the iptrunk-intercom view of the SE2600. The SE2600 sends OPTIONS messages regularly to an IP trunk to detect the IP trunk status. If the SE2600 detects that the master IP trunk is faulty, the SE2600 forwards an out-of-dialog message originating from the core network to the backup IP trunk. You can configure this function by running option-detect and backup iptrunk.

mahmud_h
mahmud_h  Diamond 
7 years 10 months ago
2F
Very good documentation!
user_2837311
user_2837311  Diamond 
3 years 11 months ago
3F
useful document, thanks