Hi,
Thanks for obligation Jeogen and Douglas.
yum updated and unfortunately it still does'nt work.

sipxregistry                           x86_64
4.4.0-375.g7849e                            sipXecs
235 k
[root@sipx ~]# /etc/init.d/sipxecs
...
[root@sipx ~]# tshark -R "sip"
Running as user "root" and group "root". This could be dangerous.
Capturing on eth0
 71.654139 10.99.149.203 -> 10.99.10.9   SIP Request: REGISTER
sip:10.99.10.9
 71.659553   10.99.10.9 -> 10.99.149.203 SIP Status: 401 Unauthorized
(0 bindings)
 71.827241 10.99.149.203 -> 10.99.10.9   SIP Request: REGISTER
sip:10.99.10.9
 71.832948   10.99.10.9 -> 10.99.149.203 SIP Status: 401 Unauthorized
(0 bindings)
 71.998402 10.99.149.203 -> 10.99.10.9   SIP Request: REGISTER
sip:10.99.10.9
 72.004052   10.99.10.9 -> 10.99.149.203 SIP Status: 401 Unauthorized
(0 bindings)

Any other ideas?

-----Ursprüngliche Nachricht-----
Von: [email protected]
[mailto:[email protected]] Im Auftrag von Douglas
Hubler
Gesendet: Freitag, 30. März 2012 10:39
An: Joegen Baclor
Cc: Discussion list for users of sipXecs software
Betreff: Re: [sipx-users] Backward Compatibility for "qop"

OK, pushed fix to stage area.  Can folks retest? thanks!

On Fri, Mar 30, 2012 at 2:52 AM, Joegen Baclor <[email protected]> wrote:
>
> Douglas,
>
> After looking at the logs, I realized that the registrar performs it's
> own authorization.   We therefore need to also get rid of qop checking
> in SipRegistryServer.  I have committed the change to 4.4.
>
> Joegen
>
>
> On 03/27/2012 12:17 AM, Douglas Hubler wrote:
>>
>> On Mon, Mar 26, 2012 at 7:12 AM, Douglas Hubler<[email protected]>
 wrote:
>>>
>>> On Sun, Mar 25, 2012 at 2:04 PM, Adam
>>> Newman<[email protected]>
>>>  wrote:
>>>>
>>>> I would be delighted if you could send me the patch for testing.
>>>
>>> I should have patch and instructions later today. We're simply
>>> pushing the rpms to 4.4 stage directory.
>>
>> RPMs are in
>>   http://download.sipfoundry.org/pub/sipXecs-stage/4.4.0/
>>
>> You need to edit
>>    /etc/yum.repos.d/sipxecs.repo
>> with appropriate url and perform a yum update on at least sipx
>>   yum update 'sipx*'
>> _______________________________________________
>> sipx-users mailing list
>> [email protected]
>> List Archive: http://list.sipfoundry.org/archive/sipx-users/
>>
>
_______________________________________________
sipx-users mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users/
_______________________________________________
sipx-users mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users/

Reply via email to