Author Topic: Inbound Trunk call processing  (Read 1728 times)

Offline martyn

  • Hero Member
  • *****
  • Posts: 688
  • Country: au
  • Karma: +10/-0
    • View Profile
Inbound Trunk call processing
« on: February 23, 2016, 07:08:09 PM »
Does anyone know the order that a SIP trunk processes the stripping of digits on an inbound call for the called party? ie, does trunk attributes get applied, then inward dialling mod, or other way round?


Offline sarond

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 1404
  • Country: au
  • Karma: +73/-0
    • View Profile
Re: Inbound Trunk call processing
« Reply #1 on: February 24, 2016, 03:00:27 AM »
From the help files (DID Service)

Incoming DID call processing algorithm
    Trunk service digit modification is performed, based on the incoming trunk configuration.
    System Speed Calls lookup is conducted.
    CRS database is searched for the modified DID number and the associated destination number.

Possible CRS query responses:

NO MATCH - no associated destination number found
EXACT MATCH - the exact one associated destination number found
CONFLICTING MULTIPLE MATCHES - more than one associated destination number found
PARTIAL MATCH - one or more matches associated with the subset of queried digit string found

    If an exact match is found in the CRS database, the call is routed to the destination number. Otherwise, the following routing is applied:

    If the search returns conflicting multiple matches, no matches are used and the call is routed on the originally dialed digits.

    If a partial match is found, the call is routed on the originally dialed digits.

    In a rare conflict scenario where: FOPBX (Force-to-PBX) is configured as the CRS option in the Trunk Attributes form, both CRS and DID service are enabled, and the EHDU external number matches the DID number, the call will be handled by CRS and not DID Service.

In the following circumstances a call cannot be routed to its destination and an appropriate intercept handling is applied:

    CRS query returns NO MATCH (no destination number is assigned to the DID number) because a suite or a Hotel Room Extension Not In Suite (HRENIS) to which the DID was assigned is now checked out. (This occurs only if the hotel option Cancel All Features on Check-Out is enabled.)

    DID destination number cannot be routed for any other reason.

In the above scenarios, Intercept Handling for "Unassigned Directory Number" is applied and the Reorder Tone is returned.

    DID destination is out of service.

In this case, Intercept Handling for "Directory Number Out of Service" is applied and the Reorder Tone is returned.

Offline martyn

  • Hero Member
  • *****
  • Posts: 688
  • Country: au
  • Karma: +10/-0
    • View Profile
Re: Inbound Trunk call processing
« Reply #2 on: February 24, 2016, 04:41:22 PM »
Thanks for that, it covers a little bit of what I was after, and hadn't come across that in the help file. The one bit that the help doesn't cover is the called party inward dialling modification.

The scenario I am trying to understand is when a call comes in on a SIP trunk, does the trunk attribute get applied, followed by any incoming called party modification, or does the incoming call mod get processed then the trunk attribute?

Offline johnp

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 2202
  • Country: us
  • Karma: +66/-0
    • View Profile
Re: Inbound Trunk call processing
« Reply #3 on: February 24, 2016, 08:28:32 PM »
I think the sip mod happens first thing


 

Sitemap 1 2 3 4 5 6 7 8 9 10