Okay for some reason the ACK from the caller ATA is not matched with the 487 from Ser. I can not see the cause for this error. Can someone provide a Ser log with high debug value, for this matching problem?

Thanks Nils Ohlmeier

On Sunday 25 May 2003 21:52, Ricardo Villa wrote:

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@telenova.net To: "List serusers" serusers@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@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers

Ok i first overlooked a problem in the messages. I think the ATA is guilty because the request URI of the ACK is not the same as the URI from the INVITE. And if i'm not wrong the URIs has to be the same because the ACK for a negative reply belongs to the transaction.

U 63.77.141.227:5050 -> 200.219.173.140:5060 INVITE sip:99638515@sip.trdc.telenova.com.br;user=phone SIP/2.0..Via: SIP/2 .0/UDP 63.77.141.227:5050..Via: SIP/2.0/UDP 192.168.0.2:5060..From: <sip:55 514@sip.trdc.telenova.com.br;user=phone>;tag=39420929..To: <sip:99638515@si p.trdc.telenova.com.br;user=phone>..Call-ID: 1446977160@192.168.0.2..CSeq: 2 INVITE..Contact: sip:55514@63.77.141.227:5050;user=phone..Authorization : Digest username="55514", realm="sip.trdc.telenova.com.br", nonce="3ed0dc0 bff5ab94bf089aa864744f463e8e243ef", uri="sip:99638515@sip.trdc.telenova.com .br", response="21434035966cd4cd8ef8dca75515b4b4"..user-agent: Cisco ATA v 2.15 ata186 (020918a)..expires: 300..Content-Type: application/sdp..Content -Length: 248 ....v=0..o=55514 11951 11951 IN IP4 192.168.0.2..s=ATA186 Cal l..c=IN IP4 63.77.141.227.t=0 0..m=audio 7070 RTP/AVP 18 8 0 101..a=rtpmap: 18 G729/8000/1..a=rtpmap:8 PCMA/8000/1..a=rtpmap:0 PCMU/8000/1..a=rtpmap:10 1 telephone-event/8000..a=fmtp:101 0-15..

[...] U 63.77.141.227:5050 -> 200.219.173.140:5060 ACK sip:99638515@sip.trdc.telenova.com.br:5060 SIP/2.0..Via: SIP/2.0/UDP 63 .77.141.227:5050..Via: SIP/2.0/UDP 192.168.0.2:5060..From: <sip:55514@sip.t rdc.telenova.com.br;user=phone>;tag=39420929..To: <sip:99638515@sip.trdc.te lenova.com.br;user=phone>;tag=d58c1e972d22d5f66f01bb0aca7a741a-edbe..Call-I D: 1446977160@192.168.0.2..CSeq: 2 ACK..user-agent: Cisco ATA v2.15 ata186 (020918a)..Content-Length: 0....

Regards Nils Ohlmeier

On Sunday 25 May 2003 23:29, Ricardo Villa wrote:

Hi Nils, Here it is. I stopped the server, set debug=7 and log_stderror=yes, repeated the same call as before, then stopped the server and captured the output. The file is attached.

Regards, Ricardo

----- Original Message ----- From: "Nils Ohlmeier" nils@iptel.org To: "Ricardo Villa" ricvil@epm.net.co; aolchik@telenova.net; "List serusers" serusers@lists.iptel.org Sent: Sunday, May 25, 2003 3:40 PM Subject: Re: [Serusers] SER is not matching ACK Messages