Incoming Caller ID-ANI 2

[SUSANVV]

We have a Merlin Magix 3.0 and AT&T PRI. Prior to the PRI we had incoming Caller ID on the same system. Since the PRI we do not. I am told by AT&T after several checks that they are sending ANI. Is there any settings I need to make in the Merlin to recognize the Caller ID. Our console displays the following on an incoming call:
COVER DID#?
We do not yet have DID's (they are on order). TIA for any suggestions.

Sue Van

 

[jgideon]

I suspect if you press 'more' you'll see the CallerID. If a call is covered or forwarded, you see that status message first

 

[Ghostin]

Since you don't have DID's, your PRI will not work correctly. ATT is most likely using a temporary number to send calls to you. That number does not match your current numbering plan, so it overflows to the operator console. That is why you are getting the message DID ?. Once you have established DID numbers that corresponde with your extension numbers, then the caller ID info will appear. You will only get the number with a PRI, not the name.

 

[SUSANVV]

Thanks for your reply. We have a 4424LD as our console and I do not see a "more" button. At the bottom of the screen is Show Number but when I press the button along side that Cover and DID go away but there is no number and I know there is a sending number. Is there some setting that we need to change to leave the 24th channel out of a cover or group or do I need to do another AT&T trouble ticket? We are also logging all calls and it is not recording any incoming numbers. TIA again.

Sue

 

[SUSANVV]

Reply to Ghostin: First we use our PRI for incoming for our main phone number that everyone calls so how is that an issue. Secondly DID's supposedly were not an issue and were not even ordered until about one week ago and we have had the PRI since 2/9/04. Are you suggesting that incoming on a PRI cannot work with anything but DID's? I do know that our vendor has something set originally to 3 digits and had to change it to 4 but I don't think that it had anything to do with DID's. Thanks for helping.

Sue Van

 

[jinxs]

what is happening is the magix has no match for the incoming digits sent by AT&T. Just like Ghostin said. So,by default,it will send it to the back-up extension(your operator). So, with your logic, everything works as planned. Do you know what AT&T is sending you? You can match it under dialplan routing and send it to the console or you could just renumber your console to match what they are sending(assuming that it is 4 digits or less). There are ways to find what they are sending you, all though, it always becomes deleted when we discuss it. Look for it somewhere in the legend forum. Or, just call AT&T to find out what they are sending you. Then, to assign a route, go to ::
sysadmin
start
lines/trunks
pri
dialplan routing
let's say route 1 isn't in use yet
so under service route 1 select anyservice
under pattern route 1 enter what AT&T is sending you
under digits route 1 enter the number of digits being sent to you from AT&T
under delete digits route 1 enter the number of digits being sent to you
undr add digits route 1 enter the extension of your console

then you have caller ID and all will be good.

 

[SUSANVV]

Thanks for the info. Can I ask a favor of you? Since I can't seem to find the Legend forum (at least not here) can I please ask you to email me how to find what numbers are being sent to me? I can just imagine how many phone calls to AT&T it will take me to find someone who can tell me the numbers. Can I put my email address in one of these messages?

Thanks again for all of your help.

Sue Van

 

[jinxs]

sure, e-mail me at beholdthejinxs--at--rcn--dot--com

 

[SUSANVV]

First of all, thanks for all the suggestions. Second of all I still have no luck. I believe that I found the digits sent in the cut-over sheet. In addition to your suggestion is there possibly something on the console that needs to be programmed? On 3/24 AT&T is going to change what they are sending us from ANI to PSI. I am hoping that may help. Is there any way I can be sure we are gettin the signal? My vendor is telling me that nothing should have to be changed on our system and that the problem is still with AT&T. That DID# on the console bothers me as the DID's are not supposed to go through the console. Could something there be contributing to the problem? Sorry I haven't replied sooner buy I have been trying things. TIA again.

Sue Van

 

[franke]

Just out of curiosity, have you, or could you print out your dialplan and see how your trunks are 'labeled'? It could be your vendor did not re-label them from a prior setup.

Your vendor undoubtedly changed your 3 to 4 digits to accomodate the DID calls. My question would be do you currently have 3 or 4 digit extension numbers?

It would be very helpful if you could cut & paste a printout of your 'PRI'.

As to the caller ID, it should work fine with ANI.

 

[Ghostin]

A couple things to note for you Susan. PRI does not function like standard caller ID. You will not be able to log calls under the PRI. Having ATT switch to ANI vs. PRI will not work unless the circuit is changed.

Second, the basic principle of a PRI is to route calls based on the digits being sent, so in essence, they act the same as a DID number. You cannot receive a call on a PRI circuit without sending some "DID" digits. If you are receiving digits that do not match your dial plan, then the system will route that call to the operator console and display DID # ?. This indicates you have received a call not matching the numbering plan. This could happen several ways, but most likely is the numbers being sent don't match extension numbers. let's say your console number is 1000, and your DID range is 1000-1099. Anytime someone dials 555-1000, it will route to the console. Anytime someone dials 555-1001, it will go to 1001. If 1001 does not exist, then it routes to the console. This assumes that the provider is sending the correct number of digits, in this case, 4. If they were only sending 3, then all calls would go to the console and display DID # ?.

PRI setup can be a bit complicated, especially when you have to insure all parties involved are on the same page. I would highly recommend getting a local vendor to assist you on site. let us know where your at, and someone will come forward.

 

[SUSANVV]

First thanks for all the replies. When we had AT&T change the type of caller ID from ANI to PSI Caller ID started to work. Our vendor mentioned (a bit late in the game) that Merlin Magix doesn't function that well with ANI. It seems to like PSI. Whether it was that or something missing in the original cutover that was fixed with the new order i may never know. But it does work now. Thanks again.

Sue Van

 

[quincyb]

I know this has been solved, but we were having the same problem, with only one line of Caller ID being displayed. So I downloaded the manual, and found out this tidbit of information:
¦ Simultaneous display of Caller Number and Caller Name is not available for PRI
lines with Automatic Number Identification (ANI) service; PRI (ANI) displays Caller
Number only.
¦ Simultaneous display of Caller Number and Caller Name is available for analog
loop-start lines connected to the following types of modules capable of supplying
Caller ID ports:
— 800 GS/LS-ID module
— 408 GS/LS-ID-MLX module
— 412 LS-ID-TDL module
¦ If you program the Calling Party Name button on 4400-Series and MLX telephones
and activate the feature (the button’s LED is lit), Calling Party Name appears on
line 1 of the display and Calling Party Number appears on line 2 of the display. It is
not necessary to program the button to see both Calling Party Number and Calling
Party Name simultaneously on these telephones.

Hope this resloves the "mystery"...

 

[merlinman]

SUSANVV - is this not resolved now???