I've got a Mer Mail running rel 12.12 and all is working well with the system. Problem is that I've been asked to add another key to an existing menu service. There are already 3 which all go to internal numbers (7 digit) but the new key #4 they want to go to an external local number. When I enter it and press 4 there is a long pause and then the message "call can not be completed at this time". I have also tried putting in a number that is in the CDP and have the same results. Most out dialing on the switch is through CDP and the local trunks are by using the ACOD in the RDB. LD 15 RDR CFTA is set to yes. Phones have no problem doing a CFW to a local trunk using the ACOD. So what am I missing, something stupid probabbly. any suggestions are 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 strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
MerMail
- Thread starter steve64
- Start date
notapropergeordie
IS-IT--Management
TGAR on voice ports?
you could try forwarding via an ACDN's NCFW.
you could try forwarding via an ACDN's NCFW.
- Thread starter
- #3
Tgar is not the same as the route TARG so it should go through. I reconfigured the main incomming number for the VSDN to a Phanton that DCFWs to the Mermail main ACD then built 3 ACDs that NCFW to the Cell #s and pointed the MS selections to the ACDs. Works fine now. Just don't understand why the I can't point the MS keys directly to the Cell #s. Well whatever it takes to make it work. It seems as though the ACD NCFW works better for forwarding in some situations. Have had to go this route before.
Thanks for the suggestion
Thanks for the suggestion
You might be using FTOP
In summary, if FTOP = FTLY in the Customer Data Block ~and~ the mail TNs are CLS=FTTC or FTTR, then that's the problem. You'd have to set the mail ports to FTTU.
Or the mail ports are CLS= FRE or SRE, or ?
CFTA only applies to Call Forward All Calls, not transfer or conferencing, which is what the mail ports are performing.
GHTROUT.com | FAQs | Recent Replies
In summary, if FTOP = FTLY in the Customer Data Block ~and~ the mail TNs are CLS=FTTC or FTTR, then that's the problem. You'd have to set the mail ports to FTTU.
Or the mail ports are CLS= FRE or SRE, or ?
CFTA only applies to Call Forward All Calls, not transfer or conferencing, which is what the mail ports are performing.
GHTROUT.com | FAQs | Recent Replies
- Thread starter
- #5
Looked at FTOP in net data and it was set to FRES so I changed it to FTLY. The mail TNs CLS were CTD and FTTC. I changed the FTTC to FTTU. Then I added keys 6 and 7 to the MS service. 6 was routed to a phantom with DCFW to an external #. key 7 programmed to directly go to an external number. Everything else still works on the MS services but the the 2 new ones still give me the message " call can't be completed at this time".
Change it back to FTLY=FRES, or Tuesday people that used to be able to transfer calls to external numbers are going to cutting people off. Notice that all of your phones are CLS FTTC - they default to that.
If FTLY used to be FRES, then that eliminated that feature from being the cause of your problem.
What we have not eliminated:
- The NCOS of the Mail TNs. Is it high enough.
- Trunk Route Disconnect Controls. The NEDC and FEDC values in the incoming and outgoing Trunk Routes - is that restricting the connection.
- The trunk routes used. Is the caller coming in on a COT route and then is mail trying to send the call out on the same COT route. If so, that transfer is restricted always.
GHTROUT.com | FAQs | Recent Replies
If FTLY used to be FRES, then that eliminated that feature from being the cause of your problem.
What we have not eliminated:
- The NCOS of the Mail TNs. Is it high enough.
- Trunk Route Disconnect Controls. The NEDC and FEDC values in the incoming and outgoing Trunk Routes - is that restricting the connection.
- The trunk routes used. Is the caller coming in on a COT route and then is mail trying to send the call out on the same COT route. If so, that transfer is restricted always.
GHTROUT.com | FAQs | Recent Replies
acewarlock
Technical User
Quote: "call can not be completed at this time". I don't think that is a MM or PBX message, it sounds more like a Telco recording. Have you tred doing a TRAC in LD 80 on the Vmail port when you try this? Or turn on D channel messages to see what your sending.
This is a Signature and not part of the answer, it appears on every reply.
This is an Analogy so don't take it personally as some have.
Why change the engine if all you need is to change the spark plugs.
This is a Signature and not part of the answer, it appears on every reply.
This is an Analogy so don't take it personally as some have.
Why change the engine if all you need is to change the spark plugs.
- Thread starter
- #8
Yes when it didn't work I put the settings back. Yes the NCOS on the MM TNs are high enough and calls the the numbers are only originate internally. As far as transferring to external numbers no sets are allowed to tranfer to an external number directly. This is the first instance that is being allowed and then only through the MM MS service. The route being used for the outgoing calls only has 5 COT LOP with no supervision. That's all the Telco can provide us. We are still fighting with them to get the routing and translation tables correct on the PRI2 ckt. Don't think they know how or just don't care. Finally I'm sure the message is from the MM as any messages from the Telco are not in English. I think we will just wait until the PRI2 is working and then attack the problem again as the COTs will go away.
If the source of the call is internal - same PBX as the Mail system - then it's the same as anyone transferring the person in the next office to an outside line. That points to a dialing string problem on the menu choice.
GHTROUT.com | FAQs | Recent Replies
GHTROUT.com | FAQs | Recent Replies
- Thread starter
- #10
- Thread starter
- #12
- Status
Similar threads
- Locked
- Question
- Locked
- Question
- Locked
- Question