Difference between revisions of "M4 Origination Points"
From Kolmisoft Wiki
Jump to navigationJump to search
m (Admin moved page M2 Origination Points to M4 Origination Points) |
|||
| Line 1: | Line 1: | ||
Origination Point is connection from some initial entity (device/line/trunk/provider/supplier/etc) where call starts/originates. | Origination Point is a connection from some initial entity (device/line/trunk/provider/supplier/etc) where the call starts/originates. | ||
The call comes from Origination Point and goes to [[M4 Termination Points | Termination Points]]. | |||
==Timeouts== | ==Timeouts== | ||
* '''Ringing Timeout''' - allows | * '''Ringing Timeout''' - allows limiting ringing duration (in seconds). Leave 0 for unlimited.<br> | ||
* '''Call Timeout''' - allows | * ''' Call Timeout''' - allows limiting Call duration (in seconds). Leave 0 for unlimited (global Call timeout (7200 seconds) is still applicable in this case).<br> | ||
==Servers== | ==Servers== | ||
Origination Points (OP) can be assigned to one or more servers. If call comes from server where OP is not assigned, call will not go through.<br> | Origination Points (OP) can be assigned to one or more servers. If a call comes from the server where OP is not assigned, the call will not go through.<br> | ||
==Authentication Simple== | ==Authentication Simple== | ||
| Line 21: | Line 21: | ||
* '''IP Address''' - IP Address of Origination Point (subnetting and IP range is allowed. For more information read Subnetting and IP range sections below).<br> | * '''IP Address''' - IP Address of Origination Point (subnetting and IP range is allowed. For more information read Subnetting and IP range sections below).<br> | ||
* '''Port''' - Port of Origination Point.<br> | * '''Port''' - Port of Origination Point.<br> | ||
* '''Tech. Prefix''' - Destination technical prefix that is used to authenticate OP. If this field is empty, calls will be accepted with any Destination number only based on IP:PORT. If this field is not empty, then only calls with specific | * '''Tech. Prefix''' - Destination technical prefix that is used to authenticate OP. If this field is empty, calls will be accepted with any Destination number only based on IP:PORT. If this field is not empty, then only calls with specific prefixes in Destination will be authenticated (for example if Tech. Prefix is 00, then OP accepts Destination numbers that start with 00xxxxxxx).<br> | ||
'''Dynamic IP:''' | '''Dynamic IP:''' | ||
| Line 55: | Line 55: | ||
** g - replace all matches | ** g - replace all matches | ||
Before putting Transformations | Before putting Transformations into production, it is advisable to test them on various values. | ||
====Test in Linux console==== | ====Test in Linux console==== | ||
| Line 69: | Line 69: | ||
====Validate regex==== | ====Validate regex==== | ||
The regex part of a Transformation can be validated using https://regexr.com/ (or any other online regex editor). | |||
====Examples==== | ====Examples==== | ||
| Line 94: | Line 94: | ||
* '''Act as Origination Point''' - if set to 'yes', this Connection Point will be handled as Origination Point.<br> | * '''Act as Origination Point''' - if set to 'yes', this Connection Point will be handled as Origination Point.<br> | ||
* '''Active''' - allows to activate or deactivate OP. If OP is deactivated, calls will not be accepted from this OP.<br> | * '''Active''' - allows to activate or deactivate OP. If OP is deactivated, calls will not be accepted from this OP.<br> | ||
* '''Destination Transformation''' - special [[M2 Destination Transformation | Destination Transformation]] rules used to modify outgoing number. Rules are applied before billing so | * '''Destination Transformation''' - special [[M2 Destination Transformation | Destination Transformation]] rules used to modify outgoing number. Rules are applied before billing so they can be used to correct non-E164 formats.<br> | ||
* '''Source Transformation''' - special [[M2 Source Transformation | Source Transformation]] rules used to modify Source number.<br> | * '''Source Transformation''' - special [[M2 Source Transformation | Source Transformation]] rules used to modify Source number.<br> | ||
* '''Routing Algorithm''' - defines how Termination Points are ordered for this Origination Point.<br> | * '''Routing Algorithm''' - defines how Termination Points are ordered for this Origination Point.<br> | ||
| Line 100: | Line 100: | ||
* '''Use MNP''' - enable [[M2 Mobile Number Portability|MNP]] for this OP.<br> | * '''Use MNP''' - enable [[M2 Mobile Number Portability|MNP]] for this OP.<br> | ||
* '''MNP Routing Group''' - name of Routing Group used for [[M2 Mobile Number Portability|MNP]]. | * '''MNP Routing Group''' - name of Routing Group used for [[M2 Mobile Number Portability|MNP]]. | ||
* '''OP Tariff when MNP is used''' - select OP Tariff when MNP is used. Default OP Tariff will be used | * '''OP Tariff when MNP is used''' - select OP Tariff when MNP is used. Default OP Tariff will be used if no match is found. | ||
* '''Capacity''' - limit the number of concurrent calls for this OP (both ringing and answered calls are included in this limit).<br> | * '''Capacity''' - limit the number of concurrent calls for this OP (both ringing and answered calls are included in this limit).<br> | ||
* '''Source (CallerID) Allow''' - regular expression (regexp) that defines which CallerIDs are allowed to go through this OP. If you want to allow all CallerIDs, enter '''.*''' in this input field.<br> | * '''Source (CallerID) Allow''' - regular expression (regexp) that defines which CallerIDs are allowed to go through this OP. If you want to allow all CallerIDs, enter '''.*''' in this input field.<br> | ||
* '''Source (CallerID) Deny''' - regular expression (regexp) that defines which CallerIDs are denied to go through this OP.<br> | * '''Source (CallerID) Deny''' - regular expression (regexp) that defines which CallerIDs are denied to go through this OP.<br> | ||
* '''Custom Tariff''' - Custom Tariff that can override regular OP Tariff. If rates are found in Custom Tariff then these rates will be applied in accounting. If rates are not found in Custom Tariff, then regular OP Tariff is used.<br> | * '''Custom Tariff''' - Custom Tariff that can override regular OP Tariff. If rates are found in Custom Tariff then these rates will be applied in accounting. If rates are not found in Custom Tariff, then the regular OP Tariff is used.<br> | ||
* '''Conditional Tariff''' : XXXXX (description why and how to use it [[M2_EU_Roaming_Regulations | here]]) | * '''Conditional Tariff''' : XXXXX (description why and how to use it [[M2_EU_Roaming_Regulations | here]]) | ||
Change Tariff and (or) Routing Group if: | Change Tariff and (or) Routing Group if: | ||
** CallerID matches/not matches Rule-Set: [[M2 Number Pools | Number Pool Rule Set]] <br> | ** CallerID matches/not matches Rule-Set: [[M2 Number Pools | Number Pool Rule Set]] <br> | ||
** Use CallerID Number from PAI Header if available: No / Yes <br> | ** Use CallerID Number from PAI Header if available: No / Yes <br> | ||
** and if Destination: do not use/matches/not | ** and if Destination: do not use/matches/not matches Rule-Set [[M2 Number Pools | Number Pool Rule Set]] <br> | ||
** Using this option it is possible to | ** Using this option it is possible to use another tariff if CallerID and Destination matched Rule-Set. It is possible to create a Rule-Set at Maintenance - Number Pools. Also, it offers the possibility to use the CallerID Number from PAI Header if available. | ||
* '''Default Tariff''' - Tariff used for OP accounting if previous option is not used.<br> | * '''Default Tariff''' - Tariff used for OP accounting if the previous option is not used.<br> | ||
* '''USA Jurisdictional Routing''' - Jurisdictional routing is telephone call routing logic based upon the locations of the calling and called number and regulatory considerations. More information can be found here [https://transnexus.com/whitepapers/jurisdictional-routing Here]. | * '''USA Jurisdictional Routing''' - Jurisdictional routing is telephone call routing logic based upon the locations of the calling and called the number and regulatory considerations. More information can be found here [https://transnexus.com/whitepapers/jurisdictional-routing Here]. | ||
** '''M2''' - '''Can be enabled by Kolmisoft only. Please contact support to enable.''' <br>[[File:USAJurisdictionalRouting.png]] | ** '''M2''' - '''Can be enabled by Kolmisoft only. Please contact support to enable.''' <br>[[File:USAJurisdictionalRouting.png]] | ||
*** Intra Tariff- Tariff for Intrastate routing. Calls between two points within the same state | *** Intra Tariff- Tariff for Intrastate routing. Calls between two points within the same state | ||
*** Inter Tariff - Tariff for Interstate routing. Calls made from one state to another | *** Inter Tariff - Tariff for Interstate routing. Calls made from one state to another | ||
*** Indeter Tariff - Tariff for Invalid ANI, or indeterminate routing. Calls where the calling number is any value other than a valid telephone | *** Indeter Tariff - Tariff for Invalid ANI, or indeterminate routing. Calls where the calling number is any value other than a valid telephone number — are usually rated at the intrastate rate | ||
** '''M4''': M4 configuration available [[M4 Local Number Portability|here]] | ** '''M4''': M4 configuration available [[M4 Local Number Portability|here]] | ||
| Line 123: | Line 123: | ||
* '''Name''' - set name part for CallerID.<br> | * '''Name''' - set name part for CallerID.<br> | ||
* '''Number''' - set number part for CallerID.<br> | * '''Number''' - set number part for CallerID.<br> | ||
* '''Random Number from Number Pool''' - set random number from Number Pool. Only number part for CallerID is set. | * '''Random Number from Number Pool''' - set random number from Number Pool. Only the number part for CallerID is set. | ||
** '''Random''' - Send random CallerID from Number Pool. | ** '''Random''' - Send random CallerID from Number Pool. | ||
** '''Pseudorandom with Deviation''' - Range can vary from 0 to 9999999. If 0 is chosen, then all numbers will be chosen same amount of times. If 9999999 is set, then numbers will be completely random. | ** '''Pseudorandom with Deviation''' - Range can vary from 0 to 9999999. If 0 is chosen, then all numbers will be chosen the same amount of times. If 9999999 is set, then numbers will be completely random. | ||
==Codecs== | ==Codecs== | ||
| Line 131: | Line 131: | ||
Set which codecs are allowed for OP.<br> | Set which codecs are allowed for OP.<br> | ||
* '''Inherit leg B Codecs''' - if enabled, system will try to force leg B negotiated Codec to leg A. If leg A does not support that Codec, then system uses any other available Codec. This option is used to prevent transcoding in some cases. More information can be found [[M2 Codec Negotiation | here]]. | * '''Inherit leg B Codecs''' - if enabled, the system will try to force leg B negotiated Codec to leg A. If leg A does not support that Codec, then the system uses any other available Codec. This option is used to prevent transcoding in some cases. More information can be found [[M2 Codec Negotiation | here]]. | ||
==Advanced== | ==Advanced== | ||
* '''Grace Time''' - if call duration is less than Grace Time, it will not be accounted (CDR will be generated, but OP balance will not be reduced).<br> | * '''Grace Time''' - if call duration is less than Grace Time, it will not be accounted for (CDR will be generated, but OP balance will not be reduced).<br> | ||
* '''Custom SIP Header''' - adds custom header to SIP request. Format is header: value (for example x-My-Custom-Header: my value).<br> | * '''Custom SIP Header''' - adds custom header to SIP request. Format is header: value (for example x-My-Custom-Header: my value).<br> | ||
* '''Limit up to X Calls, during Y seconds''' - allows | * '''Limit up to X Calls, during Y seconds''' - allows controlling Calls per Second (CPS).<br> | ||
* '''Disable Q.850 Reason''' - by default M2 returns Q.850 Reason header in SIP responses to Originator. This can be disabled by setting this option to "yes". | * '''Disable Q.850 Reason''' - by default M2 returns Q.850 Reason header in SIP responses to Originator. This can be disabled by setting this option to "yes". | ||
* '''Bypass Media''' - when set, the media (RTP) from the originating endpoint is sent directly to the destination endpoint and vice versa. The signaling (SIP) for both endpoints still goes through M2, but the media is point-to-point. | * '''Bypass Media''' - when set, the media (RTP) from the originating endpoint is sent directly to the destination endpoint and vice versa. The signaling (SIP) for both endpoints still goes through M2, but the media is point-to-point. | ||
| Line 143: | Line 143: | ||
==Advanced Origination Point Settings== | ==Advanced Origination Point Settings== | ||
* '''Accept calls from any port''' - if set to 'yes', then calls from any port are accepted. If set to 'no', then only calls from a specific port are accepted (see Port input field in authentication section).<br> | * '''Accept calls from any port''' - if set to 'yes', then calls from any port are accepted. If set to 'no', then only calls from a specific port are accepted (see Port input field in the authentication section).<br> | ||
* '''Change RPID/PAI Host''' - allows overwriting original host address in RPID/PAI header with proxy server's IP address. | * '''Change RPID/PAI Host''' - allows overwriting the original host address in RPID/PAI header with the proxy server's IP address. | ||
* '''Use Destination from INVITE request''' - by default M2 uses Destination number from SIP '''To''' header (To: <sip:123@sip.com>). If you set this option to "yes", M2 will use Destination number from SIP '''INVITE''' request line (INVITE sip:123@sip.com SIP/2.0). | * '''Use Destination from INVITE request''' - by default M2 uses Destination number from SIP '''To''' header (To: <sip:123@sip.com>). If you set this option to "yes", M2 will use the Destination number from SIP '''INVITE''' request line (INVITE sip:123@sip.com SIP/2.0). | ||
* '''Ring instead Session Progress''' - if enabled, M2 translates SIP 183 Session Progress from terminator side to SIP 180 Ringing to originator side ( | * '''Ring instead Session Progress''' - if enabled, M2 translates SIP 183 Session Progress from the terminator side to SIP 180 Ringing to the originator side (M4 receives SIP 183 from the terminator but sends SIP 180 to the originator). | ||
* '''Send CallerID in Contact header''' - when this option is enabled, the Contact header will be set to CallerID number. | * '''Send CallerID in Contact header''' - when this option is enabled, the Contact header will be set to the CallerID number. | ||
* '''Disconnect Code Changes''' - allows changing hangup code which is returned to OP.<br> | * '''Disconnect Code Changes''' - allows changing hangup code which is returned to OP.<br> | ||
* '''Use PAI Number for Routing''' - uses PAI Number instead of FROM callerID for routing. | * '''Use PAI Number for Routing''' - uses PAI Number instead of FROM callerID for routing. | ||
| Line 157: | Line 157: | ||
* '''Ignore SIP 183 without SDP''' - by default disabled. Select '''Yes''' to enable the option. | * '''Ignore SIP 183 without SDP''' - by default disabled. Select '''Yes''' to enable the option. | ||
* '''Ignore SIP 180 after 183''' - by default disabled. Select '''Yes''' to enable the option. | * '''Ignore SIP 180 after 183''' - by default disabled. Select '''Yes''' to enable the option. | ||
* '''Allow | * '''Allow using own User's TPs''' - by default, it is not allowed to route the call through TP which belongs to the same User. Such a call results in HGC 339. By setting this option to Yes, you can disable this protection. | ||
=Subnetting= | =Subnetting= | ||
It is possible to set [http://en.wikipedia.org/wiki/Subnetwork subnetwork] (subnet) for Origination Point. Subnets allow you to have single Origination Point for multiple IP addresses. Instead of IP address, you can set subnet in '''IP Address''' input field. Subnet should be written in [http://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing CIDR notation] (for example 192.168.0.1/28). When subnet is used in Origination Point, all calls coming from that subnet will be authenticated. | It is possible to set [http://en.wikipedia.org/wiki/Subnetwork subnetwork] (subnet) for Origination Point. Subnets allow you to have a single Origination Point for multiple IP addresses. Instead of IP address, you can set subnet in '''IP Address''' input field. Subnet should be written in [http://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing CIDR notation] (for example 192.168.0.1/28). When a subnet is used in Origination Point, all calls coming from that subnet will be authenticated. | ||
M2 subnet value range is 4-30. | M2 subnet value range is 4-30. | ||
<br><br> | <br><br> | ||
You can use online subnet [http://www.aboutmyip.com/AboutMyXApp/SubnetCalculator.jsp? calculator] to check IP addresses for given subnet.<br> | You can use an online subnet [http://www.aboutmyip.com/AboutMyXApp/SubnetCalculator.jsp? calculator] to check IP addresses for a given subnet.<br> | ||
=IP range= | =IP range= | ||
If you need to set multiple IP addresses for single | If you need to set multiple IP addresses for a single Origination Point and Subnetting does not meet your needs, then you can set IP ranges. Ranges are written in the following format: | ||
xxx.xxx.xxx.xxx-yyy | xxx.xxx.xxx.xxx-yyy | ||
When IP range is used in Origination Point, all calls coming from that IP range will be authenticated. For example, if we have IP range 192.168.0.101-150, then all IP addresses starting from 192.168.0.101 to 192.168.0.150 will be authenticated (50 different IP addresses are allowed to call to this Origination Point).<br> | When an IP range is used in Origination Point, all calls coming from that IP range will be authenticated. For example, if we have an IP range 192.168.0.101-150, then all IP addresses starting from 192.168.0.101 to 192.168.0.150 will be authenticated (50 different IP addresses are allowed to call to this Origination Point).<br> | ||
Revision as of 10:46, 29 November 2022
Origination Point is a connection from some initial entity (device/line/trunk/provider/supplier/etc) where the call starts/originates.
The call comes from Origination Point and goes to Termination Points.
Timeouts
- Ringing Timeout - allows limiting ringing duration (in seconds). Leave 0 for unlimited.
- Call Timeout - allows limiting Call duration (in seconds). Leave 0 for unlimited (global Call timeout (7200 seconds) is still applicable in this case).
Servers
Origination Points (OP) can be assigned to one or more servers. If a call comes from the server where OP is not assigned, the call will not go through.
Authentication Simple
Static IP:
- IP Address - IP Address of Origination Point (subnetting and IP range is allowed. For more information read Subnetting and IP range sections below).
- Port - Port of Origination Point.
- Tech. Prefix - Destination technical prefix that is used to authenticate OP. If this field is empty, calls will be accepted with any Destination number only based on IP:PORT. If this field is not empty, then only calls with specific prefixes in Destination will be authenticated (for example if Tech. Prefix is 00, then OP accepts Destination numbers that start with 00xxxxxxx).
Dynamic IP:
- Username - Username you enter in your Device.
- Password - Password you enter in your Device.
- Status - Registration status
- UNREGISTER - last registration information will be deleted (ipaddr, port, fullcontact).
- Tech. Prefix - Destination technical prefix that is used to authenticate OP.
Authentication Advanced
Static IP:
Dynamic IP:
Old Format transformation rules can be found here and here.
Regexp transformation format is:
/match_expression/replacement_expression/flags
- match_expression - POSIX regular expression
- replacement_expression - replacement expression with back references to matched tokes: \1, \2, …, \9
- flags:
- i - match ignore case
- g - replace all matches
Before putting Transformations into production, it is advisable to test them on various values.
Test in Linux console
Execute sed command (add s before transformation s/regex/replacement/flags):
echo '00370123456789' | sed -E 's/^00//'
Test in online sed live editor
If you do not have access to the Linux console, use https://sed.js.org/ (or any other online sed editor).
Validate regex
The regex part of a Transformation can be validated using https://regexr.com/ (or any other online regex editor).
Examples
| Transformation | Original number | Modified number | Comment |
| /^00// | 003701234567 | 003701234567 | Cut prefix 00 |
| /^370/8/ | 370123456789 | 8123456789 | Replace 370 with 8 |
| /\+// | +370123456789 | 370123456789 | Cut + (here + is escaped by \ since it is special regex symbol) |
| /\+370/86/ | +370123456789 | 86123456789 | Cut prefix +370, add prefix 86 |
| /\+?(.*)/+\1/ | 370123456789 | +370123456789 | Add + if it is not present already |
Origination Point
- Act as Origination Point - if set to 'yes', this Connection Point will be handled as Origination Point.
- Active - allows to activate or deactivate OP. If OP is deactivated, calls will not be accepted from this OP.
- Destination Transformation - special Destination Transformation rules used to modify outgoing number. Rules are applied before billing so they can be used to correct non-E164 formats.
- Source Transformation - special Source Transformation rules used to modify Source number.
- Routing Algorithm - defines how Termination Points are ordered for this Origination Point.
- Routing Group - Routing Group used for OP routing.
- Use MNP - enable MNP for this OP.
- MNP Routing Group - name of Routing Group used for MNP.
- OP Tariff when MNP is used - select OP Tariff when MNP is used. Default OP Tariff will be used if no match is found.
- Capacity - limit the number of concurrent calls for this OP (both ringing and answered calls are included in this limit).
- Source (CallerID) Allow - regular expression (regexp) that defines which CallerIDs are allowed to go through this OP. If you want to allow all CallerIDs, enter .* in this input field.
- Source (CallerID) Deny - regular expression (regexp) that defines which CallerIDs are denied to go through this OP.
- Custom Tariff - Custom Tariff that can override regular OP Tariff. If rates are found in Custom Tariff then these rates will be applied in accounting. If rates are not found in Custom Tariff, then the regular OP Tariff is used.
- Conditional Tariff : XXXXX (description why and how to use it here)
Change Tariff and (or) Routing Group if:
- CallerID matches/not matches Rule-Set: Number Pool Rule Set
- Use CallerID Number from PAI Header if available: No / Yes
- and if Destination: do not use/matches/not matches Rule-Set Number Pool Rule Set
- Using this option it is possible to use another tariff if CallerID and Destination matched Rule-Set. It is possible to create a Rule-Set at Maintenance - Number Pools. Also, it offers the possibility to use the CallerID Number from PAI Header if available.
- CallerID matches/not matches Rule-Set: Number Pool Rule Set
- Default Tariff - Tariff used for OP accounting if the previous option is not used.
- USA Jurisdictional Routing - Jurisdictional routing is telephone call routing logic based upon the locations of the calling and called the number and regulatory considerations. More information can be found here Here.
- M2 - Can be enabled by Kolmisoft only. Please contact support to enable.
- Intra Tariff- Tariff for Intrastate routing. Calls between two points within the same state
- Inter Tariff - Tariff for Interstate routing. Calls made from one state to another
- Indeter Tariff - Tariff for Invalid ANI, or indeterminate routing. Calls where the calling number is any value other than a valid telephone number — are usually rated at the intrastate rate
- M4: M4 configuration available here
- M2 - Can be enabled by Kolmisoft only. Please contact support to enable.
CallerID
- Name - set name part for CallerID.
- Number - set number part for CallerID.
- Random Number from Number Pool - set random number from Number Pool. Only the number part for CallerID is set.
- Random - Send random CallerID from Number Pool.
- Pseudorandom with Deviation - Range can vary from 0 to 9999999. If 0 is chosen, then all numbers will be chosen the same amount of times. If 9999999 is set, then numbers will be completely random.
Codecs
Set which codecs are allowed for OP.
- Inherit leg B Codecs - if enabled, the system will try to force leg B negotiated Codec to leg A. If leg A does not support that Codec, then the system uses any other available Codec. This option is used to prevent transcoding in some cases. More information can be found here.
Advanced
- Grace Time - if call duration is less than Grace Time, it will not be accounted for (CDR will be generated, but OP balance will not be reduced).
- Custom SIP Header - adds custom header to SIP request. Format is header: value (for example x-My-Custom-Header: my value).
- Limit up to X Calls, during Y seconds - allows controlling Calls per Second (CPS).
- Disable Q.850 Reason - by default M2 returns Q.850 Reason header in SIP responses to Originator. This can be disabled by setting this option to "yes".
- Bypass Media - when set, the media (RTP) from the originating endpoint is sent directly to the destination endpoint and vice versa. The signaling (SIP) for both endpoints still goes through M2, but the media is point-to-point.
Advanced Origination Point Settings
- Accept calls from any port - if set to 'yes', then calls from any port are accepted. If set to 'no', then only calls from a specific port are accepted (see Port input field in the authentication section).
- Change RPID/PAI Host - allows overwriting the original host address in RPID/PAI header with the proxy server's IP address.
- Use Destination from INVITE request - by default M2 uses Destination number from SIP To header (To: <sip:123@sip.com>). If you set this option to "yes", M2 will use the Destination number from SIP INVITE request line (INVITE sip:123@sip.com SIP/2.0).
- Ring instead Session Progress - if enabled, M2 translates SIP 183 Session Progress from the terminator side to SIP 180 Ringing to the originator side (M4 receives SIP 183 from the terminator but sends SIP 180 to the originator).
- Send CallerID in Contact header - when this option is enabled, the Contact header will be set to the CallerID number.
- Disconnect Code Changes - allows changing hangup code which is returned to OP.
- Use PAI Number for Routing - uses PAI Number instead of FROM callerID for routing.
- Send PAI Number as CallerID to TP - uses PAI Number as CallerID.
- Forward RPID - by default forward RPID header from Originator to Terminator. This can be disabled by setting this option to "no". More info
- Forward PAI - by default forward PAI header from Originator to Terminator. This can be disabled by setting this option to "no". More info
- PAI Transformation - apply Transformation on PAI header. More info
- RPID Transformation - apply Transformation on RPID header. More info
- Ignore SIP 183 without SDP - by default disabled. Select Yes to enable the option.
- Ignore SIP 180 after 183 - by default disabled. Select Yes to enable the option.
- Allow using own User's TPs - by default, it is not allowed to route the call through TP which belongs to the same User. Such a call results in HGC 339. By setting this option to Yes, you can disable this protection.
Subnetting
It is possible to set subnetwork (subnet) for Origination Point. Subnets allow you to have a single Origination Point for multiple IP addresses. Instead of IP address, you can set subnet in IP Address input field. Subnet should be written in CIDR notation (for example 192.168.0.1/28). When a subnet is used in Origination Point, all calls coming from that subnet will be authenticated.
M2 subnet value range is 4-30.
You can use an online subnet calculator to check IP addresses for a given subnet.
IP range
If you need to set multiple IP addresses for a single Origination Point and Subnetting does not meet your needs, then you can set IP ranges. Ranges are written in the following format:
xxx.xxx.xxx.xxx-yyy
When an IP range is used in Origination Point, all calls coming from that IP range will be authenticated. For example, if we have an IP range 192.168.0.101-150, then all IP addresses starting from 192.168.0.101 to 192.168.0.150 will be authenticated (50 different IP addresses are allowed to call to this Origination Point).
