|Summary:||ASTERISK-16920: after update 126.96.36.199 to 1.8.0 registration from peers fails|
|Date Opened:||2010-11-05 05:09:12||Date Closed:||2015-02-26 09:54:41.000-0600|
|Environment:||Attachments:||( 0) sip.conf|
( 1) tracker_issue_0018263
( 2) tracker_issue_0018263_full_log_2.log
|Description:||Updated 1.6.2 asterisk to 1.8.0:|
Asterisk 1.8.0 built by lukasz @ Cawdor on a armv5tel running Linux on 2010-11-04 10:16:03 UTC
Linux Cawdor 2.6.32-5-orion5x #1 Sat May 22 02:17:44 UTC 2010 armv5tel GNU/Linux
The attempts of peers registrations fails.
|Comments:||By: pepesz (pepesz) 2010-11-05 08:21:36|
there are two logfiles:
first (tracker_issue_0018263) for the soft client
second (tracker_issue_0018263_full_log_2.log) for the siemens gigaset client
By: Paul Belanger (pabelanger) 2010-11-05 09:24:03
I don't like the looks of:
WWW-Authenticate: Digest algorithm=MD5, realm="asterisk", nonce="4c315317 "
Note the extra tab char within nonce.
By: Paul Belanger (pabelanger) 2010-11-05 09:25:40
Do you mind attaching your sip.conf file?
By: pepesz (pepesz) 2010-11-05 09:42:28
I Added sip config
For obvious reason I changed secrets and external ip
By: Loc (fivn) 2010-11-08 22:17:35.000-0600
I have the same issue on dockstar. OS: OpenWRT 10.3. If I retry many times, I can authenticate one. The success rate is about 1/25.
By: Loc (fivn) 2010-11-11 01:08:06.000-0600
I don't this issue on Ubuntu 10.04 but on dockstar. This may be related to cross compiling.
By: pepesz (pepesz) 2010-11-15 09:12:47.000-0600
It's not cross-compiled. It is build on the same machine on which it is running (arm).
By: pepesz (pepesz) 2011-01-20 07:27:37.000-0600
I can't agree with "Severity minor" - it makes asterisk unusable since peers cannot register...
By: Matt Jordan (mjordan) 2015-02-26 09:54:32.214-0600
Per the Asterisk versions page , the maintenance (bug fix) support for the Asterisk branch you are using has ended. For continued maintenance support please move to a supported branch of Asterisk. After testing with a supported branch, if you find this problem has not been resolved, please open a new issue against the latest version of that Asterisk branch.