Ok, so I'm setting up an enterprise fax server. Internally we dial 4 digits for one location and 5 for 2 others. We dial 9+the number to get out to the outside world.
I need to set the fax server to either not append a 9 to any phone number of a length of 4 or 5, but append a 9, to everything else.
Here is a field in the INI that can be used. Ideas?
------
TelNumEdit: "<match>" "<replace>" "<route type>"
Default: none, none, optional
Purpose: Historically this line was used to allow the user to set up some simple phone number editing rules to make sure only the required parts of a fax number were dialled. The '<match>' specified the start of numbers which would need editing and the '<replace>' field specified the digits which should replace the '<match>' field. The rules are applied in sequence to every number, until either all the rules have been tried or the number matches a rule where the '<match>' and '<replace>' fields are identical. For example a US user in area code '222' might set up rules like
TelnumEdit: "0111" "" TelnumEdit:"011" "011"
TelnumEdit: "1" ""
TelnumEdit: "" "1"
TelnumEdit: "1222" "222"
The first rule removes the international dial code and country code for US numbers. The second rule causes the telnum editing to stop at this point for non-US international numbers. The following rules will thus only be applied to US numbers. The next two rules ensure that all numbers start with the national access code ('1'). Finally the last rule ensures that all numbers in the local area are dialled without the national access code. This role of the telnum edit rules has been taken over by the 'dialling properties' option which can be enabled using the configuration program from the 'Change server settings' section. An extra, optional, field has now been added to this line, the '<route type>'. Without this field the rules will behave as they previously have done. The only setting which is currently recognised for this new field is 'LAN-ANY'. This is used to set up rules for recognising internal phone numbers so the Zetafax server can forward these faxes to user's inboxes via LAN transfer rather than needlessly 'dialling itself'. The two possible syntaxes are
TelnumEdit: "<match>", "<username>", LAN-ANY
and
TelnumEdit: "<match>", "<username:n>", LAN-ANY
The first type will route all numbers matching the '<match>' field to the user '<username>' (which can be any valid Zetafax user name) via LAN transfer. The second type of rule performs the same operation except it appends the last 'n' digits of the original fax number to the new address which may then be matched against any configured internal routing rules. For example, TelnumEdit: "123", "MAIN:4", LAN-ANY will route any number starting '123' to user 'MAIN' appending the last four digits of the number to the new address, so '1234567' would be changed to 'MAIN:4567'. If there is a user 'JSMITH' who has an internal routing sub-address of '4567' then the fax is routed to them via LAN transfer or email (if the user is so configured). otherwise the fax is routed to user 'MAIN'. In addition if a number starting with the specified match digits ('123' for either of the two syntaxes) has a valid Zetafax user as a sub-address then this is used instead of the given replace field. Thus a fax addressed to '1234444:JONES' will be routed to Zetafax user 'JONES' if they exist, otherwise it will be routed to 'MAIN:4444'. If a number matches a rule with a '<route type>' field then the Zetafax server will not try and match it to any subsequent telnum edit rules. The Telnum edit rules are now used in conjunction with the 'dialling properties'. the Zetafax server will create temporary 'canonical' and 'diallable' versions of any number and it will try and match both of these to any rules. Thus rules starting, TelnumEdit: '2221234' ... TelnumEdit: '+12221234' ... will both match a number like '1234???' in the US area code '222'. Note once a number matches a rule this is used to create a new 'diallable' version and this is used to match any following rules. No further matches will be made to canonical numbers after the first match to either a canonical or diallable rule. If dialling properties are not enabled the Zetafax server is limited in its ability to create diallable and canonical versions of numbers. Typically it can only convert numbers which are already canonical, where it replaces the leading '+' with the international dial prefix to produce a diallable number, or numbers starting with the international dial prefix, where it can perform the reverse operation to produce a canonical version. To ensure that the inward routing rules perform consistently the user can precede these rules with a set of 'old-style' telnum edit rules designed to produce a diallable version of any number. Following the first example given above we might produce a set of rules like,
TelnumEdit: "0111" ""
TelnumEdit: "011" "011"
TelnumEdit: "1" ""
TelnumEdit: "" "1"
TelnumEdit: "1222" "222"
TelnumEdit: "222123", "MAIN:4" LAN-ANY
This should ensure that numbers starting '+1222123...', '0111222123...', '1222123...' and '222123...', all get routed internally.
_____________________________________________________
TelNumType: <type> "<preface>"
Default: none
Purpose: Specifies the Zetafax telephone number type rules. Zetafax will look at the telephone number of a fax and decide, from these rules, whether the call is local, national or international. Zetafax user accounts can specify the telephone number types which may be sent to, allowing specific users to be prohibited from making international calls, or calls to certain countries, for example.
<type> is one of the following: "Local", "National", "International", "National1" to "National9", "International1" to "International9". <preface> is matched against the first few characters of the phone number - the phone number is of the given type if the first characters (ignoring non-alphanumeric characters) match.
An example of a set of rules which might be used in London are as follows:
TelNumType: Local "071"
TelNumType: Local "081"
TelNumType: International "010"
TelNumType: National "0"
TelNumType: Local "x"
TelNumType: Local ""
Up to 30 rules may be defined as required. The rules are evaluated by the system from top to bottom. Thus in the above example, if the number being called starts with "071" or "081" it is a local call, if it starts with "010" it is international. Any other number starting with 0 is national, while any internal extension ("x") calls, and indeed all other calls ("") are classified as local.
You can expand the number of types available for each of National and International by appending a digit (eg "National2" or "International7"). "National" and "National1" are interchangeable, as are "International" and "International1".
I need to set the fax server to either not append a 9 to any phone number of a length of 4 or 5, but append a 9, to everything else.
Here is a field in the INI that can be used. Ideas?
------
TelNumEdit: "<match>" "<replace>" "<route type>"
Default: none, none, optional
Purpose: Historically this line was used to allow the user to set up some simple phone number editing rules to make sure only the required parts of a fax number were dialled. The '<match>' specified the start of numbers which would need editing and the '<replace>' field specified the digits which should replace the '<match>' field. The rules are applied in sequence to every number, until either all the rules have been tried or the number matches a rule where the '<match>' and '<replace>' fields are identical. For example a US user in area code '222' might set up rules like
TelnumEdit: "0111" "" TelnumEdit:"011" "011"
TelnumEdit: "1" ""
TelnumEdit: "" "1"
TelnumEdit: "1222" "222"
The first rule removes the international dial code and country code for US numbers. The second rule causes the telnum editing to stop at this point for non-US international numbers. The following rules will thus only be applied to US numbers. The next two rules ensure that all numbers start with the national access code ('1'). Finally the last rule ensures that all numbers in the local area are dialled without the national access code. This role of the telnum edit rules has been taken over by the 'dialling properties' option which can be enabled using the configuration program from the 'Change server settings' section. An extra, optional, field has now been added to this line, the '<route type>'. Without this field the rules will behave as they previously have done. The only setting which is currently recognised for this new field is 'LAN-ANY'. This is used to set up rules for recognising internal phone numbers so the Zetafax server can forward these faxes to user's inboxes via LAN transfer rather than needlessly 'dialling itself'. The two possible syntaxes are
TelnumEdit: "<match>", "<username>", LAN-ANY
and
TelnumEdit: "<match>", "<username:n>", LAN-ANY
The first type will route all numbers matching the '<match>' field to the user '<username>' (which can be any valid Zetafax user name) via LAN transfer. The second type of rule performs the same operation except it appends the last 'n' digits of the original fax number to the new address which may then be matched against any configured internal routing rules. For example, TelnumEdit: "123", "MAIN:4", LAN-ANY will route any number starting '123' to user 'MAIN' appending the last four digits of the number to the new address, so '1234567' would be changed to 'MAIN:4567'. If there is a user 'JSMITH' who has an internal routing sub-address of '4567' then the fax is routed to them via LAN transfer or email (if the user is so configured). otherwise the fax is routed to user 'MAIN'. In addition if a number starting with the specified match digits ('123' for either of the two syntaxes) has a valid Zetafax user as a sub-address then this is used instead of the given replace field. Thus a fax addressed to '1234444:JONES' will be routed to Zetafax user 'JONES' if they exist, otherwise it will be routed to 'MAIN:4444'. If a number matches a rule with a '<route type>' field then the Zetafax server will not try and match it to any subsequent telnum edit rules. The Telnum edit rules are now used in conjunction with the 'dialling properties'. the Zetafax server will create temporary 'canonical' and 'diallable' versions of any number and it will try and match both of these to any rules. Thus rules starting, TelnumEdit: '2221234' ... TelnumEdit: '+12221234' ... will both match a number like '1234???' in the US area code '222'. Note once a number matches a rule this is used to create a new 'diallable' version and this is used to match any following rules. No further matches will be made to canonical numbers after the first match to either a canonical or diallable rule. If dialling properties are not enabled the Zetafax server is limited in its ability to create diallable and canonical versions of numbers. Typically it can only convert numbers which are already canonical, where it replaces the leading '+' with the international dial prefix to produce a diallable number, or numbers starting with the international dial prefix, where it can perform the reverse operation to produce a canonical version. To ensure that the inward routing rules perform consistently the user can precede these rules with a set of 'old-style' telnum edit rules designed to produce a diallable version of any number. Following the first example given above we might produce a set of rules like,
TelnumEdit: "0111" ""
TelnumEdit: "011" "011"
TelnumEdit: "1" ""
TelnumEdit: "" "1"
TelnumEdit: "1222" "222"
TelnumEdit: "222123", "MAIN:4" LAN-ANY
This should ensure that numbers starting '+1222123...', '0111222123...', '1222123...' and '222123...', all get routed internally.
_____________________________________________________
TelNumType: <type> "<preface>"
Default: none
Purpose: Specifies the Zetafax telephone number type rules. Zetafax will look at the telephone number of a fax and decide, from these rules, whether the call is local, national or international. Zetafax user accounts can specify the telephone number types which may be sent to, allowing specific users to be prohibited from making international calls, or calls to certain countries, for example.
<type> is one of the following: "Local", "National", "International", "National1" to "National9", "International1" to "International9". <preface> is matched against the first few characters of the phone number - the phone number is of the given type if the first characters (ignoring non-alphanumeric characters) match.
An example of a set of rules which might be used in London are as follows:
TelNumType: Local "071"
TelNumType: Local "081"
TelNumType: International "010"
TelNumType: National "0"
TelNumType: Local "x"
TelNumType: Local ""
Up to 30 rules may be defined as required. The rules are evaluated by the system from top to bottom. Thus in the above example, if the number being called starts with "071" or "081" it is a local call, if it starts with "010" it is international. Any other number starting with 0 is national, while any internal extension ("x") calls, and indeed all other calls ("") are classified as local.
You can expand the number of types available for each of National and International by appending a digit (eg "National2" or "International7"). "National" and "National1" are interchangeable, as are "International" and "International1".