gv-sipsorcery-xlite dropped calls at around 4-5min into conv

[GoogleCodeExporter]

Hi there, I use x-lite with the sipsorcery-gv-gizmo5 complex dialplan.  but at 
around 4-5min into the conversation always get disconnected.  what could 
possibly be causing this??

below is the sipsorcery console output with the private info removed:
could this be a biding issue? and if so, how do i address it? TY

DialPlan 16:51:37:843 sip1: New call from tcp:24.xx.xx.xx:53144 successfully 
authenticated by digest.
DialPlan 16:51:37:874 sip1: Using dialplan default for Out call to 
sip:8003251999@sipsorcery.com.
NewCall 16:51:37:890 sip1: Executing script dial plan for call to 8003251999.
DialPlan 16:51:37:984 sip1: ** Call from "sipsorcery.com" 
<sip:xxxxx@sipsorcery.com>;tag=3c063f4b to 8003251999 **
DialPlan 16:51:37:984 sip1: Local time: 06/22/2010 12:51
DialPlan 16:51:37:999 sip1: Number in ENUM format: 18003251999
DialPlan 16:51:38:031 sip1: SDP on GoogleVoiceCall call had RTP socket mangled 
from 192.168.2.2:45376 to 24.xx.xx.xx:45376.
DialPlan 16:51:38:031 sip1: UAS call progressing with Ringing.
DialPlan 16:51:38:031 sip1: Logging into google.com for xxxxxxx@gmail.com.
DialPlan 16:51:38:093 sip1: Google Voice pre-login page loaded successfully.
DialPlan 16:51:38:093 sip1: GALX key xxxxxxxxxxx successfully retrieved.
DialPlan 16:51:38:906 sip1: Google Voice home page loaded successfully.
DialPlan 16:51:38:937 sip1: Call key xxxxxxxxxxxxxxxx successfully retrieved 
for xxxxxxxxx@gmail.com, proceeding with callback.
DialPlan 16:51:38:952 sip1: SIP Proxy setting application server for next call 
to user xxxxxx as udp:69.59.142.213:5070.
DialPlan 16:51:38:999 sip1: Google Voice Call to 18003251999 forwarding to 
747xxxxxxx successfully initiated, callback timeout=30s.
DialPlan 16:51:39:437 sip1: SIP Proxy directing incoming call for user xxxxx to 
application server udp:69.59.142.213:5070.
DialPlan 16:51:39:452 sip1: Google Voice Call callback received.
DialPlan 16:51:39:452 sip1: Answering client call with a response status of 200.
DialPlan 16:51:39:531 sip1: Google Voice Call was successfully answered in 
1.50s.
DialPlan 16:51:39:968 sip1: Dial plan execution completed with normal clearing.
ContactRegisterInProgress 16:56:03:574 sip1: Checking SIP Provider registration 
for sipgate.
ContactRegisterInProgress 16:56:03:574 sip1: Sending initial register for 
sindra and sipgate to udp:204.155.28.10:5060.
ContactRegisterInProgress 16:56:03:605 sip1: Initiating registration for xxxxxx 
on sip:sipgate.com.
ContactRegistered 16:56:04:090 sip1: Contact successfully registered for sindra 
on sip:sipgate.com, expiry 600s.
Registrar 16:56:43:558 sip1: Authentication required for xxxxx@sipsorcery.com 
from tcp:24.xx.xx.xx:53762.
Registrar 16:56:43:995 sip1: Binding update request for xxxxxx@sipsorcery.com 
from tcp:24.xx.xx.xx:53762, expiry requested 3600s granted 3600s.
RegisterSuccess 16:56:44:027 sip1: Registration successful for 
xxxxxx@sipsorcery.com from tcp:24.xx.xx.xx:53762 
(proxy=tcp:69.59.142.213:5060), expiry 3600s.
BindingExpired 16:56:44:495 sip1: Binding expired by client for 
xxxx@sipsorcery.com from tcp:24.xx.xx.xx:53762.
RegisterSuccess 16:56:44:542 sip1: Registration successful for 
xxxxx@sipsorcery.com from tcp:24.xx.xx.xx:53762 (proxy=tcp:69.59.142.213:5060), 
expiry -1s.
BindingInProgress 16:56:44:902 sip1: New binding request for 
xxxxx@sipsorcery.com from tcp:24.xx.xx.xx:53762, expiry requested 3600s granted 
3600s.
RegisterSuccess 16:56:44:933 sip1: Registration successful for 
xxxxx@sipsorcery.com from tcp:24.xx.xx.xx:53762 (proxy=tcp:69.59.142.213:5060), 
expiry 3600s.
DialPlan 16:56:45:464 sip1: Matching dialogue found for BYE to 
sip:69.59.142.213:5060;transport=tcp from udp:69.59.142.213:5060.

Original issue reported on code.google.com by vitaly.s...@gmail.com on 22 Jun 2010 at 5:05

[GoogleCodeExporter]

ok nvrmd, sorted.  it was a problem in a dial plan - one of the lines had a 
line-break at a wrong place...

Original comment by vitaly.s...@gmail.com on 22 Jun 2010 at 5:40

[GoogleCodeExporter]

Thanks for letting us know you got it worked out.

Original comment by easter...@gmail.com on 24 Jun 2010 at 12:38

• Changed state: Invalid