Info from Cisco:
Dialplan provided is only a "Template".
Users can easily change if necessary.
As for dialplan per line, I am sure there is a memory limitation since
the dialplan is managed on the phone. Dialplan files can be
manipulated with creative dialplans to handle most dialplan
requirements.
(1) Short problem description:
Dialplan.xml is global
[This may be incorrect and something I just haven't figured out how to
do from the instructions.]
(2) Longer problem description (what happens):
From what I can tell, the 7960 applies the same dialplan.xml to all
lines. Though appropriate if all lines are part of the same SIP
system, it is not appropriate if your phone is connected to multiple
independent systems with separate dial plans. Example: I
provisioned a 7960 with one line into INOC-DBA which has the
ASN*Extension dial plan, a second line into iptel.org, and a 3rd line
into fwd.pulver.com. If you provision this with the default dial
plan, then iptel.org won't work because they have 5 digit extensions
some of which include 911XX@iptel.org - the default dial plan
automatically puts the call through when you press 911.
The dialplan with the standard distribution assumes US PSTN
dialing. It would be better if a minimalist example was also
included with the standard distribution that did not assume
PSTN-specific features like 411, 911....
(3) Possible solution (what did you expect):
I expected some way in the config file to specify a dialplan per
extension.
(4) How to reproduce (if possible / applicable):
Set up a SIP server and assign the phone 91123 as it's number and use
the default dialplan. You can never reach that number.
(5) Workaround used currently (if applicable):
I'm using the minimalist inoc-dba dialplan which seems to work for all
systems.
<DIALTEMPLATE>
<TEMPLATE MATCH="0" Timeout="1"
User="Phone"/> <!-- Local operator-->
<TEMPLATE MATCH="*"
Timeout="15"/>
<!-- Anything else -->
</DIALTEMPLATE>
(7) Would you classify this as:
(D) Missing feature: Ok to deploy with workaround (see 5)
(8) Version
P0S3-04-3-00.bin
(9) Contact information:
Richard V. Ford <rvf@SPAM.packeteer.com>
(10) Report:
Message-Id: <5.1.0.14.0.20030623160213.03a97378@10.100.99.30>
Date: Mon, 23 Jun 2003 16:13:34 -0700