Norstar PRI - Call Forwarding Not Working

[sajeedlakhani]

Hello Everyone,

I have a Norstar MICS 7.1 w/XO PRI Lines. When I forward my extension 2223 to my cell phone 817.803.0000, and then call from outside the company and dial my extension, I hear "One Moment Please, followed by a ring and a busy tone for 1 second and then the call drops/disconnects.

If I call my extension 2223 from inside the company using my colleagues extension 2224 (2224 to 2223), then the call gets forwarded to my cell phone and my cell phone shows the Caller ID for my colleagues DID.

The call forwarding was working fine before until I recently had XO removed a temporary BTN Place Holder from the router so that my OLI could work. I am using NI-2 Protocol.

What can I do to make this work? Any ideas or help will be appreciated. Thanks!

 

[DBrewsky]

When you CFA (feature 4) on a PRI, the originating caller's CLID will forward as well. I believe since XO doesn't show the originating CLID as a valid number within your range, it has blocked the call.

A way to test is to set your PublicOLI on your set to your cell phone then try to make a call. It should be rejected. If it is, that's your problem. If it does work then call XO and have them trace the call to them via the forwarding, and they should be able to tell you why the call is being rejected.

--DB

http://support.csctech.us

 

[cook1082]

Have same issue with XO that is a dynamic PRI that shares voice and data was told by XO it needs to be switched to a SIP trunk for it to work. They are switching it soon and will see if it works for forwarding a call. This is on a BCM 3.7.

 

[sajeedlakhani]

Thanks for your prompt responses. I agree with both of you about XO blocking the caller's CLID as its not a valid number in my DID Block.

Any ideas or suggestions as to how I can get around it? I am trying to bug XO to see if there's a Modification that they can make.

In the mean time, any ideas / workaround(s) or help will be appreciated.

 

[peterbokunet]

XO might be able to stop the unknown CLID to the ANI of the trunk group (or a number you ask them). I've never looked at how to change the forwarded CLID as I considered it important info for the receiver. My solution was to change vendors to one who let me originat calls with any CLID -- a luxury I could afford at the time.

The SIP trunk suggestion is a little amusing because they probably do the same blocking there as with the PRI. You might have to include a diversion header in the SIP call setup. Depending on your capabilities and system that may be even more trouble. (I haven't had to do SIP with XO yet, ymmv)

 

[cook1082]

Like I said they said the fix was to make it a sip trunk. Still waiting on XO to change it.