CallPilot has problems dialing DNs

This topic helps you to identify and correct addressing problems in desktop messaging, My CallPilot, and CallPilot Manager.

Symptom

Remote notification, fax default printing, or revert DN dialing fails because CallPilot is unable to dial the number.

Problem description

When mailbox owners configure dialing numbers for various CallPilot features, they must use the correct dialing format. If mailbox owners have problems configuring dialing numbers for CallPilot services such as remote notification, you may need to verify the format of the address or dialing number.

Note/Tip Mailbox owners typically do not receive a Non Delivery Notification (NDN) for the revert DN, default fax printing DN, or broadcast addresses.

Troubleshooting steps

IF this happened

THEN

A mailbox owner is unable to dial a  telephone number or fax number.

Verify

  • The number includes any required dialing prefixes (such as  61) before a long-distance number.

  • The dialing rights for the mailbox owner by checking the appropriate restriction permission list.

  • The use of any pause characters or authorization or access code indicators.
    You can include pause characters and number signs in the following dialing numbers.

    • mailbox revert DN

    • mailbox default Printing DN

    • remote notification DN

  • The mailbox owner has rights to use the selected address type. For example, if mailbox owners who do not have broadcast addressing rights cannot send messages to broadcast addresses.

Dial the number manually to verify that the number is in service. If the address includes pauses, verify the configured pause timing.

A telset application service is unable to dial a  telephone number or fax number.

Remote notification and Default Fax DN Attendant Transfer issues require Telset Apps investigation (SLEE trace).

Reproduce the problem and verify that the appropriate application service started.

  • If the telset application service did not start, then the address format on the server-side needs to be checked.

  • If the telset service started but did not complete the connection, run a SLEE trace for further analysis.