Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Lloyd]

Along with static and echo problems, we're having issues with incoming calls using through the PSTN lines. That is to say when 2 calls come in close together the receptionist can only answer one call, the system sends the other caller to the secondary receptionist in the group. It doesn't allow the primary receptionist to answer the second call even though she's parked the first caller. This doesn't become an issue until the secondary receptionist is away from her desk which happens quite frequently. If the secondary receptionist is away the only method for the primary receptionist to answer the second caller is to run to the secondary receptionist's office and answer the call there.

We've tried duplicating this issue using cell phones and its very consistent.....whenever the incoming calls for the primary receptionist are close together it allows one call to be answered but not the second one.

I spoke with several technicians at Dlink and received a myriad of work-arounds including putting 2 phones in the primary receptionist's office so the second call can be answered on the 2nd phone . Another technician told me this problem will be addressed in SP2 but yet another said he wasn't aware of that.

At one point I talked with a Dlink Tech who thought the problem could be the Dlink switch we're using (DES1228). He recommended a level 2 switch like the DGS-3100-24.

My question is; has anyone tried using a level 2 switch like the DGS-3100 on your Response Point system and did it help?

Thanks
Lloyd

[Mlachake]

I remember talking to you about the above issue. As I indicated to you, we are working on a solution to that specific issue.

[Lloyd]

Are you thinking the problem lies in the D-Link firmware?

Thanks
Lloyd

[Mlachake]

Please upgrade the phones to the latest firmware release on the support site. I could not duplicate your issue using the latest firmware on the support site.

[mavrrick]

What type of switches are you using.

I deployed the Dlink Response point system on a friends small business and they experience similar issues with sporadic Static and echoe's believed to be caused by spikes in network traffic. Their network configuration was a central SBM router and two 8 port Gig/E switches from the local office supply store. It worked fairly well for them from a raw data perspective. but as soon as the connected the phone system they started were having static and echoing(Should be noted we deployed 7 phones immediately). They were also in a slight bind because most of their systems used Gig/E to connect to their server, and they were being forced in a few occasions to drop to 10/100 because they didn't have enough ports when the phones were added.

They have sense bought a 48 port 10/100/1000 Layer2/some layer3 switch from a national computer company. They got it from them just because it was were they had their financing. I looked for a DLINK actually to keep it all the same company, they just didn't offer it.

The important thing is to make sure the switch can do QoS and that you can set it up on a port level. I initially configured it up to run on a separate Voice VLan but that causes issues with some of the Response Point functionality. Response point wants to be on the same subnet and the response point assistant can't work if it isn't. The phone will work fine you just can't use the assistant software. So now we run that 48 port Gig/E with just the default Vlan and QoS priority given to the voice traffic, with all of the DLink Phone system given maximum priority and then the external router below that and then internal traffic the lowest.

It should be noted that this change improved their environment considerably, and i expect it will make it better for the foreseeable future even if they add several phones. Their complaints about the static have gone completely away, and I was told they only have occasional echoing( i could probably do more tuning to remove the echoing). The QoS is probably the most important thing to think about, most of your problems with VoIP will be caused the voice traffic either arriving out of order or with just lag. Being able to provide the voice traffic priority over other traffic should be able to resolve that.

[Lloyd]

Thanks for the tips and information mavrrick. We'll give that a try.

Lloyd

[Lloyd]

One other thing I should point out. The latest firmware update greatly help the dropped call problem we were having when incoming calls came in close together. Now I need to resolve some of the voice quality issues.

Kudos to D-Link support for the firmware update!

Lloyd