Neax 2000 IVS and incomming calls 2

[neaxtester2000]

I am reposting this because the post title was incorrect. the problem lies with the pbx not the call logging software.

"all calls comming in on our pots lines are not showing up in our call logging software. Some of the incomming calls on our t1 (voice) do not show caller id in the software as well and on the display they just show (DDD). Now our main office phone number is connected to our t1, the pots lines are strickly for outgoing local calling. But we are receiving calls on them. which leads me to believe people are calling out locally and then people are calling us back on the number that showed up on there caller id. now when they call that pots line, it rings our main line. the number we give out as our business number. Then the receptionist forwards them to a ext. Well all of this shows up in our call log. it shows a incomming call with no caller id. it shows the station number which is our business line. then the log shows a second call that has the station that the call was fowarded to. so one incomming call on our pots lines. shows up as 2 incomming calls in the call log. I am sure this is confusing. if anyone can help it would be great. It seems as though any incomming call on those pots lines is being directed to out main line. where would I look for something like that. Thanks again

 

[OzzieGeorge]

The incoming calls to your T1 which just show DDD are probably from people who have the caller ID blocked so the system has no info to show and substitues DDD as the default. As for the pots calls they are not redirected to the main line they are simply programmed to ring the LDN.
CMDs 3002 & 3003 set how the lines terminate in day and night respectively and CMDs 3004 and 3005 set where to in day and night. What you could do is set up another LDN and direct all pots to this, have it apear on it's own key on the console and don't include calls to this number in the SMDR that way you would eliminate the duplication of call records.

 

[neaxtester2000]

Thanks for you help. Shortly after I posted this I found the info in cmd 3002-3005. 3002 and 3003 were 04 and then 3004 and 3005 were set to our front desk extension. So for the caller id on the T1 the ddd means its blocked and there is nothing that can be done about that? As for the POTS lines, is there anyway to have that show the caller id info? You used the term LDN, what does that stand for? Thanks again for all your help. This site has been most helpful.

 

[dontworx]

To get caller ID on a T1 you need to get telco to setup what is called feature group D. You also have to have a 4-rstb card in your switch to recieve the ANI from telco. For pots lines you need a 4-cotg (for IVS) and a 4-rstc to recieve the caller ID. Hope this helps.

 

[OzzieGeorge]

The LDN is the "Listed Directory Number" and is normally the Published main number for your indail range. It is assigned in CMD5001 and is treated differently from normal extension numbers,One example is CMD 58XX. An LDN is most often used where a console is provided as you can set the key it rings on. As for the caller ID In OZ the calling party can opt to block the sending of caller ID so whether your carrier allows it or not you won't recieve it. I don't know if it's different there but I would expect similar possiblities.

 

[neaxtester2000]

Our system had the 4COTB card. So I would need to purchase the 4COTG card to have caller ID over the POTS lines. If I purchased the 4COTG card, how hard is it to install and configure, also would I remove the 4COTB card? The T1 gets 75% of calls with caller ID info. So I guess the calls that show up as DDD are ones that are blocked/private calls. So there is nothing that can be done about that right. Thanks guys for your support.

 

[dontworx]

Yes you do need a 4cotg and a 4rstc. Their is a cheat sheet available from NTAC website. If you decide to do it and you don't have acces to NTAC, I will list the commands for you. You can change the name of the trunk route to something else besides DDD but it will be the same for each trunk in that route. I don't think you can actually change the individual trunk names inside the same route. If you are getting caller ID on your t1 you must have a 4-rstb. If your t1 gets multiple incoming ringing calls at the same time, you may need another 4-rstb to help catch all of those incoming calls caller ID. The best thing to do is to switch over to a PRI. You can usually get just about as good of a switched rate on LD as you can on a LD t1. Also you out to retrofit that IVS to an IPS.