V4 Dialler Programming Guide

Report as inappropriate Your report has been received

Shared by: HC120727085712

Tags

Stats

views:: 7
posted:: 7/27/2012
language:: English
pages:: 18

Public Domain

Document Sample

The Orchid V4 Dialler
A Manual Programming Guide
by Roger Shilcock

Orchid V4 Dialler Manual Programming Guide - Version 1.214 Page 1 of 18
Table of Contents
Introduction ...................................................................................................... 3
Ways to program the dialler ................................................................................ 3
How to use a telephone to program the dialler ....................................................... 3
Make changes or start from scratch? .................................................................... 4
Command strings explained ................................................................................ 4
Set Non-Managed Mode ........................................................................ 4
Set Daytime Time Band ........................................................................ 4
Set Weekend Time Band ....................................................................... 5
Set the internal clock ........................................................................... 5
Set the local STD Code ......................................................................... 5
Clear the Carrier Code Table .................................................................. 5
Clear the Routing Code Table................................................................. 5
Write a new entry to the Carrier Code Table ............................................ 5
Sample Carrier Code Table .................................................................... 7
Write an entry into the Routing Code Table ............................................. 8
Sample Routing Code Table ................................................................. 12
Routing Code Attributes ...................................................................... 12
Manual Programming Template .......................................................................... 14
Reference Carrier Code Table .............................................................. 14
Reference Routing Code Table ............................................................. 14
Checking the Dialler Output .............................................................................. 15
The BT Socket Recording Lead ............................................................. 15
Connecting the recording lead to your computer or laptop ...................... 16
Recording and Analysing the Dialler Output ........................................... 16
Screen Shots from DTMF Decoder and Switch Sound File Converter ......... 17
Conclusion and Disclaimer ................................................................................. 18
Document History ............................................................................................ 18

Orchid V4 Dialler Manual Programming Guide - Version 1.214 Page 2 of 18
Introduction
The purpose of the Orchid V4 Dialler is to intercept phone numbers dialled by telephones connected
to it and process them before passing them through to the telephone network. Processing is based
on a pair of programmable lookup tables held in the dialler, one called the Routing Code Table and
the other called the Carrier Code Table. When a number is dialled by a connected telephone, the
dialler looks through the Routing Code Table to try and find a best match for some or all of the
number dialled. If it manages to find a match, it uses fields from the Routing Code Table entry to
decide what to do with the number which is usually to add a carrier code prefix from the Carrier
Code Table to the front of it such as 1899, 18185, 1280, etc. before sending the whole number
including the added prefix out to the telephone network. It can however convert the dialled number
into a different number (this is called “translating”) and it can also block certain numbers completely
(this is called “barring”) so that if someone dials one of these restricted or barred numbers, the
phone doesn't dial the number at all and just returns a dial tone.
One thing to appreciate first of all is that the dialler is a “write only device” which means that you
can send commands to it but you can't read it's configuration from it. You send it commands to do
things such as write entries into the Routing Code and Carrier Code tables, set the time/date,
configure daytime/evening/weekend time bands, clear the internal tables, and various other
configuration things. You cannot view the device's tables or other configuration afterwards
so it is essential that you keep an accurate record of what you have programmed,
particularly the two tables.

Ways to program the dialler
The manufacturers of the dialler used to provide a PC program called CWClient which allowed you to
make changes to your dialler's configuration tables and store them on their server from where they
could be downloaded to your dialler over the phone line. Unfortunately, this facility is no longer
available and since the only way to program the dialler is via the phone line OR a telephone (or
modem) connected to it, another method was needed. A spreadsheet was subsequently written by
Kevin Lawry which worked in a similar way to the original CWClient program using tables, macros
and a modem connected to the dialler and allowed full programming to be carried out but requires
you to have a modem and Microsoft Excel before you can use it. The alternative way of
programming the dialler is to do it simply using a telephone handset attached to the dialler and
issue “command strings” to it by dialling special numbers rather than simple telephone numbers.
This document has been written to describe how to do this and gives worked examples as well as an
explanation of the two tables (Routing Code and Carrier Code) describing what the various entries in
them actually do.

How to use a telephone to program the dialler
The best type of telephone to use for programming the dialler is one that has some kind of number
display so you can see the string of characters and numbers you are dialling, and can enter the
whole string before lifting the handset (or if it's a cordless phone, pressing the dial button) to dial it
but if you don't have a phone like that, pretty much any phone that supports tone dialling (all
modern phones work that way) should do. However, you must remember that for each “command
string” dialled, you have to hang up the phone after you have dialled it before entering and dialling
the next one. Have your dialler connected to the telephone socket in your house and plug a
telephone into the dialler, you are then ready to go. If you use a phone that allows you to pre-enter
a number first and then dial it, enter the whole command string, then either press the dial button on
your phone or lift the handset to dial the command string. After the string has been dialled, hang
up or replace the handset. If you use a more basic phone, lift the handset and when you hear the
dial tone, enter the command string then hang up.

Orchid V4 Dialler Manual Programming Guide - Version 1.214 Page 3 of 18
Make changes or start from scratch?
If you already have a dialler that is programmed and working, configured as it was supplied by the
manufacturer, you don't really want to mess about with it unless you know what you are doing and
have an exact record of how it is programmed already. In other words, you need to know the
contents of the Routing Code Table and Carrier Code Table so that you don't accidentally mess up
entries already programmed. If you are lucky and have a record of your dialler's configuration,
either in the form of a printout from the CWClient program or a spreadsheet which the manufacturer
sometimes provided after they ceased support of the CWClient program, then you can use that as
your reference and just make changes as and when you need to. If however, you don't have this
information or your dialler has played up and you want to reset its configuration starting again from
scratch, you can do that using the procedures described in this document. To start from scratch,
you would need to go through the following steps by sending the dialler command strings to do the
following things:-
 Set Non-Managed mode
 Set Daytime time band
 Set Weekend time band
 Set the internal clock
 Set you local STD code
 Clear the Carrier Code Table
 Clear the Routing Code Table
 Program entries into the Carrier Code Table
 Program entries into the Routing Code Table

Command strings explained
The command strings that you send to your dialler using the attached telephone are made up of
ordinary numbers and the “special characters” star (*) and hash (#) because when the dialler
receives a string that starts with and contains these “special characters” it understands that it is
being told to do something to it's internal programmed configuration rather than just dial a number.
All the command strings start with a star (*) and then contain further numbers, stars or hashes
depending on what type of command string it is. Below is a description of the command strings
that were mentioned above in the order that you would use them to help understand how they are
made up.

Set Non-Managed Mode
This command tells the dialler that it is NOT to be programmed via the telephone line from the
manufacturer's server as this facility no longer exists.
**#0000*0*8

Set Daytime Time Band
This command starts with three stars (***) followed by the start and end times of the daytime time
band in 24 hour format and ends with a star followed by a 5. BT is currently using 7am as the start
and 7pm as the end of their Daytime call charging band so that is what the example below is
setting.
***07001900*5

Orchid V4 Dialler Manual Programming Guide - Version 1.214 Page 4 of 18
Set Weekend Time Band
This command starts with three stars and a 6 (***6) followed by the day of the week and time (24
hour format) for the start and end of the weekend charge period where Monday is day 1 and Sunday
is day 7. It ends with a star followed by a 6. In the example the weekend starts at one minute into
Saturday and ends at one minute before midnight on Sunday.
***6000172359*6

Set the internal clock
This command starts with **#0000* followed by the time, day of week, date in ddmmyy format
and ends with a star followed by a 2. In the example I'm setting the clock at 9:30am on Tuesday
the 28th of February 2012.
**#0000*09302280212*2
Note: It is worth running this command every so often to ensure that the internal clock is still
correct.

Set the local STD Code
This command starts with three stars (***) followed by an STD code and ends with a star followed
by a 4. It sets your local STD code so that if you dial a local number without using the STD code, the
dialler will add the stored STD code to the front of the number dialled before sending it out to the
telephone network. In the example below it is setting as code of 01329.
***01329*4
Note: Remember that your STD code may be 3 digits (e.g. London 020, Cardiff 029), 4 digits (e.g.
Manchester 0161) or 5 digits (e.g. Fareham 01329).

Clear the Carrier Code Table
This command is used to completely empty the Carrier Code Table before you start programming it
with your own entries.
**#0000*2222*6

Clear the Routing Code Table
This command is used to completely empty the Carrier Code Table before you start programming it
with your own entries.
**#0000*1111*6

Write a new entry to the Carrier Code Table
This command starts with *#** followed by a sequence of numbers, usually the prefix you want to
add to the dialled number before sending it out (1899, 18185, 1280, etc.) and ends with a star (*)
followed by the location in the Carrier Code Table that you want to write the carrier code into (1 to
8). It is important to note that you cannot erase an individual Carrier Code Table entry, only
overwrite it with new data.
There are exceptions to this format, one being the Translate function where the sequence of
numbers after the *#** is a number that you want to substitute in place of a number that was
dialled. The use of Translate will be described in a bit more detail later.
Note: According to the official Orchid manual, location 9 is reserved and must NOT be used.

Orchid V4 Dialler Manual Programming Guide - Version 1.214 Page 5 of 18
Example 1.
This carrier code adds 18185 to the dialled number before being sent out. This is written to location
1 of the Carrier Code Table.
*#**18185*1
*#** The command identifiers
18185 The prefix to be added to the original dialled number
* Field separator
1 The Carrier Code Table Location

Example 2.
This carrier code adds 1899 to the dialled number before being sent out. This is written to location
2 of the Carrier Code Table.
*#**1899*2
*#** The command identifiers
1899 The prefix to be added to the original dialled number
* Field separator
2 The Carrier Code Table Location

Example 3.
This carrier code adds 1280 to the dialled number before being sent out which in this case will
override any carrier pre-select feature on your phone line and drop the call through to your
telephone line provider. This is written to location 3 of the Carrier Code Table.
*#**1280*3
*#** The command identifiers
1280 The prefix to be added to the original dialled number
* Field separator
3 The Carrier Code Table Location

Example 4.
This carrier code is used for the Translate feature and will replace the original number dialled with
1280 followed by a pause and then 08001183733. This is written to location 4 of the Carrier Code
Table.
*#**1280#08001183733*4
*#** The command identifiers
1280 The first part of the number to be sent out
# A one second pause
08001183733 The rest of the number to be sent out
* Field separator
4 The Carrier Code Table Location

Orchid V4 Dialler Manual Programming Guide - Version 1.214 Page 6 of 18
Sample Carrier Code Table
Below is a sample Carrier Code Table to give you an idea of the type of entries to be found. You
should note that the columns headed “Carrier Code” and “Description” are for information only and
are not actually programmed into the dialler.

Location Carrier Code Description Programming Code
1 18185 Call 18185 *#**18185*1
2 1899 Call 1899 *#**1899*2
3 1280 CPS Override *#**1280*3
4 1280#08001183733 Call 08001183733 via your line provider *#**1280#08001183733*4
5 empty
6 empty
7 empty
8 empty
9 **** RESERVED ****

If you look at location 4 in the above table you can see that it has been used along with the
Translate feature to call a Freephone number 08001183733 when you actually dialled a different
number. There is a free Director Enquiries service on that number so you can put an entry in your
Routing Code Table so that when you dial 192 on your phone, your dialler will actually dial 1280
followed by a one second pause, followed by 08001183733 for you. The Routing Code Table entry
will look like the one below and is in location 11 of the sample table shown later in this document.

*###192#5444#11#
*### The command identifiers
192 The part of the dialled number to be matched
# Field separator
5 Routing Code Attribute (Translate)
4 The carrier code location to be used for Daytime
4 The carrier code location to be used for Evening
4 The carrier code location to be used for Weekend
# Field Separator
11 The Routing Table Location
# Terminating character

Orchid V4 Dialler Manual Programming Guide - Version 1.214 Page 7 of 18
Write an entry into the Routing Code Table
This command is the most complicated to understand and starts with *### followed by all or part of
a dialled number that you want the dialler to detect and process. It then has a hash (#) followed by
a Routing Code Attribute (this can be 1 = Barred, 2 = Exclude, 3 = Allowed, 4 = Local, 5 = Translate
or 6 = Special). Routing Code Attributes will be explained in more detail later in this document. The
next part of the command string is a set of three numbers which are the carrier code locations to be
used for Daytime, Evening and Weekend calls. ( It should be noted that if you put a zero (0) in any
of these three fields, that means that for that time band you don't use any entry from the Carrier
Code Table at all and just send out the number as it is). The command string then has another hash
(#) followed by the two digit location you want to write into the Routing Code Table and finally a
terminating hash character (#). It is important to note that you cannot erase an individual
Routing Code Table entry, only overwrite it with new data.
Note: The official Orchid manual says that you can use locations from 0 to 99 but the Kevin
spreadsheet and the sample spreadsheets that Orchid used to provide seem to ignore location 00 for
some reason.
Because this command is a bit tricky to get your head round, there are some examples below to
give you a better idea how it works. They are broken down into their separate parts to make them
easier to understand.

Example 1.
All dialled numbers starting with 01 are “Allowed” and are prefixed with the carrier code held in
location 2 of the Carrier Code Table before being sent out but only for daytime and evening calls as
the third carrier code entry is a zero meaning no routing of the call is done. This is written to
location 02 of the Routing Code Table.
*###01#3220#02#

*### The command identifiers
01 The part of the dialled number to be matched
# Field separator
3 Routing Code Attribute (Allowed)
2 The carrier code location to be used for Daytime
2 The carrier code location to be used for Evening
0 The carrier code location to be used for Weekend (zero means no routing)
# Field Separator
02 The Routing Table Location
# Terminating character

Orchid V4 Dialler Manual Programming Guide - Version 1.214 Page 8 of 18
Example 2.
Numbers starting with 0845 are Allowed and are ALWAYS prefixed with the carrier code held in
location 2 of the Carrier Code Table before being sent out. This is written to location 07 of the
Routing Code Table.
*###0845#3222#07#
*### The command identifiers
0845 The part of the dialled number to be matched
# Field separator
3 Routing Code Attribute (Allowed)
2 The carrier code location to be used for Daytime
2 The carrier code location to be used for Evening
2 The carrier code location to be used for Weekend
# Field Separator
07 The Routing Table Location
# Terminating character

Example 3.
When the number 192 is dialled it is ALWAYS translated into the number held in location 4 of the
Carrier Code Table before being sent out. This is written to location 11 of the Routing Code Table.

Orchid V4 Dialler Manual Programming Guide - Version 1.214 Page 9 of 18
Example 4.
When the number starting with 09 is dialled it is ALWAYS barred so you will just get dialling tone
returned if you try to dial an 09 number. This is written to location 06 of the Routing Code Table.

*###09#1000#06#
*### The command identifiers
09 The part of the dialled number to be matched
# Field separator
1 Routing Code Attribute (Barred)
0 The carrier code location to be used for Daytime – always zero for barred calls
0 The carrier code location to be used for Evening – always zero for barred calls
0 The carrier code location to be used for Weekend – always zero for barred calls
# Field Separator
06 The Routing Table Location
# Terminating character

Example 5.
Numbers starting with 07 are “Allowed” and are prefixed with the carrier code held in location 1 of
the Carrier Code Table for daytime calls and the code in location 2 for evening and weekends calls
before being sent out. This is written to location 04 of the Routing Code Table.

*###07#3122#04#
*### The command identifiers
07 The part of the dialled number to be matched
# Field separator
3 Routing Code Attribute (Allowed)
1 The carrier code location to be used for Daytime calls
2 The carrier code location to be used for Evening calls
2 The carrier code location to be used for Weekend calls
# Field Separator
04 The Routing Table Location
# Terminating character

Orchid V4 Dialler Manual Programming Guide - Version 1.214 Page 10 of 18
Example 6.
Numbers starting with 08 are Allowed and are ALWAYS passed straight through to your line service
provider without modification. This is written to location 05 of the Routing Code Table.
*###08#32000#065#
*### The command identifiers
08 The part of the dialled number to be matched
# Field separator
3 Routing Code Attribute (Allowed)
0 The carrier code location to be used for Daytime
0 The carrier code location to be used for Evening
0 The carrier code location to be used for Weekend
# Field Separator
05 The Routing Table Location
# Terminating character

Note: Something interesting to realise here is that numbers that start with 0845 will NOT be
excluded, even though they start with 08. This is because there is a better match for 0845 in the
Routing Code Table and is shown in Example 2 so that routing will be used instead. Example 6.

Example 7.
Local numbers that start with any number from 2 to 9 and are dialled without using the STD code
are processed as Local numbers and are passed through to your line service provider after adding
the STD code that you have programmed into your dialler and then prefixed with the Carrier Code
identified in the Routing Code Table entry. This is written to location 01 of the Routing Code Table.
*###*2*9#4220#01#
*### The command identifiers
*2*9 Numbers that start with any character from 2 to 9
# Field separator
4 Routing Code Attribute (Local)
2 The carrier code location to be used for Daytime
2 The carrier code location to be used for Evening
0 The carrier code location to be used for Weekend
# Field Separator
01 The Routing Table Location
# Terminating character

Note: The STD code is NOT added where a Carrier Code Location of zero is specified. This makes
sense as no routing will be applied so the call will go out via your default carrier which is already
associated with your local STD code. In the above example it will NOT be added at weekends.

Orchid V4 Dialler Manual Programming Guide - Version 1.214 Page 11 of 18
Sample Routing Code Table
Below is a small sample Routing Code Table to give you an idea of the type of entries to be found.
Please note that it is a short sample table only and doesn't contain all possible types of entry that
can be used. The real table can have up to 100 entries in locations numbering from 00 to 99
(although location 00 seems to be unused in most table examples provided, even from Orchid
themselves)

Location Call Type Description Handling Day Night Weekend Programming Code
1 *2*9 Local Calls – No STD Local 2 2 0 *###*2*9#4220#01#
2 01 National Allowed 2 2 0 *###01#3220#02#
3 02 National Allowed 2 2 0 *###02#3220#03#
4 07 Mobiles Allowed 1 1 1 *###07#3111#04#
5 08 08 Freephone Allowed 0 0 0 *###08#3000#05#
6 09 Premium Barred 0 0 0 *###09#1000#06#
7 0845 0845 Dialling Code Allowed 2 2 2 *###0845#3222#07#
8 0870 0870 Dialling Code Allowed 2 2 2 *###0870#3222#08#
9 1470 Force CLI on Special 0 0 0 *###1470#6000#09#
10 999 Emergency Calls Excluded 0 0 0 *###999#2000#10#
11 192 Directory Enquiries Translate 4 4 4 *###192#5444#11#

12 121 Dialler Override Translate 0 0 0 *###121#5000#12#

Routing Code Attributes
When a dialled number (or part of it) is matched in the Routing Code Table, it is handled in
different ways depending on the Routing Code Attribute used in the Routing Code Table entry. There
are six different Routing Code Attributes that are supported by the dialler, these being described
below. PSTN stands for Public Switched Telephone Network and is the default provider that handles
charging for your telephone calls. It may be BT, Primus, Talk Talk or some other provider.

Call Barring (1)
If a dialled number (such as a number starting with 09) is defined in the Routing Code Table as
Barred, the user simply receives a dialling tone forcing the user to disconnect. Effectively, the Barred
number cannot be called through the dialler. Example 4 earlier in this document demonstrates this.

Exclusion (2)
This Routing Code Attribute simply passes the call straight through to your PSTN without any
modification or routing.

Allowed (3)
This is the most common Routing Code Attribute to be used and simply means that the dialled
number is Allowed through the dialler and will be prefixed with the contents of the associated Carrier
Code Table entry. Example 1 earlier in this document demonstrates this.

Orchid V4 Dialler Manual Programming Guide - Version 1.214 Page 12 of 18
Local (4)
These calls will be routed over the corresponding carrier (determined by the Carrier Code specified
in the Routing Coder Table entry) but will have your local STD code that has been programmed into
the dialler added to it.

Translation (5)
When a match is found in the Routing Code Table, the matching part of the dialled number is
stripped off and replaced by the number (or part number) contained in the associated Carrier Code
Table entry. Example 3 earlier in this document demonstrates this.
Note: Translate is also used for the 121 Routing Code Table entry and here, it appears to mean
“Translate to Nothing” because carrier codes are all set to zero so the 121 code is effectively thrown
away and the remainder of the dialled number is passed through to the phone line unmodified.

Special Handling (6)
This is a confusing one! The official Orchid programming manual says the following:-
“On seeing these codes, the dialler will prefix the specific carrier information. These are generally
for BT services, which would normally route back to BT, i.e. 141”
Examples given in the Orchid Programming Manual are reproduced below.

141
Number withheld call. Please note that the S attribute indicates that the call will route not across the PSTN as the
Carrier 0 would suggest, but by the corresponding carrier of the post 141 number routing entry.
Example: 14101536xxxxxx will be routed as 141####01536xxxxxx.

1470
Customers who have their number withheld can use the 1470 prefix to force the PSTN to present your CLI to the
call recipient on a per call basis. As with the 121 routing entry, the S attribute indicates that the call will route not
across the PSTN as the Carrier 0 allocation would suggest, but by the corresponding carrier of the post 1470
number routing entry.
Example: 147001536xxxxxx will be routed as 1470####01536xxxxxx

I believe what the above examples actually mean is that when you dial a number that starts with
141, 1470 or any other number in the Routing Code Table that has the S attribute, the dialler will
initially strip that bit of the dialled number off, then look through the Routing Code Table for a match
on the remainder of the number you dialled and if it finds a match, routes the call accordingly but
also adds the stripped off 141 or 1470 back onto the front of it.

Orchid V4 Dialler Manual Programming Guide - Version 1.214 Page 13 of 18
Manual Programming Template
The following blank tables are provided for you to record your own programming details for future
reference.

Reference Carrier Code Table
No Carrier Code Description Programming Code
1
2
3
4
5
6
7
8
9 RESERVED – DO NOT USE

Reference Routing Code Table
No Call Type Description Handling Day Night Weekend Programming Code
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20

Orchid V4 Dialler Manual Programming Guide - Version 1.214 Page 14 of 18
Checking the Dialler Output
Having programmed the V4 Dialler with your required Routing Codes and Carrier Codes, the only
way that you can normally to verify that it is sending the correct numbers down your phone line is to
make various calls and then check your phone bills to see that the desired carrier was used.
However, if you want to see exactly what numbers the dialler is sending out, there is a way to do
this using a BT Socket Recording Lead (available from Maplins) and piece of free software called
DTMF Decoder.
The BT Recording Lead is a small piece of electronics that plugs into your phone socket and provides
an audio monitor output that can be connected to a suitable recording device or the microphone
input of your computer or laptop. It is primarily intended for recording conversations onto a tape
recorder or MP3 recorder but can actually be used to record the tones that your phone sends down
the telephone line when making a call and it is this facility that we can use to verify the tones the
dialler outputs.

The BT Socket Recording Lead
The BT Socket Recording Lead is available from Maplin Electronics (Order Code ZQ79L) and is shown
below. It is manufactured by a company called Retell Limited (Model 145) and although they state
on their web site that a different model (Model 157) is meant for recording to PC's, this one seems
to do the job and is easily available from Maplins at a lower price. More info can be found at the
Retell web site below.
http://www.retellrecorders.co.uk/en/retell-direct/single-line-recording

The white double adapter plugs into your phone line. You then plug the short white lead of the box
into one side of the adapter and a phone in the other side. The black lead has a 3.5mm mono jack
plug and provides the audio signal that you can connect into the microphone input of your computer
or laptop or other recording device.

Orchid V4 Dialler Manual Programming Guide - Version 1.214 Page 15 of 18
Connecting the recording lead to your computer or laptop
Below is a diagram showing how the BT Socket Recording Lead is connected.

Be warned that you may need to experiment with setting up your computer sound card or laptop
audio properties in order to achieve a decent clean recording. The author achieved the best results
using the microphone input of an Acer Netbook and the sound recording program that was included
in the Windows 7 operating system.

Recording and Analysing the Dialler Output
Once you have everything connected, set your PC recording and dial a number using the phone
connected to your dialler. You only need to record the DTMF tones so hang up and stop recording
once dialling has completed. Now you need to take the audio file that has just been created on your
on your PC and assuming it is a good clear recording (try playing it back with media player), pass it
to a program called DTMF Decoder. This program can be downloaded at the following web site.
http://www.twopaths.com/software/index.htm
The program is found about half way down the page. The way to pass your audio file to DTMF
Decoder is to find the file in file explorer and then drag it over the icon for the DTMF Decoder
program. You will also need to make sure that the file is in a format that DTMF Decoder will accept
(WAV for example). Windows 7 Sound Recorder seems to create files in WMA format so you will
need to convert to WAV. This can be done with another piece of software called Switch Sound File
Converter and a free version that can be found at the following web address.
http://www.nch.com.au/switch/index.html

Orchid V4 Dialler Manual Programming Guide - Version 1.214 Page 16 of 18
Screen Shots from DTMF Decoder and Switch Sound File Converter

The Switch Sound File Converter program will look like this so you simply add the file you want to
convert and them tell it what format you want the output file to be in and where to save it.

Once you have your WAV file, drag it over the icon for DTMF Decoder. The program will run and you
should get a screen similar to the following.

You can see that the program has decoded the DTMF tones you recorded from your dialler and has
displayed them as the number that was dialled. In the case of the above example, I dialled the local
number 888576 and the dialler added 1280 followed by my stored STD code to the front of it.

Orchid V4 Dialler Manual Programming Guide - Version 1.214 Page 17 of 18
Conclusion and Disclaimer
I hope this document will be of use in helping you to manually program your Orchid V4 Dialler. It is
provided free and is supported on a “best can do” basis. It should be used at your own risk and
the author accepts no responsibility for any damage or problems that you may have when
programming you dialler as a result of following this document. It is written based on personal
experience gained by the author when programming his own dialler. It should not be considered as
an official Orchid support manual. However, if you have any comments, corrections or suggestions,
please feel free to contact me via the MSE Forum where you found this document and I will do my
best to incorporate them.
My MSE forum user name is “SHILCOR”.

I would also like to take this opportunity to thank HEINZ from the MSE forum for his help in proof
reading and sanity checking this document before I published it.

Document History
Date Version Comments
02/03/12 1 First draft
03/03/12 1.1 Corrections following review by HEINZ
05/03/12 1.2 Add TOC, Doc History, notes, Routing Code Attributes, Templates
06/03/12 1.21 Fix incorrect Freephone number referred to in Carrier Code Example 4
08/03/12 1.22 Error in Routing Code Example 6, Add note about Local Attribute.
12/03/12 1.23 Add section about testing the dialler output, add note to Routing Code Example 7
13/03/12 1.24 Fix typo in Example 5 of Routing Code Table entry

Orchid V4 Dialler Manual Programming Guide - Version 1.214 Page 18 of 18