Re: [Serusers] SER is not matching ACK Messages

Same thing happens on our network (0.8.10). I have attached a sample ngrep of this. (I dial #2001 from local ATA with IP:192.168.0.15 and hangup as soon as the ringing starts) SER is at IP 200.75.73.22 and remote ATA is 200.75.91.137. After the call is cancelled SER keeps sending ACK messages to the remote ATA and 487s to the local ATA. It has always been like this. Not sure who is at fault here. Any ideas? Regards, Ricardo ----- Original Message ----- From: "Alejandro Olchik" <aolchik(a)telenova.net> To: "List serusers" <serusers(a)lists.iptel.org> Sent: Sunday, May 25, 2003 10:24 AM Subject: [Serusers] SER is not matching ACK Messages I'm experiencing some strange behaviour on SER. When an enpoint sends an INVITE and after some 180 Ringing messages cancels the call, SER forwards the CANCEL message to the destination and replies with a 200 Cancelling message. (this seems to be OK up to this point) 20ms after the Cancelling message was sent, SER sends a 487 Request cancelled message twice with 80ms of difference (any ide of why this is done?) From this point on, even receiving a succession of ACK messages SER keeps sending the 487 Request cancelled message as if the ACK didn't match. Any suggestion of what it can be? I'm using as the endpoint an ATA186, v2.15, and ser version 0.8.11. Best Regards, Alejandro _______________________________________________ Serusers mailing list serusers(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers