NuPoint Supervised Transfer Query

[Martin]

Hi all,

Another problem I have come across with this. I dont know if this is possible really but it feels like it should be considering its a feature for use in call director.

When using supervised transfer through NuPoint, this goes through to a user or a group and say for example they miss the call...The missed call will be showing from a NuPoint Port rather than the external caller. This makes sense in a way as it will be the port which is performing the supervised transfer. However there must be a way to show the external number as the missed call as its not like the user can go and ask the NuPoint Port who the external caller was! Its not very useful when call history on desk phones and MiCollab clients are full of missed calls from ports..

Anyone got any ideas?

Thanks

P.s I have already investigated all CoS options on the controller and also the FCOS options on the NuPoint server. Turning "Use held caller ID on transfer" allows phones to see the external number when the call is being transferred however the missed call will still be from the voicemail port if they dont answer.

[johnp]

Why not unsupervised?

[Martin]

Using blind transfer means the call is sent back to the MiVoice Business system rather than keeping the call flow in call director in NuPoint. The call flow in this particular case requires various alternatives and programming that would be tricky to configure on the standard MiVB due to restrictions on the amount of alternatives/rerouting to other voicemail mailboxes.

Keeping the call in NuPoint using various supervised transfers means a great deal more flexibility and control over the call, e.g. no answer timers, looping the call round certain groups or pointing to a completely separate voicemail without using ACD paths or complex programming on the controller itself.

[busarmy]

Using blind transfer means the call is sent back to the MiVoice Business system rather than keeping the call flow in call director in NuPoint. The call flow in this particular case requires various alternatives and programming that would be tricky to configure on the standard MiVB due to restrictions on the amount of alternatives/rerouting to other voicemail mailboxes.

Keeping the call in NuPoint using various supervised transfers means a great deal more flexibility and control over the call, e.g. no answer timers, looping the call round certain groups or pointing to a completely separate voicemail without using ACD paths or complex programming on the controller itself.

Martin, I know it's a very long time ago, but could you ever solve this issue? Because I'm having the same problem today... Thanks!

[Martin]

Apologies mate I cant remember if I ever got to the bottom of it or not. Let me know if you do, will be useful to know!