Page 1 of 1

vicibox fresh install please help

PostPosted: Fri Mar 21, 2014 6:29 pm
by sigbinme
Please help me here..

WARNING[2158]: chan_sip.c:4014 retrans_pkt: Hanging up call 4351baa018ba1ec449afce7408a714f7@115.85.1.230:5060 - no reply to our critical packet (see https://wiki.asterisk.org/wiki/display/ ... nsmissions).
[Mar 21 15:02:53] == Everyone is busy/congested at this time (1:0/0/1)
[Mar 21 15:02:53] -- Executing [626617724612800@default:3] Hangup("SIP/gs102-0000000b", "") in new stack
[Mar 21 15:02:53] == Spawn extension (default, 626617724612800, 3) exited non-zero on 'SIP/gs102-0000000b'
[Mar 21 15:02:53] -- Executing [h@default:1] AGI("SIP/gs102-0000000b", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----18-----CHANUNAVAIL----------") in new stack

Re: vicibox fresh install please help

PostPosted: Sat Mar 22, 2014 7:50 pm
by williamconley
Um ... let's see if I get this.

You just now installed ... on an OS that's four years old with vicidial code that's a full version behind (and was never formally released, it's a "between" versions codebase that was only ever Trunk).

Your post subject is "help" which gives no information about the topic being discussed.

Your subject also contains "vicibox" but your OS is Ubuntu 10.04 which is NOT a vicibox install. You either made a mistake on the OS or in using the word "Vciibox" (which is an installer that will install Vicidial on OpenSuSE, not Ubuntu, available at Vicibox.com).

And you posted enough detail to demonstrate that you are familiar with the asterisk command line and the necessary information to tell us about your system (except for the link to your installation instructions OR your vicibox installer version, either of which would have cleared up quite a bit).

LOL You're obviously trying very hard, so I'll give you the benefit of the doubt. 8-)

Which leads us to: no response to a critical packet is usually a networking problem. Could be firewall, loss of internet, carrier fail, lots of things.

But since this is a fresh install, My Advice would be to proceed to Vicibox.com and download and install the latest Vicibox, which will result in a brand new Vicidial server with the latest code and it will be very unlikely to have the error you quoted above.

There is a PDF on Vicibox.com with install instructions. Then you can switch to the Vicidial Manager's Manual (from EFLO.net). Download the Free Version, and start at page one. Don't skip anything. Do all the exercises. Bring us the page you have a problem on, share the configuration settings involved, what you did, and what you Expected to happen, and of course what actually happened. Plus the Page/Line number of the manual where you hit your pothole. And we'll walk you through it.

Happy Hunting 8-)

Re: vicibox fresh install please help

PostPosted: Mon Mar 24, 2014 4:50 am
by geoff3dmg
Code: Select all
WARNING[2158]: chan_sip.c:4014 retrans_pkt: Hanging up call 4351baa018ba1ec449afce7408a714f7@115.85.1.230:5060 - no reply to our critical packet (see https://wiki.asterisk.org/wiki/display/ ... nsmissions).


99% of the time this is caused by a firewall/NAT issue.

Re: vicibox fresh install please help

PostPosted: Mon Mar 24, 2014 9:35 am
by sigbinme
thanks for reply william and geoff3dm...
i will re.install again.. william .. this is a vicibox from opensuse... sorry i didn't mention it..

Re: vicibox fresh install please help

PostPosted: Wed Mar 26, 2014 8:04 pm
by williamconley
This would contradict your signature, unless that is a different installation?

Re: vicibox fresh install please help

PostPosted: Thu Mar 27, 2014 7:51 am
by sigbinme
sorry for the wrong signature.. william

Re: vicibox fresh install please help

PostPosted: Tue Apr 01, 2014 8:45 pm
by williamconley
NP. Just trying to get a handle on the problem so we can get you going.

Next: Assertion has been made that it is a NAT issue. You could easily refute this by stating that the server has a Public IP (ie: not a "192.168.x.x" or "10.x.x.x" IP address). On the other hand, if you DO have a private IP it is quite likely (as observed by geoff) that this issue is firewall related.

To test, you could forward all UDP 5060 and UDP 10000-25000 ports to this server (temporarily, as this will make it impossible for other SIP servers on the same private network).