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/
