When you configure delivery to telephone (DTT) or delivery to fax (DTF), consider the following:
To ensure that the DTT/DTF service is activated, you must define one or more dialing prefixes. Publish these prefixes so users can specify them during message composition and when entering addresses in distribution lists.
For each DTT prefix, you must define an associated dialing code. When a user enters a DTT prefix, the system actually replaces the prefix the user entered with the associated dialing code. The dialing code is the public network access code that the system needs to place the call.
DTT prefixes cannot conflict with mailbox numbers. If you have a controlled dialing plan (CDP), the prefix can be the same as the initial number(s) of a CDP steering code, but cannot be the same as the entire code. For example, if one of your steering codes is 566, 5 or 56 can be used as a DTT prefix, but 566 cannot be used. For these cases, you need an arbitrary prefix that does not conflict with other numbers for the system to remove and replace with a dialing code to create a dialable number.
Make the DTT prefix and dialing code the same wherever possible. This simplifies message addressing for users because the numbers users enter when addressing a DTT message are exactly the same as the numbers they dial when placing an external call. Example
If you want to allow users to send DTT messages to internal extensions, you must set up a separate DTT prefix. This prefix is different, however, from others because it does not require an associated dialing code. Dialing codes are for access to the public network, and internal extensions are on your private network. When sending DTT messages to internal extensions, the prefix is simply stripped out of the address and the local extension is dialed. The prefix is needed to inform CallPilot to use the DTT service.
You need a DTT prefix and associated dialing code for each dialing scenario that you want to allow. This is because the system requires a different dialing code to place a call in each of the scenarios. For example, one dialing code (such as 9) is used to place local calls, whereas another (91) is used for long distance calls.
|
Dialing scenario |
Example prefix |
Corresponding dialing code |
|
Internal: For internal extensions |
56* |
none |
|
ESN: For numbers on your private ESN network, if you have one |
6 |
6 |
|
Local: For local numbers on the public network |
9 |
9 |
|
Long distance: For long distance numbers in the same country code |
91 |
91 |
|
International: For long distance numbers with different country codes |
9011 |
9011 |
You can specify whether DTMF confirmation is required either for the entire system or for a single mailbox.
If most users who receive DTT messages have rotary phonesets, disable DTMF confirmation for the entire system.
If most users who receive DTT messages have answering machines, disable DTMF confirmation for the entire system.
If users need to be able to send messages to a diversity of recipients, such as in different parts of the world where there might or might not be DTMF support, enable or disable DTMF confirmation at the mailbox level.
Some answering machine greetings contain a long pause, which might trigger the playback of the message before the greeting has finished. This means that the start of the DTT message will not be recorded since the greeting is still playing. Repeating the message makes it more likely that the entire message will be successfully recorded.
People who do not have a lot of experience with automated delivery of machine-generated messages might not realize what is happening initially. Playing the message twice increases the chance that they will be able to listen to the content of the message.