PDA

View Full Version : Calls drop at exactly 29.5 minutes using provided ATA



Xponder1
01-01-2009, 06:37 PM
There is already a thread about this in the BYOD but since this is not a problem that has anything to do with BYOD (and I wonder if the staff even read that section ) I thought I would start a thread here.

http://forums.voipo.com/showthread.php?p=7904#post7904
Is the original thread on the problem. I have a trouble ticket submitted and I am waiting for a reply.

This like several other calls was made using X-Lite while I was waiting on my ATA to be shipped to me.
13:08 90. 0.000
There were several calls made longer than 30 minutes.

Now yesterday I received the provided ATA so I turned off X-Lite and installed the ATA. Since then if I make a call and it gets to 29.5 minutes the call will drop with a fast busy.
Examples
13:15 29.5 0.000
12:44 29.5 0.000

I would be interested in hearing if anyone else using the provided hardware is having this problem and if anyone knows how to fix it.

Thanks,

fisamo
01-02-2009, 11:27 AM
Does your ATA have the correct firmware version? IIRC, some of the ATAs were getting a newer version of firmware than is currently supported by Voipo.

burris
01-02-2009, 12:07 PM
Does your ATA have the correct firmware version? IIRC, some of the ATAs were getting a newer version of firmware than is currently supported by Voipo.

You bet....the upgraded software that mine had caused me many problems.

1.0.1.8 seems to be the version that works for me without a flaw..

Xponder1
01-02-2009, 09:16 PM
It has the version that came on it. Software Version: Program-- 1.0.1.8

christcorp
01-02-2009, 11:49 PM
I was wondering. This would be a GREAT FEATURE for mother-in-laws who call a lot. Less than 30 minutes later and you know the agony is over. And we can blame Tim and VoipO for it!!! Tim; let me know if this costs extra!!!!! Mike.....

Xponder1
01-03-2009, 09:25 PM
I was wondering. This would be a GREAT FEATURE for mother-in-laws who call a lot. Less than 30 minutes later and you know the agony is over. And we can blame Tim and VoipO for it!!! Tim; let me know if this costs extra!!!!! Mike.....

LOL your mother -in-law must not be as bad as mine. If I blame Tim she would hunt him down. :p

I am being sent another ATA for the noise issue I discussed in another thread. We will see if that resolves this issue for me too. I would be interested in knowing if anyone else using the provided ATA has this disconnect problem.

sanchito
01-04-2009, 06:26 PM
Yes, this happened to me a couple of weeks ago. It hasn't happened since, but I haven't made any more calls that were longer than 29 minutes.

Vumes
01-04-2009, 06:31 PM
I just tried it last night without an problems past the 30 minute mark. I am also running 1.0.1.8.

Xponder1
01-04-2009, 09:01 PM
I just tried it last night without an problems past the 30 minute mark. I am also running 1.0.1.8.

Good to hear

When it comes in I am just going to dial my other phone and leave it off the hook for about 45 minutes and then check and see if it dropped it.

Vumes
01-04-2009, 11:31 PM
Exactly what I did. Dialed from one phone to the other, put them both on mute, and put them down on my desk until around the 37 minute mark. ;)

NY Tel Guy
01-07-2009, 11:25 AM
Ok this morning at 11:02 I was on an incoming call from Boston to my 212 voipo number. I had simul-ring turned on. I was speaking to the person successfully on my cell (the only target simulring number) and bingo! at the 30 minute mark, the call disconnected so it cannot be a function of the terminal adapter since the call was not connected through the adapter.
Should I file a ticket or not?

To file or not file....that is the question.
Whether 'tis nobler in the mind to suffer
The slings and arrows of outrageous cutoffs,
Or to take arms against a sea of calls,
And by submitting a ticket, end them?

dswartz
01-07-2009, 11:39 AM
Oh my. It sounds almost like the server-side code that is doing the RFC4028 stuff (session timers) is still running, and tears down the connection when no reply comes back. If it is simul-ringing your voipo adapter and the cellphone, it's possible (maybe?) that the voipo server starts the session timer. When your ata doesn't answer, but your cell does, one would think the tiimer would be cancelled. Or maybe it is erroneously starting the timer in the first place. Sounds like a ticket is definitely in order...

Montano
01-07-2009, 03:37 PM
Maybe Voipo will do away with the rfc4028 timer and everyone will be happy ;)

Xponder1
01-07-2009, 10:51 PM
They must have done something because my calls do not cut off anymore at 29.5 using the ATA. I dunno about the other.

Montano
01-08-2009, 06:56 AM
I'll try later today on my BYOD and see if anything has changed there.

darylo
01-10-2009, 01:34 PM
My calls are now dropping at 11 min and 15 sec. I submitted a ticket.

scott2020
01-11-2009, 08:19 AM
Maybe Voipo will do away with the rfc4028 timer and everyone will be happy ;)

I can't remember, but what is the benefit to the timer? Does it clean up broken registrations or something?

burris
01-11-2009, 08:37 AM
I can't remember, but what is the benefit to the timer? Does it clean up broken registrations or something?

This is a bit dated, but may explain its purpose..

http://rfc.sunsite.dk/rfc/rfc4028.html

gbh2o
01-11-2009, 06:36 PM
Something must surely have changed since I just placed a 32:41 minute call through the * 1.4 box and it was uninterrupted.

The bad news is I have mysterious [jerks(?)] from 93.190.137.247 and 85.25.85.70 repeatedly coming into the * box via SIP for whatever purpose... guess they just have to try my default "s" destination out! :D Just in case anyone else here worries about or watches for such events!

VOIPoTim
01-12-2009, 01:02 AM
Is anyone still seeing issues with calls dropping?