Thanks Chris. Now you mention, in fact i was doing some ethereal debugs and i have found some problems with my REGISTER's messages, specially from NAT'd endpoints. Could this be the cause of the increasing number of "WAITING" in my monitor? I'm seeing this debug from a REGISTER transaction::
U 200.xx.xx.xx:5060 -> xx.xx.154.35:5060 REGISTER sip:sip.mydomain.com SIP/2.0. Via: SIP/2.0/UDP 200.xx.xx.xx:5060;branch=z9hG4bK-a2202b91. From: 5555848141 sip:5555848141@sip.mydomain.com;tag=a5e753635c69bee8o0. To: 5555848141 sip:5555848141@sip.mydomain.com. Call-ID: 316c6f5b-e5ea970f@192.168.0.104. CSeq: 33 REGISTER. Max-Forwards: 70. Authorization: Digest username="Username1",realm="sip.mydomain.com",nonce="420d1c9d4b50d5cd531d756 e150514fdf7075880",uri="sip:5555848141@sip.mydomain.com",algorithm=MD5,respo nse="075c1cee957db126b0ea06ac88b25f22",qop=auth,nc=00000002,cnonce="394307ed ". Contact: 5555848141 sip:5555848141@200.xx.xx.xx:5060;expires=600. Warning: 399 spa "Restricted Cone NAT Dectected". User-Agent: Linksys/RT31P2-2.0.10(LIc). Content-Length: 0. Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER. Supported: x-sipura. .
## U xx.xx.154.35:5060 -> 200.xx.xx.xx:5060 SIP/2.0 401 Unauthorized. Via: SIP/2.0/UDP 200.xx.xx.xx:5060;branch=z9hG4bK-a2202b91. From: 5555848141 sip:5555848141@sip.mydomain.com;tag=a5e753635c69bee8o0. To: 5555848141 sip:5555848141@sip.mydomain.com;tag=6eb14299de2cc731d173c135064daec5.4858. Call-ID: 316c6f5b-e5ea970f@192.168.0.104. CSeq: 33 REGISTER. WWW-Authenticate: Digest realm="sip.mydomain.com", nonce="420d1ef86fb6cf9709576f1e81b628556d3c932e", qop="auth", stale=true. Server: Sip EXpress router (0.8.14-3 (i386/linux)). Content-Length: 0. Warning: 392 xx.xx.154.35:5060 "Noisy feedback tells: pid=18215 req_src_ip=200.xx.xx.xx req_src_port=5060 in_uri=sip:sip.mydomain.com out_uri=sip:sip.mydomain.com via_cnt==1". .
## U 200.xx.xx.xx:5060 -> xx.xx.154.35:5060 REGISTER sip:sip.mydomain.com SIP/2.0. Via: SIP/2.0/UDP 200.xx.xx.xx:5060;branch=z9hG4bK-a2202b91. From: 5555848141 sip:5555848141@sip.mydomain.com;tag=a5e753635c69bee8o0. To: 5555848141 sip:5555848141@sip.mydomain.com. Call-ID: 316c6f5b-e5ea970f@192.168.0.104. CSeq: 33 REGISTER. Max-Forwards: 70. Authorization: Digest username="Username1",realm="sip.mydomain.com",nonce="420d1c9d4b50d5cd531d756 e150514fdf7075880",uri="sip:5555848141@sip.mydomain.com",algorithm=MD5,respo nse="c145f825cc6c14e1e27b6b17f1b2c332",qop=auth,nc=00000003,cnonce="394307ed ". Contact: 5555848141 sip:5555848141@200.xx.xx.xx:5060;expires=600. Warning: 399 spa "Restricted Cone NAT Dectected". User-Agent: Linksys/RT31P2-2.0.10(LIc). Content-Length: 0. Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER. Supported: x-sipura. .
## U xx.xx.154.35:5060 -> 200.xx.xx.xx:5060 SIP/2.0 401 Unauthorized. Via: SIP/2.0/UDP 200.xx.xx.xx:5060;branch=z9hG4bK-a2202b91. From: 5555848141 sip:5555848141@sip.mydomain.com;tag=a5e753635c69bee8o0. To: 5555848141 sip:5555848141@sip.mydomain.com;tag=6eb14299de2cc731d173c135064daec5.4858. Call-ID: 316c6f5b-e5ea970f@192.168.0.104. CSeq: 33 REGISTER. WWW-Authenticate: Digest realm="sip.mydomain.com", nonce="420d1ef86fb6cf9709576f1e81b628556d3c932e", qop="auth", stale=true. Server: Sip EXpress router (0.8.14-3 (i386/linux)). Content-Length: 0. Warning: 392 xx.xx.154.35:5060 "Noisy feedback tells: pid=18214 req_src_ip=200.xx.xx.xx req_src_port=5060 in_uri=sip:sip.mydomain.com out_uri=sip:sip.mydomain.com via_cnt==1". .
## U 200.xx.xx.xx:5060 -> xx.xx.154.35:5060 REGISTER sip:sip.mydomain.com SIP/2.0. Via: SIP/2.0/UDP 200.xx.xx.xx:5060;branch=z9hG4bK-a2202b91. From: 5555848141 sip:5555848141@sip.mydomain.com;tag=a5e753635c69bee8o0. To: 5555848141 sip:5555848141@sip.mydomain.com. Call-ID: 316c6f5b-e5ea970f@192.168.0.104. CSeq: 33 REGISTER. Max-Forwards: 70. Authorization: Digest username="Username1",realm="sip.mydomain.com",nonce="420d1c9d4b50d5cd531d756 e150514fdf7075880",uri="sip:5555848141@sip.mydomain.com",algorithm=MD5,respo nse="c145f825cc6c14e1e27b6b17f1b2c332",qop=auth,nc=00000003,cnonce="394307ed ". Contact: 5555848141 sip:5555848141@200.xx.xx.xx:5060;expires=600. Warning: 399 spa "Restricted Cone NAT Dectected". User-Agent: Linksys/RT31P2-2.0.10(LIc). Content-Length: 0. Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER. Supported: x-sipura. .
## U xx.xx.154.35:5060 -> 200.xx.xx.xx:5060 SIP/2.0 401 Unauthorized. Via: SIP/2.0/UDP 200.xx.xx.xx:5060;branch=z9hG4bK-a2202b91. From: 5555848141 sip:5555848141@sip.mydomain.com;tag=a5e753635c69bee8o0. To: 5555848141 sip:5555848141@sip.mydomain.com;tag=6eb14299de2cc731d173c135064daec5.4858. Call-ID: 316c6f5b-e5ea970f@192.168.0.104. CSeq: 33 REGISTER. WWW-Authenticate: Digest realm="sip.mydomain.com", nonce="420d1ef937646ad8e71e1c566161be30607c89da", qop="auth", stale=true. Server: Sip EXpress router (0.8.14-3 (i386/linux)). Content-Length: 0. Warning: 392 xx.xx.154.35:5060 "Noisy feedback tells: pid=18215 req_src_ip=200.xx.xx.xx req_src_port=5060 in_uri=sip:sip.mydomain.com out_uri=sip:sip.mydomain.com via_cnt==1". .
## U 200.xx.xx.xx:5060 -> xx.xx.154.35:5060 REGISTER sip:sip.mydomain.com SIP/2.0. Via: SIP/2.0/UDP 200.xx.xx.xx:5060;branch=z9hG4bK-14bd512b. From: 5555848141 sip:5555848141@sip.mydomain.com;tag=a5e753635c69bee8o0. To: 5555848141 sip:5555848141@sip.mydomain.com. Call-ID: 316c6f5b-e5ea970f@192.168.0.104. CSeq: 34 REGISTER. Max-Forwards: 70. Authorization: Digest username="Username1",realm="sip.mydomain.com",nonce="420d1ef86fb6cf9709576f1 e81b628556d3c932e",uri="sip:5555848141@sip.mydomain.com",algorithm=MD5,respo nse="901a43b3665d197579ed76483032841d",qop=auth,nc=00000001,cnonce="97900177 ". Contact: 5555848141 sip:5555848141@200.xx.xx.xx:5060;expires=600. Warning: 399 spa "Restricted Cone NAT Dectected". User-Agent: Linksys/RT31P2-2.0.10(LIc). Content-Length: 0. Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER. Supported: x-sipura. .
## U xx.xx.154.35:5060 -> 200.xx.xx.xx:5060 SIP/2.0 200 OK. Via: SIP/2.0/UDP 200.xx.xx.xx:5060;branch=z9hG4bK-14bd512b. From: 5555848141 sip:5555848141@sip.mydomain.com;tag=a5e753635c69bee8o0. To: 5555848141 sip:5555848141@sip.mydomain.com;tag=6eb14299de2cc731d173c135064daec5.3c44. Call-ID: 316c6f5b-e5ea970f@192.168.0.104. CSeq: 34 REGISTER. Contact: sip:5555848141@200.xx.xx.xx:5060;q=0.00;expires=600. Server: Sip EXpress router (0.8.14-3 (i386/linux)). Content-Length: 0. Warning: 392 xx.xx.154.35:5060 "Noisy feedback tells: pid=18214 req_src_ip=200.xx.xx.xx req_src_port=5060 in_uri=sip:sip.mydomain.com out_uri=sip:sip.mydomain.com via_cnt==1". .
#### U 200.xx.xx.xx:5060 -> xx.xx.154.35:5060 REGISTER sip:sip.mydomain.com SIP/2.0. Via: SIP/2.0/UDP 200.xx.xx.xx:5060;branch=z9hG4bK-14bd512b. From: 5555848141 sip:5555848141@sip.mydomain.com;tag=a5e753635c69bee8o0. To: 5555848141 sip:5555848141@sip.mydomain.com. Call-ID: 316c6f5b-e5ea970f@192.168.0.104. CSeq: 34 REGISTER. Max-Forwards: 70. Authorization: Digest username="Username1",realm="sip.mydomain.com",nonce="420d1ef86fb6cf9709576f1 e81b628556d3c932e",uri="sip:5555848141@sip.mydomain.com",algorithm=MD5,respo nse="c03835111b84859ce7a63a83f9ef5045",qop=auth,nc=00000002,cnonce="97900177 ". Contact: 5555848141 sip:5555848141@200.xx.xx.xx:5060;expires=600. Warning: 399 spa "Restricted Cone NAT Dectected". User-Agent: Linksys/RT31P2-2.0.10(LIc). Content-Length: 0. Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER. Supported: x-sipura. .
## U xx.xx.154.35:5060 -> 200.xx.xx.xx:5060 SIP/2.0 200 OK. Via: SIP/2.0/UDP 200.xx.xx.xx:5060;branch=z9hG4bK-14bd512b. From: 5555848141 sip:5555848141@sip.mydomain.com;tag=a5e753635c69bee8o0. To: 5555848141 sip:5555848141@sip.mydomain.com;tag=6eb14299de2cc731d173c135064daec5.3c44. Call-ID: 316c6f5b-e5ea970f@192.168.0.104. CSeq: 34 REGISTER. Contact: sip:5555848141@200.xx.xx.xx:5060;q=0.00;expires=600. Server: Sip EXpress router (0.8.14-3 (i386/linux)). Content-Length: 0. Warning: 392 xx.xx.154.35:5060 "Noisy feedback tells: pid=18216 req_src_ip=200.xx.xx.xx req_src_port=5060 in_uri=sip:sip.mydomain.com out_uri=sip:sip.mydomain.com via_cnt==1". .
Can someone help me to understand why this is happening. I don't understand why my endpoint is sending the REGISTER message with the Authentication parameters!!? I really hope that someone can help me!!! Thanks in advance.
Ricardo Javier Martinez Ogalde
-----Mensaje original----- De: Chris [mailto:ser@cannes.f9.co.uk] Enviado el: Viernes, 11 de Febrero de 2005 15:16 Para: 'Ricardo Martinez'; serusers@lists.iptel.org Asunto: RE: [Serusers] serctl moni question.
I had it once (350 waiting) when I was running on a very old slow PII machine and I had a UA trying to re-register continuously after failure. use ethereal to see what is coming into to your ser. Mine was fixed by stopping continuous retries without gap and making register succeed :)) Chris
-----Original Message----- From: serusers-bounces@lists.iptel.org [mailto:serusers-bounces@lists.iptel.org] On Behalf Of Ricardo Martinez Sent: 11 February 2005 20:06 To: 'serusers@lists.iptel.org' Subject: RE: [Serusers] serctl moni question.
Hello again. Have anyone idea about this issue? Thanks!
Ricardo Martinez.-
-----Mensaje original----- De: Ricardo Martinez [mailto:rmartinez@redvoiss.net] Enviado el: Jueves, 10 de Febrero de 2005 16:29 Para: 'serusers@lists.iptel.org' Asunto: [Serusers] serctl moni question.
Hello list. I used the "serctl moni" command and i have found these statistics :
Transaction Statistics Current: 0 (40 waiting) Total: 584 (0 local) Replied localy: 1082 Completion status 6xx: 27, 5xx: 7, 4xx: 212, 3xx: 0,2xx: 356
I'm particular interested in the Transactions Statics - Current and the 40 Waiting. Does this means something?
Thanks in advance.
Ricardo Martinez
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
-- No virus found in this incoming message. Checked by AVG Anti-Virus. Version: 7.0.300 / Virus Database: 265.8.7 - Release Date: 10/02/2005
-- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.300 / Virus Database: 265.8.7 - Release Date: 10/02/2005