Registration failure


#1

I have a Asterisk setup as a PBX registered with Broadvoice. On the inside, my analog phones are registered with it via a Sipura SPA3000 ATA.
It appears that about once a day Asterisk “looses” registration with Broadvoice. It is rather tough to debug because Asterisk doesn’t print much usefull information even at a log level 5. The only regularity I think exists is that the registration appears to working fine when there are no active calls. If there are active calls Asterisk seems to stay registered. I wonder if there is a problem if registration happens to expire during an active SIP call.
Has anybody seen anything similar? I have Asterisk version 1.0.5.

Greg


#2

Its probably Broadvoice and their crappy service.


#3

A similar behavior is found on 1.0.7 of Asterisk@home and the system uses a Broadvoice Sip.
The log is filling with (/var/log/asterisk/full) -
May 17 20:26:09 DEBUG[2316]: Manager received command 'Command’
May 17 20:26:09 DEBUG[2316]: Manager received command 'Command’
May 17 20:26:24 DEBUG[2316]: Scheduled a registration timeout # 1314
May 17 20:26:24 DEBUG[2316]: Stopping retransmission on ‘3d1b58ba507ed7ab2eb141f241b71efb@127.0.0.1’ of Request 532: Found
May 17 20:26:24 DEBUG[2316]: Registration successful
May 17 20:26:24 DEBUG[2316]: Cancelling timeout 1314
May 17 20:26:40 DEBUG[2316]: Scheduled a registration timeout # 1317
May 17 20:26:40 DEBUG[2316]: Stopping retransmission on ‘3d1b58ba507ed7ab2eb141f241b71efb@127.0.0.1’ of Request 533: Found
May 17 20:26:40 DEBUG[2316]: Registration successful
May 17 20:26:40 DEBUG[2316]: Cancelling timeout 1317

Anybody know what this mean?


#4

So I guess upgrading to 1.0.7 will not resolve the problem. I was hoping that it would be resolved already.

Have you noticed any regularities as to when the registration fails? Does it have to do with calls being active at the some time? I noticed that * manages to stay registered if there are no calls going.

BTW, how did you get the DEBUG statements to show up in the log? I started * with 14 -v and about 5 -d it sill prints only NOTICE and WARNING statements.


#5

The debug info appears in the log without my intervention. The system is booted, asterisk runs, and the log fills with that info. Asterisk starts automatically.

BTW, I’ve noticed several strange things using Broadvoice. Often, if a second call immedately follows a previous call, allison says “no lines are available”.
Secondly, Broadvoice billing. The web interface displays Instate calls within the home exchange as charged. State to state calls aren’t. I thought it was the other way around. The web interface nice but may be faulty.