search

Sunr1ses / google-voice-sipsorcery-dialplans

Automatically exported from code.google.com/p/google-voice-sipsorcery-dialplans
1 stars 0 forks source link

Calls Disconnect After 5:03 #65

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1.  Anytime I receive or dial a call it works fine, but I am disconnected after 
5 min 03 sec.

What is the expected output? What do you see instead?
Not really a relevant question

What version of the product are you using? On what operating system?
XLite - Sipsocery (simple dial plan) - SipGate 
Win7 64 bit

Please provide any additional information below.

Original issue reported on code.google.com by danielar...@gmail.com on 16 Jun 2010 at 8:35

GoogleCodeExporter commented 9 years ago 
I've done some troubleshooting, including switching to the complex plan.  I 
still have the same problem.  After a little more than 5 minutes calls 
disconnect.

In sipsocery it says "remote end hungup".  I'd appreciate any help!

Original comment by danielar...@gmail.com on 16 Jun 2010 at 10:05

GoogleCodeExporter commented 9 years ago 
Did some more googling and this fixed my problem.

http://www.google.com/support/forum/p/voice/thread?tid=4f0b0c48c00732a9&hl=en

Specifically this post

"I was having the same problem. The 5 minute limit didn't occur when receiving 
calls through gizmo5 so it had to be x-lite (using 4.0 beta). Researched x-lite 
settings and listened to movie theater schedules many many times while testing 
calls and got mine working. Try this:
x-lite > Account Settings > Advanced
In the "Timers" section, select "Enable session timers" and leave "Session 
timer pref." at NONE.

Just listened to another 8 minutes, 27 seconds of movie listings. Looks good to 
me!"

Perhaps that should be added to the wiki?

Original comment by danielar...@gmail.com on 16 Jun 2010 at 10:44

GoogleCodeExporter commented 9 years ago 
I hope Steve will notice this thread and add it to the Wiki. I just wanted to 
point out that Sipsorcery aborts dialplans upon successful connection of a call 
(sys.Dial returned code 200 / OK) and therefore, a dialplan can't possibly 
cause an issue like this.

Original comment by mte...@gmail.com on 17 Jun 2010 at 4:29