Partner Messaging, cannot transfer x76

[rocketpwerdtelecom]

I have a Partner messaging system that will not transfer me to x76. I get an 'invalid extension' message. I did setup the #505 option and I can connect to the Remote Access card via attendant transfer. This is the 15th system that I am connecting to, so I am wondering what is going on.

Any ideas?

Thanks in advance.

 

[ttech]

Is the selector code for 7 set to direct extention transfer?

 

[exsmogger]

If this is indeed a silver remote access card and not a green backup/restore card, I would suspect the modem in the card is defective.

Can you dial 76 from intercom dialtone and hear the modem answer? If the modem does answer then check the selector code 7 as suggested by ttech.

Brian Cox

http://www.jandjcommunications.com

 

[TouchToneTommy]

A feature of Partner Messaging is Transfer Restrictions. You cannot transfer to an extension that does not either have a maibox or has transfer only permission. This is so someone can't transfer from the Auto Attendant to something like a lunch room phone. (All this is unless you turn transfer restrictions OFF. It is set to on by default)

The solution is to create a transfer only mailbox for Ext. 76.

Log into the System Administrator's mailbox, press 9 for programming, press 2 for extensions, dial 76#, and press 2.

 

[itpphoneguy]

Hi rocketpwerdtelecom,
TTT has hit the nail on the head. That and exsmoggers instruction to make 7 direct ext xfer will solve this for you.
-Chris

 

[rocketpwerdtelecom]

Dudes,
Thanks much for the info. Makes sense when you think about it. Lucent/Avaya have generally good for believing in the KISS theory.

 

[DWLaurie]

What I tend to do is add extension 76 to Hunt group 7. This is indicated in Avaya documentation as well. If you are dialing in by modem, set your software to dial in using the AA, I put in the number to be dialed as 9,XXX-XXXX,,,,,,,,776 (you might not need the "9,") [and yes, that is 8 commas, it depends on the timing you need though, each comma is about 1.5 seconds] and it usually works like a charm.

--Dan

 

[itpphoneguy]

Hi Dan,
Yup, that's about right. I used to do that but now I just xfer to 76 (xfer only mailbox on the messaging series). *8,76 may work to.
-Chris

 

[TouchToneTommy]

I'm sure you meant hunt group 6, not 7. The reason is with VS Mail, Partner Mail, and Partner Voice Messaging (PC Card), 76 is an invalid extension. But 776 IS recgonized as a valid destination. With 76 being the only member of the hunt group, you get there with "5551212,,,,,,,,776".

Even with 76 set up as a transfer only extension in Partner Messaging, selector code 7 may not be set up as Direct Extension Transfer (by default it is Not Assigned), so I usually do the "5551212,,,,,,,,*876" routine to be sure and get there.

 

[itpphoneguy]

Hi TTT,
Hey, I missed that to. Good eye. I normally set all our systems up, and so do set 76 up as xfer only. When it isn't. I do the *8,76. Yes, I do set selector code 7 as direct extension transfer. Just dialed into an R7 today from remote through Mess R6 using XXX-XXX-XXXX,,,,,,76 . The dashes are for clarity. It was an LD call and it worked perfectly. Saved 1 1/2 Hrs windshield time each way.
-Chris