1.10 New Parameters
1.10.2 B2BUA Transcoding Parameters
The table below describes the new B2BUA application parameters for Release 6.0. Table 1-2: New B2BUA Transcoding Parameters for Release 6.0
Parameter Description
Web: Enable B2BUA Application
Enables the [EnableSBCApplication]
Back-to-Back User Agent (B2BUA) Transcoding application. [0] Disable (default) [1] Enable
For this parameter to take effect, a device reset is required. Notes:
In addition to enabling this parameter, the number of maximum IP-to-IP SIP dialog sessions must be defined in the Software Upgrade Key Web: . Enable IP2IP Application [EnableIP2IPApplication]
Enables the IP-to-IP call routing application.
[0] Disable (default) [1] Enable
Note: For this parameter to take effect, a device reset is required. [ProxySet] Parameter added to existing
Proxy Set table:
[ProxySet_SRD] SRD Index: The SRD associated with the Proxy Set ID. Note: If no SRD is defined for this parameter, by default, SRD ID 0 is associated with the Proxy Set.
[Account]
Parameter added to existing Account table:
[ApplicationType]: [0] GW/IP2IP (default); [2] B2BUA [IPProfile]
•
Parameters added to existing IP Profile table:
[IpProfile_SBCExtensionCodersGroupID] SBC Extension Coders Group ID:
• [IPProfile_TranscodingMode]
Defines the Coder Group ID for extended (additional) coders. This is used when transcoding is required between two user agents (i.e., the SDP answer from one user agent doesn’t include any coder included in the offer previously sent by the other user agent). Therefore, to allow user agents of different IP Groups to communicate with each other (regardless of their capabilities), an extended coders table with at least one coder that is supported by each IP Groups' user agents needs to be assigned to each IP Group. Therefore, each offer destined to specific IP Groups include this coder.
Transcoding Mode:
Defines the voice transcoding mode (media negotiation) for the SBC
application, between the two SBC legs. [0]
Only if Required = Do not force (default). Many of the media settings (such as gain control) are not implemented on the voice stream. The SBC application passes packets RTP to RTP without any processing.
[1] Force = Force transcoding on outgoing SBC leg. The device's SBC application interworks the media by implementing DSP transcoding.
Mediant 2000 & Mediant 3000
Parameter Description
[IPGroup]
[IPGroup_SRD] SRD: The SRD associated with the IP Group. The default is 0.
Parameters added to existing IP Group table
[IPGroup_MediaRealm]Media Realm: The Media Realm name associated with this IP Group.
[IPGroup_ClassifyByProxySet]Classify By Proxy Set: Determines whether the incoming INVITE is classified to an IP Group according to the Proxy Set: [0] Disable; [1] Enable (default) [WanMgmtHttpPort] WAN HTTP port number. This parameter allows remote device Web
management from the WAN. To enable Web management from the WAN, configure the desired port (e.g., port 80, which is the default HTTP port).
The default is 0 (i.e., no remote Web management).
Note: If the parameter HTTPSOnly is set to 1, HTTP access is not allowed.
[WanMgmtHttpsPort] WAN HTTPS port number. This parameter allows secure remote device Web management from the WAN. To enable secure Web management, configure the desired port (e.g., port 443). The default is 0 (i.e., remote Web management is not secured).
Web: Transcoding Mode Defines the voice transcoding mode (media negotiation) for the SBC application, between the two SBC legs.
[TranscodingMode]
[0]
Only if Required = Do not force (default). Many of the media settings (such as gain control) are not implemented on the voice stream. The SBC application passes packets RTP to RTP without any processing.
[1] Force = Force transcoding on outgoing SBC leg. The device's SBC application interworks the media by implementing DSP transcoding.
Note: Web: Allow Unclassified Calls
This parameter can also be defined for an IP Profile (using the IPProfile parameter).
Determines whether calls (incoming packets) that cannot be
classified (i.e. classification process fails) into a Source IP Group (in the Classification table) are either rejected or processed.
[AllowUnclassifiedCalls]
[0]
Reject = the call is rejected if classification fails.
[1] Allow = if classification fails, the incoming packet is assigned to the default IP Group of the default SRD (and the call is subsequently processed). (Default.)
Parameter Description Web: SIP Media Realm Table
[CpMediaRealm] This ini file table parameter configures the SIP Media Realm table. The Media Realm table allows you to divide a Media-type interface (defined in the Multiple Interface table) into several realms, where each realm is specified by a UDP port range. Once created, the Media Realm can be assigned to an IP Group (in the IP Group) or SRD (in the SRD table).
The format of this parameter is as follows: [CpMediaRealm] FORMAT CpMediaRealm_Index = CpMediaRealm_MediaRealmName, CpMediaRealm_IPv4IF, CpMediaRealm_IPv6IF, CpMediaRealm_PortRangeStart, CpMediaRealm_MediaSessionLeg, CpMediaRealm_PortRangeEnd; [\CpMediaRealm] For example,
CpMediaRealm 1 = Mrealm1, Voice, , 6600, 20, 6790; CpMediaRealm 2 = Mrealm2, Voice, , 6800, 10, 6890;
Notes:
If different Media Realms are assigned to an IP Group and SRD, the IP Group’s Media Realm takes precedence.
This table can include up to 16 indices (where 0 is the first index). However, only up to 8 Media Realms can be used by the device (as a maximum of 8 IP Groups can be configured).
Each table index must be unique.
For this parameter to be effective, a device reset is required. The parameter cpDefaultMediaRealmName can be used to define one of the Media Realms appearing in this table as the default Media Realm, if no Media Realm is assigned to an SRD or IP Group for a specific call. If the parameter
cpDefaultMediaRealmName is not configured, then the first Media Realm appearing in this table is used as the default Media Realm. If this table is not configured, then the default realm includes all defined media interfaces.
Web: Signaling Routing Domain (SRD) Table This
[SRD] ini
[[SRD]
FORMAT SRD_Index = SRD_Name, SRD_MediaRealm, SRD_IntraSRDMediaAnchoring, SRD_BlockUnRegUsers, SRD_MaxNumOfRegUsers,
SRD_EnableUnAuthenticatedRegistrations; [\SRD]
file table parameter configures the Signaling Routing Domain (SRD) table. The format of this parameter is as follows:
For example:
SRD 1 = NW1_SRD, MR1, 1, 1, -1, 1; SRD 2 = NW2_SRD, MR1, 1, 1, -1, 1;
Note: This table can include up to 5 indices (where 0 is the first index).
Mediant 2000 & Mediant 3000
Parameter Description
Web: SIP Interface Table
This ini file table parameter configures the SIP Interface table. The SIP Interface represents a SIP signaling entity, comprising ports (UDP, TCP, and TLS) and associated with a specific IP address and an SRD ID. SIP Interfaces allow you (for example) to use different SIP signaling interfaces for each of the two SBC legs. The format of this parameter is as follows:
[SIPInterface]
[SIPInterface]
FORMAT SIPInterface_Index = SIPInterface_NetworkInterface, SIPInterface_ApplicationType, SIPInterface_UDPPort,
SIPInterface_TCPPort, SIPInterface_TLSPort, SIPInterface_SRD; [\SIPInterface]
For example:
SIPInterface 0 = Voice, 2, 5060, 5060, 5061, 1; SIPInterface 1 = Voice, 2, 5070, 5070, 5071, 2; SIPInterface 2 = Voice, 0, 5090, 5000, 5081, 2;
This table can include up to 6 indices (where 0 is the first index). Notes:
Each SIP Interface must have a unique signaling port (i.e., no two SIP Interfaces can share the same port - no port overlapping). You can define up to three different SIP Interfaces per SRD,
where each SIP Interface pertains to a different application type (i.e., GW, SAS, and SBC).
Web: SBC Classification Table This [Classification] ini
[Classification]
FORMAT Classification_Index = Classification_SrcIPGroupID, Classification_SrcSRDID, Classification_SrcAddress,
Classification_SrcUsernamePrefix, Classification_SrcHost, Classification_DestUsernamePrefix, Classification_DestHost; [\Classification]
file table parameter configures the Classification table for SBC. This table classifies the incoming SIP INVITE to a Source IP Group. The format of this parameter is as follows:
For example:
Classification 1 = -1, -1, , *, *, *, *;
This table can include up to 20 indices (where 0 is the first index). Notes:
Parameter Description Web: IP-to-IP Routing Table
This [IP2IPRouting] ini
[IP2IPRouting]
FORMAT IP2IPRouting_Index = IP2IPRouting_SrcIPGroupID, IP2IPRouting_SrcUsernamePrefix, IP2IPRouting_SrcHost, IP2IPRouting_DestUsernamePrefix, IP2IPRouting_DestHost, IP2IPRouting_DestType, IP2IPRouting_DestIPGroupID, IP2IPRouting_DestSRDID, IP2IPRouting_DestAddress, IP2IPRouting_DestPort, IP2IPRouting_DestTransportType, IP2IPRouting_AltRouteOptions; [\IP2IPRouting]
file table parameter configures the IP-to-IP Routing table for routing received SIP INVITE messages to a destination IP address. The format of this parameter is as follows:
For example:
IP2IPRouting 1 = -1, *, *, *, *, 0, -1, -1, , 0, -1, 0;
This table can include up to 120 indices (where 0 is the first index).
Notes:
For a specific routing rule to be effective, the matching
characteristics must match. If no matching rule is located, the call is rejected.
If neither Destination SRD nor Destination IP Group are configured, the destination SRD is the source SRD and the destination IP Group is its default IP Group.
Web: Alternative Routing Reasons Table This [SBCAlternativeRoutingRea sons] ini [ SBCAlternativeRoutingReasons ] FORMAT SBCAlternativeRoutingReasons_Index = SBCAlternativeRoutingReasons_ReleaseCause; [ \SBCAlternativeRoutingReasons ]
file table parameter configures the SBC Alternative Routing Reasons table. This table is used for alternative IP-to-IP routing (defined in the IP2IP Routing table). If 4xx, 5xx, or 6xx SIP responses are received as a result of outgoing INVITE (or OPTIONS, SUBSCRIBE and other dialog initiating methods), the device re-sends this message if the response is defined in this table, and if there is an alternative route in the IP2IP Routing table. The format of this parameter is as follows:
For example:
SBCAlternaiveRoutingReasons 0 = 403; SBCAlternativeRoutingReasons 1 = 404;
Note: This table can include up to five indices (where 0 is the first index).
Mediant 2000 & Mediant 3000
Parameter Description
Web:IP to IP Inbound Manipulation Table This [IPInboundManipulation] ini [IPInboundManipulation] FORMAT IPInboundManipulation_Index = IPInboundManipulation_IsAdditionalManipulation, IPInboundManipulation_ManipulatedURI, IPInboundManipulation_ManipulationPurpose, IPInboundManipulation_SrcIPGroupID, IPInboundManipulation_SrcUsernamePrefix, IPInboundManipulation_SrcHost, IPInboundManipulation_DestUsernamePrefix, IPInboundManipulation_DestHost, IPInboundManipulation_RequestType, IPInboundManipulation_RemoveFromLeft, IPInboundManipulation_RemoveFromRight, IPInboundManipulation_LeaveFromRight, IPInboundManipulation_Prefix2Add, IPInboundManipulation_Suffix2Add; [\IPInboundManipulation]
file table parameter configures the IP to IP Inbound
Manipulation table. This table allows you to manipulate the SIP URI user part (source and/or destination) of the inbound INVITE
message. The format of this parameter is as follows:
For example:
IPInboundManipulation 1 = 0, 0, -1, *, *, *, *, 0, 0, 255, , ; Notes:
This table can include up to 100 indices.
For a specific manipulation rule to be effective, the matching characteristics must match.
Manipulated destination SIP URI user names are done in the following SIP headers: Request URI, To, and Remote Party ID (if exists). Manipulated source SIP URI user names are done in the following SIP headers: From, P-Asserted (if exists), P-Preferred (if exists), and Remote Party ID (if exists).
For SIP URI host name (source and destination) manipulations, use the 'IP Group' table. These host names are simply replaced with the names configured for the Source and Destination IP Groups respectively.
Web: IP to IP Outbound Manipulation Table This
Parameter Description IPOutboundManipulation_DestHost, IPOutboundManipulation_RemoveFromLeft, IPOutboundManipulation_RemoveFromRight, IPOutboundManipulation_LeaveFromRight, IPOutboundManipulation_Prefix2Add, IPOutboundManipulation_Suffix2Add; For example: IPOutboundManipulation 1 = 0, 0, -1, -1, *, *, *, *, 0, 0, 255, , ; Notes:
This table can include up to 100 indices (where 0 is the first index).
For a specific manipulation rule to be effective, the matching characteristics must match.
IP-to-IP manipulation rules apply to INVITE and other dialog initiating SIP messages (except REGISTER messages). Manipulated destination SIP URI user names are done in the
following SIP headers: Request URI, To, and Remote Party ID (if exists). Manipulated source SIP URI user names are done in the following SIP headers: From, P-Asserted (if exists), P-Preferred (if exists), and Remote Party ID (if exists).
For SIP URI host name (source and destination) manipulations, use the 'IP Group' table. These host names are simply replaced with the names configured for the Source and Destination IP Groups respectively.
Mediant 2000 & Mediant 3000