Dial Rules Call Server Configuration
Polycom, Inc. 247
If you have special configuration needs and want to modify the dial plan, be aware that some of the default dial rules are necessary for “normal” operation. Removing or modifying them takes the system out of compliance with ITU and IEEE standards. Here are some suggestions and guidelines for modifying the dial plan:
Table 10-5 How the default dial plan works
Rule Effect
1 Dial registered
endpoints by alias If the dial string is the alias or SIP URI of a
registered endpoint, the call is routed to that
endpoint.
2 Dial by conference
room ID Otherwise, if the dial string is the dial-in number of
a conference room on the Polycom DMA system,
the call is routed to that conference room.
3 Dial by virtual entry
queue ID Otherwise, if the dial string is the dial-in number of
a virtual entry queue on the Polycom DMA system,
the call is routed to that VEQ.
4 Dial services by prefix Otherwise, if the dial string begins with the
configured prefix of a service (such as an MCU,
ISDN gateway, SBC, neighbor gatekeeper, SIP
peer proxy, or simplified ISDN dialing service) the
call is routed to that service.
Note: For a SIP peer, the dial string must consist of
only the prefix and user name (no @domain). For
instance, if the SIP peer’s prefix is 123, the dial
string for a call to alice@polycom.com must be:
123alice
5 Dial external networks
by H.323 URL, email ID,
or SIP URI
Otherwise, if the address is an external address,
the call is routed to that external address (H.323
calls use an SBC to reach IP addresses outside the
enterprise network).
Examples of external addresses:
H323:johnsmith@someothercompany.com
sip:johnsmith@someothercompany.com
6 Dial endpoints by IP
address Otherwise, if the address is an IP address, the call
is routed to that IP address (H.323 calls use an
SBC to reach IP addresses outside the enterprise
network).
Examples of IP addresses:
1.2.3.4
1.2.3.4##abc
sip:abc@1.2.3.4
sip:1.2.3.4@mycompany.com