|
Joined: Jun 2008
Posts: 60
Member
|
OP
Member
Joined: Jun 2008
Posts: 60 |
I have a Mitel 5000 running 6.0 SP1 PR3. We are working with TWC to send originating caller ID when forwarding or transferring to an outside line and I just wanted to be sure I'm looking at the right settings before calling them back. Currently, the destination phone sees our primary DID as the caller ID.
In our initial testing before calling TWC, I located the setting under System>Devices and Feature Codes>CO Trunk Groups>"PRI Trunk" named Propagate Original Caller ID. This was originally set to No. When we set this to Yes, external calls could no longer be forwarded or transferred to an outside line. Stations with dynamic extension enabled would ring the station but would no longer ring the external number.
This lead us to believe that TWC had not enabled the capability on our line to pass caller ID. After some back and forth between TWC support and our TWC account rep, they told us to make sure that our system was configured to send ISDN RNIE, and also configured to send 10 digit caller ID. Once we confirm those settings, they will enable the feature on the line.
I believe that "Propagate Original Caller ID" is the setting that would match "send ISDN RNIE". If someone can confirm that would be great.
I have not been able to locate any setting that designates the number of digits for caller ID. Any guidance on that setting would be appreciated.
|
|
|
Visit Atcom to get started with your new business VoIP phone system ASAP
Turn up is quick, painless, and can often be done same day.
Let us show you how to do VoIP right, resulting in crystal clear call quality and easy-to-use features that make everyone happy!
Proudly serving Canada from coast to coast.
|
|
|
Joined: Oct 2009
Posts: 109
Member
|
Member
Joined: Oct 2009
Posts: 109 |
The issue is that Time Warner (TW) will not allow a number to be sent out that is not on the native PRI. My company has been working with them for a long time now to resolve the issue which they report only happens on Mitel systems. We know this to not be true. TW requires RNIE tagging to prevent spoofing of calls but this also breaks re-propagation of the original CID. We have bee able to over come this with ALL of the other carriers we deal with accept TW. Please express this to the TW folks so we can break this chain of finger pointing. It is a setting in the Cisco IAD that they refuse to change. I know of only 2 systems that provide RNIE tagging. Cisco (duh it is a Cisco IAD Router), and Shoretel. I am sure there are others but I don't know them. The test is simple. FWD an extension to the PSTN and send out the original CID. TW will fail this call every time. This issue has been a deal breaker for customers that want to use TW. Educate your customer and tell them TW is the bad guy here and to not go with their service. STOP THE MADNESS!!
Inter-tel Axxess, Mitel CS/HX5000, MiVoice Office CCS/CSM, VPU, EM, ATM4, A+, CTP+, NET+, OAISYS, Audicodes, Polycom, Spectralink, NEC Red, Samsung, Mitel Call Recording, Mitel MBG, MiVoice Office, Xarios. Mitel Phone Manager
|
|
|
|
Joined: Jun 2008
Posts: 60
Member
|
OP
Member
Joined: Jun 2008
Posts: 60 |
Thanks for the response. That's exactly what happened, and we never got any traction with TWC on getting it changed.
|
|
|
Forums84
Topics94,284
Posts638,772
Members49,765
|
Most Online5,661 May 23rd, 2018
|
|
0 members (),
136
guests, and
278
robots. |
Key:
Admin,
Global Mod,
Mod
|
|
|
|