CS1000 SIP Integration with FACSys (Brooktrout SR140)

[klamb]

we are trying to get faxes coming through the CS1000 (rel 6.0) and route to a Fax server via SIP.

We have setup the trunks, etc and everything is working fine outbound (from server through CS1000). Incoming faxes are processed and routed to the Fax server who then sits on them and marks as unrouted.

Our server guys are telling us that they are unrouted because the incoming calls are being routed with the phone-context and the server only know what to do with the routing number.

Example from Fax Server log:
Routing digits 7411;phone-context=SYSTEMS.CS1000 Calling party number 1xxxxxxxxx;phone-context=44 [1]

I think this is normal operation but am up against it with the server guys - question is, can the CS1000 send the calls to the fax server without the phone-context field added??

Routing digits 7411 Calling party number 1xxxxxxxxx [1]

thanks in advance,
Kenny

 

[ndambrosio]

@KLamb

You might want to have your Fax Admin/Integrator check the version/service release of RightFax you're currently running. Open Text has a software fix for the Fax Server, the Open Text Software has an issue parsing the alternately formatted SIP invite. == Details below ==


Open Text Tracking Number:
RF-4240

Module:
Doc Transport

Description:
DNIS digits from Nortel CS 1000 SIP Invites are not parsed.

Resolution:

Modify Registry to parse Nortel DNIS

1. Open the Windows Registry Editor to the key HKLM\Software\RightFax\DocTransport\Transports\Brooktrout.
(x64: HKLM\Software\Wow6432Node\RightFax\DocTransport\Transports\Brooktrout)
2. Create a new REG_DWORD called CheckDNISForNortelRoutecode

3. Double-click the new REG_DWORD to edit it.

4. Set the value to 1 and click OK.

Reference the latest version/service release readme file for more information.

Good Luck, The SR140 is a major pain. Dialogic has done the bare minimum with regards to testing, internally and with a few end-users. Their support site states that it has been tested against the CS1000, however, it was never officially tested, certified and supported through the Avaya DevConnect program.

Have a good day!

Nick