Page tree
Skip to end of metadata
Go to start of metadata

When executing either Digit Matching/Translations or Routing, the digits 0x0A-0x0F react differently depending on whether routing/digit matching is on the incoming leg or outgoing leg. See Below. This feature is supported in all protocols.

 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 needs to be completed.

 Support Digit A to F = False (Default)

Example 1:

If a call is received 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 could 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 2020 will match the incoming # character and then convert it to an F character. 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 2020 would convert the # to an F characters and the number 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 either True or False from the drop down menu in Channel Group in the Web GUI channel group page. The Default is value is False. The value False does not offer support for digits 0x0A-0x0F on outgoing leg.

 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 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 completed 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.

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

Portion of Call Trace

20:15:27.418 CALL(GCL) (00:00005:00) Supporting digits A to F (Enabled!!!)

20:15:27.428 CALL(GCL) (00:00005:01) Supporting digits A to F (Disabled!!!)

  • Messaging between the IMG 2020 and RADIUS server is also converted. Refer to screen captures below.

Call Trace (RADIUS)

Below is 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 2010
   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 2010
   NAS-IP-Address = 10.11.1.48
   NAS-Port = 1813
   Called-Station-Id = "45abfbe7ef"  <-- "Number was 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


  • No labels