asterisk users - May 2011 - Asterisk 1.41 - Warning and Notice about contact info and stale nonce

Hi list,

We have devices since more then 4 years which where running well with 
Asterisk. But with latest version (1.38 or more) we face problem with 
those devices when they try to register. We got

[2011-05-14 17:18:06] WARNING[28559]: chan_sip.c:9950 register_verify: 
Failed to parse contact info
<--- Transmitting (NAT) to XXX.XXX.XXX.XXX:5062 --->
SIP/2.0 400 Bad Request

Followed by

[2011-05-14 17:19:06] NOTICE[28559]: chan_sip.c:9502 check_auth: Correct 
auth, but based on stale nonce received from 
'<sip:714 at YYY.YYY.YYY.YYY;user=phone>;tag=63d2ba80bffb016f'

Checking logs we found

Contact: *

in headers before the failed parse contact info.

We checked in source chan_sip and saw the parse info reject with Error 
400 after "the auth is correct" comment.

We modified in sip.conf the type=peer in type=friend, same result.

Could someone explain us what happends here?

Thanks

-- 
Daniel

Of course it's 1.4.41. And the result is that devices doesn't register 
anymore.

Thanks for any hint.

Le 14/05/2011 17:37, Administrator TOOTAI a ?crit :
> Hi list,
>
> We have devices since more then 4 years which where running well with 
> Asterisk. But with latest version (1.38 or more) we face problem with 
> those devices when they try to register. We got
>
> [2011-05-14 17:18:06] WARNING[28559]: chan_sip.c:9950 register_verify: 
> Failed to parse contact info
> <--- Transmitting (NAT) to XXX.XXX.XXX.XXX:5062 --->
> SIP/2.0 400 Bad Request
>
> Followed by
>
> [2011-05-14 17:19:06] NOTICE[28559]: chan_sip.c:9502 check_auth: 
> Correct auth, but based on stale nonce received from 
> '<sip:714 at
YYY.YYY.YYY.YYY;user=phone>;tag=63d2ba80bffb016f'
>
> Checking logs we found
>
> Contact: *
>
> in headers before the failed parse contact info.
>
> We checked in source chan_sip and saw the parse info reject with Error 
> 400 after "the auth is correct" comment.
>
> We modified in sip.conf the type=peer in type=friend, same result.
>
> Could someone explain us what happends here?
>
> Thanks
-- 
Daniel