![]() |
Good point. That also brings up the question of faxmaster. In hylafax there is no such acount that can kill/alter other jobs. I think there is such a need ( I mean an account to control other jobs) So after some looking around I thing the way is to submit a new job at the dest. Host ( via a sendfax ....-f my_local_user -h ttyS1@remotehost ....) and remove the queue file from sendq. Maybe alitle bit dirty but may work) We can get the my_local_user, number to dial ...etc from the queue file. Dest host should accept all job submitions from myhost (so that we do not need password). There is still the question of how the user will see/remove/control his job after it is transfered to the remote host. Sedat YILMAZER -----Original Message----- From: hylafax-users-bounce@hylafax.org [mailto:hylafax-users-bounce@hylafax.org] On Behalf Of Lee Howard Sent: Thursday, March 21, 2002 8:32 AM To: Sedat Yilmazer Cc: 'Enrico Payne'; hylafax-users@hylafax.org Subject: Re: [hylafax-users] Routing faxes to other fax servers based on phone number On 2002.03.20 22:13 Sedat Yilmazer wrote: > > What about modifying the faxsend and make it a script and copy the > original faxsend to faxsend.local and then > > a-) if the fax can be sent localy then activate the faxsend.local > b-) if a least cost route can be found then do a faxalter to set the > host to the least cost routing host This is a very promising approach. However, how do you propose to get faxalter to work properly when the job may be owned by a user other than uucp? Lee. ____________________ HylaFAX(tm) Users Mailing List _______________________ To unsub: mail -s unsubscribe hylafax-users-request@hylafax.org < /dev/null ____________________ HylaFAX(tm) Users Mailing List _______________________ To unsub: mail -s unsubscribe hylafax-users-request@hylafax.org < /dev/null