Now I see what you mean. The phone indeed is inserting both Authorization and Proxy-Authorization. I know for a fact that multiple authorization headers is allowed by the specs and the proxy should be able to determine which one it should validate against so there can be something here that can be corrected on sipXecs side. I'll let the senior SIP gurus comment on this. Perhaps Dale can pitch in.

On a side note, the phone is misbehaving in this case so perhaps it should also be reported to the manufacturer and if we opt to do something in sipXecs code, that it would either make it as a 4.4 update or as a 4.6 bug fix. I would heed Tony's advise to test this using 4.4.



On 09/26/2011 08:40 PM, Audrey Simpson 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 <mailto:[email protected]>
    *To:* Discussion list for users of sipXecs software
    <mailto:[email protected]>
    *Cc:* Audrey Simpson <mailto:[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 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