Unsolved FANVIL Deskphone setting for dialing
-
@JaredBusch said in FANVIL Deskphone setting for dialing:
Also, one can only assume that it matches in order sequentially.
The manual contradicts itself. In one section it says if a number matches more than one dial plan rule, no rules are applied. In another section it says if a number matches more than one rule, the first rule is applied.
I don't see any way to re-index the rules. So I guess you have to delete and re-create in order.
Maybe I can export, modify, and import to sort the rules. Dumb.
Probably need to get a fanvil developer to start hanging out here...
-
@JasGot said in FANVIL Deskphone setting for dialing:
@JaredBusch said in FANVIL Deskphone setting for dialing:
Also, one can only assume that it matches in order sequentially.
The manual contradicts itself. In one section it says if a number matches more than one dial plan rule, no rules are applied. In another section it says if a number matches more than one rule, the first rule is applied.
I don't see any way to re-index the rules. So I guess you have to delete and re-create in order.
Maybe I can export, modify, and import to sort the rules. Dumb.
Probably need to get a fanvil developer to start hanging out here...
If I was using this phone I would have it all in provisioning files. so I would fix it there and tell the phone to update with a sip notify.
-
It falls under the
<call>heading.<call> <dialplan index="1"> <Number>933</Number> <ApplyToCall>0</ApplyToCall> <MatchToSend>1</MatchToSend> <Media>0</Media> <Line>-1</Line> <Address></Address> <Port>0</Port> <Alias></Alias> <DelLen>0</DelLen> <Suffix></Suffix> </dialplan> <dialplan index="2"> <Number>1xx</Number> <ApplyToCall>0</ApplyToCall> <MatchToSend>1</MatchToSend> <Media>0</Media> <Line>-1</Line> <Address></Address> <Port>0</Port> <Alias></Alias> <DelLen>0</DelLen> <Suffix></Suffix> </dialplan> </call> -
This was fun. You can export the config as a txt file. Alter this section:
--Dial Plan List-- : Item1 Number :[2-8]xxxxxxxxx Item1 ApplyToCall :0 Item1 MatchToSend :1 Item1 Media :0 Item1 Line :-1 Item1 Address : Item1 Port :0 Item1 Alias : Item1 DelLen :0 Item1 Suffix : Item2 Number :911 Item2 ApplyToCall :0 Item2 MatchToSend :1 Item2 Media :0 Item2 Line :-1 Item2 Address : Item2 Port :0 Item2 Alias : Item2 DelLen :0 Item2 Suffix : Item3 Number :1xxxxxxxxxx Item3 ApplyToCall :0 Item3 MatchToSend :1 Item3 Media :0 Item3 Line :-1 Item3 Address : Item3 Port :0 Item3 Alias : Item3 DelLen :0 Item3 Suffix : Item4 Number :9xxxxxxxxx Item4 ApplyToCall :0 Item4 MatchToSend :1 Item4 Media :0 Item4 Line :-1 Item4 Address : Item4 Port :0 Item4 Alias : Item4 DelLen :0 Item4 Suffix :And then import the config.
What you cannot do is change the "Item" order. I tried Item4, Item2, Item3, Item1 and all it did was erase all dial plans.And, to import, you only need the file header, section header, and items. So this imported just fine:
<<VOIP CONFIG FILE>>Version:2.0000000000 <CALL FEATURE MODULE> --Dial Plan List-- : Item1 Number :[2-7]xxxxxxxxx Item1 ApplyToCall :0 Item1 MatchToSend :1 Item1 Media :0 Item1 Line :-1 Item1 Address : Item1 Port :0 Item1 Alias : Item1 DelLen :0 Item1 Suffix : Item2 Number :911 Item2 ApplyToCall :0 Item2 MatchToSend :1 Item2 Media :0 Item2 Line :-1 Item2 Address : Item2 Port :0 Item2 Alias : Item2 DelLen :0 Item2 Suffix : Item3 Number :1xxxxxxxxxx Item3 ApplyToCall :0 Item3 MatchToSend :1 Item3 Media :0 Item3 Line :-1 Item3 Address : Item3 Port :0 Item3 Alias : Item3 DelLen :0 Item3 Suffix : Item4 Number :9xxxxxxxxx Item4 ApplyToCall :0 Item4 MatchToSend :1 Item4 Media :0 Item4 Line :-1 Item4 Address : Item4 Port :0 Item4 Alias : Item4 DelLen :0 Item4 Suffix : -
And Order does matter. In this rule set, if rule 4 comes before rule 2, it complains about conflicting rules.
-
@JaredBusch said in FANVIL Deskphone setting for dialing:
It falls under the <call> heading.
This will be good when we go from playing to production with these phones.
-
@JasGot said in FANVIL Deskphone setting for dialing:
And Order does matter. In this rule set, if rule 4 comes before rule 2, it complains about conflicting rules.
It's likely not required, but I would change rule 4 to "9[2-8]xxxxxxxxx" then it's very obvious to anyone looking at your system that your intent is to allow for a 9 before the ten digit number is dialed.
You should also change #3 to "1[2-8]xxxxxxxxx"
and I would add
"91[2-8]xxxxxxxxx"Do your inhouse rules require dialing a 9 before getting an outside line? or is that only there for users of a previous system?
-
@JasGot said in FANVIL Deskphone setting for dialing:
@JaredBusch said in FANVIL Deskphone setting for dialing:
It falls under the <call> heading.
This will be good when we go from playing to production with these phones.
- Use XML. You can at least validate that the syntax is valid.
- Never set everything. Only set what you are changing from default.
- Assuming your users will be unable to change their phone themselves.
-
-
Here is the full config for my test phone (X4U).
<?xml version="1.0" encoding="UTF-8"?> <sysConf> <Version>2.0000000000</Version> <sip> <line index="1"> <PhoneNumber>119</PhoneNumber> <RegisterAddr>pbx.bundystl.com</RegisterAddr> <RegisterPort>5061</RegisterPort> <RegisterUser>119</RegisterUser> <RegisterPswd>b...............................................3</RegisterPswd> <EnableReg>1</EnableReg> <MediaCrypto>2</MediaCrypto> <Transport>3</Transport> <VoiceCodecMap>G722,OPUS,PCMU</VoiceCodecMap> </line> </sip> <phone> <powerLed> <Power>0</Power> <MWIOrSMS>3</MWIOrSMS> <InUsing>0</InUsing> <Ring>2</Ring> <Hold>0</Hold> <Mute>0</Mute> <MissedCall>0</MissedCall> </powerLed> <date> <EnableSNTP>1</EnableSNTP> <SNTPServer>0.pool.ntp.org</SNTPServer> <SecondSNTPServer>time.nist.gov</SecondSNTPServer> <TimeZone>-24</TimeZone> <TimeZoneName>UTC-6</TimeZoneName> <SNTPTimeout>60</SNTPTimeout> <DSTType>1</DSTType> <DSTLocation>4</DSTLocation> <DSTRuleMode>0</DSTRuleMode> <DSTMinOffset>60</DSTMinOffset> <DSTStartMon>3</DSTStartMon> <DSTStartWeek>5</DSTStartWeek> <DSTStartWday>0</DSTStartWday> <DSTStartHour>2</DSTStartHour> <DSTEndMon>10</DSTEndMon> <DSTEndWeek>5</DSTEndWeek> <DSTEndWday>0</DSTEndWday> <DSTEndHour>2</DSTEndHour> </date> <timeDisplay> <EnableTimeDisplay>0</EnableTimeDisplay> <TimeDisplayStyle>1</TimeDisplayStyle> <DateDisplayStyle>3</DateDisplayStyle> <DateSeparator>0</DateSeparator> </timeDisplay> </phone> <dsskey> <SelectDsskeyAction>0</SelectDsskeyAction> <MemoryKeytoBXfer>1</MemoryKeytoBXfer> <DSSHomePage>1</DSSHomePage> <SidekeyConfig1 index="1"> <Type>2</Type> <Value>SIP1</Value> <Title>Line</Title> <ICON>Green</ICON> </SidekeyConfig1> <SidekeyConfig1 index="2"> <Type>2</Type> <Value>SIP1</Value> <Title>Line</Title> <ICON>Green</ICON> </SidekeyConfig1> <SidekeyConfig1 index="3"> <Type>1</Type> <Value>721@1</Value> <Title>Park 1</Title> <ICON>Green</ICON> </SidekeyConfig1> <internal index="1"> <Fkey index="1"> <Type>1</Type> <Value>118@1/bb</Value> <Title>Test 2</Title> <ICON>Green</ICON> </Fkey> <Fkey index="2"> <Type>1</Type> <Value>103@1/bb</Value> <Title>Jared</Title> <ICON>Red</ICON> </Fkey> </internal> </dsskey> <call> <port index="1"> <EnablePreDial>0</EnablePreDial> </port> <dialplan index="1"> <Number>933</Number> <ApplyToCall>0</ApplyToCall> <MatchToSend>1</MatchToSend> <Media>0</Media> <Line>-1</Line> <Address></Address> <Port>0</Port> <Alias></Alias> <DelLen>0</DelLen> <Suffix></Suffix> </dialplan> <dialplan index="2"> <Number>1xx</Number> <ApplyToCall>0</ApplyToCall> <MatchToSend>1</MatchToSend> <Media>0</Media> <Line>-1</Line> <Address></Address> <Port>0</Port> <Alias></Alias> <DelLen>0</DelLen> <Suffix></Suffix> </dialplan> </call> </sysConf>I haven't put firmware update in it yet or anything.
-
@Dashrender Those rules are not my real rules. I was playing with them to test importing.
Rule 4 is so we can dial 10 digits to area code 989 without creating a 911 issue before the 911 rule was created.
Rules 1 was 2-9, but I change it to see it I could import modified rules.I need to get my rules straight and repost for you to look at.
-
I've found overlapping issues with my posted rules...
I can't dial any area code that starts with 2 or 3, as that will pull the call to an extension (i.e. 1-213 goes to ext 1213)
-
@Dashrender said in FANVIL Deskphone setting for dialing:
I've found overlapping issues with my posted rules...
I can't dial any area code that starts with 2 or 3, as that will pull the call to an extension (i.e. 1-213 goes to ext 1213)
This is a typical scenario to be aware of and design for. Nothing more than attention to detail.
-
@JaredBusch said in FANVIL Deskphone setting for dialing:
@Dashrender said in FANVIL Deskphone setting for dialing:
I've found overlapping issues with my posted rules...
I can't dial any area code that starts with 2 or 3, as that will pull the call to an extension (i.e. 1-213 goes to ext 1213)
This is a typical scenario to be aware of and design for. Nothing more than attention to detail.
Yeah - and I wonder if that's one of the leading reasons for adding a 9 for dialing out?
-
@Dashrender said in FANVIL Deskphone setting for dialing:
@JaredBusch said in FANVIL Deskphone setting for dialing:
@Dashrender said in FANVIL Deskphone setting for dialing:
I've found overlapping issues with my posted rules...
I can't dial any area code that starts with 2 or 3, as that will pull the call to an extension (i.e. 1-213 goes to ext 1213)
This is a typical scenario to be aware of and design for. Nothing more than attention to detail.
Yeah - and I wonder if that's one of the leading reasons for adding a 9 for dialing out?
no.
