problems with registering

[blwegrzyn]

Hello,

I have two broadvoice accounts.
Lately, very often my broadvoice accounts are in unregistered state.
When I log into asterisk I see:

voip*CLI> sip show registry
Host Username Refresh State
sip.broadvoice.com:5060 yyy@s 120 Request Sent
sip.broadvoice.com:5060 xxx@s 120 Request Sent

xxx and yyy are my ohone numbers,

when I do tcpdump on my router, I see only packets comming out my router to broadvoice but nothing comming back on port 5060

23:06:41.398952 IP adsl-myip.dsl.chcgil.ameritech.net.5060 > 147.135.12.128.5060: UDP, length 411
23:06:42.306975 IP adsl-myip.dsl.chcgil.ameritech.net.5060 > 147.135.12.128.5060: UDP, length 411
23:06:42.398951 IP adsl-myip.dsl.chcgil.ameritech.net.5060 > 147.135.12.128.5060: UDP, length 411
23:06:44.306932 IP adsl-myip.dsl.chcgil.ameritech.net.5060 > 147.135.12.128.5060: UDP, length 411
23:06:44.398921 IP adsl-myip.dsl.chcgil.ameritech.net.5060 > 147.135.12.128.5060: UDP, length 411

the only way to get registered is to change the proxy in the host file,
after some time same story happens, I am in register sent state and nothing is coming back from the broadvoice, changing proxy in the host file again solves problem,

For me it sounds like broadvoice servers does not want talk with my servers for some unknown reason,

I called them but their support is unqualified, and I could not get any answer,

Any ideas?
Did anyone experience something like that?

thx


Bartosz Wegrzyn

[alexdds]

you know they probably are unqualified to setup your asterisk, but I have a feeling the problem can be fixed at your end by a setting.
I originally set up my spa2100 adaptor using the voxilla wizard and had problems with the device not being registered on the network almost everyweek. Later my device stopped working, I managed to fix the problem by resetting to factory default and reflashing the firmware. I had forgotten my sip password so and web portal loggin info, so I called support. A woman tech support answered the phone and reset my webportal and gave me my sip password. We went throught the settings again(after I used the voxilla wizard with the wrong password) and she made quite a few changes on the line tab including time out info etc... there was significant change from what I found on the voxilla wizard for broadvioce configuration. Since then my registration problems have disappeared. So maybe you can get these setting from them and see if it works.

[dchris]

Hi, i have the same problem with my SPA400. I followed all instructions in order to set it up with trixbox. I only managed to make calls. I cannot recieve any. It cannot register!!!! Do you guys have any ideas?

That's what i get from CLI:

Host Username Refresh State
192.168.1.72:5060 spa400 120 Request Sent

[o2bad455]

I was having trouble with the BroadVoice settings on my PAP2-NA, and finally called in for help today. A very helpful lady made some apparently important corrections to what the Voxilla Configuration Wizard had done. I'd post screen shots here if I could figure out how, but the changes/comments that I remember are:

SIP 100rel enable changed to YES (was NO)
Outbound proxy server names use "proxy-" for hardware adapters, but "proxy." for softphones.
Register expires changed to 3600 (was 1800)
Proxy fallback intvl changed to 1800 (was 1)
G723 enable changed to NO (was YES)

Mine's now working great! Hope that helps some folks

[kamalpa]

That helped me getting my PAP2 registered. Changing the proxy setting to be "proxy-" from "proxy." makes all the difference.

Thanks o2bad455.

[LostAussie]

Originally Posted by blwegrzyn

Hello,

I have two broadvoice accounts.
Lately, very often my broadvoice accounts are in unregistered state.
When I log into asterisk I see:

voip*CLI> sip show registry
Host Username Refresh State
sip.broadvoice.com:5060 yyy@s 120 Request Sent
sip.broadvoice.com:5060 xxx@s 120 Request Sent

......

the only way to get registered is to change the proxy in the host file,
after some time same story happens, I am in register sent state and nothing is coming back from the broadvoice, changing proxy in the host file again solves problem,

For me it sounds like broadvoice servers does not want talk with my servers for some unknown reason,

I called them but their support is unqualified, and I could not get any answer,

Any ideas?
Did anyone experience something like that?

thx


Bartosz Wegrzyn

Bartosz,

Did you ever solve this problem.

I seem to be having an identical problem. I read one discussion Asterisk Forums :: View topic - broadvoice experiences which suggested adding the entry registertimeout=70 to my sip.conf.

I am trying it out but as its intermitent I will have to wait to see if it works. If you solved yours and know how it would be much appreciated if you could let me know what worked.

Thanks in advance.

[LostAussie]

Originally Posted by LostAussie

Bartosz,

Did you ever solve this problem.

I seem to be having an identical problem. I read one discussion Asterisk Forums :: View topic - broadvoice experiences which suggested adding the entry registertimeout=70 to my sip.conf.

I am trying it out but as its intermitent I will have to wait to see if it works. If you solved yours and know how it would be much appreciated if you could let me know what worked.

Thanks in advance.

It looks like the registertimeout=70 solved my sporadic problem.

I suspect that if BroadVoice sees a user trying to register too often it just stops communicating. This is probably only kept at local proxy hence moving proxies solves issue. Adding this entry just stops it from trying to reregister too quickly so broadvoice no longer seems to ignore.