Login
Register
Search
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Forums
Enterprise Resource Planning & Manufacturing
Lawson S3 Procurement
Fax Integrator dialing rules
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Who's On?
Membership:
Latest:
Wayne Willis
Past 24 Hours:
0
Prev. 24 Hours:
0
Overall:
5190
People Online:
Visitors:
201
Members:
0
Total:
201
Online Now:
New Topics
Lawson Landmark
Executing IPA from PR160
5/3/2024 2:46 PM
We're facing a situation where we need to upda
IPA/ProcessFlow
Executing IPA from PR160
5/3/2024 2:46 PM
We're facing a situation where we need to upda
S3 Customization/Development
Cobol - Extract Current Time
4/24/2024 7:21 PM
How do you extract just the Current System Time in
Lawson Landmark
LPL INSTR Functions
4/5/2024 8:32 PM
I'm writing a simple report using the Create R
Infor SCM
Translating 856 to get the ~ REF^CN^ field
4/3/2024 8:24 PM
We are trying to get the tracking number which is
IPA/ProcessFlow
Sample XML file create Flow
4/3/2024 3:43 PM
Hello everyone, I am new to creating XML files
Lawson S3 HR/Payroll/Benefits
bn105 error message
3/26/2024 6:40 PM
I need to change some of the set ups in our Life I
IPA/ProcessFlow
IPA executing Job
3/13/2024 7:08 PM
New to the IPA world and was wondering, can an IPA
Lawson S3 HR/Payroll/Benefits
Life Age Reduction on benefits plans
3/12/2024 7:15 PM
For our optional life we have an age based coverag
Lawson S3 HR/Payroll/Benefits
BN53.1 Add-In
3/7/2024 3:31 PM
We are migrating to Solstice. They require a
Top Forum Posters
Name
Points
Greg Moeller
4184
David Williams
3349
JonA
3288
Kat V
2984
Woozy
1973
Jimmy Chiu
1883
Kwane McNeal
1437
Ragu Raghavan
1354
Roger French
1311
mark.cook
1244
Forums
Unanswered
Active Topics
Most Liked
Most Replies
Search Forums
Search
Advanced Search
Topics
Posts
Prev
Next
Forums
Lawson S3 Procurement
Fax Integrator dialing rules
Sort:
Oldest First
Most Recent First
You are not authorized to post a reply.
Author
Messages
Mike Schlenk
Veteran Member
Posts: 71
10/20/2008 9:05 PM
After much wrestling, the only way I got the Fax Integrator 9.0.0.2 to use dialing rules is to include the country code like this: +1 (913) 222-2222. The regular 10-digit number stored in Lawson PO10 doesn't work.
Has anyone else ran in to this? Perhaps a MS patch to fax services or .net?
David Williams
Veteran Member
Posts: 1127
10/20/2008 9:18 PM
The 10 digit phone number in Lawson should be fine - it's usually the fax program (WinFax 10?) that has to be set up to use the country code or not.
Mike Schlenk
Veteran Member
Posts: 71
10/20/2008 9:22 PM
It's the fax integrator 9 using Windows fax services. No winfax. Windows 2003 server
JonA
Veteran Member
Posts: 1162
10/21/2008 10:37 AM
From MyLawson.com Communities...
ROBERT STEPHENS
Sr. Business Analyst
SUTTER HEALTH
8/16/2007 11:05:40 AM
Small Warning for Fax Integrator 9.0.0.1
For those of you moving to the Fax Integrator 9.0.0.1, moving away from WinFax to the Windows Fax Services sounds like a relief. I am sure it will be. Uncle Bill seems to have taken care of us with the Fax Console and Fax Monitor. There is an issue that some of you may run into, though, especially if you are relying on the Dialing Rules that you set up for your modem.
In our situation, our fax server needs to dial a '9' to open an outside line. I don't think this is an uncommon situation, but there are probably some other variants as well (using dialing cards or transmission time constraints). During our testing I had the hardest time getting the faxes to abide by our dialing rules.
I did find the answer and it is not a Lawson issue, but it is a Windows XP issue. If the fax number is not in something similar to the full canonical format, Windows Fax Services (WFS) simply tries to dial the numbers as given--ignoring any dialing rules.
Currently, all of our telephone numbers are formatted as 1-555-999-1234. In its ideal, WFS would like to see every phone number as +1 (555) 999-1234 (this is the canonical format). The '+1' is the US country code, other countries would have their code in this position.
Here is the problem...the fax field for the PO10.2 doesn't allow enough characters to fully format the number in canonical--especially for countries other than the US. I have gotten two formats to work so far (there may be others).
1 - Compress everything. The number would look like +1(555)999-1234 (no spaces). This does trigger the dialing rules, but the formatted number looks a little odd (+1 +1(555)999-1234). It works though.
2 - Ignore the country code. The number would look like (555) 999-1234. This triggers the dialing rules as well, and formats prettier, but it also assumes that the phone number is internal to the US. Not being familiar with the international versions of Windows XP, perhaps the local country code is assumed based on the individual setup.
So, while this will be a big issue for us, as we have to reformat all of our PO10.2 entries, perhaps you can dodge this bullet. If you have any questions, or if my explanation was not clear enough, you can look at Windows Knowledge Base article 318575 at
http://support.microsoft.com/kb/318575
Enjoy,
Russell Spreeman
Business Applications Development Analyst
LAPORTE
HOSPITAL
10/17/2007 8:47:50 AM
RE: Small Warning for Fax Integrator 9.0.0.1
I have just been through the Fax Integrator upgrade and would like to offer some thoughts for those who will be running it under Windows XP with its picky dialing rules. Whether you choose to use XP's dialing rules, or to enter the number complete with any leading character(s) to get an outside line, you have to stick to the same format for all vendors. In our case I decided to just put the exact dialup string into Lawson rather than deal with the parenthesis etc. needed for XP's dialing rules to work. I had heard that the fax numbers were pulled from PO10.1 from some people and from PO10.2 from other people so I decided to upload the new format to both forms. I used MS Addins to download the fax numbers, Excel and its string functions to reformat them, then used Add-ins again to upload the reformatted phone numbers.
As soon as Fax Integrator downloads the faxes from your Lawson system they go immediately over to the fax console for dialing out and you can't halt the process (stopping the Windows Fax service is not an option, trust me) so at least a few faxes may be attempted to be sent before you can fix the phone numbers, "re-send" the faxes from Fax Integrator, and delete out the ones from Fax Console which are incorrectly formatted. You can't edit the fax numbers in the Fax Console window - you have to edit them in Fax Integrator and re-send them to the Fax Console. Those faxes which are mis-dialed before you delete them may end up being sent (repeatedly) to an incorrect phone number, perhaps one that is in-house and not a fax number. (People do not like repeated calls from a fax modem, however innocently they come about. Oops!)
The key point is to prepare to get all of your fax phone numbers in proper format prior or concurrent to going live with this version of Fax Integrator (at least if running it on XP) because once it goes live and the phone numbers don't work you have an annoying problem to baby-sit and you will still need to fix the fax numbers.
Yatrik Shah
DBA
LOYOLA
UNIVERSITY
MEDICAL CTR
10/17/2007 1:23:08 PM
RE: Small Warning for Fax Integrator 9.0.0.1
We just moved this to production this week and we did something similar as well in terms of changing the fax number. If you don't want to go through the hassle of using addins or doing it by hand here's the SQL I used with Oracle to change the data(make sure you make a backup of the table first):
This will show you what it would look like BEFORE you change it --
select substr(fax_number,1,1) || '(' || substr(fax_number,3,3) || ')' || substr(fax_number,7,8) from schemaowner.povendloc
where purch_fr_loc='FAX' and length(rtrim(fax_number))=14
Update SQL
update schemaowner.povendloc
set fax_number substr(fax_number,1,1) || '(' || substr(fax_number,3,3) || ')' || substr(fax_number,7,8)
where purch_fr_loc='FAX' and length(rtrim(fax_number))=14
/
commit
/
Remember this is for Oracle, you may have to adjust it for MS Sql server, etc. Plus I based it on the length of the values in the FAX_NUMBER field. You may have to adjust this also for your table. I would suggest playing with the SELECT sql to make sure you will get the right results before updating
You are not authorized to post a reply.