30 minute cutoff

**dswartz** · 01-01-2009 02:46 PM

Originally Posted by Xponder1

Well the softphone did work and it was not just once. I checked my call log and there are at least 5 calls over 30 minutes from the softphone. I have opened a ticket.

Something else weird I noticed last night. The mac address printed on this adapter is off by exactly one digit. The last digit was off by one number.

Well, half the mystery is solved; from what I can find online, x-lite implements the session timer feature

**voxabox** · 01-01-2009 03:01 PM

Originally Posted by Xponder1

I am using the device they shipped me that I received yesterday and its cutting calls off at exactly 29.5 minutes. I just sent a email to support. Odd because before I hooked up this device I was using X-Lite to make calls and was on the phone 90 minutes with no problem except a slight bit of noise on the line and the person on the other end if out of state saying they heard a echo of some kind (odd since I was using a headset).

with VOIPo supplied ATA (HT-502/HT-286), you should not experience the 30 min. cut off

I see some possibilities:

your ATA is improperly provisioned
your ATA is not been automatically provisioned by VOIPo

**Xponder1** · 01-01-2009 03:13 PM

Originally Posted by voxabox

with VOIPo supplied ATA (HT-502/HT-286), you should not experience the 30 min. cut off

I see some possibilities:

your ATA is improperly provisioned
your ATA is not been automatically provisioned by VOIPo

I think #1 is the answer. Perhaps because I was using the softphone before I got the ATA.

**burris** · 01-01-2009 03:19 PM

These are the settings on my 502 relating to call timing. Don't know if this is relevant. All of mine are set to no..

Caller Request Timer: No Yes (Request for timer when making outbound calls)
Callee Request Timer: No Yes (When caller supports timer but did not request one)
Force Timer: No Yes (Use timer even when remote party does not support)

**voxabox** · 01-01-2009 09:21 PM

Originally Posted by burris

These are the settings on my 502 relating to call timing. Don't know if this is relevant. All of mine are set to no..

Caller Request Timer: No Yes (Request for timer when making outbound calls)
Callee Request Timer: No Yes (When caller supports timer but did not request one)
Force Timer: No Yes (Use timer even when remote party does not support)

AFIAK, these settings should do the trick (for VOIPo openser configuration)

**Montano** · 01-12-2009 05:10 PM

I'm very happy to report that I made a 45 minute call today !! No more 30 minute cutoff

Is Voipo a great company or what !?!?

**Xponder1** · 01-12-2009 05:19 PM

Originally Posted by Montano

I'm very happy to report that I made a 45 minute call today !! No more 30 minute cutoff

Is Voipo a great company or what !?!?

Yes they are. I think the service is great.
I can not wait to see what happens next. I have had the service less than a month and despite a few minor problems I am really happy with the product. I can not wait to see what happens next. Even in my short time here I have seen things continue to change for the better.

Thank you Tim and all the staff for your hard work and dedication.

**voxabox** · 01-12-2009 05:18 PM

Good news, but
Need to further elaborate on equipment, call, server, etc

**Montano** · 01-12-2009 05:24 PM

Originally Posted by voxabox

Good news, but
Need to further elaborate on equipment, call, server, etc

PAP2T, sip.voipwelcome, local call.

**zcnkac** · 01-12-2009 05:50 PM

Session timers are enabled only on incoming calls. Please test incoming calls to be sure of the cutoff.

I use Asterisk 1.4, and I manually backported session timer support from the 1.6 branch (digium bug id 10665). If people are interested, I can provide the compiled chan_sip.so and also the merged source file. Overwriting chan_sip.so in /usr/lib/asterisk/modules/ is enough (a restart of asterisk or the system is not required).