IMG 1010 - Digit 0x0a to 0x0f Support

Up until and including software 10.5.0 the IMG supported accepting the digits 0x00-0x09, * , and # for processes such as routing, translations, Dialing Plan Events, and Radius. In software 10.5.1, feature F-1212 Support for the digits 0x0a - 0x0f was implemented. With the added functionality, the IMG can be configured to process the digits 0x0a though 0x0f. The added functionality impacts how the functions such as the Dialing Plan Event (DPE), Router, and RADIUS use the digits for digit matching, routing and Billing. Feature F-1212 is supported in all protocols. Refer to the information below.

Incoming/Outgoing Leg Channel Group functionality

Support for digits 0x0a - 0x0f is configured on a channel group basis. If the user wants the digits 0x0a - 0x0f support to be enabled end-to-end, the user has to enabled it on both the incoming and outgoing channel groups. If the digits 0x0a - 0x0f is not required, then nothing in the initial configuration of the IMG needs to be completed.

Prior to 10.5.3 SP12, digits 0x0a-0x0f, *, and # is enabled all the time on the incoming leg and the user only needed to enabled the 0x0a - 0x0f support on the outgoing Channel Group.

In the scenario when sending/routing digits only digits 0x0a-0x0f are supported. The * and # characters will be converted to 0x0e and 0x0f respectively. Below are some examples:

Support Digit A to F = False (Default)

Example 1:

If a call comes in as 8623000# and the user wants to match that digit string then 8623000# or 8623000f entered in the string field of the Translation Table pane would satisfy the match.

Example 2:

If a call comes in and the user wants to append # to 8623000 then the string value entered in Translation Table would be 8623000 and the Originating # Translation field would be 8623000# or 8623000f. Both would satisfy the digit matching.

Example 3:

A call is sent through Radius Server for billing purposes and the number being sent is 8623000#. It would appear in the CDR as 8623000#

Example 4:

If a call comes in as 862abcd the digits will not be passed correctly. The digits abcd will be matched on the incoming side but will be dropped on outgoing side. The digits being sent out on outgoing side will go out as 862 and abcd will be dropped.

Support Digit A to F = True (Support for Digit A to F enabled)

Example 1:

If a call comes in as 8623000# the IMG will match the incoming '#' and then convert it to an 'f'. When the call is sent out on the outgoing leg the digits 8623000f will be sent.

Example 2:

A call comes in as 8623000. You would like to append the 'f' character to the end of the incoming call. The string value entered in Translation Table would be 8623000 which will match the incoming side. The Originating # Translation field would be set to 8623000f. The call would then be sent out as 8623000f.

Example 3:

A call is sent through Radius and the number being sent is 8623000#. The IMG would convert the # to an 'f' and it would appear in the CDR as 8623000f

Example 4:

If a call comes in as 862abcd and the user wants to match that digit string then 862abcd entered in the string field of the Translation Table pane would satisfy the match.

Configuration:

To enable/disable the Support for BCD digits 0x0a - 0x0f select from the drop down menu in IMG 1010 - Channel Group in ClientView. The Default is False which does not offer support for digits 0x0a-0x0f on outgoing leg. Channel Group for CAS shown below. See Below

Additional Information

• This feature is enabled in the Channel Group Pane, therefore some channel groups can be configured as supporting digits 0x0a through 0x0f and other channel groups can be left as the default which is supporting digits 0x00-0x09, '#', and '*'.

• All sorting is done as explained in the IMG 1010 - Digit Matching Topic.

• The digit table supports only 0-9, *, #, x, and &. If 0x0a through 0x0d is in the matching string then that entry should go to the sequential list. The tree match is done first and then the sequential list is used if there is no match in the Digit tree. For Example: If 862& and 862d are entries in a routing table and the string to match is set at 862d the router will return 862& as the match found.

• The CAS protocol supports digits 0x0a - 0x0e but does not support digit 0x0f. In the CAS protocol when an 'f' is received, it is interpreted as a group change signal. If it was collecting the Dialed Number, upon receiving the digit 0x0f it will start collecting ANI digits instead.

  • Call Tracing displays whether the Support for digits A to F is enabled or disabled. Refer to the portion of call trace displayed below. The first line in the table displays that the Support for digits A to F is set to Enabled on the incoming (00) channel group. The second line in the table displays that the Support for digits A to F is set to Disabled on the outgoing (01) channel group.

Messaging between the IMG 1010 and RADIUS server is also converted. Refer to screen capture below.

Call Trace (RADIUS)

Below are Call Trace of a SIP to ISDN call. The Dialed number is 45ab#b*7ef which is shown below

Incoming SIP Call:

Thu Jul 10 21:14:11 2012

NAS-IP-Address = 10.11.1.48

NAS-Port = 1813

Called-Station-Id = "45abfbe7ef"  <--- Shows converted number. The # and * were converted to f and e

Acct-Session-Id = "00201c11139f008400f010002c58393c002e"

Acct-Status-Type = Start

NAS-Port-Type = Ethernet

Service-Type = Login-User

Dialogic-call-origin = "originate"

Dialogic-call-type = "SIP"

Acct-Delay-Time = 0

Login-IP-Host = 10.11.1.92

Tunnel-Client-Endpoint:0 = "10.11.1.48"

Dialogic-setup-time = "FRI JAN 02 03:09:12:380 1970"

Dialogic-voip-dst-sig-ip-in = "10.11.1.29"

Dialogic-voip-dst-rtp-ip-in = "10.11.1.29"

Dialogic-dnis-pre-translate = "45abfbe7ef"

Dialogic-call-direction = "INCOMING LEG"

Dialogic-trunk-grp-in = "SIP"

Dialogic-voip-src-rtp-ip-in = "10.11.1.201"

Dialogic-voip-src-sig-ip-in = "10.11.1.48"

Dialogic-call-id = "1-2564@10.11.1.29"

Dialogic-prev-hop-ip = "10.11.1.29:5060/UDP"

Dialogic-prev-hop-via = "sip:10.11.1.29:5060"

Dialogic-incoming-req-uri = "sip:45ab#b*7ef@10.10.1.48" <--- "Shows Original Dialed Number 45ab#b*7ef"

Dialogic-voip-local-vocoders = "PCMU,PCMA"

Dialogic-voip-remote-vocoders = "PCMU"

Dialogic-voip-codec-priority = "Local"

Client-IP-Address = 10.11.1.48

Acct-Unique-Session-Id = "d898dbf224a2e7c1"

Timestamp = 1215692051

SIP to ISDN:

Thu Jul 10 21:14:12 2012

NAS-IP-Address = 10.11.1.48

NAS-Port = 1813

Called-Station-Id = "45abfbe7ef" <--Number has been converted. The # and * were converted to f and e

Acct-Session-Id = "00201c11139f008400f010002c58393c002e"

Acct-Status-Type = Start

NAS-Port-Type = Ethernet

Service-Type = Login-User

Dialogic-call-origin = "answer"

Dialogic-call-type = "ISDN"

Acct-Delay-Time = 0

Login-IP-Host = 10.11.1.92

Tunnel-Client-Endpoint:0 = "10.11.1.48"

Dialogic-setup-time = "FRI JAN 02 03:09:13:470 1970"

Dialogic-connect-time = "FRI JAN 02 03:09:13:530 1970"

Dialogic-dnis-post-translate = "45abfbe7ef"  <--- Shows the DNIS translation

Dialogic-call-direction = "OUTGOING LEG"

Dialogic-trunk-grp-out = "ISDNOut"

Client-IP-Address = 10.10.1.48

Acct-Unique-Session-Id = "d898dbf224a2e7c1"

Timestamp = 1215692052