Avaya CM No Longer Sending Caller-ID for Fax Machines Using Rightfax Server

[Louis87]

HI Everyone,

Someone could please provide some suggestions of troubleshooting steps for the below issue:

Would a list trace essential to start the verification correct?

CM Stations not sending caller # out when fax calls are made. Avaya is no longer sending call ID for fax machines using the Rightfax server (APPS49) which is integrated to the Session Manager. As well as fax machines that are on the Ericcson that are connected to the Avaya

Thank you so much in advance,

 

[kyle555]

So, rightfax-->sm-->cm-->PSTN (PRI? SIP?) and not sending CPN?

Is rightfax registering stations to SM or does it have a trunk to SM? If it's stations, you look in the public unknown table. If it's trunks, you'd look in the tandem table.

 

[Louis87]

Thank you for your reply kyle555.

Yes, you are correct, rightfax-->sm-->cm-->PSTN (SIP) and not sending CPN. Before it was working fine.
I checked the CM trunks, and it is showing two trunks, one for Righfax2017-SM1 and a second one named Rightfax2017-SM2.
It is being very complex because the issue can be in CM, RIghfax Server or System Manager. The Rightfax is integrated with SM. I will get a list trace tac (correct trunk), then maybe I can see if the problem is at CM, SM or Rightfax. If you have any further suggestion, please let me know.

Thank you

 

[AuraPS]

If you have the extn and correct SM SIP trunk/s in the Public unknown numbering (or private unknown numbering table) it should pass out the CLI in the FROM header on a SIP trace (CM will add a + prefix to a SIP trunk) this can be removed on SMGR if your not using the e.164 format.

A traceSM will show you if the CLI is going out and passed to the rightfax server or if 'anonymous' is appearing in the FROM header