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

Floating DID doesn't ring at desk, goes to reception?!? 1

Status
Not open for further replies.
Sep 12, 2007
143
US
Hi All, I have one floating extension for a manger who moves around. He has to log in and out of that extension. When a caller calls his DID, it rings at reception, and not at his desk, any idea why?

Thanks, Dawn
 
dawn,
I know I am joking, but the reality is it would not be funny if it were not truly a great opportunity based on this companies performance level. From what I understand you are remote enough they have no competitors, and neither would you if you provided quality service.

 
aarenot, thanks for the vote of confidence :) You are probably right, but I am not much of one for all that administrative bookkeeping stuff. I'm happiest in a room full of blinking lights, beeps and whirrs, and I'd rather create forms than fill them out <g>.

It is kind of funny that the BP keeps saying how great they are and how no one else has any problems. Apparently they have forgotten that this is not a big community. People talk, and we are most certainly not the only local business with problems on an IPO, although they are the vendor for all of them.

Meanwhile, did some testing with packet capture this afternoon, now all I have to do is figure out how to decipher it <g>. All test calls dropped as planned, too. I have now proven that if a call comes in to the remote with the AMI circuit, and is transferred to the "trouble site" it will drop. Over and over and over. BUT, if that same call is transferred to the Main site FIRST, and THEN transferred to the trouble site, the call will stay connected. OR, if the main site answers the calls for the AMI site, and then transferrs, the calls will stay connected. I am becoming more and more convinced that the AMI circuit is a big part of the problem.
 
What are your direct media path settings. I am sure you have been down this road but why not ask. maybe you could turn it off to force calls to use the main site. it uses more resources but it may keep the call up.
 
On the IP Line -> VOIP tab there is a tick box called "allow Direct media path".

This setting will allow calls between IP endpoints to require a VCM for call setup (on connection the VCM is dropped)

Kwing112000 is suggesting that you clear this setting. It will mean higher VCM use, but may be more stable

Take Care

Matt
If at first you don't succeed, skydiving is not for you.
 
Thanks Matt.

Dawn
From your remote sites can you ping another remote site? Do your remotes have the ability to connect direct to another remote site? Maybe with the main IPO holding the call the whole time it will not cause these drops untill you can get that T1 converted.

Kevin Wing
ACA- Implement IP Office
Carousel Industries
 
mattKnight, allow direct media path is unchecked for all lines, I think we did that last year trying to resolve the issue.

kwing112000, the main can ping all of the remotes, but the remotes can't ping directly (router to router).
 
ok so it is already off. that was what i was getting at. So you are already using the main to control the call from start to finish.

Kevin Wing
ACA- Implement IP Office
Carousel Industries
 
kwing112000, I'll take you're word for it :) I do know that when I did a packet capture of the test calls yesterday that there wer no conversations between the units at the source and destination. I am getting the contract for the AMI T1 to be replaced with B8ZS sometime today, and I am going to get that signed and back to ATT as fast as I can. I would be over the moon is that fixed the problem.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top