Call Pilot Transfer Question 1

This might be what you're running into...

While the originating side of a call is linked to a transfer or conference key (that is, the originator of a transfer/conference call has not yet completed the
transfer/conference), the terminating side cannot initiate a transfer or conference.

This is from the CP DTR 2.2/3.0/4.0

You might be right.

Person is transferring me thru Call Pilot that is transferring me to the end user.

Cannot double transfer. This is a design intent. I remember that will Call Pilot and Symposium.

Only problem is I have a customer that is saying...

"This used to work" We just picked this up under maintenance so we are troubleshooting all kinds of problems with the work.

And as a reminder. If you have single density phantom loops programmed and you go to Succession, you will need to reprogram or they won't work.

John

Good Luck, I hate hearing those words "This used to work"...

Maybe adding a announcement block before the mb or ext., but have a announcement block record several seconds of silence... maybe???

That's what I was going to try to do, is record a quick announcment with a ring or two.

John

Just to let you all know. I found the entry in Primus

Solution ID: NORT205818 Product Family: Enterprise Voice Create Date: 04/19/2005

Title:
CallPilot Menu service cannot transfer a call to CDN acquired by SCCS or internal set when call is made via transfer or conference key.

Facts:
CallPilot

CallPilot 2.02


Symptoms:
CallPilot Menu service cannot transfer a call to CDN acquired by SCCS or internal set when call is made via transfer or conference key.

Error: "Your Call cannot be completed at this time. Please try again later."

Event 58006

Event 55741

Scenario: External call calls set A. Set A selects transfer key and dials menu service. Menu service answers and Set A presses option which is supposed to transfer the call to an SCCS CDN. Upon pressing menu selection, error message is heard from CallPilot: "Your call cannot be completed at this time. Please try again later". Note that Set A never completed the transfer that he had initiated with the external caller.


Fix:

Design intent.

Per NTP 553-3001-306, under section for Conference:

Double conferences are blocked to avoid conference chains (that is, set A and set B are on an established call. The user of set B presses the Conference key to call set C. Any attempt by set C to initiate another conference is blocked if set B has not yet completed the conference).

While the originating side of a call is linked to a transfer or conference key (that is, the originator of a transfer/conference call has not yet completed the
transfer/conference), the terminating side cannot initiate a transfer or conference. Conference calls cannot be transferred.