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 Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Dropped Calls on INDECT System

Status
Not open for further replies.

Fodrod

Vendor
Apr 4, 2022
58
CA
Hi, has anybody else experienced a large volume of dropped calls on the NEC INDECT system? (Specifically with the AP400 and G577 handsets). I'm trying to work through nec support on it, but they suddenly went from answering within the hour to answering once a day and arn't being helpful. I have all of the handsets programmed just as in the additional information guide. The Indect is at version 1.60, handsets updated to the newest, and pbx on 4.1.
The customer seems to have no dropped calls for a few days, then 20 minute periods where every call will drop within 5 minutes. I am somewhat concerned that the one DAP is only two feet away from a wifi AP, but the customer is an hour away so I can't just run over and change that at a whim.
Has anybody else had similar issues and solved it?
 
What system you on?
I have SL2100/SV9100 working pretty good, DECT is probaly my fav thing about the NEC

Calum M
ACSS
 
Are you sure it's handsets or the trunks? Anyone check the network to make sure there aren't IP conflicts? Has this ever worked 100% or is this from day one? Why were 2 AP's put that close to begin with?
 
Sl2100. It's been like that relatively since day 1
Same trunk provider as their old panasonic pbx
There's also never dropped calls
Our pbx is on it's own network consisting of literally only the pbx, our router, and the daps.
I don't know why my coworker put one dap so close to their wifi ap, but I also doubt that's the issue.

Also, how long have you been using the indect? Before version 1.60? Because nec support admitted to me (over the phone) that it there was so many bugs and workarounds pre 1.6, that it basically didn't work, and now it's sorta ok, which follows my experience. The sheer amount of features (like half) that are on paper "not supported" is also extremely frustrating, including line keys, cap keys. Also after about 2 weeks it just decides to stop working, so the pbx needs to be on daily reboot.
Since you say it works fine for you though, I'm curious, are you in Europe or north America?
 
Hello,
Did you ever find a solution?

We are having the same issue, with not much help from NTAC.

Thnaks!
 
Yes, the customer couldn't tolerate the crap anymore, and it was impossible to reach any solution, and nec was absolutely unwilling to put in the extra effort, instead insisting that it has to be awesome because some line of cruise ships use them. (But those enterprise deployments are a different product even if it uses similar hardware). So the crap was taken out, and we switched the affected customer to grandstream WiFi phones, and will never sell the product again. (And the three or so clients with one or two phones will hobble along and not use the phones enough to realize how bad the dropped calls are)
 
We have the DECT Wireless phones on one install and they stop working. Coincidentally the SV9100 gets constant "IP Conflict" alarms and it is the only install with Cisco switch's and I have been told ARP Probing on the Cisco switch's can cause problems. We had the IT company turn off ARP Probing on the ports of the SV9100 and the alarms went away but came back because somebody moved the SV9100 to different ports.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top