VoIP Mailing List Archives

[nicolas at medularis.com]

Hi,

Today I ran out of credit in one of my voip providers. When this happened, all my outgoing calls started failing with hangup cause NETWORK_OUT_OF_ORDER. Once I got some more credit, the calls kept failing. I restarted freeswitch and then everything worked fine again.

Unfortunately this is not something I'd like to reproduce, and the only thing I have is the logs (no SIP trace). But I was wodering if someone here has had a similar experience or could tell if this is plausible or even likely to happen.

Another part of the platform I'm running, runs on Asterisk, using the same voip providers, nevertheless the calls originating there only failed during the no credit period, and began working again automatically as soon as credit was added to the account.

Thanks,

Nicolas

[brian at freeswitch.org]

Open a jira with everything you can provide.. I'll try my best to
reproduce the issue.

/b

On Jul 17, 2009, at 3:35 PM, Nicolas Brenner wrote:

[nicolas at medularis.com]

A little bit more info:

When the calls failed, the following was recorded in the log:

2009-07-17 15:19:07.880175 [ERR] switch_ivr_originate.c:1495 Cannot create outgoing channel of type [sofia] cause: [NETWORK_OUT_OF_ORDER]
2009-07-17 15:19:07.880175 [DEBUG] switch_ivr_originate.c:2123 Originate Resulted in Error Cause: 38 [NETWORK_OUT_OF_ORDER]
2009-07-17 15:19:07.880175 [WARNING] mod_spidermonkey.c:3013 Cannot Create Outgoing Channel! [{ignore_early_media=true,originate_timeout=30,execute_on_answer='sched_hangup +30 ALLOTED_TIMEOUT'}sofia/gateway/mygateway/005698793046]
2009-07-17 15:19:07.880175 [NOTICE] new_energizer_async.js:15 *********** CAUSE: NETWORK_OUT_OF_ORDER ***********
2009-07-17 15:19:34.158980 [NOTICE] sofia_reg.c:319 Registering mygateway
2009-07-17 15:19:34.294518 [ERR] sofia_reg.c:1445 mygateway Registration Failed with status Operation has no matching challenge  [904]. failure #37
2009-07-17 15:19:34.365065 [WARNING] sofia_reg.c:348 mygateway Failed Registration, setting retry to 190 seconds.

I searched for the "Registration Failed with status Operation has no matching challenge" error on the list, and someone else had a similar issue, but apparently it had something to do with NAT, and in this case there's no NAT involved. Anyway, I'm running a rev 13973 so I'll update to the latest svn rev and hope it doesn't happen again.

On Fri, Jul 17, 2009 at 4:35 PM, Nicolas Brenner <nicolas@medularis.com (nicolas@medularis.com)> wrote: