Forwarding issue

[peterbokunet]

MICS 7.1, PRI

An extension on the KSU is forwarded to a local number. Local callers calling that extension can connect just fine. If a long distance caller (calling to us) calls the same extension, telco blocks the call with a busy.

The explanation from telco is: They block the call because the KSU is originating a call with an out of area originating number. (It's using the original caller's info.)

Is there a way to force a redirect rather than do the conf call like Feature 4 typically does? (That was telco's question to me.)

F84 won't work as it's not a line forward but an extension forward.

Any advice?

Thanks!

 

[lugerlover]

try changing OLI on set u forward to your published number

 

[senk1s]

F84 is to redirect a DID call (or other CO call) to another outside tel #

try what lugerlover suggested and lets know if that works... (its that time of year again ... we already got some snow in the higher elevations in CA)

that being said - i remember reading something about this problem ... i cant find the info it is solved or not.
"the incoming calls caller ID is being sent as OLI"

Is the call answered by the CP or directly going as a DID?
Try saying caller ID no for that station/ target line

 

[peterbokunet]

I tried clearing the OLI with no change. I didn't try setting it to anything else though. Telco will use the first number out of the set if I leave it blank.

The KSU still uses the originating callers number on the outbound call though. The call just goes out as a DID.

Is it typical for telco to have such a restriction? I know a guy there and asked him if this restriction can be lifted.

Can I have both F4 and F84 active at the same time? That might end up doing the trick. The F4 would cover the internal transfers and the F84 would cover the DID. I can try that tomorrow while on-site. If not they'll probably just have to live with F84 using the Intercom.

Thanks again,

 

[peterbokunet]

F84 has the same result as F4 -- the originating number is associated with the outbound call. This was the same if the OLI was set or not set.

Odd.

 

[RikRodgers]

What protocol are you using on the pri? I've come to understand (the hard way) that there are some distinct differences in the overhead info transmitted between them.

 

[jerryreeve]

can you set feature 819 into the string before it forwards? or would this be a case of the telco not caring anyway and still blocking you?

----------------------------
JerryReeve
Communications Systems Int'l
com-sys.com

 

[peterbokunet]

F-819 didn't help either. Yes, it's PRI.

I talked to a switchman at telco this morning. He says I have three options (because they can't bill off trunk group):
- send all 3 numbers (caller, originating ext and callee)
- originate the call from the extension
- send a "fowarding indicator" in the D channel signaling

As I don't think the MICS can do either we're going to re-order the service do a different switch.

The current service comes through a "convergence" solution where data (private net, Internet and voice) appear on some MUX'd T1s. Voice is delivered to telco's router (cisco IAX something) as VoIP. The forwarded call originates to them as VoIP. Because it's VoIP, they can't do accounting on logical trunk groups <-- an issue with THEIR Broadsoft software.

The Broadsoft issue: The billing records for toll calls (again, local calls forward, incoming LD calls fail) are assembled by using the source and destination numbers. If the source number isn't "one of theirs" they'll block the call.

NB. I've proven the "one of theirs" to be a way to make free LD through them. Until our call this morning they defined "one of theirs" as any number in the local NPA-NXXs. If I call from my mobile to the forwarded number, it's a free call because their software can't bill the call to an account.

The re-order is going to convert one of the T1s to a dedicated PRI to their DMS.

I wish I wouldn't have learned all this. <grin>

 

[RikRodgers]

VOIP- The Wave of the Future, right?

Makes you miss POTS.

 

[peterbokunet]

Ok, I'm back to this.

We've converted the service off VoIP onto ISDN into a DMS. Same problem. Telco says the MICS isn't putting the forwarded info into the "redirecting" field but, instead, presenting the originating caller's info.

Did I miss such an option in the documentation & configuration all this time?

Thanks!