Last updated on 20 March 2021
IMAP service cannot connect to Exchange Server - the token supplied to the function is invalid
The msXfax IMAP log will display the message "the token supplied to the function is invalid".
This means there is an issue with the server certificate which is used by the Exchange Server IMAP service(s).
DLMs are no longer used.
Also the classifications changed. eg: UNCLASSIFIED is gone.
In the msXfaxboot.ini edit the highlighted to allow the new classifications through the gateway.
All OFFICIAL:SENSITIVE, ACCESS=XXXXXXX will also be allowed.
The epm version string is not used to check outgoing EPM checks. it is used for generating EPM on emails created by msXfax.
General-EPM-Permitted-SEC-Classification-Fax-Pair-str=UNOFFICIAL>UNOFFICIAL,OFFICIAL>OFFICIAL,OFFICIAL:SENSITIVE>OFFICIAL:SENSITIVE
General-EPM-Permitted-DLM-Classification-Fax-Pair-str=FOR-OFFICIAL-USE-ONLY>FOR-OFFICIAL-USE-ONLY,SENSITIVE>SENSITIVE,SENSITIVE:LEGAL>SENSITIVE:LEGAL,SENSITIVE:PERSONAL>SENSITIVE:PERSONAL
General-EPM-Support-Email-str=support@agency.com.au
General-EPM-Support-Name-str=Agency Support
General-EPM-Support-Phone-str=+61 x xxxxxxxxx
General-EPM-User-Classification-URL-str=http://www.agency.com.au/agency_userclassification.htm
General-EPM-User-Marking-Url-str=http://www.agency.com.au/agency_usermarking.htm
General-EPM-Version-str=VER=2018.3
General-EPM-Process-XHeader-int=1
Upgrading a customer to msXfax build 28c which supports TLS 1.2 may result in the error message "The client and server cannot communicate because they do not possess a common algorithm"
This is because most likely that their exchange server is not configured to support TLS 1.2 eg Exchange 2010.
https://jaapwesselius.com/2018/10/05/exchange-2010-and-tls-1-2/
Microsoft dropped support for legacy TLS 1.0 and 1.1 in this release of Microsoft Exchange.
If you see a log entry in the msXfax IMAP log
Error : Unable to connected to Cloud Service none at <IP ADDRESS>
31Oct2019 11:23:41:157 : < INT-TXmsXfaxCloudFromImapINT > : < MsgRef: N/A > :Error : The connection to the server is not active
Then the issue is definitely with TLS support.
If the customer claims they have support for TLS 1.0 and 1.1 and are not getting the connection issue described above then you may want to get their exchange admin to activate server logging on their Exchange server to allow them to further diagnose their problems.
SBC platforms that can support an acceptable call set up rate, this parameter can be set to 1 so it keeps the TX service busier.
Recommended settings:
1. TXRX server because of this issue we you HAVE TO SET “Always respond to SIP options irrespective of state” to ensure that software does not send 503’s.
2. TX ONLY Server because of this issue you HAVE TO SET “Always respond to SIP options irrespective of state” to ensure that software does not send 503’s.
3. On a RX only Server you do not have to set the option and allow XCAPI to correctly report if the application level is listening.
Creating a trace:
Analyzing a trace for fax calls:
https://www.1300numbersaustralia.com.au/1300-number-routinghttps://www.1300numbersaustralia.com.au/1300-number-routing
Yes and it uses open standards for security of messaging.
IMAPSSL (TLS) is used to process messages from a mailbox by the fax server.
SMTPTLS is used to send Faxes and messages to Office 365.
Yes. The fax server can be configured and licensed to run in your AzureAWS type implementation.
You may have a software based SBC which runs in one of those environments also. Subject to which SBC is used, it is technically possible to use the software SBC to leverage telephony from that environment.
Fax is highly sensitive to jitter and latency so T.38 is required to provide reliability. However, it may be possible to use G.711 fax subject to how well the implementation is.
Yes and it uses open standards for security of messaging.
IMAPSSL (TLS) is used to process messages from a mailbox by the fax server.
SMTPTLS is used to send Faxes and messages to Office 365.
Yes subject to qualification and integration testing.
Comvergence Australia is an example of a qualified service provider.
Yes, to securely setup a fax server to use an external IP Telephony provider we recommend that IPSEC or an equivalent secure connection be established between your network and that of Comvergence. Comvergence also support Megaport connections.
Contact BNS Group support to confirm that the upgrade will not cause any problems.
BNS support will provide a link to the correct version of XCAPI.
When you do update XCAPI the server will need to be restarted. Snap shot the VM before applying any updates.
Dialogic® Brooktrout® SR140 Fax Software (SR140) licenses are tied to the system node ID (also called 'node lock') which is based on the host machine's MAC address. If this address changes for any reason, the license will become invalid and you will see a 'wrong host' error in the License Manager.
http://www.dialogic.com/support/helpweb/helpweb.aspx/2852/how_to_re_host_an_sr140_license/sr140
msXfax uses Dialogic Brooktrout SR140 SDK. Therefore the Node ID is VID which requires only the MAC address to be fixed. You can change the computer name without affecting your SR140 license.
http://www.bnsgroup.com.au/bns-group/helpdesk/admin/manage_knowledgebase.php?a=edit_article&id=135
For SBC platforms that can support an acceptable call set up rate, this parameter can be set to 1 so it keeps the TX service busier.