Phone Disconnects at 1 hour

jtucker
Posts: 11
Member Since:
2008-10-24

I have 2 offices that are using trixbox 2.6.2 and both are complaining about not being able to stay on the phone longer that 1 hour. I was able to test and confirm that if you make the call out it will disconnect or the audio goes completely out on both phones internal and external and you have to hang up. But if they call into the trixbox system you can stay on longer than a hour. Here is the copy of the log at when user complained about the phone dropping. Looked at the call monitor for his extension and it said he was on the phone for 3613 seconds. He started at 8:56:06. I scrolled up to 9:33 and then searched for the sip/103 and could not find anything until the phone disconnected nor did I see anything right before it about RTP timeout or lack of response or anything suggesting disconnection. I had seem something similar that mentioned about adjusting the rtp timeout in the sip conf but I am not seeing anything in the log about it. These are Polycom phones and ranging from 330, 430, 550, and 650, all of which will disconnect. Ideas on where to check. Thanks

[Nov 3 09:56:19] VERBOSE[8118] logger.c: == Spawn extension (macro-dialout-trunk, s, 19) exited non-zero on 'SIP/103-085c1378' in macro 'dialout-trunk'
[Nov 3 09:56:19] VERBOSE[8118] logger.c: == Spawn extension (macro-dialout-trunk, s, 19) exited non-zero on 'SIP/103-085c1378'
[Nov 3 09:56:19] VERBOSE[8118] logger.c: -- Executing [h@macro-dialout-trunk:1] Macro("SIP/103-085c1378", "hangupcall|") in new stack
[Nov 3 09:56:19] VERBOSE[8118] logger.c: -- Executing [s@macro-hangupcall:1] ResetCDR("SIP/103-085c1378", "w") in new stack
[Nov 3 09:56:19] DEBUG[8118] app_macro.c: Executed application: ResetCDR
[Nov 3 09:56:19] VERBOSE[8118] logger.c: -- Executing [s@macro-hangupcall:2] NoCDR("SIP/103-085c1378", "") in new stack
[Nov 3 09:56:19] DEBUG[8118] app_macro.c: Executed application: NoCDR
[Nov 3 09:56:19] VERBOSE[8118] logger.c: -- Executing [s@macro-hangupcall:3] GotoIf("SIP/103-085c1378", "1?skiprg") in new stack
[Nov 3 09:56:19] VERBOSE[8118] logger.c: -- Goto (macro-hangupcall,s,6)
[Nov 3 09:56:19] DEBUG[8118] app_macro.c: Executed application: GotoIf
[Nov 3 09:56:19] VERBOSE[8118] logger.c: -- Executing [s@macro-hangupcall:6] GotoIf("SIP/103-085c1378", "1?skipblkvm") in new stack
[Nov 3 09:56:19] VERBOSE[8118] logger.c: -- Goto (macro-hangupcall,s,9)
[Nov 3 09:56:19] DEBUG[8118] app_macro.c: Executed application: GotoIf
[Nov 3 09:56:19] VERBOSE[8118] logger.c: -- Executing [s@macro-hangupcall:9] GotoIf("SIP/103-085c1378", "1?theend") in new stack
[Nov 3 09:56:19] VERBOSE[8118] logger.c: -- Goto (macro-hangupcall,s,11)
[Nov 3 09:56:19] DEBUG[8118] app_macro.c: Executed application: GotoIf
[Nov 3 09:56:19] VERBOSE[8118] logger.c: -- Executing [s@macro-hangupcall:11] Hangup("SIP/103-085c1378", "") in new stack
[Nov 3 09:56:19] VERBOSE[8118] logger.c: == Spawn extension (macro-hangupcall, s, 11) exited non-zero on 'SIP/103-085c1378' in macro 'hangupcall'
[Nov 3 09:56:19] VERBOSE[8118] logger.c: == Spawn extension (macro-hangupcall, s, 11) exited non-zero on 'SIP/103-085c1378'



jdwebcc
Posts: 149
Member Since:
2006-09-27
Could it be the provider

Are you using a VOIP provider or PSTN ? Did you try calling from one extension to another -- putting one on speaker and the other pressing the hold button... and seeing if it is your box doing it or the provider.. could help narrow it down.

If this reproduces the issue - then it will be easier to trace.

JD

--

Jason S Derr, JDWEB.cc LLC
Creator of ASR Manager



jtucker
Posts: 11
Member Since:
2008-10-24
Interoffice Call

Interoffice call lasted for 4354 seconds. Roughly 1 hour 13 minutes. During the call the phone was placed on hold, muted, and eventually a conversation was put through and there were no issues. Input from log file. I am using Broadvox as my voip provider.

[Nov 4 09:10:52] VERBOSE[30514] logger.c: == Spawn extension (macro-dial, s, 7) exited non-zero on 'SIP/114-b6a6c5e8' in macro 'dial'
[Nov 4 09:10:52] VERBOSE[30514] logger.c: == Spawn extension (macro-dial, s, 7) exited non-zero on 'SIP/114-b6a6c5e8' in macro 'exten-vm'
[Nov 4 09:10:52] VERBOSE[30514] logger.c: == Spawn extension (macro-dial, s, 7) exited non-zero on 'SIP/114-b6a6c5e8'
[Nov 4 09:10:52] VERBOSE[30514] logger.c: -- Executing [h@macro-dial:1] Macro("SIP/114-b6a6c5e8", "hangupcall") in new stack
[Nov 4 09:10:52] VERBOSE[30514] logger.c: -- Executing [s@macro-hangupcall:1] ResetCDR("SIP/114-b6a6c5e8", "w") in new stack
[Nov 4 09:10:52] DEBUG[30514] app_macro.c: Executed application: ResetCDR
[Nov 4 09:10:52] VERBOSE[30514] logger.c: -- Executing [s@macro-hangupcall:2] NoCDR("SIP/114-b6a6c5e8", "") in new stack
[Nov 4 09:10:52] DEBUG[30514] app_macro.c: Executed application: NoCDR
[Nov 4 09:10:52] VERBOSE[30514] logger.c: -- Executing [s@macro-hangupcall:3] GotoIf("SIP/114-b6a6c5e8", "1?skiprg") in new stack
[Nov 4 09:10:52] VERBOSE[30514] logger.c: -- Goto (macro-hangupcall,s,6)
[Nov 4 09:10:52] DEBUG[30514] app_macro.c: Executed application: GotoIf
[Nov 4 09:10:52] VERBOSE[30514] logger.c: -- Executing [s@macro-hangupcall:6] GotoIf("SIP/114-b6a6c5e8", "1?skipblkvm") in new stack
[Nov 4 09:10:52] VERBOSE[30514] logger.c: -- Goto (macro-hangupcall,s,9)
[Nov 4 09:10:52] DEBUG[30514] app_macro.c: Executed application: GotoIf
[Nov 4 09:10:52] VERBOSE[30514] logger.c: -- Executing [s@macro-hangupcall:9] GotoIf("SIP/114-b6a6c5e8", "1?theend") in new stack
[Nov 4 09:10:52] VERBOSE[30514] logger.c: -- Goto (macro-hangupcall,s,11)
[Nov 4 09:10:52] DEBUG[30514] app_macro.c: Executed application: GotoIf
[Nov 4 09:10:52] VERBOSE[30514] logger.c: -- Executing [s@macro-hangupcall:11] Hangup("SIP/114-b6a6c5e8", "") in new stack
[Nov 4 09:10:52] VERBOSE[30514] logger.c: == Spawn extension (macro-hangupcall, s, 11) exited non-zero on 'SIP/114-b6a6c5e8' in macro 'hangupcall'
[Nov 4 09:10:52] VERBOSE[30514] logger.c: == Spawn extension (macro-hangupcall, s, 11) exited non-zero on 'SIP/114-b6a6c5e8'
[Nov 4 09:11:00] VERBOSE[31275] logger.c: -- Nobody picked up in 21000 ms



AxelLotte
Posts: 18
Member Since:
2006-06-07
I had a similar problem

It was my provider. They would disconnect after 1 hour. I asked and they removed the restriction.

Good luck.



jtucker
Posts: 11
Member Since:
2008-10-24
So i finally got them to run

So i finally got them to run the packet capture for the whole hour. They say that I quit sending media after 1 hour and I saw the in the capture this occurs but not sure why, obviously that is why I am here.



gianthobbit
Posts: 39
Member Since:
2007-03-19
Check zapata.conf. Change

Check zapata.conf. Change resetinterval to "never". Reboot server.

Test it by making a call lasting over 1 hour. If it continues after 1 hour then that was causing it.



jtucker
Posts: 11
Member Since:
2008-10-24
zapata change

This is completely sip. Well IAX connect to the other building but outs our sip trunk. So I question the change for the zapata.conf



antidelldude
Posts: 287
Member Since:
2009-05-18
So, Let's see your trunk

So, Let's see your trunk settings to Broadvoice, x out some of the user/password please. What is the brand/model of the firewall on your main trixbox? What about running a packet capture program your self for that entire hour?

--

Regards,
Jon
Please respond if your problem was ever solved, and how you solved it. It'll help the next guy.



jtucker
Posts: 11
Member Since:
2008-10-24
trunk

peer details
host=broadvox host
username=xxxxxx
secret=xxxxxx
type=peer
port=5060
nat=no
fromdomain=xxxxxxxxxx
fromuser=xxxxxxxxxxxxx
insecure=invite,port
context=default

incoming settings
secret=xxxxxxxxxx
type=friend
context=from-trunk
fromuser=xxxxxxxxxxxx
canreinvite=no
insecure=very
nat=no
host=xxxxxxxxx
username=xxxxxxxxxxxx

The router is a intertex.



jtucker
Posts: 11
Member Since:
2008-10-24
configs

No body has anything else to say? Don't tell me that I need to just pony up and actually ask support. There has got to be somebody out there that is aware of how to fix this issue.



SkykingOH
Posts: 9540
Member Since:
2007-12-17
It's a setting at your

It's a setting at your carrier.

--

Scott

aka "Skyking"



danbronx
Posts: 12
Member Since:
2009-07-26
I would say check your carrier as well

I had something similar with Broadvoice my fix was change proxy settings from DC to ATL and that fixed the issue. See if your carrier has several connecting SIP proxies for you to registar Good luck



jtucker
Posts: 11
Member Since:
2008-10-24
Can I say craptastic hardware.

Fixed it a couple of days ago. Was a setting with my router for "timeout before client registration" and it was set at one hour. Score one for the sip based router.



Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.