On 05/05/11 04:37, Richard Kenner wrote:
> I recently tried to update my Aastra 57i to version 3.2 and ran into
> a problem. It won’t properly register and says “contact mismatch”.
> I added “sip contact matching: 2” to aastra.cfg, but that didn’t help.
> When I look at the SIP trace, but I see is the Aastra sending a
> REGISTER and Asterisk replying with the 401. The phone then sends
> the REGISTER again, this time with the hash. Asterisk now replies OK,
> but sends an OPTION packet FIRST and I think that confuses the Aastra.
> Has anybody seen this? Is there any way to have the packets sent in the
> proper order?
Since I was keen to see if there was a phone bug I’ve just tested this
here. I am using firmware 18.104.22.168 on my 57i which I have just
downloaded from aastra.co.uk this morning and Asterisk 22.214.171.124.
Asterisk does indeed send an Options before the OK but my 57i doesn’t
seem to mind. See the SIP debug trace below. Perhaps you need to
upgrade firmware on the Aastra phone? Or turning off qualify for this
peer might work-around it for you.
Reliably Transmitting (no NAT) to 192.168.2.73:5060:
OPTIONS sip:firstname.lastname@example.org:5060;transport=udp SIP/2.0
Via: SIP/2.0/UDP 192.168.2.201:5060;branch=z9hG4bK6c97be12;rport
From: “asterisk” ;tag=as71d2aacd
CSeq: 102 OPTIONS
User-Agent: Asterisk PBX
Date: Thu, 05 May 2011 10:43:00 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY