M2 Origination Points

From Kolmisoft Wiki

Jump to: navigation, search

Origination Point is connection from some initial entity (device/line/trunk/provider/supplier/etc) where call starts/originates.

Call comes from Origination Point and goes to Termination Points.


[edit] Why there is no Register option on Origination Point?

Registrations are needed when Dynamic IP addresses are used. Dynamic IP addresses are very common on Retail business, but not on Wholesale. That is why M2 does not have such option.

You as a system owner can allow traffic from IP:Port:Technical Prefix. This is enough to receive traffic from any OP.

[edit] Connection Point configuration

[edit] General

  • Description - short name for Origination Point.
  • Ringing Timeout - allows to limit ringing duration (in seconds). Leave 0 for unlimited.
  • Call Timeout - allows to limit Call duration (in seconds). Leave 0 for unlimited (global Call timeout (7200 seconds) is still applicable in this case).

[edit] 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.

[edit] Authentication

  • 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 prefix in Destination will be authenticated (for example if Tech. Prefix is 00, then OP accepts Destination numbers which start with 00xxxxxxx).
  • 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.

[edit] 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 it 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.
  • 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.
  • Use Tariff : XXXXX (description why and how to use it here)
    • 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 matces Rule-Set Number Pool Rule Set
    • Using this option it is possible to Use other tariff if CallerID and Destination matched Rule-Set. It is possible to create a Rule-Set at Maintenance - Number Pools. Also, it offers possibility to use CallerID Number from PAI Header if available.
  • Default Tariff - Tariff used for OP accounting if previous option is not used.
  • Custom Tariff - Custom Tarrif 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.

[edit] 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 number part for CallerID is set.

[edit] Codecs

Set which codecs are allowed for OP.

  • 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 here.

[edit] 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).
  • 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 to control 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".
  • Forward RPID - by default M2 forwards RPID header from Originator to Terminator. This can be disabled by setting this option to "no".
  • Forward PAI - by default M2 forwards PAI header from Originator to Terminator. This can be disabled by setting this option to "no".
  • 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.

[edit] 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 specific port are accepted (see Port input field in authentication section).
  • Change RPID/PAI host - allows to overwrite original host address in RPID/PAI header with M2 host 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).
  • Ring instead Session Progress - if enabled, M2 translates SIP 183 Session Progress from terminator side to SIP 180 Ringing to originator side (M2 receives SIP 183 from terminator but sends SIP 180 to originator).
  • Send CallerID in Contact header - when this option is enabled, Contact header will be set to CallerID number.
  • Disconnect Code Changes - allows to change hangup code which is returned to OP.

[edit] Subnetting

It is possible to set 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 CIDR notation (for example When subnet is used in Origination Point, all calls coming from that subnet will be authenticated.

You can use online subnet calculator to check IP addresses for given subnet.

[edit] IP range

If you need to set multiple IP addresses for single Orignation Point and Subnetting does not meet your needs, then you can set IP ranges. Ranges are written in the following format:


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, then all IP addresses starting from to will be authenticated (50 different IP addresses are allowed to call to this Origination Point).

Personal tools


Try M2