30 minute cutoff

[scott2020]

Cool ! RFC 4028 timers are no longer required. I disabled session-timers on my asterisk box and the call status showed session timers to be inactive. I also made an incoming call that lasted more than 30 mins.

Very interesting. Is this just a fluke or did Tim or someone from VOIPo come out and say they definitely have taken the timers out of the mix? In the past I would get hit or miss 30 minute cutoffs with my Asterisk box. Now I am tempted to go back.

But, my GS 502 is working so well I don't really want to mess with it!

[voxabox]

BYOD'ers,
I'm happy to report that that outbound calls (to plain POT numbers) have been verified working for 30+ minute durations - thanks to the wife
ATA: SPA-1001, 3.1.19(SE), behind router with STUN, NAT keep-alive, ports: 5062,16384-16482 forwarded

02/13/09, inbound calls have been working for more than 30+ mins.
Last time I checked to call log, my wife answered "her call" and talked to her friend for 80+ mins

Cheers,
-v

[scott2020]

Cool ! RFC 4028 timers are no longer required. I disabled session-timers on my asterisk box and the call status showed session timers to be inactive. I also made an incoming call that lasted more than 30 mins.

I'd still like the official word from VOIPo on whether or not the session timers are in fact gone, or is it a coincidence that some BYOD devices are working past 30 minutes. When I was running Asterisk 1.4 I would sometimes have calls go longer than 30 minutes and sometimes not.

Scott

[bubbanc]

Did anyone get an official response on this?

[scott2020]

Not that I have heard, but with the Linksys PAP2's they suffered from the same session timer problem. In order to get those to work, from what I understand, VOIPo had to turn off the session timers. That is how I understand it but I don't know for sure and didn't get an official answer yet.
Scott

[bubbanc]

Since Voipo is now shipping PAP2T's because of shortage of GS devices, you would think they would have disabled the timers.

[Xponder1]

Tim said it was taken care of. Lets just take his word for it.

[scott2020]

Tim said it was taken care of. Lets just take his word for it.

No problem, I must have missed where he said specifically the 30 minute session timers were removed. When I was using Asterisk sometimes I would get cut off at 30 and sometimes not, so I was wondering if it was more coincidence or if the timers were indeed taken off.

[scott2020]

I moved everything back over to my Asterisk box, since people have had good luck with it. I am running Asterisk 1.4, and I was talking with my brother this morning. At exactly the 30 minute mark, my call got cut off. I got a fast busy on my end. So I don't know what people are doing to get around it or whatever, but I got cut off at exactly 30 minutes. This makes me think the session timers are on somewhere and that is why I wanted an official word whether they were enabled, disabled for some, or disabled across the board. My other trunks always work over 30 minutes so I'm not sure if it is on my end or not.

Edit: I called him back, and talked to him for 35 minutes without getting cut off. So I have no idea what is going on.

Scott

[dswartz]

Was the cutoff call initiated by you or him? I remember speculation that which end originated it mattered as far as the timers being on or not. I got irritated enough several months ago to roll out asterisk 1.6.0 and it's been stable for me.