To use the destination, the administrator must add Routes to the destination.
A route links a destination to a specific endpoint/gateway. This is also done in the Destinations table of Lotus Sametime Unified Telephony Assistant. The user selects a defined destination, which opens a window with the destination parameters. On the Routes tab, the administrator can select Add to add a new route. To define a route, the following parameters must be defined:
A Route ID
– actually the priority of the route. If there are multiple routes to a destination, the route with the lowest numbered route ID has the highest priority, and will be selected first.
– selected from the list of already defined endpoints. These endpoints may have been defined in any numbering plan of the Lotus Sametime Unified Telephony system.
Originating Signaling Type
(normally left as undefined – which means “any”). By selecting a specific signaling type, the administrator can give special routing based on the protocol of the originating device.
Originating Bearer Capability
(normally left as undefined – which means “any”). The bearer cap field make it possible to give special routing to selected bearer types (speech, audio, unrestricted 56kb data, unrestricted 64 kbps data). Certain gateways might be suitable for voice (speech) but not for modem data (audio), for example.
Digits to delete / insert
can be specified. This permits limited manipulation of the destination digits prior sending the outgoing setup/invite.
NOA (Nature of Adress)
of the resulting number can be specified (national, international, and so on). Some endpoints/gateways ignore this and others consider it important.
SIP protocol does not care the NOA information so this setting is meaningless if the destination is a SIP gateway.
SIP-Q protocol does carry the NOA information so it is important that it be set correctly if the destination is a SIP-Q gateway such as the HG3540. In this context, “correctly” means in accordance with what the receiving gateway expects.