This topic provides some notes and workarounds for specific fax issues. The first issues relate to special configuration requirements, and the second set of issues relate to specific fax outcome codes.
The BladeWare profile is changed by first editing sip_rsm_profile.cfg, which is found in the Commetrex\otf\Config folder under Program Files or Program Files (x86). This file can be edited using Notepad or COPIAEDIT. However this is merely a text representation of the real Profile used by BladeWare:
 | After making a change in sip_rsm_profile.cfg, you must update the corresponding BladeWare Profile. The simplest way to do this is to stop both COPIAFACTS and the BladeWare service, then run OTFCONFIG and click the Update Profile button on the Protocols page. Then restart the BladeWare service and COPIAFACTS. |
Please take care when editing sip_rsm_profile.cfg, and do not make changes other than those below without advice from Copia support. Some changes to this file will prevent your BladeWare system from operating.
Configuration Issues
| SIP Port | The default SIP port of 5060 cannot be used with some fax service providers and switch types. To change the default port it is necessary to modify the profile entry near line 45 of the file: |
| Change the port number 5060 to that required by your provider, for example 5080. |
| Media Ports | The default media port range starting 49152 may not be suitable at some sites. To change the default starting port it is necessary to modify the profile entry near line 47 of the file: |
| | SIP_OTF_MediaPort = 49152; |
| Change the port number 49152 to that required for your network, for example 30000. The number of ports in the range is calculated from the CCR count entry on the Protocols page in OTFCONFIG (see also IP Requirements for FoIP). |
Fax Outcome Codes
| 7649 | (No Fax / Busy). This outcome can result from a late T.38 re-invite. It is known to affect connections with a Cisco CallManager but may also be encounted with other remote systems. If the re-invite is not issued by the remote end within 10 seconds of starting the call, then T.38 will either not be enabled or the call will fail with outcome code 7649. To resolve this issue, it is necessary to modify the profile entry (near line 55 of the file: |
| | SIP_OTF_HeuristicReinviteTimeout = 10000; |
| | Change the value from the default 10000 to 30000 (the value is in milliseconds). |
| 7649 | (No Fax / Busy) On some ATA connections, this error can be caused by a normal Busy condition, in which case it is returned immediately. It can be changed to outcome class B automatically if it occurs within a specified interval after the start of the call. |
| | If poor line quality is intermittent, an alternative is to set a minimum baud rate in the profile entries near lines 459 and/or 593 of the file: |
| FaxSender_OTF_T30MinRate = 2400 ; |
| FaxReceiver_OTF_T30MinRate = 2400 ; |
| Change the value 2400 to (for example) 9600. This will cause a retry when a lower speed cannot be negotiated. |
Important
| | After making a change in sip_rsm_profile.cfg, you must update the corresponding BladeWare Profile. The simplest way to do this is to stop both COPIAFACTS and the BladeWare service, then run OTFCONFIG and click the Update Profile button on the Protocols page. Then restart the BladeWare service and COPIAFACTS. |
