also...
It appears you are trying to authenticate with the host part set for an ip
address. Why is it that you are not using the sipdomain instead of the IP?
Session Initiation Protocol
Status-Line: SIP/2.0 401 Unauthorized
Status-Code: 401
[Resent Packet: False]
[Request Frame: 27560]
[Response Time (ms): 20]
Message Header
From: "" <sip:[email protected]>;tag=378bdca40023
SIP Display info: ""
SIP from address: sip:[email protected]
SIP from address User Part: 314
SIP from address Host Part: 10.0.10.1
SIP tag: 378bdca40023
On Mon, Sep 26, 2011 at 8:50 AM, Tony Graziano <[email protected]
> wrote:
> are you serious in that you are running sipXecs/3.10.2? can you consider
> building a test 4.4.0 system to test against?
>
>
> On Mon, Sep 26, 2011 at 8:40 AM, Audrey Simpson <[email protected]> wrote:
>
>> **
>> I've attached the packets.
>>
>> invite = to a sip trunk, after the 407
>> register = attempt to re-reg after above call
>> 401 = from the pbx after the register
>>
>> Thanks,
>>
>> Audrey
>>
>> ----- Original Message -----
>> *From:* Joegen Baclor <[email protected]>
>> *To:* Discussion list for users of sipXecs
>> software<[email protected]>
>> *Cc:* Audrey Simpson <[email protected]>
>> *Sent:* Friday, September 23, 2011 8:28 PM
>> *Subject:* Re: [sipx-users] Polycom Kirk Dect KWS300
>>
>> Could be a QoP/auth-int issue. Only a packet capture of what the register
>> and invite looks like would tell for sure.
>>
>> On 09/24/2011 03:38 AM, Audrey Simpson wrote:
>>
>> Hello,
>>
>> I have been using the KWS300 successfully for a long time now with version
>> 3.10.
>>
>> I upgraded the KWS300 firmware to address a problem with TCP invites.
>>
>> This created another problem. When the phone calls a trunk, the pbx sends
>> a 407. The dect inserts a proxy authorization header in response. When it
>> comes time for the dect phone that called the trunk to re-register, it
>> fails. The proxy authorization header from the previous call is included in
>> the registration along with the authorization header and the request is
>> being ignored by the pbx. If I don't call any trunks, the phone continues
>> to register no problem. I have to physically reboot the KWS300 to get it to
>> register again.
>>
>> Has anyone seen anything like this?
>>
>> Handsets are 5020 & 4040
>> Firmware versions starting from PCS05 all the way up to current.
>>
>> Thanks,
>>
>> Audrey
>>
>>
>> _______________________________________________
>> sipx-users mailing [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/
>>
>
>
>
> --
> ======================
> Tony Graziano, Manager
> Telephone: 434.984.8430
> sip: [email protected]
> Fax: 434.465.6833
>
> Email: [email protected]
>
> LAN/Telephony/Security and Control Systems Helpdesk:
> Telephone: 434.984.8426
> sip: [email protected]
>
> Helpdesk Contract Customers:
> http://support.myitdepartment.net
>
> <http://support.myitdepartment.net>Blog:
> http://blog.myitdepartment.net
>
> Linked-In Profile: http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4
>
> Ask about our Internet faxservices!
>
>
--
======================
Tony Graziano, Manager
Telephone: 434.984.8430
sip: [email protected]
Fax: 434.465.6833
Email: [email protected]
LAN/Telephony/Security and Control Systems Helpdesk:
Telephone: 434.984.8426
sip: [email protected]
Helpdesk Contract Customers:
http://support.myitdepartment.net
<http://support.myitdepartment.net>Blog:
http://blog.myitdepartment.net
Linked-In Profile: http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4
Ask about our Internet Fax services!
_______________________________________________
sipx-users mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users/
