Richard Kenner
2011-May-05 03:37 UTC
[asterisk-users] Issue with Asterisk & Aastra 57i at v3.2
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?
2011/5/5 Richard Kenner <kenner at gnat.com>> 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. >Hi, Is asterisk replying differently when firmware 3.2 is used ?> > Has anybody seen this? Is there any way to have the packets sent in the > proper order? > > -- > _____________________________________________________________________ > -- Bandwidth and Colocation Provided by http://www.api-digital.com -- > New to Asterisk? Join us for a live introductory webinar every Thurs: > http://www.asterisk.org/hello > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20110505/5f71e015/attachment.htm>
Richard Kenner
2011-May-05 04:59 UTC
[asterisk-users] Issue with Asterisk & Aastra 57i at v3.2
> Is asterisk replying differently when firmware 3.2 is used ?No, but the phone cares with 3.2 and not with 2.6.
Paul Hayes
2011-May-05 10:49 UTC
[asterisk-users] Issue with Asterisk & Aastra 57i at v3.2
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 3.2.1.43 on my 57i which I have just downloaded from aastra.co.uk this morning and Asterisk 1.4.25.1. 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:2002 at 192.168.2.73:5060;transport=udp SIP/2.0 Via: SIP/2.0/UDP 192.168.2.201:5060;branch=z9hG4bK6c97be12;rport From: "asterisk" <sip:asterisk at 192.168.2.201>;tag=as71d2aacd To: <sip:2002 at 192.168.2.73:5060;transport=udp> Contact: <sip:asterisk at 192.168.2.201> Call-ID: 0d0ecb8721126fdc43a44660792b63b6 at 192.168.2.201 CSeq: 102 OPTIONS User-Agent: Asterisk PBX Max-Forwards: 70 Date: Thu, 05 May 2011 10:43:00 GMT Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY Supported: replaces Content-Length: 0 --- sark500*CLI> <--- Transmitting (no NAT) to 192.168.2.73:5060 ---> SIP/2.0 200 OK Via: SIP/2.0/UDP 192.168.2.73;branch=z9hG4bKb06503cf2bc96500f;received=192.168.2.73 From: <sip:2002 at 192.168.2.201:5060>;tag=893258dbbd To: <sip:2002 at 192.168.2.201:5060>;tag=as6fe265b2 Call-ID: eb5b051757397d5d CSeq: 18419 REGISTER User-Agent: Asterisk PBX Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY Supported: replaces Expires: 160 Contact: <sip:2002 at 192.168.2.73:5060;transport=udp>;expires=160 Date: Thu, 05 May 2011 10:43:00 GMT Content-Length: 0 <------------> Scheduling destruction of SIP dialog 'eb5b051757397d5d' in 32000 ms (Method: REGISTER) sark500*CLI> <--- SIP read from 192.168.2.73:5060 ---> SIP/2.0 200 OK Via: SIP/2.0/UDP 192.168.2.201:5060;branch=z9hG4bK6c97be12;rport=5060;received=192.168.2.201 From: "asterisk" <sip:asterisk at 192.168.2.201>;tag=as71d2aacd To: <sip:2002 at 192.168.2.73:5060;transport=udp>;tag=2437297184 Call-ID: 0d0ecb8721126fdc43a44660792b63b6 at 192.168.2.201 CSeq: 102 OPTIONS Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, OPTIONS, UPDATE, PRACK, SUBSCRIBE, INFO Server: Aastra 57i/3.2.1.43 Supported: path Content-Length: 0
Possibly Parallel Threads
- A little OT but need an opinion on Aastra 57i CT
- Extension status as XML for an Aastra 57i
- Problem between Asterisk and an Aastra 57i
- OT: Aastra 57i configuration via TFTP problem
- [PATCH][v3.2.y] xen-netfront: delay gARP until backend switches to Connected