StoneFax. 20 Mar TM and copyright Imagicle spa

Transcription

1 StoneFax 20 Mar 2019 TM and copyright Imagicle spa

2 Table of Contents Administration Guide...1/73 Description and Architecture...1/73 Configuration Task List...4/73 PBX Configuration...5/73 Product Administration...12/73 License Activation...13/73 Print To Fax...14/73 Advanced Configuration...24/73 Solution-specific Configuration...30/73 Troubleshooting...32/73 Product Configuration...33/73 Product Integration API...40/73 Overview...40/73 Submit Fax...41/73 Get Outbound Fax Details...46/73 Download outbound fax document...48/73 User Guides...50/73 StoneFax User Guides...50/73 FAQ and Solutions...51/73 Issue with return receipt not being sent when sending fax through web interface (Application Suite Winter )...51/73 How to retrieve fax activity reports - understanding Stonefax reports...53/73 Several incoming faxes can be found in Windows Fax and Scanner Console but not in Stonefax. Fxssvc.exe error on dll as INETCOMM.dll in the event viewer...55/73 Saving faxes in structured folders...56/73 Solution:...56/73 Unable to receive faxes on Windows Server 2012 R2 with fxssvc crashing in the module fxst30.dll Error Code: 0xC /73 Enable G.729 signaling for Stonefax...60/73 How to modify mail notification templates for admin and users in Stonefax application...61/73 Stonefax status is undefined/stopped and won't start - Windows fax service crash with faulting module FXSTIFF.dll...63/73 How to modify a cover in Stonefax...65/73 How to change resolution and rendering method of faxes...67/73 How to set fax rate / modem max speed in Stonefax...68/73 How to configure network-clock options on Cisco ISR series routers...69/73 Video...70/73 Product Overview...70/73 Sending and receiving a fax via /73 Using Fax Jabber Gadget...72/73 Using Fax Mobile App...73/73

3 Administration Guide Description and Architecture Traditional manual faxes are out of date. StoneFax is a complete software solution including a robust fax server based on Imagicle unique Fax to IP driver, able to interoperate directry with the PBX trough Voip comminication. A professional fax server grants substantial savings and it improves customer service and company image; the process of sending a fax is faster and incoming faxes are automatically integrated with today's web and -based workflow. StoneFax delivers a complete IP fax server solution, allowing users to send and receive faxes directly from any client or through a dedicated web interface. StoneFax can be seamlessly integrated with any server using standard SMTP/IMAP-POP3 protocols without enforcing specific infrastructure requirements. StoneFax can automatically route incoming faxes in TIFF/PDF formats to each user's mailbox and personal web interface, picking out the right recipient by the Called Line Identifier (also known as "extension") or by the line on which the fax was received. This enables users to check faxes from anywhere in the world using either: A traditional desktop client (i.e.: Outlook, Lotus Notes...). This is the to Fax feature A web browser (Internet Explorer, Chrome, Firefox...). This is the Web To Fax feature To send a fax, each user can either: Create it as a new message in his/her client, the To Fax feature Upload a document via web through a dedicated web page, the Web To Fax feature Directly print from any application to the StoneFax network printer, the Print To Fax feature After the fax is sent, the user receives a transmission report in his/her inbox. StoneFax automatically manages the outgoing queue, trying to send the fax again if it not succeeded. Together with the other units of the Application Suite, StoneFax completes the Unified Messaging Solution for Cisco Unified Communication. Architecture StoneFax can be used as an To Fax gateway together with any SMTP/POP3 or IMAP mail server, allowing users to send and receive faxes directly by their client. Special system will be discussed later (MS Outlook). In order to set up this feature, you must create a dedicated mailbox on the mail server, from which StoneFax will fetch the faxes that will be sent out. StoneFax needs an server to: Download s sent by the users to a specified account (ex. fax@company.com) with the file to be faxed (this is the Outgoing faxes - POP3 behavior) Notify each user of incoming faxes via with the fax as attachment (this is the Incoming faxes - SMTP behavior). See the Receive a fax section for further details on how let users receive a fax This is the architecture of the To Fax behaviour: Administration Guide 1/73 Administration Guide

4 Users send s to a specified recipient (for instance: fax@company.com), specifying the fax recipient number in the subject field and attaching the file to be faxed. Multiple recipients and multiple attachments are supported. StoneFax must be configured with the designated IMAP/POP3 account (in our example: fax@company.com) and the polling interval for checking. StoneFax downloads the and converts the attached file to a fax by printing it to a graphic file. This will be queued to be sent to the specified recipient number. Note: StoneFax can send many faxes at the same time, limited only by the number of avaliable lines and license channels. Even if many channels are free, faxes addressed to the same recipient number will always start one after the other. This means that the second fax will start only when the first has been sent or it has exhausted its retries. When the fax has been processed, StoneFax notifies the sender with a return receipt in his/her mailbox. This is the architecture for the incoming faxes: Administration Guide 2/73 Description and Architecture

5 StoneFax is receiving a fax for a specific number. StoneFax manages the dnis (called number) and ani (caller number) to pick out the user to whom the fax is addressed to (see User configuration). StoneFax notifies the user by of a received fax. It can also attach the received fax. To enable forwarding capabilities, please double check that a fax address has been configured for such that users. This address is exclusive to the fax. Although it can be the same of the user ordinary address, it is to be entered in a different field. Administration Guide 3/73 Description and Architecture

6 Configuration Task List Warning: you must install and configure the Application Suite before being able to configure the single applications. Please go through the AppSuite Deployment, Main Configuration, and User Management sections before reading on. You can easily configure StoneFax trough the following mandatory steps: Create the end user's list through users management Configure the PBX Configure the application, including the parameters and fax routing Start the service Configure the fax service parameters Activate the license (in 30 days) Optionally, you may want to configure: Print to Fax Multifunctional printer integration Automatic Fax Backup Incoming Fax Print Group Faxing Mass Faxing These tasks are described in the Advanced Configuration section of this guide. Administration Guide 4/73 Configuration Task List

7 PBX Configuration Cisco Unified Communications configuration StoneFax interacts with the Unified Communications system through both SIP or H.323 protocols using both T.38 or G.711 passthrough modes. The SIP configuration is suggested and will be detailed. Remember to enable the new StoneFax engine and enable SIP in the StoneFax - Manage Service - IP Routes page on the Application Suite. In the following examples, we are supposing the StoneFax server IP address is General concepts The PBX sees the StoneFax server as a SIP trunk or H.323 gateway The signaling transport must be SIP over UDP or H.323 over TCP for both directions (PBX to StoneFax and StoneFax to PBX) The audio encoding of the rtp stream must be T.38 or G.711alaw/G.711ulaw/ On the PBX you must configure routing rules to make incoming faxes reach StoneFax and outgoing faxes to exit on the PSTN Note: if you configure StoneFax on H.323, remember that it listens for incoming faxes on the non-standard port 1721 Configuring Voice Gateways using SIP or H.323 protocol In this configuration, StoneFax directly sends and receives SIP calls managing faxes through T.38 first and fallback to passthrough in case T.38 is not available (e.g.: sending fax internally to Cisco ATA devices). This configuration can be chosen if you have CallManager Express or if you have CallManager with at least one voice port configured in h.323 or SIP. You cannot directly send faxes through the Voice Gateway if it is configured with MGCP. On the voice gateway you must enable T.38 and fallback to G.711 passthrough in global configuration mode (G.711alaw in the examples) voice service voip fax protocol t38 fallback pass-through g711alaw Then a dial-peer must be added to route incoming faxes to StoneFax. The session target points to the IAS machine and the codec is g711alaw. dial-peer voice 1 voip description INCOMING FAX FROM PSTN TO STONEFAX destination-pattern 4.. session target ipv4: session protocol sipv2 codec g711alaw no vad Quick troubleshooting tips Warning: effective from IOS ver. 15.2(1)T calls from non trusted IP addresses are blocked by default. To allow outgoing faxes from StoneFax you must either add it to the ip address trusted list or disable the toll-fraud prevention application completely (with the no ip address trusted authenticate command). If StoneFax does not seem to negotiate outgoing faxes, remember that you need the SIP to SIP, h323 to h323 or SIP to H323 commands on the VG global configuration Install Wireshark on the StoneFax machine to check negotiation (from the Telephony Menu select "Voip Calls") Administration Guide 5/73 PBX Configuration

8 If incoming faxes do not reach the StoneFax machine, ensure that no dial-peer is diverting the call (usually dial-peers with destination pattern.t). Use the show dial-peer voice summary command If you want the remote hardware fax machines sending faxes to your Stonefax to get a busy tone when all StoneFax licensed channels are in use, add the max-conn X command to the StoneFax incoming dial-peer, where X is the number of licensed channels Configuring Cisco Unified CallManager In this configuration, StoneFax interacts with Cisco CallManager to send and receive SIP calls managing faxes through T.38 first and fallback to passthrough in case of T.38 not available (ex: sending fax internally to Cisco ATA devices). This configuration must be chosen if you want to be able to bill outgoing faxes (for example with Imagicle Billing). The CallManager must be configured by adding a new SIP trunk with the StoneFax address and the correct inbound calling search space for StoneFax to be able to send outgoing faxes. Administration Guide 6/73 PBX Configuration

9 Remember to set a valid CSS for inbound calls on the Trunk configuration, to allow StoneFax to send outgoing faxes. The Calling Party Selection in the Outbound Calls section must be set to Originator. Since the signaling must be transported over UDP only, a new SIP Secure Profile is needed. Select System - Security - SIP trunk Security Profile. Click the Add New button. Leave all the options to default values except for the Outgoing transport type, which must be set to UDP. The security mode must be left "Non Secure". Administration Guide 7/73 PBX Configuration

10 Then go back to Device - Trunk, Edit the StoneFax trunk and ensure that the StoneFax SIP Security profile is selected in the SIP Information panel. The last step is to add a Route Pattern, which is needed to route incoming faxes to the StoneFax SIP trunk. In the following example we configure all calls for destinations starting with 400 to 499 to be sent to StoneFax. Administration Guide 8/73 PBX Configuration

11 Then the voice gateway must be configured to enable T.38 and fallback to passthrough in global configuration mode (G.711alaw in the examples) voice service voip fax protocol t38 fallback pass-through g711alaw Configuring MGCP Gateways While dealing with Cisco Unified CallManager using MGCP controlled voice gateways, specific commands must be issues on the gateways: Router(config)# no mgcp fax t38 inhibit Router(config)# mgcp package-capability fxr-package Router(config)# mgcp default-package fxr-package show mgcp command should then list the fax properties as shown below: MGCP supported packages: gm-package dtmf-package trunk-package line-package hs-package ms-package dt-package res-package mt-package fxr-package MGCP T.38 Fax is ENABLED MGCP T.38 Fax ECM is DISABLED MGCP T.38 Fax NSF Override is DISABLED MGCP T.38 Fax Low Speed Redundancy: 0 MGCP T.38 Fax High Speed Redundancy: 0 This would enable propagation of t38 capabilities in SDP and notifications of t38start and t38stop events as defined in fax package. An example of IOS configuration for MGCP T.38 support follows: voice-port 0/0/0 bearer-cap Speech! ccm-manager mgcp ccm-manager music-on-hold Administration Guide 9/73 PBX Configuration

12 ccm-manager config server CCM-IP ccm-manager config! mgcp mgcp call-agent CCM-IP 2427 service-type mgcp version 0.1 mgcp dtmf-relay voip codec all mode out-of-band mgcp rtp unreachable timeout 1000 action notify mgcp modem passthrough voip mode nse mgcp package-capability rtp-package no mgcp package-capability res-package mgcp package-capability sst-package mgcp package-capability pre-package no mgcp timer receive-rtcp mgcp sdp simple mgcp rtp payload-type g726r16 static! mgcp profile default! dial-peer voice 2 pots service mgcpapp port 0/0/0! Warning: after configuring the voice gateway in MGCP mode, please save your configuration and reboot it. To troubleshoot MGCP T.38 fax relay, perform the following steps: Router# show mgcp 1. Make sure that you have a working MGCP network and that you can make a voice call 2. Make sure that T.38 fax relay for MGCP is configured on both the originating and terminating gateways 3. Use the following commands to debug problems while making the call: 1. The show mgcp [connection endpoint statistics] command displays information about MGCP calls. 2. The show voice call summary command indicates, during a T.38 fax transmission, a change of state from S_CONNECT to S_FAX in the VTSP STATE column and a change from the codec name to a numeric fax rate in the CODEC column (for example, g711u changes to 14400) 4. For CA-controlled T.38 fax relay, you can verify the MGCP side of the call flow by using the debug mgcp packets command. You should see the following output: 1. CRCX from the call agent with "fxr/fx:t38-loose" or "fxr/fx:t38" parameter 2. RQNT from the call agent with "R: fxr/t38" parameter 3. NTFY from the gateway with "O: fxr/t38(start)" parameter (optionally) 4. MDCX from the call agent with either "m=image" in the SDP message, or "a:image/t38" in the Local Connection Options message, or both 5. For CA-controlled T.38 fax relay, you should see the following messages in the output from a show voice call summary command on the MGCP gateway during a T.38 fax transmission: Change of state from S_CONNECT to S_FAX in the VTSP STATE column; change from codec name to numeric fax rate (such as "g711u" to 14400") in the CODEC column. General troubleshooting tips for Cisco Unified CallManager On CuCm most issues are related to the partitions or Calling search spaces. The CSS for Inbound Calls on the SIP trunk must be suitable to reach the PSTN through the voice gateway Test incoming and outgoing faxes separately If you need to change the properties of the default SIP profile, remember to create a custom SIP profile for StoneFax so that its SIP trunk remains unaffected by the changes Warning for CuCM cluster installations: Placing the StoneFax SIP trunk in the Default device pool does not ensure it can be always reached. In CCM cluster installations, ensure that the Cisco Unified CallManager Group associated with the Default device pool contains all the CuCms in the "Cisco Unified Communications Manager Group Members" selection list Direct Inward Dial (DID) Or Shared Numbers? StoneFax manages the dnis (called number) and ani (caller number) to directly address the incoming fax to the specific user. This Administration Guide 10/73 PBX Configuration

13 feature requires DID (Direct-Inward-Dial) configuration from the TELCO, in order to manage a pool of public numbers. If you don't have DID, you can have: Only a public number dedicated to fax A unique public number to share between voice and fax In the former case, you have a simpler context with one user only (the company fax). So you can follow the sample provided in this guide and apply it to the unique available user. In the latter case, you can use the IVR feature of Application Suite in order to provide an automated voice response to choose between voice and fax. You simply need to configure the IVRMANAGER with a special script called DirectInwardDial.tcl. The script is able to answer the incoming call prompting the message: "Please dial the extension you wish to reach". If no extension is dialled, the script will automatically connect to the default extension after a timeout. If you specify the fax extension as the default one, the fax calls will be connected to that fax. Please refer to Imagicle IVR Manager Enterprise configuration guide for details. Administration Guide 11/73 PBX Configuration

14 Product Administration Starting Services Open the Application Suite folder in Start -> Programs and click "Administration". In the left pane of the web page, select StoneFax -> Manage Service. Here you can find the diagnostic page of StoneFax. Just click on the Start button to start StoneFax. You can also start StoneFax services through Windows service console by starting the SFXAL service. SFXAL is only a stub that will start StoneFax and then stop. It is needed to start StoneFax when you reboot the server. You can check the status of StoneFax services through the web interface. Administration Guide 12/73 Product Administration

15 License Activation StoneFax is licensed per channel, regardless the number of users and gateways. The channel number is the total of fax calls (incoming and/or outgoing) that it is able to handle at the same time. StoneFax can handle up to 90 channels per server. StoneFax supports high availability clusters with hot-swap redundancy and load balancing, both for incoming and outgoing faxes. Each server requires a separate license because all the nodes are active at the same time (active/active model). You can add more nodes at a later time. Evaluation StoneFax will run for 30 days in evaluation mode. During evaluation, StonaFax will allow 2 concurrent faxes (2 channels). How to activate the license The license can be activated by purchasing the product from Imagicle. You can enable the license in the license page as described in the Application Suite common configuration section of this guide. To activate the license, follow the standard procedure you can find in the General configuration section. Administration Guide 13/73 License Activation

16 Print To Fax StoneFax provides the Print To Fax feature to any user who is in the same Windows Domain of the StoneFax server. Note: StoneFax and the client PC using this feature must be in the same Windows Domain Using the Print To Fax is no different than from printing to a network printer: simply print from the application to the Print To Fax printer driver named "Stonefax". Print to Fax setup for the Server To enable Print to Fax, you have to configure some roles and settings on the Imagicle Application Suite server. Failing to do so will prevent Stonefax to assign the fax to the right user, and to display the sent faxes in the web interface. You must: Assign special permission to the LOCAL_SYSTEM account. Enable a setting in a configuration file Restart the StoneFax service from the web interface Share the Fax printer in the domain. Windows Firewall service must be running 1. Assign special permissions to the LOCAL_SYSTEM account Log onto the IAS server as Administrator. Open the Windows Fax Service Manager with administrator rights. Select "Fax (Local)", then right click and select "Properties", then select the Security tab. Add the Local SYSTEM account to authorized users. Administration Guide 14/73 Print To Fax

17 Select it and press the "Advanced" button. Administration Guide 15/73 Print To Fax

18 Press "Edit", then click the "Show advanced permissions" link. Administration Guide 16/73 Print To Fax

19 Assign full fax permission to the SYSTEM account, then confirm. Administration Guide 17/73 Print To Fax

20 2. Enable Print to Fax status polling Edit this configuration file with Notepad: <Install dir>\apps\stonefax\server\system\stonefax.ini Add the following parameter in the [Settings] section: [Settings] Poll=1 3. Restart StoneFax Service Log onto the IAS web interface as administrator. On the menu, select Fax Service, Manage Service. Press the Stop button, then Start. 4. Share the Fax Printer in the domain Share the "StoneFax" printer as you would with any network printer. Ensure Windows Firewall Service is running. Printer sharing does not work if Windows Firewall is stopped or disabled. Please check this Microsoft article. Even if the service is running, the firewall can be disabled at the application level. Note: when enabled at the application level, Windows Firewall could interfere with Imagicle Application Suite. Please make sure all incoming and outgoing TCP and UDP communication is allowed. For more information, check the Network Setup page in the deployment section of this guide. Administration Guide 18/73 Print To Fax

21 5. Make sure the fax users list include Active Directory Username and Domain When a new fax job is submitted to StoneFax, it receives the sender login username and domain. That is, the user who was logged onto the Windows client and who sent the fax through Print To Fax. StoneFax need to match those credentials with the users list. So, make sure you fill the Active Directory Username and Domain fields in Application Suite User Management for all the fax-enabled users. Print to Fax setup for the Client If you wish to enable the Print To FAX feature on a client machine, you must install the shared fax printer driver on that machine. This is exactly the same procedure as for any other Windows network printer driver. This procedure usually takes 15 minutes. Installing a Fax printer on Windows Vista, Windows 7 and later: automatic procedure Click Start > All Programs > Windows Fax and Scan, or press the Windows button and search for "Windows Fax and Scan". In Windows Fax and Scan menu, select Tools > Fax Accounts. In the Fax Accounts dialog box, Click Add. 2. Specify the StoneFax Server Name or IP Address: Administration Guide 19/73 Print To Fax

22 3. Set the name for the local StoneFax printer to StoneFax:: Installing a Fax printer on Windows Vista, Windows 7 and later: manual procedure On the client machine, from the start menu, go to Settings > Printers > Add Printer. Select Network printer. Administration Guide 20/73 Print To Fax

23 Click on "the printer that I want isn't listed". Select the printer by specifying the StoneFax server IP address as computer name and then StoneFax as printer name (if StoneFax is not found, type Fax as printer name). Click on Next to complete. Administration Guide 21/73 Print To Fax

24 Activate the fax account Click Start, All Programs, and then click or search for Windows Fax and Scan. In Windows Fax and Scan, click Tools, and then click Fax Accounts. In the Fax Accounts dialog box, Click Add, and then follow the wizard steps to create a new fax account. Note: If you do not have Windows Fax and Scan installed, add this Windows feature through the control panel. Click next again to enter the server name. Administration Guide 22/73 Print To Fax

25 You can now send a fax by printing from any document and selecting the fax printer you just added. Your fax will be automatically submitted to StoneFax and sent to the recipient fax number that you provided. Users can specify an address for feedbacks ( receipt). How to send a fax on behalf of another user If you need to send a fax on behalf of another user, or group fax user, enter his/her IAS username in the Billing Code field on Windows Fax and Scan on the PC from which you send the fax. You need to do this procedure only once. 1. Log onto the PC and run Windows Fax and Scan 2. On the application menu, select Tools, then Sender Information 3. In Billing Code enter the IAS username 4. Optionally, you may want to fill in other information, which will be displayed on the cover page Administration Guide 23/73 Print To Fax

26 Advanced Configuration This section describes how to enable some StoneFax advanced features, including: Defining a "catch all" default user for incoming faxes Creating fax workgroups Printing incoming faxes Storing Incoming Faxes Changing the name of the attachment Configuring Advanced Fax Routing Specifying recipient numbers in the "To:" field Enabling additional file types as attachments, or as Web to Fax documents The default "catch all" user The default user can be any user from the IAS users list. A user named "default" is automatically added to the user list by the setup program. To change the default user, click on Manage Service, enter the IAS username you want to use and press Save. Warning: Ensure the user is available and has permissions suitable to receive faxes. If the user is not selected or if the user does not exist, StoneFax will reject the fax. When a default user is defined: When an incoming fax is addressed to a number which cannot be found in the users list, it will forwarded to a default user When an incoming fax is addressed to a number associated to a user who is not allowed to receive faxes, it will forwarded to a default user When an outgoing fax sent through print-to-fax cannot be associated to any user, it will NOT be stored in the default user outbox. You can see them through the Outgoing report web page You can access the default user outbox and inbox as you would for a standard user; or you can see the his faxes in the Inbox/Outbox report web pages. Some faxes received by StoneFax may be addressed to numbers which are not in the user list. By default StoneFax sends these faxes to the "catch all" user if it has been defined. It prints them or stores them according to this user' preferences. To setup a "catch all" user, create it as a normal user. Then click on "Manage Service" and enter his username in the "send all faxes for unknown users to user..." textbox. Note: Use the internal Application Suite name of the user you defined, not the Active Directory credentials. Press the Save button to save the changes. Restart is not required. Busy tone for unknown recipients and the "catch all" user If this user is not defined and the recipient number of and incoming fax is unknown, StoneFax will reject the fax (the sender will hear a busy tone). To let the sender of a fax for an unknown fax number hear the busy tone, leave the "default user" field blank. Fax Workgroups The most common way to use StoneFax is to assign a personal fax number to each user. This way each user can send and receive personal faxes which are secure and private. Sometimes the customer needs the same faxes to be accessible to multiple users through the and the web interface. The easiest way to do that is to share the same username, password and account between a group of users. This method has some disadvantages: the users cannot log onto the web interface with their domain credentials, and must explicitly select the Administration Guide 24/73 Advanced Configuration

27 shared account when sending faxes. The second way is detailed here. Fax User Groups Suppose you have five people working in the Sales department, and you want them to have one unique fax number. All of them must be able to send faxes as "Sales department" and to view the received faxes through the web interface. Create one additional Application Suite user for the fax workgroup; we'll call it "sales_grp". Set the "Fax number" (e.g. 794), "Fax enable send" and "Fax enable receive" fields. Optionally, fill the other fax fields too. Then create the five application suite users in the users list with no fax number and no fax offnet number. Set the "Fax group username" to "sales_grp". The users can be created through user synchronization. With this configuration: Web inbox: The users in the group will be able to see the incoming fax addressed to the group fax number (794 in our example) through the web interface by logging with their credentials. Only one copy of the fax is stored. If one of the users deletes the fax, it will be lost for all of them Web To Fax: on the "Send a Fax" page the users can choose to send a personal fax (default) or a group fax. If the fax is sent as a group fax, it will be displayed in the other group members outbox Web outbox: The users in the group will be able to see the outgoing and sent faxes through the web interface by logging with their credentials. Their personal faxes will be displayed too Fax To The group members who enabled " to fax" will receive a copy of the fax in their inbox To Fax: The faxes sent by the group members with their personal accounts will use the group user ("sales_grp") properties, including offnet fax number and cover page if specified. The fax will be available to all group members in the web interface Print To Fax: a fax sent this way will always be considered personal, and will not be displayed in the outbox of the other users in the group Special case: if you want a user to be able to send both personal and group faxes, set his "Fax number" field. This user will still be able to receive group faxes but will send personal faxes by default. He or she will be able to send a group fax by adding the ";shared" suffix to the subject. Printing Incoming Faxes The print incoming fax feature allows StoneFax to print all the fax documents a user receives. The following steps are required to be able to print incoming faxes. 1. Create a new Windows Administrator Account During installation the IAS setup ask for a Windows account to be used to run the services and web interface. Enter the credentials of a domain administrator or create a new local administrator and add it to the Windows domain. Let's call it "FaxAdministrator" in our examples. 2. Install all the printers you need on the StoneFax server StoneFax can only print incoming faxes on printers which can be reached by the server on which it runs. The printers must be either local or mapped locally. Log onto StoneFax server to ensure that the "FaxAdminstrator" account can access the printers you want to use (i.e. has the "print" permission). If you want to use network printers, adjust sharing permissions of the remote printers too. 3. Select the users which will have their fax printed Administration Guide 25/73 Advanced Configuration

28 You can select which users will have their incoming faxes printer by activating the "Print Incoming Faxes" checkbox field in IAS User Management page. If you must set the field for a large number of IAS users, you may export users' data to a CSV file, edit it with MS Excel, and import the data again. 4. Choose a different printer for each user You can select a different printer for each user by entering its name in the "Printer Name" field in the "User Management - Modify user" page. For Local printers, enter the name of the printer as you see it in the Control Panel. For networks printer enter: \\RemoteServer\MyPrinter Where "RemoteServer" is the name of the server which shares the printer to the Windows domain and MyPrinter is the NetBIOS name of the printer itself, i.e. the printer name when it is shared in the local network. Warning: Incoming Faxes with unknown recipient number (that is addressed to numbers which are not in the IAS database) will be printed only if a default "catch all" user is defined. Note: Since IAS you can test the access rights to a network printer from the Manage Service -> Print and Storage page. Storing Incoming Faxes StoneFax can store incoming faxes to a local or network folder. It can also create a folder for each IAS user. Warning: No check is made on disk usage or disk quota Warning: Old faxes are not deleted from these folders 1. Select the users who will have their fax stored You can select which users will have their incoming faxes stored by ticking the "Store to Folder" checkbox field in IAS User Management page. If you want to set the field for a large number of users, you may export users' data to a CSV file, edit it with MS excel, and import the data again. 2. (optionally) choose the storage root folder Log onto the Application Suite server and edit this configuration file: c:\program Files\StonevoiceAS\Apps\StoneFax\Server\System\Stonefax.ini Under the [Settings] section add the following line: CopyRootFolder=c:\FaxBackup Where c:\faxbackup is the directory under which the incoming faxes will be stored. StoneFax will create a subfolder for each IAS user. By default, StoneFax uses this directory: c:\program Files\StonevoiceAS\Apps\StoneFax\Server\System\Stored_Faxes 3. Choose a different storage path for some users You can override the default storage path for a user by entering an ABSOLUTE directory path in the "Storage Folder" field. E.g. c:\sales\jsmith Administration Guide 26/73 Advanced Configuration

29 4. Configure network access credentials Go to the Manage Service -> Print and Storage page. Here you can set the credentials of a valid domain user to be used when accessing the network folders. You can also test the access rights to a network folder. Changing the name of the stored faxes An advanced setting controls the way the fax are renamed before storing them to target folder. If you need to change it, log onto the Application Suite server and edit this configuration file: c:\program Files\StonevoiceAS\Apps\StoneFax\Server\System\Stonefax.ini Under the [Settings] section add the following line: RenameStoredFaxAs = Fax{date}{time}-{uniqueid}{rnd3} This is the default value. The available options are: Field {uniqueid} {username} Meaning A unique identifier automatically generated by the Microsoft Fax Service The username (in the Application Suite) of the recipient of the incoming fax {callednumber} The called number for the incoming fax as signaled by the PBX {callingnumber} The calling number {date} {shortdate} {time} {pages} {size} {serial} {rnd3} {rnd4} {rnd5} Receiving date in this format: "yyyymmdd" Receiving date in this format: "yymmdd" Receiving time in this format: "hhmm" Number of pages of the fax Size of the fax file in bytes Serial number, equivalent to the number of received faxes Three digits long random number Four digits long random number Five digits long random number Changing the name of the attachment An advanced setting controls the way the fax are renamed before sending them as attachment. The file extension cannot be changed. The change will affect the name of the document that will be printed if the Print per user feature is enabled. If you need to change the file name, log onto the Application Suite server and edit this configuration file: c:\program Files\StonevoiceAS\Apps\StoneFax\Server\System\Stonefax.ini Under the [Settings] section add the following line: NotifyAttachmentFormat=Fax-{date}-{time}_form_{callingnumber}_to_{callednumber} This is the default value. The available options are: Field {uniqueid} {username} Meaning A unique identifier automatically generated by the Microsoft Fax Service for the local machine The username (in the Application Suite) of the recipient of the incoming fax {callednumber} The called number for the incoming fax as signaled by the PBX {callingnumber} The calling number {date} {shortdate} Receiving date in this format: "yyyymmdd" Receiving date in this format: "yymmdd" Administration Guide 27/73 Advanced Configuration

30 {time} {pages} {size} Receiving time in this format: "hhmm" Number of pages of the fax Size of the fax file in bytes {serial} Serial number, equivalent to the number of received faxes You can enter other characters but they must compatible with the file system conventions. For instance, characters like *, \ or : are not allowed. Advanced Fax Routing Different calling numbers for outgoing faxes (ANI) StoneFax puts a different calling number in the h.323 or SIP signaling of each user's outgoing fax so that billing programs such as Imagicle Imagicle Billing will be able to correctly track the cost of each fax. If the recipient uses a traditional fax, he / she will see the callers' number on the display. If the user's "Offnet Fax number" is not blank, this E.164 number will be put in the signaling as CALLER number if ANI signaling is enabled. If it is blank, the user's "Fax number" will be used as caller number. On-net and Off-net faxes Outgoing faxes reaching their destination through the PSTN or the WAN are called OFF-NET faxes. Faxes sent to other StoneFax users (loopback) or to fax devices connected to the same network (usually traditional fax machines connected through ATA) are called ON-NET faxes. By default, StoneFax considers all outgoing faxes to be off-net except the ones sent to other StoneFax users. There is a second Network Routing type you can choose: "Both external and internal faxes". If you choose this routing strategy, you'll have to specify a prefix (e.g. "0"). You can enter this prefix in the "Off-net pattern" field. All the faxes beginning with that prefix will be considered off-net All the others will be considered on-net Differences between On-net and Off-net faxes The distinction between On-net and Off-net faxes affects the ANI, i.e. the calling number which will be signaled to the PBX. For On-net faxes, the ANI will always be the user's "Fax Number" For Off-net faxes, the ANI will be the user's "Offnet Fax Number". If this field is blank, the "Fax Number" will be used The distinction between On-net and Off-net faxes also affects the "Per-User" PBX Routing type: For On-net faxes, no prefix will be added to the called number For Off-net faxes, the user's "Fax Routing Prefix" will be added to the called number Note that the "Global" PBX routing type is unaffected by the distinction between On-net and Off-net faxes. Per User routing - Fax routing based on caller Suppose your company has two offices with two gateways and one StoneFax. For billing purposes you want the faxes sent by the people working in office A to reach the PSTN through gateway A and the ones from office B through gateway B. In the Routing Parameters box select the "Per User" PBX routing type. Administration Guide 28/73 Advanced Configuration

31 Edit the users' properties and set the values of the "Fax Routing Prefix" field so that users form office A have (e.g.) 11 and users from office B have 22. Those prefixes will be added to the fax recipient number. It the original called number is , the PBX will receive if the fax is sent form a person working in office A, if the fax is sent form a person working in office B. Then create a rule on the PBX that strips the first two digits and sends the call to the right voice gateway. If you deal directly with the gateway you can define IP routes in StoneFax that match 11 and 22 as described in the Multiple Routes section. This option will affect Web To Fax and To Fax only. User-based routing is not supported for Print To Fax. To Fax: specifying recipient numbers in the "To:" field Effective from version , StoneFax supports sending specifying the called number in the "To:" field like this: TO: @stonefax.yourdomain.com The parameters specified in the "Subject" field will be taken into account as usual. To be able to send faxes this way, a special configuration on your server is need. 1. On the DNS, add a third level domain, e.g. StoneFax.Yourdomain.com 2. On the server, create the reserved StoneFax account as usual. E.g. stonefax@yourdomain.com 3. On the server, create a "Catch All" account for that domain which redirects all the messages to the reserved StoneFax account (E.G. *@Stonefax.yourdomain.com -> StoneFax@yourdomain.com) Multiple recipients are not supported when you specify the called number in the "To:" field. Administration Guide 29/73 Advanced Configuration

32 Solution-specific Configuration Alice Corporate In the "Manage Service", "Ip Routes" web page configure the following parameters. Protocol: SIP Negotiation: Allow G.711 for outgoing faxes Network routing type: Both offnet and on-net Off-net pattern: Enter the common prefix to reach the PSTN PBX Routing Type: Per user Edit the default route so that it points to the PBX. In the user's management configure the "Fax Routing Prefix" and "Fax Off-net Number" as required. Impresa semplice In the "Manage Service", "Ip Routes" web page configure the following parameters: Protocol: SIP Negotiation: Allow G.711 for outgoing faxes, Disable T.38 for incoming faxes Network routing type: Extenal (offnet) faxes only PBX Routing Type: Global Prefix to the called number: enter 0 if needed to reach the PSTN Administration Guide 30/73 Solution-specific Configuration

33 Edit the default route so that it points to the PBX. In the user's management configure "Fax Off-net Number" as required. Unigate - FastWeb In the "Manage Service", "Ip Routes" web page, configure the following parameters: Protocol: SIP Negotiation: No selection (Allow G.711 UNCHECKED and Disable T.38 UNCHECKED) Network routing type: External (offnet) faxes only PBX Routing Type: Global Prefix to the called number: enter 0 if needed to reach the PSTN Administration Guide 31/73 Solution-specific Configuration

34 Troubleshooting StoneFax web interface offers integrated diagnostic features. To test outgoing faxes: Log onto the web interface as a user with privilege level 10 on StoneFax and on User Management. Do not use the main administrator, who is not allowed to send and receive faxes, since it does not have a full profile. Try to send a fax through the web interface. Click on "global outbox" and check the error description. Detailed error reference is attached to this article. Administration Guide 32/73 Troubleshooting

35 Product Configuration This section will lead you to configure to Fax and Fax to , which are the main StoneFax features. Web to fax shares the same configuration. You will also learn how to configure basic routing for outgoing fax. It is strongly recommended you go through the following steps, before moving to Print-to-Fax and advanced configuration: Create a IAS user for each person entitled to send or receive faxes with StoneFax Configure outgoing fax routing Customize cover pages Users Management Basic User Configuration You should create a IAS user for each person that you want to allowed to send or receive a fax with StoneFax. You could also create group fax numbers, or receive all the faxes on a single mailbox, buth those tasks are described in the advanced configuration. These are the fields you must fill in the Users Management for each user who needs to send/receive faxes: Fax number: this enables the personal incoming fax for each user (if DID - Direct Inward Dial - is available by TELCO * ), in order to let the fax reach the user directly, so it must match exactly the number received by the Voice gateway. Enable Receive: to enable the user to receive faxes. If this is set to "True", the faxes addressed to the user's fax number (403 in our example) will be available to him/her from the Inbox web page. If this field is set to "False", the fax will be received anyway but forwarded to the default user (if defined). Enable Send: this gives the user the sending capabilities. Set to "True" to enable the user to send faxes. A user who is not enabled to send faxes but still tries to use the To Fax or the Web To Fax features will receive a message stating that the feature is not enabled for him/her Enable Fax To a field to activate the notification of a received fax, which causes the faxes addressed to that user (403) to be forwarded to his/her mailbox, specified in the Fax2 address field. The user can also receive a copy of the fax attached to the if you enter "True" in the Fax To Attach Fax textbox Attach Fax: this is to receive a copy of the fax together with the notification * If you don't have DID and only one fax number is available, this procedure is still useful, as you have a simpler situation with 1 user only (the company fax). To know how to edit the user's fields please refer to the IAS Configuration, User Management section. Users' Permissions User's permission control both the ability to send and receive faxes and the access to the Web To Fax feature. StoneFax can be enabled or disabled per user. In order to enable fax for a given user (in our example the user "Test"), you need to enable the user to access the StoneFax menu in the tree view of the Application Suite web access page. You can do this by selecting the "User permissions" icon from the Main->User Management link. You need to specify at least level 2 to enable fax operation to that user. If you like to give complete fax service control to that user, specify level 10. You do not need to change the access level for each user. Just set the defaults and it will be inherited by all (level 2 it the default). Then you can set the differences. See IAS Configuration, User Management, Setting user permissions. Note: you also have to enable incoming and outgoing faxes globally as a service. Please refer to the StoneFax Administrative Configuration section. User Preferences Administration Guide 33/73 Product Configuration

36 The users with permission level 2 or higher will be able to change some preference through the web interface: enable or disable fax to , the fax2 destination address, and if the fax will be attached to the notification. Fax Users List Configuration Example Suppose you have a public pool of numbers like xxx. This means a DID (Direct Inward Dial) with one thousand available numbers (from to ). You have reserved 3xx numbers for the phone extensions of the users You will now reserve 4xx numbers for the related fax extensions Then we will create a user to test fax features with the following parameters: Name and Surname: Christian Bianchi Phone number: 303 Fax number: 403 Fax2 address: christian.bianchi@company.com Enable receive: true Enable send: true You have the IAS machine with StoneFax installed on with this IP address: You have a company server POP3/SMTP or IMAP which allows sending through SMTP without authentication. On this server, StoneFax has a reserved POP3 or IMAP account with the following parameters: address: fax@company.com Username: stone Password: stone Note: If you don't have DID and only one fax number is available, this procedure is still useful, as you have a simpler situation with 1 user only (the company fax). If you want to assign the same number to both voice and fax (for each user) or if you have only one public number for both company telephone and company fax, you can use the IVR feature of Imagicle Application Suite in order to provide an automated voice response to choose between voice and fax. StoneFax Administrative Configuration To configure StoneFax click on the "Manage Service" link on the menu. This link is available to StoneFax administrators. Outgoing Faxes Configuration - POP3/IMAP parameters Select the "Set" button near "Outgoing faxes (POP3)" to open the "Set Outgoing Faxes Parameters" page. Here flag the "Enable Outgoing Faxes" checkbox to enable the To Fax feature, so that the authorized users will be able to send faxes directly through their client. Then specify the pop3 account reserved to and test the parameters. Note that clicking the "Test" Button also saves the configuration. You can then specify the polling interval used to check s by the ToFax module. The recommended setting is 20 seconds. All the mail messages are downloaded at every check. For this reason, using values lesser than 5 seconds will cause an useless CPU load. The actual protocol to be used for connection is detected from the Port parameter. Enter: 110 for POP3 995 for SSL-POP3 143 for IMAP 993 for SSL-IMAP Administration Guide 34/73 Product Configuration

37 Incoming Faxes Configuration - SMTP parameters From the "Manage Service" page press the "Set" button near "Incoming faxes (SMTP)". Here you can set the following parameters: Enable Incoming Faxes: checkbox to globally enable or disable incoming faxes Fax attachment Format: this is the file type for ToFax attachment. You can choose between TIF and PDF. See below Enable Return Receipt: if this option is enabled, a receipt is sent by to the sending user when a fax is successfully sent or all the retries have expired Enable Fax Enqueued Receipt: if this option is enabled, whenever a fax is added to the outgoing queue a receipt is sent to the sending user Notify Failed Incoming Calls: this option is meant for debugging. When an incoming fax has been notified by the PBX but not enough data is received, an notification is sent to the fax recipient. By default, a fax without body is simply ignored You also have to specify the STMP parameters for the StoneFax account. Enable Authentication if your SMTP server requires it to relay s, and test the parameters. Note that clicking the "Test" Button also saves the configuration. The SMTP account must be reserved for exclusive use by StoneFax. Warning: in the From address do not enter the same account you used in the POP3 configuration. Doing so can lead to infinite loops if StoneFax tries to send a fax to wrong addresses or to people who set an out-of-office autoreply message. Selecting a different protocol Effective from IAS , StoneFax supports Secure SMTP. It also integrates a failsafe mechanism to resend Fax To Mail messages should the connection with the mail server fail. For a detailed description of how to configure those features, please check the shared system parameters chapter in the Common Configuration section of this guide. Selecting an attachment format for To Fax Incoming faxes can be forwarded to the users' mail boxes either in TIF or PDF format. You do not need to restart StoneFax for the change to be applied. If you enable incoming fax storage, the format of the stored documents will be the same as the ones sent by . The conversion to PDF format for incoming faxes is performed by an internal library - there is no need to install external programs to have this feature. Supported File Types To Fax and Web To Fax load documents on the server and convert them to fax format (black and white Tiff G4). StoneFax is able to convert to fax these file types without installing any third party application: Office documents:.doc,.docx,.xls,.xlsx Standard documents:.txt,.rtf Images:.bmp, png,.jpg/.jpeg,.tif/.tiff (single page and b/w multipage) Adobe:.PDF To enable additional file types, please refer to the Advanced Configuration section. Reference number Administration Guide 35/73 Product Configuration

38 Stonefax assigns a unique reference number to each fax it receives or sends. A small banner with that number is impressed on the top of each fax page. The number can also be used to search for the fax in the web interface through the inbox and outbox pages. The default format for the reference number is like this: i.e. the current year followed by a dot and a sequential number padded on 8 digits. The number is reset to 0 every year. This format is not suitable for cluster installations. If you need to edit the format of the reference number, please ask Imagicle Technical Support. Basic Routing for Outgoing Faxes Voip Routes Configuration Voip configuration can be controlled through the "IP Routes" page. From the Manage System page, click the "Manage" link next to "IP ROUTES". WARNING: you have to stop and restart the StoneFax service from the web interface after any change done in this page. Telephony Protocol and Negotiation Here you can choose between SIP and h.323. Adjust your PBX configuration accordingly. The two options on negotiation ("Allow g.711 for outgoing faxes" and "Disable t.38 for incoming faxes") are to be left unchecked for most telephony systems. Please check the PBX configuration section for additional information. Default Route By default, StoneFax routes all outgoing faxes to one IP address. This is called the Default Route, and should be the IP address of the PBX or Voice Gateway enabled to send the faxes. Warning: If the Default Route is not properly configured, StoneFax will not work. StoneFax t38 engine can route the outgoing fax calls to many different IP address. Each of these addresses is a physical device which can be a PBX or a Voice Gateway supporting t.38 or g.711 faxes. Multiple routes and Least Cost Routing StoneFax can manage multiple routes, i.e. multiple Voice Gateways or PBX, based on the first digits of the CALLED number. E.g. you can configure it so that all the outgoing fax calls that have a recipient's telephone number beginning by 06 are routed to a specific gateway. The faxes that do not match this rule will be routed to the Default Route. In the "Set IP Routes" dialog, just enter the prefix and the IP and click "Add". Fallback Routes for high availability You can add the same route multiple times associated with different IP addresses. StoneFax will try to route outgoing faxes towards the first destination. If the routing fails, it will try the next one. When no more IP addresses associated to the same prefix are found, the call is sent to the default route. Adding a prefixes to outgoing faxes Administration Guide 36/73 Product Configuration

39 Stonefax can add a prefix to outgoing fax numbers (for LCR or any other aim) through the Ip Routes Page. In the Routing Parameters box select the "Global" PBX routing type, enter the prefix and press "Save". This parameter will affect only off-net outgoing faxes, see below. This option will affect Print To Fax, Web To Fax and To Fax. Network Routing Type Set this option on "External only". If you want to send faxes form StoneFax to internal ATAs, please refer to the advanced configuration chapter. Fax Service Configuration To access to this dialog, start StoneFax and click the "Set" button next to "Service Configuration" on the "Application Settings" page. Various fax service parameters can be configured: The number of times that StoneFax will try to send a fax The time span between retries The maximum number of fax that can be sent at the same time. Note that this number cannot be greater than the number of ports you are licensed to use. Reserving Fax Ports for Incoming Faxes If your company usually has more incoming fax than the outgoing, you may want to reserve some lines for receiving. Say that you have 12 ports. You may set the "Max Concurrent Outgoing Faxes" value to 8. This way, a minimum of 4 ports will be always available to incoming fax calls. If you have no outgoing faxes, then you could receive up to 12 faxes at the same time. Company Info The values specified in this dialog will be showed on all the cover pages. The TSID will override the calling number on the small banner put on the top of each fax page. Remember to also enter a valid Fax Administrator address, to which any problem or significant fax event will be notified. Data Retention In this section it is possible to specify values for fax data retention. It is possible to both configure automatic faxes and call details records deletion from Inbox/Outobox in case they are older than a defined number of days, specifying the Maximum lifetime (in days) of historical data. That is, older data will be periodically deleted. NOTE. Setting one of these two parameters to zero (0) disables faxes/call details records automatic deletion. NOTE. The "Delete fax call details records older than (days)" setting may impact on the database size. Administration Guide 37/73 Product Configuration

40 Cover Pages The first page which is automatically added to each fax is called Cover Page. Its purpose is to display fax information such as the caller number, the called name, and so on. Using Cover Pages When the user sends a fax by the Web To Fax feature, he or she can choose the name of the cover page to be put before the fax by clicking on a drop-down list in the "Fax Body" section. When a user sends a fax through , the cover page file is selected based on the "Fax: cover page name" user field. Enter the cover page file name without extension. If this field is blank the default cover page will be used (see below). Managing Cover Pages The available cover pages are cover files (*.cov) stored in a folder on the server. For Windows Server 2003 the location is: c:\documents and Settings\All Users\Application Data\Microsoft\Windows NT\MSFax\Common Coverpages For Windows Server 2008: c:\progamdata\microsoft\windows NT\MSFax\Common Coverpages\ Just add a cover page file in this directory and the users will be able to use it in their faxes. Note: some Windows 2008 editions have subdirectories for localized cover pages. These will affect Print To Fax only. To localize you cover pages in a multi-language installation please see below. You can edit a cover page file by double-clicking on it. Warning: on Windows 2008 the.cov extension may not be associated with the cover editor. If you double click the cover page file and windows asks you the program to use, locate FXSCOVER.exe in the Windows\System32 folder. Or run "Windows Fax and Scan" on the Application Suite server. If you delete all the cover files, the feature will be disabled and the users won't see the drop-down list with the names of the cover pages anymore. Administration Guide 38/73 Product Configuration

41 Default cover page The default cover page for -To-Fax and Web-To-Fax modes is NOCALLEDNUM.COV. When StoneFax sends a fax through the To Fax feature, it uses by default the cover page. You can edit it as you wish. If you delete the file, no cover page will be put before the faxes. Localized cover pages In a multi language environment you may want the same cover page to be available in different languages and to be selected based on the sender user's language. Set the user language prefix in the User Management page Prepare one copy of the.cov file for each language in the root cover pages folder Name the files like this: <language prefix><underscore><cover page name>.cov For example: en_urgent.cov, it_urgent.cov In the "Fax: cover page name" user field enter the name without prefix. E.g. "urgent.cov" Administration Guide 39/73 Product Configuration

42 Product Integration API Overview This section describes the REST API that can be used to integrate StoneFax and third party systems, making them capable to automate fax-related activities. Basic Authentication The REST API identifies its user with HTTP Basic Authentication. That is, if a function requires authentication, then it requires the Authorization HTTP header, which must be as follows: Authorization: Basic <userpasswordbase64> where <userpasswordbase64> is the base64 encoding of <user>:<password>. For instance, suppose you need to call a function with user="myuser" and password="mypassword". You need to base64-encode the string "myuser:mypassword", which is "bxl1c2vyom15cgfzc3dvcmq=", obtaining the following HTTP header: Authorization: Basic bxl1c2vyom15cgfzc3dvcmq= Administration Guide 40/73 Product Integration API

43 Submit Fax Submits a fax job, in order to send one or more documents to one or more recipients. Resource URL POST fw/apps/stonefax/webapi/faxes/outbound Resource Information Request Content-Type: multipart/form-data Response Content-Type: application/json Requires authentication: Yes URL Parameters None Request body The request body is a multipart/form-data containing a part that describes the submit information and as many parts as the attachments you want to send along the fax. The submit information part must be as follows: Content-Type: application/json Content-Disposition: form-data; name=jsondata The content of this part must be a JSON with the following model: Fax Name Type Required Description Default Example subject string optional The subject of the fax null "The fax subject" coverpagename string optional recipients Recipient[] required The name of the cover page to use (not including the COV file extension). If specified, it must match the name of an existing cove page. If the specified coverpage does not exists, the fax will be sent without any coverpage. The recipients of the fax. It must contain at least one recipient. See below for the Recipient data structure details. sendasusername string optional The username to use as the fax sender. Level 2 users: can only send as the fax group they belong to Level 6 users: like level 2 users null [] null "BusinessCover" "usertoimpersonate" Administration Guide 41/73 Submit Fax

44 Level 10 users: can send as any valid Stonefax user If not specified, the sender will be the user invoking this method. notifyby bool optional True if you want to receive notifications about the transmission status. False otherwise false true notification address string optional Use this parameter to specify a recipient address for the transmission report , different from the sending user address. If not specified, the sending user address will be used. This parameter is ignored if notifyby =false null "mailfornotifications@domain.com" speedydirectoryname string optional The name of an existing Speedy directory. Use this parameter to send the fax to every fax contact contained of the Speedy directory (fax multicast). null "directory1" body string optional customfields CustomField[] optional Such contacts will be additional recipients respect to the ones specified by the Recipients[] array. The fax body (plain text). If null or empty, then the rest of the multipart body must contain at least one valid attachment. A collection of custom fields. Every custom field specified must exist in StoneFax. See below for the customfields data strcture details. null [] "The fax body" Recipient Name Type Required Description Default Example firstname string optional Recipient's first name null "John" lastname string optional Recipient's last name null "Doe" faxnumber string required Recipient's fax number null "123456" CustomField Name Type Required Description Default Example name string required The name of the custom field null "field1" value string required The value of the custom field null "value1" Response 202 Accepted Administration Guide 42/73 Submit Fax

45 Fax has been submitted and is being processed. Response body Name Type Description ids string[] The submitted job ids (one per recipient) Error response 400 Bad Request Response body Name Type Description reason BadRequestReason The reason why the request has been rejected BadRequestReason Value SyntaxError InvalidRecipients InvalidAttachments InvalidDirectoryName Descritpion The JSON part contains a syntax error and cannot be parsed No recipients provided, or at least one of the recipients has no fax number The attachments supplied are invalid There is no such Speedy directory having the given name InvalidCustomFieldName There is no such StoneFax custom field having the given name InvalidUsername 401 Unauthorized No authentication provided Wrong credentials There is no such user having the given username 403 Forbidden Insufficient privilege level Outgoing faxes disabled for the user Outgoing faxes disabled for the impersonated user Examples Fax without attachments This example sends a fax only containing a body (i.e. without attachments) to two recipients, enabling notifications: POST fw/apps/stonefax/webapi/faxes/outbound Request body: --dcb45cdc-6ac3-46ad-8dea-892a d Content-Type: application/json; charset=utf-8 Content-Disposition: form-data; name=jsondata { "subject" : "My fax subject", "coverpagename" : "BusinessCover", "recipients" : [ { Administration Guide 43/73 Submit Fax

46 "firstname" : "John", "lastname" : "Doe", "faxnumber" : "123456" }, { "firstname" : "Jane", "lastname" : "Doe", "faxnumber" : "789012" } ], "notifyby " : "true", "body" : "Hello everybody!" } --dcb45cdc-6ac3-46ad-8dea-892a d The response body is: { } "ids":[ ] "IAS-N1_6a504a1d-12d6-44a7-a249-db6c4389f413_0", "IAS-N1_6a504a1d-12d6-44a7-a249-db6c4389f413_1" Fax with an attachment This other example sends a fax only with a body and an attachment to one recipient, enabling notifications: POST fw/apps/stonefax/webapi/faxes/outbound Request body: a96c a-8d63-69a230e8c5ea Content-Type: application/json; charset=utf-8 Content-Disposition: form-data; name=jsondata { "subject" : "My fax subject with an attachment", "coverpagename" : "BusinessCover", "recipients" : [ { "firstname" : "John", "lastname" : "Doe", "faxnumber" : "123456" } ], "notifyby " : "true", "body" : "Hello everybody! Please find the attachment." } a96c a-8d63-69a230e8c5ea Content-Disposition: form-data; name=""; filename="attachment.txt" Content-Type: text/plain Hi, I'm an attachment! a96c a-8d63-69a230e8c5ea The response body is: { } "ids":[ ] "IAS-N1_1322b0b2-696f-4b0e-807d-3707e9a5d1d2_0" Administration Guide 44/73 Submit Fax

47 Fax with multiple attachments If you need to send a fax with two or more attachments, all you have to do is add one form part for each additional attachment you need to send. In this example we send a fax with a body and two attachments: POST fw/apps/stonefax/webapi/faxes/outbound Request body: a96c a-8d63-69a230e8c5ea Content-Type: application/json; charset=utf-8 Content-Disposition: form-data; name=jsondata { "subject" : "My fax subject with an attachment", "coverpagename" : "BusinessCover", "recipients" : [ { "firstname" : "John", "lastname" : "Doe", "faxnumber" : "123456" } ], "notifyby " : "true", "body" : "Hello everybody! Please find the attachment." } a96c a-8d63-69a230e8c5ea Content-Disposition: form-data; name=""; filename="attachment1.txt" Content-Type: text/plain Hi, I'm an attachment! a96c a-8d63-69a230e8c5ea Content-Disposition: form-data; name=""; filename="attachment2.txt" Content-Type: text/plain Hi, I'm another attachment! a96c a-8d63-69a230e8c5ea The response body is: { } "ids":[ ] "IAS-N1_1322b0b2-696f-4b0e-807d-3707e9a5d1d2_0" Administration Guide 45/73 Submit Fax

48 Get Outbound Fax Details Gets the details of an outbound fax identified by its id. Resource URL GET fw/apps/stonefax/webapi/faxes/outbound/{id} Resource Information Response Content-Type: application/json Requires authentication: Yes URL Parameters Name Type Required Description Default Example id string required The id of the fax null IAS-N1_d53957a4-c6fa-4a f32da47e6a58_0 Response 200 OK Fax info have been returned. Response body Response body is a JSON object representing outbound fax data: Name Type Description fax Fax The outbound fax data Fax Name Type Description faxid string The fax id username string The username of the user the fax belongs to subject string The fax subject recipient status Recipient[] The fax recipients Status The status of the fax. Possible values are: Completed Failed Queued InProgress Canceled detailedstatus string A more detailed version of the fax status numberofpages int The number of fax pages servername string The name of the server that sent the fax submittime DateTime The time when the fax has been submitted to the system (ISO 8601) starttime DateTime The time when the fax sending was started (ISO 8601) endtime DateTime The time when the fax sending was concluded (ISO 8601) failurereason string The possible failure reason Administration Guide 46/73 Get Outbound Fax Details

49 Q931Code int The Q931 Code representing the possible failure reason size int Size in bytes of the fax Recipient Name Type Description name string The complete name (first and last name) of the recipient faxnumber string The recipient's fax number Error response 401 Unauthorized No authentication provided Wrong credentials 403 Forbidden Insufficient privilege level 404 NotFound No such outbound fax having the given id Examples GET fw/apps/stonefax/webapi/faxes/outbound/ias-n1_d53957a4-c6fa-4a f32da47e6a58_0 { } " type":"outboundfax:stonefax.faxes", "detailedstatus":null, "endtime":" t15:57: ", "faxid":"ias-n1_6a504a1d-12d6-44a7-a249-db6c4389f413_0", "numberofpages":1, "recipient":{ "faxnumber":"10002", "name":"mario Rossi" }, "servername":"ias-n1", "size":2897, "starttime":" t15:57: ", "status":"completed", "username":"user1", "Q931Code":null, "failurereason":null, "subject":"the fax subject", "submittime":" t15:56: " Administration Guide 47/73 Get Outbound Fax Details

50 Download outbound fax document Downloads an outbound fax document. Resource URL GET fw/apps/stonefax/webapi/faxes/outbound/{id}.{format} Resource Information Response Content-Type: depending on the value of {format} parameter: tiff: image/tiff pdf: application/pdf Requires authentication: Yes URL Parameters Name Type Required Description Default Example id string required The id of the fax to download null IAS-N1_d53957a4-c6fa-4a f32da47e6a58_0 format Format required Response 200 OK Fax has been downloaded. The format of the file to download. Must be one of the following: pdf tiff null pdf Error response 401 Unauthorized No authentication provided Wrong credentials 403 Forbidden Insufficient privilege level 404 NotFound No such fax outbound having the given id 410 Gone The fax exists, but related document has been removed Examples Administration Guide 48/73 Download outbound fax document

51 GET fw/apps/stonefax/webapi/faxes/outbound/ias-n1_d53957a4-c6fa-4a f32da47e6a58_0.tiff Administration Guide 49/73 Download outbound fax document

52 User Guides StoneFax User Guides Please download the user guide here. English Italiano Deutsch Francais Espanol User Guides 50/73 User Guides

53 FAQ and Solutions Issue with return receipt not being sent when sending fax through web interface (Application Suite Winter ) to version Application Suite Applies from Application Suite Description Users who are sending fax through the web interface, do not receive return receipts. In user management the user has no " " field filled, but only "Fax2 " field. You can check the issue in log file Var\Log\Stonefax.Core.Service\Stonefax.log looking for "mail without destination address". Solution If the Application Suite is configured to sync with an external source you need to sync also field " " with the source or use this query (SQL Management or SQL panel in billing admin page) to copy Fax2Mail field in the field: UPDATE [Users] SET user_ =user_pref_fax_mailinaddr WHERE ((user_ IS NULL) OR (user_ ='')) AND NOT ((user_pref_fax_mailinaddr IS NULL) OR (user_pref_fax_mailinaddr='')) Remember to change sync rule to keep the existing value for " " field like in the screenshot below and remember to fill that field manually every time you need to add a new user: If the users are not synchronized you can run this query (SQL Management or SQL panel in billing admin page) to copy Fax2Mail field in the field: FAQ and Solutions 51/73 FAQ and Solutions

54 UPDATE [Users] SET user_ =user_pref_fax_mailinaddr WHERE ((user_ IS NULL) OR (user_ ='')) AND NOT ((user FAQ and Solutions Issue with return receipt not being sent 52/73 when sending fax through web interface(application Suite Winter )

55 How to retrieve fax activity reports - understanding Stonefax reports Applies to: Stonefax Description: How to retrieve fax activity reports Solution: To build activity reports, StoneFax relies on standard Microsoft Fax Services. Inbox and Outbox reports are enabled by default; however the user may want to set higher detail. Check that activity logs are enabled, and set detail level, by opening the Microsoft Fax Service Manager. Click Start Programs Accessories Communications Fax Fax Service Manager and then right click Fax (local) on the right pane and choose Properties. Select the Activity Logging tab and check that logging is enabled. You can also enter the location in which the log files will be written. By default it is C:\Documents and Settings\All Users\Application Data\Microsoft\Windows NT\MSFax\ActivityLog Tick "Log incoming fax activity" and "Log outgoing fax activity". Then select Event Reports tab and move all the sliders to the right (High). File Format: The report files contain tab-delimited entries that can be viewed by standard analysis programs (for instance Ms Excel). The first line is a header with field names. The fields are: Inbox: Status Error Description Error Code Start Time End Time Device Queue File Size CSID TSID CallerID Routing Info Pages OutBox: Job ID Parent Job ID Submission Time Scheduled Status Error Description FAQ and Solutions 53/73 How to retrieve fax activity reports - understanding Stonefax reports

56 Error Code Start Time End Time Device Dialed Number CSID TSID Pages Total Pages Queue File Name Document File Size Retries Server Cover Page Cover Page Subject Cover Page Note User Name Sender Name Sender Fax Number Sender Company Sender Street Sender City Sender Zip Code Sender Country/Region Sender Title Sender Department Sender Office Sender Home Phone Sender Office Phone Sender Recipient Name Recipient Fax Number Recipient Company Recipient Street Recipient City Recipient Zip Code Recipient Country/Region Recipient Title Recipient Department Recipient Office Recipient Home Phone Recipient Office Phone Recipient Billing Code FAQ and Solutions 54/73 How to retrieve fax activity reports - understanding Stonefax reports

57 Several incoming faxes can be found in Windows Fax and Scanner Console but not in Stonefax. Fxssvc.exe error on dll as INETCOMM.dll in the event viewer. Applies to: StoneFax installed on Windows Server Description: Those are symptoms typical of an unstable system: out of 50 received faxes, I get a notification for 20 and Stonefax sends those to my address. Stonefax seems not to receive the others although the system received them as they can be found in the Windows Fax and Scanner console. Cause: Installing a Fax Server on Windows Server 2008 with fax routing by , you may run into this issue, due to a BUG MICROSOFT. Furthermore it's hardly detectable, not documented and not public released.the component having to forward the s has a bug in Windows Vista/Windows 2008: it sometimes crashes and fails to send the mail with the fax correctly. The only way to notice this problem is to analyze the Event Viewer logs; actually, the fxssvc.exe service crashes and restarts automatically. Furthermore this Fax routing component is sometimes randomly crashing, sometimes not. The error log is the following: Fax server windows server 2008 routing mail error: Faulting application fxssvc.exe, version , time stamp 0Ã , faulting module INETCOMM.dll_unloaded, version , time stamp 0x49e0378f, exception code 0xc , fault offset 0x6deec766, process id 0x69c, application start time 0x01ca9539baca13a2. The Fax Routing Extension 'Microsoft Routing Extension' encountered a problem and needed to close. Error Code: 0xC This error code indicates the cause of the error. A Windows Error Report was generated with full details about the problem. The Fax service will restart now Solution: In order to solve this issue, please install the Microsoft patch described in KB More information and patch download: You can find a copy of this patch on our FTP: ftp://ftp.imagicle.com/stonefax/windows6.0-kb x86.zip for X86 systems ftp://ftp.imagicle.com/stonefax/windows6.1-kb x64.zip for X64 systems (Username and password: imagicle) Several incoming FAQ and faxes Solutions can be found in Windows Fax and Scanner Console but 55/73 not in Stonefax. Fxssvc.exe error on dll as INETCOMM.dll in the event viewer.

58 Saving faxes in structured folders Applies from Application Suite Description / Question: How to let Stonefax save incoming/outgoing faxes in structured folders on file system. Solution: If you want Stonefax save the received or sent faxes to a structured tree of folders, proceed as follows. Edit this configuration file with your favorite editor: <AppSuiteDir>\Apps\Stonefax\Server\System\StoneFax.ini Under [Settings] section verify the following parameters: CopyPathFormatIncoming and CopyPathFormatOutgoing. These parameters define how to save faxes: CopyPathFormatIncoming defines the full destination filename for incoming faxes CopyPathFormatOutgoing defines the full destination filename for outgoing faxes For example if we want to save all incoming/outgoing faxes with this structure: K:\BACKUP\2014\08\22\In\user_a\Fax_ _1504_From_ pdf K:\BACKUP\2014\08\22\Out\user_a\Fax_ _1504_To_ pdf... K:\BACKUP\2013\11\09\In\user_n\Fax_ _0957_From_ pdf K:\BACKUP\2013\11\09\Out\user_n\Fax_ _0932_To_ pdf Ensure the [Settings] section of the configuration file includes the following lines: [Settings] CopyPathFormatIncoming=K:\BACKUP\{date:yyyy}\{date:MM}\{date:dd}\In\{username}\Fax_{date}_{time}_From_{callingnumber} CopyPathFormatOutgoing=K:\BACKUP\{date:yyyy}\{date:MM}\{date:dd}\Out\{username}\Fax_{date}_{time}_To_{callednumber} ; Set the archive fax format (1=TIFF, 2=PDF) ArchiveFileFormat=2 Placeholders You can use the following placeholders as part of your file names or folder names. {serial} {callingnumber} {callednumber} {remotenumber} {localnumber} {username} {direction} {status} {date:yyyymmdd} Unique identifier (serial number) of the fax Calling fax number. Called fax number. Remote fax number, i.e. sender for incoming faxes; destination for outgoing faxes. Local fax number, i.e. the internal number and it is destination for incoming faxes; sender for outgoing faxes. Application username of the sender or destination of the fax For incoming fax it is "In". For outgoing faxes it is "Out". Applies to outgoing faxes only. It can be "OK" or "KO". FAQ and Solutions 56/73 Saving faxes in structured folders

59 yyyy: Year (4 num) yy: Yes (2 mum) MM: Month dd: Day HH: Hours mm: Minutes ss: Seconds {time} Time of the day (start of transmission/reception), expressed in the "hhmm" format. Please restart StoneFax from the web interface after changing this configuration file. FAQ and Solutions 57/73 Solution:

60 Unable to receive faxes on Windows Server 2012 R2 with fxssvc crashing in the module fxst30.dll Error Code: 0xC to version Application Suite 201x (any version) Applies to Stonefax on Windows Server 2012 R2 Description You may notice in Stonefax you are unable to receive faxes; if you keep an eye on the server while it is receiving a fax you can see that the call is answered and it attempts to receive the Fax, but then the service crashes and starts itself up again. You may notice the following events in the application event log: Event ID: 1001 Event Name: APPCRASH Problem signature: P1: fxssvc.exe P2: P3: 5215e627 P4: fxst30.dll P5: P6: 5215eb1a P7: c P8: And also: Event ID: 1000 Description: Faulting application name: fxssvc.exe, version: , time stamp: 0x5215e627 Faulting module name: fxst30.dll, version: , time stamp: 0x5215eb1a Exception code: 0xc Fault offset: 0Ã Faulting process id: 0x1dbc Faulting application start time: 0x01cf75b8c Faulting application path: C:\Windows\system32\fxssvc.exe Faulting module path: C:\Windows\system32\fxst30.dll And finally: The Fax Service Provider 'Microsoft Modem Device Provider' encountered a problem and needed to close. Error Code: 0xC This error code indicates the cause of the error. A Windows Error Report was generated with full details about the problem. The Fax service will restart now. Cause Microsoft bug on FXST30.DLL FAQ and Solutions Unable to receive faxes on Windows Server /73 R2 with fxssvc crashing in the module fxst30.dll Error Code: 0xC

61 Solution Make all Windows Updates, reboot and check the FXST30.DLL version. The buggy version of the dll is After installation of the roll-up ( ), the version of FXST30.dll should be If unable to update it with Windows Updates you can also force its replacement. Use the file attached (unzip the file and rename it FXST30.DLL) Use Unlocker tool to remove the original FXST30.DLL and replace it Reboot the services/the server and try again. FAQ and Solutions Unable to receive faxes on Windows Server /73 R2 with fxssvc crashing in the module fxst30.dll Error Code: 0xC

62 Enable G.729 signaling for Stonefax Applies to: All IAS versions. Description: Enable G.729A codec capability for Stonefax. How-to: In order to enable G.729A signaling for Stonefax please proceed as follow: 1) Open the file <StonevoiceAS>\Apps\StoneFax\Server\System\StoneFax.ini 2) Add one of the following parameters to the section [Impostazioni]: a) To enable only G.729A as audio codec: T38_LOG_OPTIONS= --sip-audio G.729 b) To enable both G.711 and G.729A as audio codecs: T38_LOG_OPTIONS= --sip-audio G.711-Alaw-64k --sip-audio G.711-ulaw-64k --sip-audio G.729 The row should appear similar to the following: [Impostazioni] T38_LOG_OPTIONS= --sip-audio G.711-Alaw-64k --sip-audio G.711-ulaw-64k --sip-audio G.729 3) Save and close the StoneFax.ini file 4) Stop and Start the Stonefax service in the page Fax Server Manage Service [Stop/Start] 5) Make a test IMPORTANT NOTE: G.729 cannot be used to send/receive faxes in voice passthrough mode. It can be enabled in certain scenarios only to permit the initial call hadshake with PBX or voice gateways. In facts, a voice call established in G.729 codec should immediately switch to a T.38 session to permit the proper fax transmission/reception. FAQ and Solutions 60/73 Enable G.729 signaling for Stonefax

63 How to modify mail notification templates for admin and users in Stonefax application Applies from Application Suite Applies to: Application suite Description: How to modify mail notification templates for admin and users in Stonefax applications How-to: Modify default template globally: 1. Open the language (en-english, it-italian, fr-french, ecc..) folder in <StonevoiceAS>\Apps\StoneFax\Locale\ accordingly to the template language you need to modify 2. Make a copy of the template files: User.FaxIn.Template.txt ( template for incoming fax status) User.FaxOut.Template.txt ( template for outgoing fax status) Admin.FaxOut.Template.txt ( template for outgoing fax issues) Admin.Mail.Template.txt ( template for general fax issues) 3. Rename the copy with.user extension like the following User.FaxIn.Template.txt.user User.FaxOut.Template.txt.user Admin.FaxOut.Template.txt.user Admin.Mail.Template.txt.user Add images from an external source: In the same txt file add html tag <html> <body> <img id="logoid" src=" <body/> <html/> Example: [Section: PartiallyReceived_Subject] Fax partially received from (([FromNr])) [Section: PartiallyReceived_Body] <html> <body> <img id="logoid" src=" <br/> Stonefax received a fax for you on [Received]. The fax has been received partially because of an unexpected error during the fax transmission. Number of received pages: [Pages] Attachment file size: [Size] FAQ and Solutions How to modify 61/73mail notification templates for admin and users in Stonefax application

64 <body/> <html/> If you need to modify one of these templates for only a specific user please proceed as follow: 1. Create a new folder and rename it (es. mailtemplate1) in <StonevoiceAS>\Settings\Enterprise\Stonefax\MailNotificationTemplates 2. Open the language folder (en-english, it-italian, fr-french, ecc..) in <StonevoiceAS>\Apps\StoneFax\Locale 3. Copy the user-specific template files User.FaxIn.Template.txt and User.FaxOut.Template.txt 4. Paste in the new folder (mailtemplate1) these templates 5. Edit both files with your customizations 6. Open Web interface Admin User Management and modify the user you customized the template for setting Notifications preferred template = the folder name as specified above (mailtemplate1) and save. FAQ and Solutions How to modify 62/73mail notification templates for admin and users in Stonefax application

65 Stonefax status is undefined/stopped and won't start - Windows fax service crash with faulting module FXSTIFF.dll to version Application Suite Applies from Application Suite 201x (any version) Applies to Microsoft Windows Server 2008/2008 R2 and Microsoft Windows Server 2012/2012 R2 Description Stonefax is in the undefined or stopped status. Trying to start the service from WEB interface or rebooting the machine does not fix the problem. Windows event registry reports an error (Application folder) like the following one: The Fax Service encountered a problem and needed to close. Error Code: 0x This error code indicates the cause of the error. A Windows Error Report was generated with full details about the problem. The Fax service will restart now. Faulting application name: fxssvc.exe, version: , time stamp: 0x4ce7b339 Faulting module name: FXSTIFF.dll, version: , time stamp: 0x4ce7c672 Exception code: 0xc Fault offset: 0x c462 Faulting process id: 0x16c0 Faulting application start time: 0x01d105096a32fab8u Faulting application path: C:\Windows\system32\fxssvc.exe Faulting module path: C:\Windows\system32\FXSTIFF.dll Report Id: b4792b9c-70fc-11e5-a bcb1ef55a The Windows fax service crashes immediately, once started Cause The problem is due to a bug of Windows Fax Service and PaperSize Configuration Solution Run "regedit" in StoneFax server and move to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Print\Printers\StoneFax\PrinterDriverData FAQ and Solutions Stonefax status is undefined/stopped 63/73 and won't start - Windows fax service crash with faulting module FXSTIFF.dll

66 Take note of the configured number in the PaperSize field Go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Print\Printers\StoneFax\DsDriver Open "printmediasupported" field and count from the first one to the "PaperSizeNumber" line It has to be "A4" format. If it is different, you have to change "PaperSizeNumber" field to point to "A4" accordingly. Then follow this procedure: Stop Stonefax from WEB interface (if not already stopped) Rename the Windows fax service queue folder into a different name (for instance \_Queue ) This folder is normally located in: Windows 2008 & 2012: C:\ProgramData\Microsoft\Windows NT\MSFax\Queue Windows 2003: C:\Documents and Settings\All Users\Application Data\Microsoft\Windows NT\MSFax\Queue Re-create the \Queue folder (empty) in the same position Start Stonefax from Web interface FAQ and Solutions Stonefax status is undefined/stopped 64/73 and won't start - Windows fax service crash with faulting module FXSTIFF.dll

67 How to modify a cover in Stonefax Applies to: Stonefax Description: How to modify a cover on Stonefax Solution: When the user sends a fax by the Web To Fax feature, he or she can choose the name of the cover page to be put before the fax by clicking on a drop-down list in the "Fax Body" section. This is the list of the cover files (*.cov) located in the common cover pages directory of the server. Just add a cover page file in this directory and the users will be able to use it in their faxes. Depending on the OS, common cover pages directory can be either (in Windows 2003): C:\Documents and Settings\All Users\Application Data\Microsoft\Windows NT\MSFax\Common Coverpages or (Windows 2008 and more recent) C:\ProgramData\Microsoft\Windows NT\MSFax\Common Coverpages You can edit a cover page file by double-clicking on it in Windows Explorer (make sure.cov file type is associated with FXSCOVER.EXE app, available in "Windows\System32" folder. If you delete all the cover files, the feature will be disabled and the users won't see the drop-down list with the names of the cover pages anymore. Additionally, Imagicle Stonefax supports different fax covers and it possible for any user to select among his covers the one to be used each time when sending a fax. This is doable via jabber, web portal and . When sending through Jabber/Website it is possible to select the cover to be used via a drop down menu. When sending via it is applied the default cover page (NOCALLENDUM.COV). However, it is possible to specify which cover to be used, adding in the mail subject "CoverPage((URGENT.COV))", where "COVER-URGENT.COV" is the name of the selected cover page for the specific fax transmission. To add the required optional covers, per each User, Department or the entire Company, it is needed to create and add the relevant cover page(s) in specific paths, as follows: Disable Cover Page: Make a backup of the file <StonevoiceAS>\Apps\Stonefax\Server\System\Stonefax.ini Edit the file <StonevoiceAS>\Apps\Stonefax\Server\System\Stonefax.ini Under [Settings] add the following line: DefaultCoverPage=<coverpage.COV> Save file Restart the stonefax service User: Assuming user name starts with A: C:\Program Files (x86)\stonevoiceas\settings\users\a\<relevant user directory name>\coverpages\new-cover.cov Assuming user name starts with F: C:\Program Files (x86)\stonevoiceas\settings\users\f\<relevant user directory name>\coverpages\new-cover2.cov FAQ and Solutions 65/73 How to modify a cover in Stonefax

68 Department: Assuming department name starts with S: C:\Program Files (x86)\stonevoiceas\settings\departments\s\<relevant department directory name>\coverpages\new-cover4.cov Assuming department name starts with T: C:\Program Files (x86)\stonevoiceas\settings\departments\t\<relevant department directory name>\coverpages\new-cover5.cov FAQ and Solutions 66/73 How to modify a cover in Stonefax

69 How to change resolution and rendering method of faxes Applies to: Imagicle StoneFax (any version) Description: How to change resolution and rendering method of faxes for a result more in keeping with the customer's expectations How-to: Talking of fax quality we can act on two different parameters: the resolution and the rendering method. Resolution: this parameter can have two settings: 200x200 dpi or 200x100 dpi. To change this setting you should act on the stonefax printer like this: - Open the printers panel in Windows - Select Stonefax printer - Right click and select "Printing preferences" - Select the desired resolution using the "Image quality" parameter. Rendering: please proceed as follow: - Open file "Stonefax.config.xml" in the folder <StonevoiceAS>\apps\stonefax\settings - Change/add the key: <preference key="print.renderingmethod" value="bitonal" /> - Save and close the file - Restart the Stonefax service The value can be: - Normal: Best for images but not so good for text (medium transmission speed) - Bitonal: Best for text but not so good for images (fast transmission speed) - HiContrast : Good for text and images (low transmission speed) The default value is Normal. In case of fax with text and images that are not black, the result may be a fax not readable. It is possibly to modify Stonefax to increase the contrast proceeding in this way: - Open folder <StonevoiceAS>\Apps\Stonefax\Settings - Backup (copy/paste) the file "Stonefax.config.xml" - Open the file "Stonefax.config.xml" and change like follow: <configuration> <preference key="print.renderingmethod" value="bitonal" /> <preference key="print.gsextraparams" value="-dnopause -dbatch -dsafer -sdevice=tiffgray -r200" /> <preference key="print.enabletiffdither" value="false" /> </configuration> - Save and close the file. - Restart Stonefax service and test FAQ and Solutions 67/73 How to change resolution and rendering method of faxes

70 How to set fax rate / modem max speed in Stonefax Applies to: Imagicle StoneFax (any version). Description: How to set fax rate/max speed (in bps) of modems in Stonefax service for incoming/outgoing faxes How-to: 1. On the Stonefax server, run Registry Editor (regedit) 2. Go in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Fax\TAPIDevices 3. For every "Modem" folders change these parameters: - ModemRecvSpeeds (11 is default value = 14400bps) - ModemSendSpeeds (11 is default value = 14400bps) Value Meaning Possibly values are: 0 V.27 (2400 bps) 1 V.29 (7200/9600 bps) 2 V.27 (2400/4800 bps) 4 V.33 (12000/14400 bps) 8 V.17 (7200/9600/12000/14400 bps) To limit the speed at 9600 bps set the value to 3. â To limit the speed at 4800 bps set the value to 2. â To limit the speed at 2400 bps set the value to 0. â 4. Save and restart Stonefax service from web interface FAQ and Solutions 68/73 How to set fax rate / modem max speed in Stonefax