MobilityManager 1.2 with FXO or BRI

[nyciscotech]

Does anyone know if MM 1.2 will work with FXO or BRI ports on a H.323 gateway?

I found the following bug which seems to indicate it was not corrected in the latest version. CSCsc10575

Thanks for any info

[pradeepde]

The H.323 GW is used for the "System Remote Access" feature. This gives the ability to call into a DID from the PSTN and be forwarded to the MobilityManager IVR. At this point the user will have the ability to dial a number on the PSTN as if they were making the call from their desk phone. They will also have several options to manage personal MobilityManager settings.

[nyciscotech]

Thanks for the response.

Will the users desk phone be able to forward to their cell phone over a FXO or BRI connection to the PSTN? According to the bug report, it seems the FXO port actually answers the outbound call before connecting to the PSTN so this is the reason for the bug. But I am wondering if this would still be an issue with BRI. Any thoughts?

Here is the bug report:

Symptoms:

Mobile Connect feature doesn't works if Remote Destination is connected through the FXO port of the H323 Gateway. Following is the outgoing call scenario

CMM ->CCM --> H323 -> FXO -> PSTN

The issue is observed due to analog port answering the call, before sending setup out to PSTN.

This results in Minimum Ring Timer getting invoked on MobilityManager as it receives the Alerting/Connect within 10ms.

Condition :

1. Configure a valid remote destination on CMM connected through the H323 FXO port to CCM.

2. Make a call from PSTN to Mobile Connect extension.

3. Remote destination doesn't receives the call and call is disconnected immediately.

Since the Alerting/Connect is received by CMM within 10 millisecs, CMM assumes that call is picked by Remote Destination's voice mail and disconnects immediately.

Workaround:

Recommending to use PRI for the PSTN calls.