DID ACD NCFW to CallPilot geting wrong mailbox 2

[DogBiscuits]

Hello,

I am using ACD NCFW to forward a DID DN to Call Pilot. If I call the DID it works fine no problems. The problem is as follows.

Affiliate forwards 1FB to the DID mentioned above. When it comes into the PBX it forwards to Call Pilot like it should. However, call pilot responds with a message that the mailbox is not setup. The kicker is the mailbox that Call Pilot isn't the DID NCFW! It is the NXX of the 1FB!

i.e. 1FB NPA-NXX-XXXX forward to DID in PBX. DID NCFW to Call Pilot. Instead of getting the correct mailbox callers get message saying NPA-NXX-XXXX does not exist.

If you just call the DID it works.

Another tidbit, I forwarded my cell phone to the DID and it worked fine. But my phone is a different NPA.

Any help would be appreciated.

 

[TAnselm]

that is because of the call tag.
PBX will send call to the mailbox of the originally dialed DN. Change class of service on the 1FB DN to SFA (second level call forwarding)

 

[bigindian65]

can you not make the ACDN the DNB of the number you are NCFW?

If I want to ncfw a did, I smoke that number & make it the DN of the ACD Queue

Mato' Was'aka

 

[DogBiscuits]

TAnselm,

The 1FB is not mine. It is a separate business that just forwards to me at night.


bigindian65,

I don't understand. I did a LD 23 new ACDN "DID" Maxp 1 NCFW "Voicemail DN"

Could you give me an example of what you mean?

 

[PERRYPJ]

Put the FB number in the mailbox

OLD ROLMEN WORKING ON NORTELS

 

[DogBiscuits]

PERRYPJ,

Good Idea but it didn't work either.

 

[Triton101]

Can you IDC the DID to a dummy number that is associated with the mailbox as secondary DN.

 

[tnphoneman]

When a call is forwarded like described you will hae the original dialed digits carried with the call, This happens when you have a PRI inbound for your calls.

The work around for this is to add the 10 digit number for example 6156667777 to the SDN table and have that express message the mailbox. It will not work by just putting the DN in the mailbox. Call the number and listen to the CallPilot and it will tell you that XXXXXXXX mail box does not exist and you will know the exact DN to put in the SDN table.

Signature===========================================
Artificial Intelligence Is No Match for Natural Stupidity.

The latest survey shows that 3 out of 4 people make up 75% of the population.

The original point and click interface was a Smith & Wesson.

Red meat is not bad for you, it is the green fuzzy meat that is bad.

 

[RahjiSupreme]

JNJRBOE- DID YOU EVER FIND A SOLUTION FOR THIS ISSUE? I AM HAVING THE EXACT SAME PROBLEM. I HAVE REMOTE SITES THAT FNA TO MY OPT 61C. CALLS RING TO THE EXTENSION FINE, BUT WHEN THERE IS NO ANSWER CALLPILOT SAYS MAILBOX NPA-NXX-XXXX DOES NOT EXIST. THIS IS A HUGE PROBLEM, BECAUSE I HAVE SEVERAL DIFFERENT REMOTE SITES FORWARDING TO MY PBX. ANY HELP IS APPRECIATED.

CALLS DIRECTLY TO THE PBX EXTENSION WORK FINE WITH CALLPILOT VOICEMAIL.

 

[acewarlock]

RahjiSupreme: Have you tried the suggestion of puttint the NPANXXxxxx in thre Vmail of the DN it is going to as a secondary DN.




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.

 

[spunkysus]

The way for this to work is as tnphoneman desribed,you will need to build the 10 digit number being forwarded as an SDN then have it EM to the extensions mailbox.

 

[DogBiscuits]

We built a SDN in Call Pilot and sent it to a menu. That worked for US. You may want to try Spunkysus idea too.

Good Luck.

 

[tnphoneman]

ACE for some stupid reason if you put the 10 digit number as a secondary DN in a mailbox it does not recognize the number as belonging to the mailbox when you make the call. That is why you have to put it in the SDN table. This was also true for Meridian Mail where you had to put the 10 digit number in the VSDN table.

Signature===========================================
Artificial Intelligence Is No Match for Natural Stupidity.

The latest survey shows that 3 out of 4 people make up 75% of the population.

The original point and click interface was a Smith & Wesson.

Red meat is not bad for you, it is the green fuzzy meat that is bad.

 

[acewarlock]

Well I guess the one time I used the 10 digit number and it work for me may have been a fluke, but hey it worked. I haven't put a patch in the switch for 5 years and it doesn't have any problems and I would bet 1 million bucks if I put all those patches in the system would crash. There is no one right way to do aything in the Meridian system, thats why I love it so much.




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.

 

[tnphoneman]

Nortel technician motto

If it ain't broke, keep Nortel out.

Signature===========================================
Artificial Intelligence Is No Match for Natural Stupidity.

The latest survey shows that 3 out of 4 people make up 75% of the population.

The original point and click interface was a Smith & Wesson.

Red meat is not bad for you, it is the green fuzzy meat that is bad.

 

[RahjiSupreme]

If anybody still has this issue, the SDN fix does work. However, if you are like me, and your calls are forwarded from several "hundred" numbers, then you need another solution. I don't want to add a SDN for each number forwarded to my CallPilot (and I don't know if it is even possible). I brought an alternative voicemail system and I forward the calls off-site. This works, but I still need the IVR functionality in the App Builder portion of CallPilot. Any ideas?

 

[NARSBARS]

My solution was suggested here by someone else. The incoming trunk restrictions were stopping the call. Sometimes you can ignore the obvious.

NARSBARS

 

[RahjiSupreme]

NARSBARS, The incoming trunk restrictions? Please elaborate. First, let me explain a little more my scenario. I have remote sites not on a PBX, simple 1FBs. A customer calls my remote site, my remote site is not available, the LEC does a Forward No Answer after 4 rings to a TF on my Corp. PBX. I've built the TF as a Phantom DN, IDC, ACD, and key 0. In either scenario, when the call is not answered on my Corp PBX, it is sent to CallPilot. CallPilot says, "the person at npanxx, does not subscribe to this system". The number given is the remote site telephone number. If I input the remote site telephone number as a SDN, it works. But I have hundreds of FNA to my system, so that is not a good solution. Of course dialing the TF or ring to DID works fine, only the additional digits from the FNA messes everything up. I was told if I had T1 it would work (no additional digits), but of course that would kill incoming CLID for everyone else in the building. Not a good solution either.

With all that being said, the incoming trunk restrictions? Please elaborate.

 

[tnphoneman]

The problem is that you have a PRI and when the 1FB forwards the calls to the PBX the original dialed digits, which is the 1FB, travels across the PRI with the call thus you get the recording that you have been forwarded to a voicemail system and that number does not subscribe.

The only way to change the original dialed digits is to answer and transfer the call. I have done this with a simple announcement that says please hold while you call is being connected and then transfer it to the proper number. This is great if you only have one or two number to deal with.

If you have hundreds of numbers to deal with the easiest way is to install some NON ISDN T1 circuits and then the original dialed digits will stop at the CO and you will get to the correct menu.

Then the drawback for that would be that if you are using the CLID for any CTI applications or scripting you lose that capability.

Take your pick, shoot yourself in the foot or head. Either way you loose something.

Signature===========================================
Artificial Intelligence Is No Match for Natural Stupidity.

The latest survey shows that 3 out of 4 people make up 75% of the population.

The original point and click interface was a Smith & Wesson.

Red meat is not bad for you, it is the green fuzzy meat that is bad.

 

[guycable2]

Seems to me we solved this issue with the CALP setting in the ACD.

CALP (POS) TER Calling party identification sent in PCI message,
where:
basic-4.0
• POS - Sends the POSID+DNIS in the called
party DN field in the PCI message.
• TER - Sends the terminating DN in the called
Party DN field in the PCI message.I could be wrong though.

I can't remember for sure if this fixed our issue or if we did something else but there are no 10 digit SDNs in our Call Pilot.