Windows Server 2003 - Shared Fax - Long Distance Dialing Rules


G

Guest

I have installed Faxing on a Server 2003 for inbound faxing...all worked great.

Now I am trying to get an XP Pro client to send faxes via the shared fax.
All the basics were easy. Share fax printer, install shared fax printer on
XP workstation. Then came dialing rules. My phone system requires local
calls in the "9 NNN NNNN " (where N is the 7 digit phone number). For long
distance the required format is "9 1 AAA NNN NNNN PPPP" (where A is area code
and P is PIN).

Since I have worked with other fax server and Microsoft's Faxing since WFW,
I already require all numbers in Outlook to be in the international format
"+1 (AAA) NNN-NNNN! However, I did not even get basic print, enter fax
number and send to work for long distance, so of course Outlook didn't work
either!

In 2000 Pro (local workstation faxing only) you had to log service in as a
user to get dialing rules. Windows Server 2003 will not allow service to run
under a local or domain user...I tried. Well on a hunch, I just added to the
adminstrator account. I started with the 9's. Seemed to work. Then I moved
to the calling card stuff for PIN. I think I have exhausted all combinations
of settings on the server and client.

Further testing resulted in this:

Local test on the Windows Sesrver 2003 using a test RTF document printed to
Fax printer follow all dialing rules. I can hear a pause (added between
number and PIN for testing) and the PIN as I have instructed the dialing
rules to insert on long distance number +1 (555) 123-4567. And a local fax
number +1 (509) 555-1234 send only the 8 digits requested (9 and number).

To test client I printed a test DOC file to the Fax printer and manually
added the number (to eliminate my Outlook 2003 from the picture). Local
faxing still follow rules dial 8 digits. I even tested setting up an Area
Code Rule to check if that worked, and the dialing was correct. I added Dial
1 and Include the area code settings to all 509 prefixes. I could hear the
extra digits dialed when +1 (509) 555-1234 was used.

Long distance from the client XP Pro workstation did NOT work. Although the
service would dial the 9 1 AAA NNN NNNN it would not dial the PIN. Running
the same test, printing DOC to Fax printer and entering phone number +1 (555)
123-4567 the service dialed only 9 1 555 123 4567, no PIN (could not tell if
pause occurred). Recording complains about project code (PIN) missing.

For fun, before the final tests, I made sure both the client and server had
the same exact dialing rules setup...same names and values in all location.
This did not change results. Also, I always checked use dialing rules since
my ultimate goal is to use Outlook contacts, and they are in international
format.

Is this the way it is supposed to work? If I have done everything a person
can, I need to know so I can have a POTS line pulled in without long distance
PIN requirements. This is a monthly expense I would like to avoid by using
our current infrastructure.

Any help is greatly appreciated...
 
Ad

Advertisements

L

Loganatr [MSFT]

When you fax through Remote Server,
1. Server side dialing rules will be applied. In
Win2003 fax service cannot be run as local user context.
2. Even though dialing rules are applied at the
server, for security reasons the final destination number wont be displayed.
3. Calling cards and Pin Information wont be
used for dialing rules translation.

--
Loganatr [MSFT]
Microsoft Printing, Imaging and Fax Team
This posting is provided "AS IS" with no warranties, and confers no rights.
Please do not send email directly to this alias. This alias is for newsgroup
purposes only.'
 
G

Guest

I have an enduser who was able to fax and use her contacts, and then
mysteriously her contacts are gone and a shared folder seems to be there. I
think that someone else logged into her machine, creating a new situation
with more than one user profile.

Can anyone help with this?



Loganatr said:
When you fax through Remote Server,
1. Server side dialing rules will be applied. In
Win2003 fax service cannot be run as local user context.
2. Even though dialing rules are applied at the
server, for security reasons the final destination number wont be displayed.
3. Calling cards and Pin Information wont be
used for dialing rules translation.

--
Loganatr [MSFT]
Microsoft Printing, Imaging and Fax Team
This posting is provided "AS IS" with no warranties, and confers no rights.
Please do not send email directly to this alias. This alias is for newsgroup
purposes only.'



Spencer Morley said:
I have installed Faxing on a Server 2003 for inbound faxing...all worked
great.

Now I am trying to get an XP Pro client to send faxes via the shared fax.
All the basics were easy. Share fax printer, install shared fax printer
on
XP workstation. Then came dialing rules. My phone system requires local
calls in the "9 NNN NNNN " (where N is the 7 digit phone number). For
long
distance the required format is "9 1 AAA NNN NNNN PPPP" (where A is area
code
and P is PIN).

Since I have worked with other fax server and Microsoft's Faxing since
WFW,
I already require all numbers in Outlook to be in the international format
"+1 (AAA) NNN-NNNN! However, I did not even get basic print, enter fax
number and send to work for long distance, so of course Outlook didn't
work
either!

In 2000 Pro (local workstation faxing only) you had to log service in as a
user to get dialing rules. Windows Server 2003 will not allow service to
run
under a local or domain user...I tried. Well on a hunch, I just added to
the
adminstrator account. I started with the 9's. Seemed to work. Then I
moved
to the calling card stuff for PIN. I think I have exhausted all
combinations
of settings on the server and client.

Further testing resulted in this:

Local test on the Windows Sesrver 2003 using a test RTF document printed
to
Fax printer follow all dialing rules. I can hear a pause (added between
number and PIN for testing) and the PIN as I have instructed the dialing
rules to insert on long distance number +1 (555) 123-4567. And a local fax
number +1 (509) 555-1234 send only the 8 digits requested (9 and number).

To test client I printed a test DOC file to the Fax printer and manually
added the number (to eliminate my Outlook 2003 from the picture). Local
faxing still follow rules dial 8 digits. I even tested setting up an Area
Code Rule to check if that worked, and the dialing was correct. I added
Dial
1 and Include the area code settings to all 509 prefixes. I could hear
the
extra digits dialed when +1 (509) 555-1234 was used.

Long distance from the client XP Pro workstation did NOT work. Although
the
service would dial the 9 1 AAA NNN NNNN it would not dial the PIN.
Running
the same test, printing DOC to Fax printer and entering phone number +1
(555)
123-4567 the service dialed only 9 1 555 123 4567, no PIN (could not tell
if
pause occurred). Recording complains about project code (PIN) missing.

For fun, before the final tests, I made sure both the client and server
had
the same exact dialing rules setup...same names and values in all
location.
This did not change results. Also, I always checked use dialing rules
since
my ultimate goal is to use Outlook contacts, and they are in international
format.

Is this the way it is supposed to work? If I have done everything a
person
can, I need to know so I can have a POTS line pulled in without long
distance
PIN requirements. This is a monthly expense I would like to avoid by
using
our current infrastructure.

Any help is greatly appreciated...
 
G

Guest

It would be nice if Microsoft would change #3 so a user based PIN could be
used in a business environment where long distance codes are used to track
activity/project (very common). If there are security risks, explain them or
develop a solution to minimize them. An informed admin can then make the
choice to use the implementation or not. I would except the risk of a long
distance project code being seen on the server...only admins have access to
it anyway. If passing it in the clear is an issue, any admin can implement
network security to protect communications (IPSec). So, where the risk?
Pass the PIN, store in queue only, use, don't log, delete...

Thanks for considering this...

Loganatr said:
When you fax through Remote Server,
1. Server side dialing rules will be applied. In
Win2003 fax service cannot be run as local user context.
2. Even though dialing rules are applied at the
server, for security reasons the final destination number wont be displayed.
3. Calling cards and Pin Information wont be
used for dialing rules translation.

--
Loganatr [MSFT]
Microsoft Printing, Imaging and Fax Team
This posting is provided "AS IS" with no warranties, and confers no rights.
Please do not send email directly to this alias. This alias is for newsgroup
purposes only.'



Spencer Morley said:
I have installed Faxing on a Server 2003 for inbound faxing...all worked
great.

Now I am trying to get an XP Pro client to send faxes via the shared fax.
All the basics were easy. Share fax printer, install shared fax printer
on
XP workstation. Then came dialing rules. My phone system requires local
calls in the "9 NNN NNNN " (where N is the 7 digit phone number). For
long
distance the required format is "9 1 AAA NNN NNNN PPPP" (where A is area
code
and P is PIN).

Since I have worked with other fax server and Microsoft's Faxing since
WFW,
I already require all numbers in Outlook to be in the international format
"+1 (AAA) NNN-NNNN! However, I did not even get basic print, enter fax
number and send to work for long distance, so of course Outlook didn't
work
either!

In 2000 Pro (local workstation faxing only) you had to log service in as a
user to get dialing rules. Windows Server 2003 will not allow service to
run
under a local or domain user...I tried. Well on a hunch, I just added to
the
adminstrator account. I started with the 9's. Seemed to work. Then I
moved
to the calling card stuff for PIN. I think I have exhausted all
combinations
of settings on the server and client.

Further testing resulted in this:

Local test on the Windows Sesrver 2003 using a test RTF document printed
to
Fax printer follow all dialing rules. I can hear a pause (added between
number and PIN for testing) and the PIN as I have instructed the dialing
rules to insert on long distance number +1 (555) 123-4567. And a local fax
number +1 (509) 555-1234 send only the 8 digits requested (9 and number).

To test client I printed a test DOC file to the Fax printer and manually
added the number (to eliminate my Outlook 2003 from the picture). Local
faxing still follow rules dial 8 digits. I even tested setting up an Area
Code Rule to check if that worked, and the dialing was correct. I added
Dial
1 and Include the area code settings to all 509 prefixes. I could hear
the
extra digits dialed when +1 (509) 555-1234 was used.

Long distance from the client XP Pro workstation did NOT work. Although
the
service would dial the 9 1 AAA NNN NNNN it would not dial the PIN.
Running
the same test, printing DOC to Fax printer and entering phone number +1
(555)
123-4567 the service dialed only 9 1 555 123 4567, no PIN (could not tell
if
pause occurred). Recording complains about project code (PIN) missing.

For fun, before the final tests, I made sure both the client and server
had
the same exact dialing rules setup...same names and values in all
location.
This did not change results. Also, I always checked use dialing rules
since
my ultimate goal is to use Outlook contacts, and they are in international
format.

Is this the way it is supposed to work? If I have done everything a
person
can, I need to know so I can have a POTS line pulled in without long
distance
PIN requirements. This is a monthly expense I would like to avoid by
using
our current infrastructure.

Any help is greatly appreciated...
 
H

Hal Hostetler [MVP-S/U]

Contacts as in Outlook? If so, what version?

Hal
--
Hal Hostetler, CPBE -- (e-mail address removed)
Senior Engineer/MIS -- MS MVP-S/U -- WA7BGX
http://www.kvoa.com -- "When News breaks, we fix it!"
KVOA Television, Tucson, AZ. NBC Channel 4
Still Cadillacin' - www.badnewsbluesband.com

mshea said:
I have an enduser who was able to fax and use her contacts, and then
mysteriously her contacts are gone and a shared folder seems to be there.
I
think that someone else logged into her machine, creating a new situation
with more than one user profile.

Can anyone help with this?



Loganatr said:
When you fax through Remote Server,
1. Server side dialing rules will be applied.
In
Win2003 fax service cannot be run as local user context.
2. Even though dialing rules are applied at
the
server, for security reasons the final destination number wont be
displayed.
3. Calling cards and Pin Information wont be
used for dialing rules translation.

--
Loganatr [MSFT]
Microsoft Printing, Imaging and Fax Team
This posting is provided "AS IS" with no warranties, and confers no
rights.
Please do not send email directly to this alias. This alias is for
newsgroup
purposes only.'



message
I have installed Faxing on a Server 2003 for inbound faxing...all worked
great.

Now I am trying to get an XP Pro client to send faxes via the shared
fax.
All the basics were easy. Share fax printer, install shared fax
printer
on
XP workstation. Then came dialing rules. My phone system requires
local
calls in the "9 NNN NNNN " (where N is the 7 digit phone number). For
long
distance the required format is "9 1 AAA NNN NNNN PPPP" (where A is
area
code
and P is PIN).

Since I have worked with other fax server and Microsoft's Faxing since
WFW,
I already require all numbers in Outlook to be in the international
format
"+1 (AAA) NNN-NNNN! However, I did not even get basic print, enter fax
number and send to work for long distance, so of course Outlook didn't
work
either!

In 2000 Pro (local workstation faxing only) you had to log service in
as a
user to get dialing rules. Windows Server 2003 will not allow service
to
run
under a local or domain user...I tried. Well on a hunch, I just added
to
the
adminstrator account. I started with the 9's. Seemed to work. Then I
moved
to the calling card stuff for PIN. I think I have exhausted all
combinations
of settings on the server and client.

Further testing resulted in this:

Local test on the Windows Sesrver 2003 using a test RTF document
printed
to
Fax printer follow all dialing rules. I can hear a pause (added
between
number and PIN for testing) and the PIN as I have instructed the
dialing
rules to insert on long distance number +1 (555) 123-4567. And a local
fax
number +1 (509) 555-1234 send only the 8 digits requested (9 and
number).

To test client I printed a test DOC file to the Fax printer and
manually
added the number (to eliminate my Outlook 2003 from the picture).
Local
faxing still follow rules dial 8 digits. I even tested setting up an
Area
Code Rule to check if that worked, and the dialing was correct. I
added
Dial
1 and Include the area code settings to all 509 prefixes. I could hear
the
extra digits dialed when +1 (509) 555-1234 was used.

Long distance from the client XP Pro workstation did NOT work.
Although
the
service would dial the 9 1 AAA NNN NNNN it would not dial the PIN.
Running
the same test, printing DOC to Fax printer and entering phone number +1
(555)
123-4567 the service dialed only 9 1 555 123 4567, no PIN (could not
tell
if
pause occurred). Recording complains about project code (PIN) missing.

For fun, before the final tests, I made sure both the client and server
had
the same exact dialing rules setup...same names and values in all
location.
This did not change results. Also, I always checked use dialing rules
since
my ultimate goal is to use Outlook contacts, and they are in
international
format.

Is this the way it is supposed to work? If I have done everything a
person
can, I need to know so I can have a POTS line pulled in without long
distance
PIN requirements. This is a monthly expense I would like to avoid by
using
our current infrastructure.

Any help is greatly appreciated...
 
Ad

Advertisements

G

Guest

I have the same problem, for long distance i need a 7 didgit pin (project #).
Is there a way to use wild card (like #) ofr add delay in number in memory?
Thanks you.
--
Ä@ΓЌ §Ħ@ÄØШ
Lan Administrator
Windows 2000, 2003


Spencer Morley said:
It would be nice if Microsoft would change #3 so a user based PIN could be
used in a business environment where long distance codes are used to track
activity/project (very common). If there are security risks, explain them or
develop a solution to minimize them. An informed admin can then make the
choice to use the implementation or not. I would except the risk of a long
distance project code being seen on the server...only admins have access to
it anyway. If passing it in the clear is an issue, any admin can implement
network security to protect communications (IPSec). So, where the risk?
Pass the PIN, store in queue only, use, don't log, delete...

Thanks for considering this...

Loganatr said:
When you fax through Remote Server,
1. Server side dialing rules will be applied. In
Win2003 fax service cannot be run as local user context.
2. Even though dialing rules are applied at the
server, for security reasons the final destination number wont be displayed.
3. Calling cards and Pin Information wont be
used for dialing rules translation.

--
Loganatr [MSFT]
Microsoft Printing, Imaging and Fax Team
This posting is provided "AS IS" with no warranties, and confers no rights.
Please do not send email directly to this alias. This alias is for newsgroup
purposes only.'



Spencer Morley said:
I have installed Faxing on a Server 2003 for inbound faxing...all worked
great.

Now I am trying to get an XP Pro client to send faxes via the shared fax.
All the basics were easy. Share fax printer, install shared fax printer
on
XP workstation. Then came dialing rules. My phone system requires local
calls in the "9 NNN NNNN " (where N is the 7 digit phone number). For
long
distance the required format is "9 1 AAA NNN NNNN PPPP" (where A is area
code
and P is PIN).

Since I have worked with other fax server and Microsoft's Faxing since
WFW,
I already require all numbers in Outlook to be in the international format
"+1 (AAA) NNN-NNNN! However, I did not even get basic print, enter fax
number and send to work for long distance, so of course Outlook didn't
work
either!

In 2000 Pro (local workstation faxing only) you had to log service in as a
user to get dialing rules. Windows Server 2003 will not allow service to
run
under a local or domain user...I tried. Well on a hunch, I just added to
the
adminstrator account. I started with the 9's. Seemed to work. Then I
moved
to the calling card stuff for PIN. I think I have exhausted all
combinations
of settings on the server and client.

Further testing resulted in this:

Local test on the Windows Sesrver 2003 using a test RTF document printed
to
Fax printer follow all dialing rules. I can hear a pause (added between
number and PIN for testing) and the PIN as I have instructed the dialing
rules to insert on long distance number +1 (555) 123-4567. And a local fax
number +1 (509) 555-1234 send only the 8 digits requested (9 and number).

To test client I printed a test DOC file to the Fax printer and manually
added the number (to eliminate my Outlook 2003 from the picture). Local
faxing still follow rules dial 8 digits. I even tested setting up an Area
Code Rule to check if that worked, and the dialing was correct. I added
Dial
1 and Include the area code settings to all 509 prefixes. I could hear
the
extra digits dialed when +1 (509) 555-1234 was used.

Long distance from the client XP Pro workstation did NOT work. Although
the
service would dial the 9 1 AAA NNN NNNN it would not dial the PIN.
Running
the same test, printing DOC to Fax printer and entering phone number +1
(555)
123-4567 the service dialed only 9 1 555 123 4567, no PIN (could not tell
if
pause occurred). Recording complains about project code (PIN) missing.

For fun, before the final tests, I made sure both the client and server
had
the same exact dialing rules setup...same names and values in all
location.
This did not change results. Also, I always checked use dialing rules
since
my ultimate goal is to use Outlook contacts, and they are in international
format.

Is this the way it is supposed to work? If I have done everything a
person
can, I need to know so I can have a POTS line pulled in without long
distance
PIN requirements. This is a monthly expense I would like to avoid by
using
our current infrastructure.

Any help is greatly appreciated...
 
Ad

Advertisements


Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top