sundance-communications.com/forum Forums TDM Business Telephone Systems Avaya - Lucent Telephones & Systems Magix fwd to cell

Magix R3.
EExt136 is set for T2T Transfer, and RCF

If you call the DID, the phone rings.
Turn on forwarding.
Call the AA, and press 136, call forwards to cell.
Call 136 internal, call forwards to cell.
Call the extesnions DID, you get the magix waive off.

23 channel PRI, Trunk FRL Is 2, extension is set for 3.

What am I missing?

aa/vm ports must be allowed to do trunk to trunk transfer

if a directly dialed pri call does not reach the correct destination, you may have faulty dial plan routing.

The forwarding works from the AA, so I dont see setting the vmail ports with trunk to trunk transfer will help the DID.

If I un-forward the extension, the calls to the DID ring that set.

I will give the voicemail T2T transfer a try though. Thanks.

You're right, if forwarding is working through the AA, then you're good with the voicemail ports. And if you think about it, a DID call bypasses the AA altogether, so AA parms don't play a role here anyway.

The fact that both internal calls and AA calls to x136 in fact forward the caller as expected suggests to me that something else is at play.

I'm thinking that x136 rings on DID calls for the wrong reasons. What I mean is that the conditions that cause x136 to ring (when you dial that DID number) are not eligible for RCF. For example, it could be that x136 covers for a real or adjunct extension that your DID number truly terminates to.

Let me explain it like this: My phone covers your phone. My phone has RCF. Somebody calls your phone's DID number, causing mine to ring as well. If my phone is forwarded, where does your call go? To your mailbox, because a covered call isn't eligible for RCF.

Maybe you've setup x136 to appear as though it had a private line--and the DID in question is advertised as the private line's number. Unless the DID call somehow lands on one of the System Access/ICOM buttons of x136, the call won't be forwarded.

I dont show anything on 136 print as far as coverage goes. The PRI print has nothing in any of the incoming routing tables.

I do see a primary coverage button for an extension (199) i=on there.....I wonder....

Yeah boi!

I tried removing the coverage button on that set. No luck, still get waiveoff.

The customer swears that these calls orinigate from that same switch.

Does the DID number end in 136? When forwarding is turned OFF, and you dial the DID, what does the display show?. Can you answer the incoming DID call, press Transfer, 9, and an outside number and transfer out?

Tom--I've dialed in and taken a look at the PRI setup. There's nothing unusual in the Dial Plan Routing and no digit manipulation.

However this Magix is part of a network, which is why I asked Matt if the DID terminated on the other switch and THEN came across the link before trying to go off-net.

You and both know that there are only a handful of conditions when RCF won't work. Even unassigned DID numbers that fall back to an Operator are eligible for forwarding.

There was a cover button on x136 for x100 (an unequipped adjunct), but it apparently does not come into play.

My next step is to get back in and trace the extension from within Monitor mode. I'd also like to see how the DID call arrives on that extension WHEN it's unforwarded. It is currently forwarded (and the digit string looks good). But dialing the DID returns the french horn waveoff.

I would describe the client as a high-end type. We can really help Matt look like a hero here if we can get to the bottom of this bugger bear.