Call waiting to Voicemail

[connervt]

I just called my house (twice) while my wife was on the phone, and was sent to my voice mail in just two rings (on my end). My "Set Ring Seconds" are set to 25 seconds.

Is it me, or did I get dumped to voicemail too quickly? I don't believe that 25 seconds passed between the time I dialed the last digit of my home number, no less when the phone began ringing.

How can I correct this, so a second incoming call can be recieved in a timely manner?

[sbradshaw]

If I'm not mistaken, it has always worked this way. I would put a request in the Feature Request thread for this change to be considered. Perhaps a separate configuration setting in the CP called "Call Waiting Ring Seconds".

[connervt]

One certainly needs more time before a call gets dumped out of call waiting to voicemail. To be polite to the caller who is currently on line, it takes a few moments of polite conversation, excusing yourself to check whom is on the other line...

[Agrajag]

I had been catching on to this lately myself and thought it was just our new phones that was the cause. Yeah, this one needs to get addressed.

[jamerican413]

I'm finding that I have the same problem. When I click over, I get a dialtone. As bad as my last service was, it was never this rude...

[abaldish]

Well that explains why when my call waiting kicks in and i get to it i have a dialtone. That is a problem that needs fixed ASAP. I for one don't like when i lose a call to nowhere land. Good thing they call my cell if i don't answer at the house. So i agree there needs to be a setting to toggle for call waiting, or on the server side set it to at least 30 secs.


Ok in case anyone is interested. I have my own BYOD and seem to have found the little bug hidden in the adapter. So i decided to give this a test using my cell to call my home, and one of my free voip account on the net to also call my home to trigger the call waiting tones. In my ATA unit there is a setting If you are using say line 1 of the adapter you need to go into the user 1 also there is a setting in there by default to 20 secs, I changed it to 60 secs and kept getting the call waiting tones it is listed as this:

Cfwd No Ans Delay:20
Change the above to 60 worked for me.

Kept getting the call waiting tones about 4 times then i hit the flash button and behold i was talking to my self and bounce back and forth. Yea allot of time to kill here on my side so once in a while i call myself to see if i am there or not lol.

Well after doing all the above, Guess what the problem came back today. My wife was on the phone my sister tried calling in, Wife never got the call waiting tone at all. then it forwarded to my cell phone.


Now to figure why it went to the cell phone and no beeps for the call waiting.

Was set using Ring Waveform:Sinusoid Now going to try Trapezoid.

Can't remember but i think the default is Trapezoid and somewhere i changed it to Sinusoid, So with it back to Trapezoid will tinker some more this evening if i get a chance and see if it starts working correctly.

Ok just testing again and this is what i see. Regardless if the time i set above in the Cfwd No Ans Delay it doesn't even look at that part of it, as in 30sec it went straight to voicemail so not sure if there is a setting somewhere on a BYOD or not for that part of it, or if there is a setting at Viatalk to set the Callwait timeout. As for changing back to the Trapezoid not sure if that cured the problem i had today when the wife didn't get a call waiting tone or not.

Well the last update on this subject from me on the matter. Was online with Linksys support. it appears there is no where in the device to set the call waiting timers. So i am guessing this is a telco issue as i remember even with Verizon when i did have them 3 yrs ago the call waiting was only for a certain amount of time. Talk to tech support at Viatalk also on the matter. And all they do is pass the info to the device they have no way of setting a timer on it. So until there is a way to configure the timer for call waiting to keep ringing just stuck with the ole 30 secs only.

[Agrajag]

Okay, a bit more on this one. I called support and reached my favorite rep there as luck would have it. I bounced this issue off the rep and the reply was, "That's something you can set in the adapter."

Oh, great! Under Advanced and SIP there are several generic settings that aren't descriptive at all. The rep was pretty sure that the call waiting ring timer is stored as "SIP Timer B". The only concern is that its default is 32 as in 32 seconds and that seems pretty long to me. I had it changed to 45 so we'll see what happens. At least it's something we can access and play around with. Now we need to find out what Timers F, D and J do.

[bubbanc]

Okay, a bit more on this one. I called support and reached my favorite rep there as luck would have it. I bounced this issue off the rep and the reply was, "That's something you can set in the adapter."

Oh, great! Under Advanced and SIP there are several generic settings that aren't descriptive at all. The rep was pretty sure that the call waiting ring timer is stored as "SIP Timer B". The only concern is that its default is 32 as in 32 seconds and that seems pretty long to me. I had it changed to 45 so we'll see what happens. At least it's something we can access and play around with. Now we need to find out what Timers F, D and J do.

Let us know what the fix is. All of my SIP Timers are set to 32, so let us know what they changed. I haven't run into this yet, but I'm sure my wife will and she'll come screaming to me!

[voxabox]

Okay, a bit more on this one. I called support and reached my favorite rep there as luck would have it. I bounced this issue off the rep and the reply was, "That's something you can set in the adapter."

Oh, great! Under Advanced and SIP there are several generic settings that aren't descriptive at all. The rep was pretty sure that the call waiting ring timer is stored as "SIP Timer B". The only concern is that its default is 32 as in 32 seconds and that seems pretty long to me. I had it changed to 45 so we'll see what happens. At least it's something we can access and play around with. Now we need to find out what Timers F, D and J do.

here ya go http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.base.doc/info/aes/ae/rsip_reftimesumm.html
and here http://rfc.net/rfc3261.html

[Agrajag]

What the hell is "INVITE transaction timeout timer"? That's what's listed as Timer B in the above link. The second link describes everything but in such technical detail that I can't focus at this late hour on it.

[voxabox]

What the hell is "INVITE transaction timeout timer"? That's what's listed as Timer B in the above link. The second link describes everything but in such technical detail that I can't focus at this late hour on it.
sorry, I was in a hurry
the "INVITE transaction timeout timer" dictates when the "INVITE transaction" is to timeout - this is to guard against transport, network latency/fault
It has nothing to do with how long an unanswered calls being forwarded into VM
forwarding of unanswered calls into VM is handled via asterisk (configurable in extensions.conf - I think)