Hello. We are using MAS NuPoint Messaging/Call Director for a new menu structure one of the options is to transfer to an external number. I have tried to use several different menu option settings Alternate Transfer/Blind Transfer/Supervised Transfer etc. to route the callers to this external number. However, when calling from outside the network. NuPoint appears to begin the transfer, the external number rings one time and then the caller gets sent to the message center. As a side note, the transfer is successful when dialing the call director menu internally. I have also looked at COS on the MCD 4.1 for Voicemail and PRI Trunks. Any idea what is missing to make this transfer successful for outside callers? Much appreciated!!!
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Westi on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
MITEL NUPOINT CALL DIRECTOR-UNABLE TO TRANSFER TO EXTERNAL NUMBER
- Thread starter acskmk
- Start date
- Thread starter
- #3
Can you call from outside to an internal phone and then transfer to the same external number? Almost soulnds like trunk to trunk connections disabled.
You need to check the COS of both the Nupoint ports and the trunks to make sure the conference feture is enabled. Often the ability to send calls from voicemail to an external trunk is disabled to prevent toll fraud i.e someone setting up a speed dial to a long distance number then using the AA to dial the number and the company incures the long distance charges for the call.
I'd tell you a UDP joke but I'm afraid you won't get it. TCP jokes are the best because you always get them.
You need to check the COS of both the Nupoint ports and the trunks to make sure the conference feture is enabled. Often the ability to send calls from voicemail to an external trunk is disabled to prevent toll fraud i.e someone setting up a speed dial to a long distance number then using the AA to dial the number and the company incures the long distance charges for the call.
I'd tell you a UDP joke but I'm afraid you won't get it. TCP jokes are the best because you always get them.
Supernova99
Technical User
You need to setup a speedcall for this to dial out externally
Share what you know - Learn what you don't
Share what you know - Learn what you don't
- Thread starter
- #6
@ LoopyLou: Yes I can successfully transfer to the external number. The Blind Transfer action also transfers successfully to the external number when dialing from an internal phone.
I am not finding the class mark you mention? All I see is conference call which enables the station to conduct a conference call.
@ Supernova99: I tried the speed call setup and used that as an entry in the Blind Transfer and the Alternate Transfer method. Fail. Same result. Rings once and sends the caller to the message center.
NuPoint is just not letting go of the call...
I am not finding the class mark you mention? All I see is conference call which enables the station to conduct a conference call.
@ Supernova99: I tried the speed call setup and used that as an entry in the Blind Transfer and the Alternate Transfer method. Fail. Same result. Rings once and sends the caller to the message center.
NuPoint is just not letting go of the call...
dryaquaman
Vendor
In the extension field add an 'h'. (Not kidding)
Example: '1234h'
Dry Aquaman
Example: '1234h'
Dry Aquaman
Can you transfer externally from a phone with the same COS/COR options as a VM Port.
As the call is initially ringing, I would think the COR is OK. The COS of the VM port may not be allowing Public to Public though. (or conference)
The message center kicking in sounds like a recall on release.
Regarding: Add an h to the extension field. This is more easily done in the System transfer strings.
Change S+X to S+XH
That being said, I do not think this will resolve the issue.
**********************************************
What's most important is that you realise ... There is no spoon.
As the call is initially ringing, I would think the COR is OK. The COS of the VM port may not be allowing Public to Public though. (or conference)
The message center kicking in sounds like a recall on release.
Regarding: Add an h to the extension field. This is more easily done in the System transfer strings.
Change S+X to S+XH
That being said, I do not think this will resolve the issue.
**********************************************
What's most important is that you realise ... There is no spoon.
- Thread starter
- #9
- Status
Similar threads