atcomsystems.ca/forum
Posted By: ltcomm External call forwarding on MICS - 02/10/16 09:25 PM
Hello I have a MICS with PRI 7.1sw

The new carrier Time Warner won't allow you to send caller ID information unless you own the DID your sending.

The problem is that external incoming calls that are call forwarded back out are sending the callers caller ID number causing the call to fail.

Can this be forced to show the programming OLI number???
Posted By: Curlycord Re: External call forwarding on MICS - 02/10/16 09:58 PM
Program the OLI and ask that the carrier allow you to send your own caller ID if it does not work.

If you fill out the OLI with your Main Billing number then it should work.....try that first.




Posted By: ltcomm Re: External call forwarding on MICS - 02/10/16 10:32 PM
The carrier is allowing us to send caller ID
The system does output call ID properly when making normal phone calls.
Note: it does work if you call from extension to extension forwarding out

I tried putting a DID, The main billing telephone number and even clearing the OLI.
Still fails
Posted By: Curlycord Re: External call forwarding on MICS - 02/11/16 01:44 AM
TW is known to give grief for this exact issue.
Client should insist it worked before and that they should not blame the system.
Tell TW that they may need "TWTC hybrid SIP/T1 service package"
Raise hell and threaten to go back to the last carrier if need.

This stuff happens in Canada when people go with a Cable company for telephone service. You want cheap? pay the price!

I dont know if this will work but most people do F4 9 XXX-XXX-XXXX
They are always forwarding to the same bloody cell number so what I do is setup a Dest code for those whom need to do Ext Forward, it's less work to forward....just F4 8X (where 8X is the Dest code).

So in this example setup Dest Code 81 to use Route 001
In Route 001 tell it to Dial XXX-XXX-XXXX (persons cell #) and to use PRI-A.

So what we have here is the Route dialing the number and not the set.
Hopefully the call will be handled differently by the carrier since the route is calling the cell and not not the set and send out as the main calling number.



Posted By: ltcomm Re: External call forwarding on MICS - 02/11/16 02:37 AM
OMG
TW told me the FCC made them not allow spoofing of numbers to eliminate fraud.
I can usually get around this with ACDs on option 11 never had to deal with this on Norstar.

Anyways im using detonation code 9 rout 0 or 1 already (can't remember) for normal calls so il try.
Code 82 use rout 2 absorb 2 digits to eliminate 82 and dial 1-310-555-5555 if this works I can use 83 rout 3 etc.....

I'll keep you posted..
Posted By: nfcphoneman Re: External call forwarding on MICS - 02/11/16 01:52 PM
We've gone through this a couple of times. I never found a way to force the MICS to output the OLI on a forwarded call. As Curly, we had to get the new telco to do some programming changes to make it work again.
Posted By: ltcomm Re: External call forwarding on MICS - 03/18/16 03:06 PM
Hello all
Thanks for the help.
Had Time Warner turn on "RNIE" in there voice gateway and that took care of it, works just fine now.
Posted By: Curlycord Re: External call forwarding on MICS - 03/19/16 12:57 PM
Thanks for the update.

Looks like in reading this Shortel doc on the first page it seems you may need to remove any OLI, was this your case too?
Posted By: ltcomm Re: External call forwarding on MICS - 04/09/16 12:46 AM
Did not have to touch the OLI settings at all.
Posted By: Cans and String Re: External call forwarding on MICS - 10/05/16 04:34 PM
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!!
© Sundance Business VOIP Telephone Help