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

3300 Delayed TX audio on initial answer

Status
Not open for further replies.

MitelInMyBlood

Technical User
Apr 14, 2005
1,990
US
I have 1 remote user off my 3300 (ver 6.0.5.7) in another town on a dedicated T1 extension of my local LAN using a 5240. The T1 is part of a DS3 running over terrestrial 6 Ghz microwave system. We've configured QOS, even built an ACL to set-aside some reserved bandwidth for voice. QOS is not the problem. Occasionally, maybe 1 in 10 calls the user's set will ring with an incoming call. He answers handsfree but his calling party cannot hear him for about 5 secs. Thereafter the call is fine. The user has started keeping a log of time and calling number when this happens but there are no corresponding logs on the 3300. Happens regardless of whether he answers on handset or handsfree. Only happens on incoming calls to this one location. His set is programmed w/2 lines of Multicall plus he has a YA Pro softphone on his laptop with an immediate ring key app of the multicall line. The occasional 5-sec delay is starting to raise some heat. We've tried to dupe the users configuration in the office but we cant' make it happen. We also tried replacing the user's set. Anyone seen this or have any suggestions to offer? Thanks
 
Does he have this problem on his YA/Laptop EVER? Have we tested the phone right off the ICP (within the same LAN)? Is there a firewall or VPN between the phone and the ICP? Does any other phone IE 5220d have the same issue? I would think it would, as they are using the same (well, almost) call control.
 
Thanks for reply. I was just getting ready to reply to this myself and close the problem. We discovered in investigation after an 80-mile drive and physical site visit today that the GN Netcom cordless headset base unit (which no one knew the client had) was the culprit. With this aftermarket junk removed we can no longer cause the problem to appear. Tried a total of 50 calls today and were 50 for 50. Thank God. I hate intermittent problems that become high level gripes. We especially love it when one backfires in the clients face. This guy really made an ass of himself and in front of his boss. Something like this also helps reinforce our position about NOT supporting aftermarket accessories.
 
Oh yes. I made sure to get a ticket signed and also made sure they understood this was not covered under their MA. Truth of the matter is I probably would have written it off for customer goodwill if the guy hadn't been such an ass.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top