Hi,
Im using ser 0.9.3. The PA and Watcher are located on my UA, so basically my SUBSCRIBEs and NOTIFYs just need to be forwarded between clients.
Here's a part of ser.cfg that does the SUBSCRIBE and NOTIFY processing (please, note that I disabled the authentication for now):
. . . . . .
if(method=="SUBSCRIBE") { if(!lookup("location") ) { log(1, "No registered user found for SUBSCRIBE request"); sl_send_reply("404", "Not Found"); break; }; };
if(method=="NOTIFY") { if (!lookup("location")) { log(1, "No registered user found for NOTIFY request"); sl_send_reply("404", "Not Found"); break; }; };
if( !t_relay() ) { sl_reply_error(); };
. . . . . . . .
The problem is that only SOMETIMES SUIBSCRIBEs and NOTIFYs get through without any problem. However, MOST OF THE TIMES they get stuck in the server. The message log does not show any errors and tracesviewer tool shows only retransmissions for the issued requests. In the end SER replies with 408 Timeout response. I have tried to use forward(uri:host, uri:port) instead of t_relay(), but result is the same.
I have used eyeBeam to do the presence subscriptions, and the result is the same as with my UA...
Can you, please, explain to me what might have happened??? I am out of ideas.
Andrey.
Could you post your SIP message dumps ?
Jan.
On 13-12-2005 15:03, Andrey Kouprianov wrote:
Hi,
Im using ser 0.9.3. The PA and Watcher are located on my UA, so basically my SUBSCRIBEs and NOTIFYs just need to be forwarded between clients.
Here's a part of ser.cfg that does the SUBSCRIBE and NOTIFY processing (please, note that I disabled the authentication for now):
. . . . . .
if(method=="SUBSCRIBE") { if(!lookup("location") ) { log(1, "No registered user found for SUBSCRIBE request"); sl_send_reply("404", "Not Found"); break; }; };
if(method=="NOTIFY") { if (!lookup("location")) { log(1, "No registered user found for NOTIFY request"); sl_send_reply("404", "Not Found"); break; }; };
if( !t_relay() ) { sl_reply_error(); };
. . . . . . . .
The problem is that only SOMETIMES SUIBSCRIBEs and NOTIFYs get through without any problem. However, MOST OF THE TIMES they get stuck in the server. The message log does not show any errors and tracesviewer tool shows only retransmissions for the issued requests. In the end SER replies with 408 Timeout response. I have tried to use forward(uri:host, uri:port) instead of t_relay(), but result is the same.
I have used eyeBeam to do the presence subscriptions, and the result is the same as with my UA...
Can you, please, explain to me what might have happened??? I am out of ideas.
Andrey.
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
Hi,
I think the problem is solved... I forgot to mention that if I subscribed to myself, then it always worked... So, i plugged in the code for authentication, and it seemed to start working well for every other subscription. I also forgot that RFC metion, that it's a must to authenticate subscriptions. Is that what SER must do for subscriptions??? Is that the case?
Anyway, my SUBSCRIBE request is as follows:
SUBSCRIBE sip:12345@203.159.32.35:5060 SIP/2.0 Call-ID: 4c9d9cf6ff739599a9a3648001df9239@203.159.32.35 CSeq: 1 SUBSCRIBE From: "12345" sip:12345@sip.interlab.ait.ac.th;tag=32997440 To: sip:12345@sip.interlab.ait.ac.th Via: SIP/2.0/UDP 203.159.31.36;branch=0,SIP/2.0/UDP 203.159.32.35:5060;branch=z9 hG4bKb44ee5d83eb2b06d538a6152ca27914a Max-Forwards: 16 Allow: REGISTER,INVITE,BYE,ACK,CANCEL,SUBSCRIBE,NOTIFY,MESSAGE User-Agent: IntERLab User Agent 1.0a Event: presence Expires: 600 Accept: application/pidf+xml,application/xpidf+xml,application/xvcresource+xml Contact: sip:12345@203.159.32.35:5060 Content-Length: 0
After that the 408 Timeout was issued by SER...
On 12/13/05, Jan Janak jan@iptel.org wrote:
Could you post your SIP message dumps ?
Jan.
On 13-12-2005 15:03, Andrey Kouprianov wrote:
Hi,
Im using ser 0.9.3. The PA and Watcher are located on my UA, so basically my SUBSCRIBEs and NOTIFYs just need to be forwarded between clients.
Here's a part of ser.cfg that does the SUBSCRIBE and NOTIFY processing (please, note that I disabled the authentication for now):
. . . . . .
if(method=="SUBSCRIBE") { if(!lookup("location") ) { log(1, "No registered user found for SUBSCRIBE request"); sl_send_reply("404", "Not Found"); break; }; };
if(method=="NOTIFY") { if (!lookup("location")) { log(1, "No registered user found for NOTIFY request"); sl_send_reply("404", "Not Found"); break; }; };
if( !t_relay() ) { sl_reply_error(); };
. . . . . . . .
The problem is that only SOMETIMES SUIBSCRIBEs and NOTIFYs get through without any problem. However, MOST OF THE TIMES they get stuck in the server. The message log does not show any errors and tracesviewer tool shows only retransmissions for the issued requests. In the end SER replies with 408 Timeout response. I have tried to use forward(uri:host, uri:port) instead of t_relay(), but result is the same.
I have used eyeBeam to do the presence subscriptions, and the result is the same as with my UA...
Can you, please, explain to me what might have happened??? I am out of ideas.
Andrey.
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
Hi,
I am having the same problem again.... SER just keeps on sending me back timeouts for SUBSCRIBES... The problem, as I described in previous emails, persists for any other presentity except myself.
Here's a part of ser.cfg:
. . . . . .
if(method=="SUBSCRIBE") { if (!www_authorize("sip.interlab.ait.ac.th", "subscriber")) { log(1, "Authentication for SUBSCRIBE"); www_challenge("sip.interlab.ait.ac.th", "0"); break; };
if(!lookup("location") ) { log(1, "No registered user found for SUBSCRIBE request"); sl_send_reply("404", "Not Found"); break; }; };
if(method=="NOTIFY") { if (!www_authorize("sip.interlab.ait.ac.th", "subscriber")) { log(1, "Authentication for SUBSCRIBE"); www_challenge("sip.interlab.ait.ac.th", "0"); break; };
if (!lookup("location")) { log(1, "No registered user found for NOTIFY request"); sl_send_reply("404", "Not Found"); break; }; };
if( !t_relay() ) { sl_reply_error(); };
. . . . . . . .
Here are the traces:
Message 1 from 203.159.32.39:5060 to 203.159.31.36:5060
SUBSCRIBE sip:12345@sip.interlab.ait.ac.th SIP/2.0 Call-ID: 7762edc6f3954c87c8b95a0270653250@203.159.32.39 CSeq: 1 SUBSCRIBE From: "Andrey Kuprianov" sip:andrey@sip.interlab.ait.ac.th;tag=15493888 To: sip:12345@sip.interlab.ait.ac.th Via: SIP/2.0/UDP 203.159.32.39:5060;branch=z9hG4bK3ad443c5b49de4b050bd2b028597a868 Max-Forwards: 70 Allow: REGISTER,INVITE,BYE,ACK,CANCEL,SUBSCRIBE,NOTIFY,MESSAGE User-Agent: IntERLab User Agent 1.0a Event: presence Expires: 600 Accept: application/pidf+xml,application/xpidf+xml,application/xvcresource+xml Contact: sip:andrey@203.159.32.39:5060 Content-Length: 0
Message 2 from 203.159.31.36:5060 to 203.159.32.39:5060
SIP/2.0 401 Unauthorized Call-ID: 7762edc6f3954c87c8b95a0270653250@203.159.32.39 CSeq: 1 SUBSCRIBE From: "Andrey Kuprianov" sip:andrey@sip.interlab.ait.ac.th;tag=15493888 To: sip:12345@sip.interlab.ait.ac.th;tag=1a5a85ff3e08e000f4c2527642cf14ac.5e75 Via: SIP/2.0/UDP 203.159.32.39:5060;branch=z9hG4bK3ad443c5b49de4b050bd2b028597a868 WWW-Authenticate: Digest realm="sip.interlab.ait.ac.th",nonce="439ee222efefefbb8cbb78e75d6d15b723a1e1d0" Server: Sip EXpress router (0.9.3 (i386/freebsd)) Warning: 392 203.159.31.36:5060 "Noisy feedback tells: pid=17754 req_src_ip=203.159.32.39 req_src_port=5060 in_uri=sip:12345@sip.interlab.ait.ac.th out_uri=sip:12345@sip.interlab.ait.ac.th via_cnt==1" Content-Length: 0
Message 3 from 203.159.32.39:5060 to 203.159.31.36:5060
SUBSCRIBE sip:12345@sip.interlab.ait.ac.th SIP/2.0 Call-ID: 7762edc6f3954c87c8b95a0270653250@203.159.32.39 CSeq: 2 SUBSCRIBE To: sip:12345@sip.interlab.ait.ac.th Via: SIP/2.0/UDP 203.159.32.39:5060;branch=z9hG4bK991c906a283ca5d57e8856c98097e81c Max-Forwards: 70 Allow: REGISTER,INVITE,BYE,ACK,CANCEL,SUBSCRIBE,NOTIFY,MESSAGE User-Agent: IntERLab User Agent 1.0a Event: presence Expires: 600 Accept: application/pidf+xml,application/xpidf+xml,application/xvcresource+xml Contact: sip:andrey@203.159.32.39:5060 Authorization: Digest username="andrey",realm="sip.interlab.ait.ac.th",nonce="439ee222efefefbb8cbb78e75d6d15b723a1e1d0",uri="sip:12345@sip.interlab.ait.ac.th",response="1c7fa7ceb1f654d0e2ea91c54823bb8d" From: "Andrey Kuprianov" sip:andrey@sip.interlab.ait.ac.th;tag=15493888 Content-Length: 0
Message 4 from 203.159.32.39:5060 to 203.159.31.36:5060
SUBSCRIBE sip:12345@sip.interlab.ait.ac.th SIP/2.0 Call-ID: 7762edc6f3954c87c8b95a0270653250@203.159.32.39 CSeq: 2 SUBSCRIBE To: sip:12345@sip.interlab.ait.ac.th Via: SIP/2.0/UDP 203.159.32.39:5060;branch=z9hG4bK991c906a283ca5d57e8856c98097e81c Max-Forwards: 70 Allow: REGISTER,INVITE,BYE,ACK,CANCEL,SUBSCRIBE,NOTIFY,MESSAGE User-Agent: IntERLab User Agent 1.0a Event: presence Expires: 600 Accept: application/pidf+xml,application/xpidf+xml,application/xvcresource+xml Contact: sip:andrey@203.159.32.39:5060 Authorization: Digest username="andrey",realm="sip.interlab.ait.ac.th",nonce="439ee222efefefbb8cbb78e75d6d15b723a1e1d0",uri="sip:12345@sip.interlab.ait.ac.th",response="1c7fa7ceb1f654d0e2ea91c54823bb8d" From: "Andrey Kuprianov" sip:andrey@sip.interlab.ait.ac.th;tag=15493888 Content-Length: 0
. . . . . .
And so it goes, until SER replies with Timeout.
Can you tell me what is wrong???
On 12/13/05, Andrey Kouprianov andrey.kouprianov@gmail.com wrote:
Hi,
I think the problem is solved... I forgot to mention that if I subscribed to myself, then it always worked... So, i plugged in the code for authentication, and it seemed to start working well for every other subscription. I also forgot that RFC metion, that it's a must to authenticate subscriptions. Is that what SER must do for subscriptions??? Is that the case?
Anyway, my SUBSCRIBE request is as follows:
SUBSCRIBE sip:12345@203.159.32.35:5060 SIP/2.0 Call-ID: 4c9d9cf6ff739599a9a3648001df9239@203.159.32.35 CSeq: 1 SUBSCRIBE From: "12345" sip:12345@sip.interlab.ait.ac.th;tag=32997440 To: sip:12345@sip.interlab.ait.ac.th Via: SIP/2.0/UDP 203.159.31.36;branch=0,SIP/2.0/UDP 203.159.32.35:5060;branch=z9 hG4bKb44ee5d83eb2b06d538a6152ca27914a Max-Forwards: 16 Allow: REGISTER,INVITE,BYE,ACK,CANCEL,SUBSCRIBE,NOTIFY,MESSAGE User-Agent: IntERLab User Agent 1.0a Event: presence Expires: 600 Accept: application/pidf+xml,application/xpidf+xml,application/xvcresource+xml Contact: sip:12345@203.159.32.35:5060 Content-Length: 0
After that the 408 Timeout was issued by SER...
On 12/13/05, Jan Janak jan@iptel.org wrote:
Could you post your SIP message dumps ?
Jan.
On 13-12-2005 15:03, Andrey Kouprianov wrote:
Hi,
Im using ser 0.9.3. The PA and Watcher are located on my UA, so basically my SUBSCRIBEs and NOTIFYs just need to be forwarded between clients.
Here's a part of ser.cfg that does the SUBSCRIBE and NOTIFY processing (please, note that I disabled the authentication for now):
. . . . . .
if(method=="SUBSCRIBE") { if(!lookup("location") ) { log(1, "No registered user found for SUBSCRIBE request"); sl_send_reply("404", "Not Found"); break; }; };
if(method=="NOTIFY") { if (!lookup("location")) { log(1, "No registered user found for NOTIFY request"); sl_send_reply("404", "Not Found"); break; }; };
if( !t_relay() ) { sl_reply_error(); };
. . . . . . . .
The problem is that only SOMETIMES SUIBSCRIBEs and NOTIFYs get through without any problem. However, MOST OF THE TIMES they get stuck in the server. The message log does not show any errors and tracesviewer tool shows only retransmissions for the issued requests. In the end SER replies with 408 Timeout response. I have tried to use forward(uri:host, uri:port) instead of t_relay(), but result is the same.
I have used eyeBeam to do the presence subscriptions, and the result is the same as with my UA...
Can you, please, explain to me what might have happened??? I am out of ideas.
Andrey.
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
Could you make ngrep dumps on the server ? If SER replies with 408 that means it received the request and tried to forward it somewhere, but the dumps below do not show anything.
Do you have any record for sip:12345@sip.interlab.ait.ac.th in location table ?
Jan.
On 13-12-2005 22:01, Andrey Kouprianov wrote:
Hi,
I am having the same problem again.... SER just keeps on sending me back timeouts for SUBSCRIBES... The problem, as I described in previous emails, persists for any other presentity except myself.
Here's a part of ser.cfg:
. . . . . .
if(method=="SUBSCRIBE") { if (!www_authorize("sip.interlab.ait.ac.th", "subscriber")) { log(1, "Authentication for SUBSCRIBE"); www_challenge("sip.interlab.ait.ac.th", "0"); break; };
if(!lookup("location") ) { log(1, "No registered user found for SUBSCRIBE request"); sl_send_reply("404", "Not Found"); break; };
};
if(method=="NOTIFY") { if (!www_authorize("sip.interlab.ait.ac.th", "subscriber")) { log(1, "Authentication for SUBSCRIBE"); www_challenge("sip.interlab.ait.ac.th", "0"); break; };
if (!lookup("location")) { log(1, "No registered user found for NOTIFY request"); sl_send_reply("404", "Not Found"); break; };
};
if( !t_relay() ) { sl_reply_error(); };
. . . . . . . .
Here are the traces:
Message 1 from 203.159.32.39:5060 to 203.159.31.36:5060
SUBSCRIBE sip:12345@sip.interlab.ait.ac.th SIP/2.0 Call-ID: 7762edc6f3954c87c8b95a0270653250@203.159.32.39 CSeq: 1 SUBSCRIBE From: "Andrey Kuprianov" sip:andrey@sip.interlab.ait.ac.th;tag=15493888 To: sip:12345@sip.interlab.ait.ac.th Via: SIP/2.0/UDP 203.159.32.39:5060;branch=z9hG4bK3ad443c5b49de4b050bd2b028597a868 Max-Forwards: 70 Allow: REGISTER,INVITE,BYE,ACK,CANCEL,SUBSCRIBE,NOTIFY,MESSAGE User-Agent: IntERLab User Agent 1.0a Event: presence Expires: 600 Accept: application/pidf+xml,application/xpidf+xml,application/xvcresource+xml Contact: sip:andrey@203.159.32.39:5060 Content-Length: 0
Message 2 from 203.159.31.36:5060 to 203.159.32.39:5060
SIP/2.0 401 Unauthorized Call-ID: 7762edc6f3954c87c8b95a0270653250@203.159.32.39 CSeq: 1 SUBSCRIBE From: "Andrey Kuprianov" sip:andrey@sip.interlab.ait.ac.th;tag=15493888 To: sip:12345@sip.interlab.ait.ac.th;tag=1a5a85ff3e08e000f4c2527642cf14ac.5e75 Via: SIP/2.0/UDP 203.159.32.39:5060;branch=z9hG4bK3ad443c5b49de4b050bd2b028597a868 WWW-Authenticate: Digest realm="sip.interlab.ait.ac.th",nonce="439ee222efefefbb8cbb78e75d6d15b723a1e1d0" Server: Sip EXpress router (0.9.3 (i386/freebsd)) Warning: 392 203.159.31.36:5060 "Noisy feedback tells: pid=17754 req_src_ip=203.159.32.39 req_src_port=5060 in_uri=sip:12345@sip.interlab.ait.ac.th out_uri=sip:12345@sip.interlab.ait.ac.th via_cnt==1" Content-Length: 0
Message 3 from 203.159.32.39:5060 to 203.159.31.36:5060
SUBSCRIBE sip:12345@sip.interlab.ait.ac.th SIP/2.0 Call-ID: 7762edc6f3954c87c8b95a0270653250@203.159.32.39 CSeq: 2 SUBSCRIBE To: sip:12345@sip.interlab.ait.ac.th Via: SIP/2.0/UDP 203.159.32.39:5060;branch=z9hG4bK991c906a283ca5d57e8856c98097e81c Max-Forwards: 70 Allow: REGISTER,INVITE,BYE,ACK,CANCEL,SUBSCRIBE,NOTIFY,MESSAGE User-Agent: IntERLab User Agent 1.0a Event: presence Expires: 600 Accept: application/pidf+xml,application/xpidf+xml,application/xvcresource+xml Contact: sip:andrey@203.159.32.39:5060 Authorization: Digest username="andrey",realm="sip.interlab.ait.ac.th",nonce="439ee222efefefbb8cbb78e75d6d15b723a1e1d0",uri="sip:12345@sip.interlab.ait.ac.th",response="1c7fa7ceb1f654d0e2ea91c54823bb8d" From: "Andrey Kuprianov" sip:andrey@sip.interlab.ait.ac.th;tag=15493888 Content-Length: 0
Message 4 from 203.159.32.39:5060 to 203.159.31.36:5060
SUBSCRIBE sip:12345@sip.interlab.ait.ac.th SIP/2.0 Call-ID: 7762edc6f3954c87c8b95a0270653250@203.159.32.39 CSeq: 2 SUBSCRIBE To: sip:12345@sip.interlab.ait.ac.th Via: SIP/2.0/UDP 203.159.32.39:5060;branch=z9hG4bK991c906a283ca5d57e8856c98097e81c Max-Forwards: 70 Allow: REGISTER,INVITE,BYE,ACK,CANCEL,SUBSCRIBE,NOTIFY,MESSAGE User-Agent: IntERLab User Agent 1.0a Event: presence Expires: 600 Accept: application/pidf+xml,application/xpidf+xml,application/xvcresource+xml Contact: sip:andrey@203.159.32.39:5060 Authorization: Digest username="andrey",realm="sip.interlab.ait.ac.th",nonce="439ee222efefefbb8cbb78e75d6d15b723a1e1d0",uri="sip:12345@sip.interlab.ait.ac.th",response="1c7fa7ceb1f654d0e2ea91c54823bb8d" From: "Andrey Kuprianov" sip:andrey@sip.interlab.ait.ac.th;tag=15493888 Content-Length: 0
. . . . . .
And so it goes, until SER replies with Timeout.
Can you tell me what is wrong???
On 12/13/05, Andrey Kouprianov andrey.kouprianov@gmail.com wrote:
Hi,
I think the problem is solved... I forgot to mention that if I subscribed to myself, then it always worked... So, i plugged in the code for authentication, and it seemed to start working well for every other subscription. I also forgot that RFC metion, that it's a must to authenticate subscriptions. Is that what SER must do for subscriptions??? Is that the case?
Anyway, my SUBSCRIBE request is as follows:
SUBSCRIBE sip:12345@203.159.32.35:5060 SIP/2.0 Call-ID: 4c9d9cf6ff739599a9a3648001df9239@203.159.32.35 CSeq: 1 SUBSCRIBE From: "12345" sip:12345@sip.interlab.ait.ac.th;tag=32997440 To: sip:12345@sip.interlab.ait.ac.th Via: SIP/2.0/UDP 203.159.31.36;branch=0,SIP/2.0/UDP 203.159.32.35:5060;branch=z9 hG4bKb44ee5d83eb2b06d538a6152ca27914a Max-Forwards: 16 Allow: REGISTER,INVITE,BYE,ACK,CANCEL,SUBSCRIBE,NOTIFY,MESSAGE User-Agent: IntERLab User Agent 1.0a Event: presence Expires: 600 Accept: application/pidf+xml,application/xpidf+xml,application/xvcresource+xml Contact: sip:12345@203.159.32.35:5060 Content-Length: 0
After that the 408 Timeout was issued by SER...
On 12/13/05, Jan Janak jan@iptel.org wrote:
Could you post your SIP message dumps ?
Jan.
On 13-12-2005 15:03, Andrey Kouprianov wrote:
Hi,
Im using ser 0.9.3. The PA and Watcher are located on my UA, so basically my SUBSCRIBEs and NOTIFYs just need to be forwarded between clients.
Here's a part of ser.cfg that does the SUBSCRIBE and NOTIFY processing (please, note that I disabled the authentication for now):
. . . . . .
if(method=="SUBSCRIBE") { if(!lookup("location") ) { log(1, "No registered user found for SUBSCRIBE request"); sl_send_reply("404", "Not Found"); break; }; };
if(method=="NOTIFY") { if (!lookup("location")) { log(1, "No registered user found for NOTIFY request"); sl_send_reply("404", "Not Found"); break; }; };
if( !t_relay() ) { sl_reply_error(); };
. . . . . . . .
The problem is that only SOMETIMES SUIBSCRIBEs and NOTIFYs get through without any problem. However, MOST OF THE TIMES they get stuck in the server. The message log does not show any errors and tracesviewer tool shows only retransmissions for the issued requests. In the end SER replies with 408 Timeout response. I have tried to use forward(uri:host, uri:port) instead of t_relay(), but result is the same.
I have used eyeBeam to do the presence subscriptions, and the result is the same as with my UA...
Can you, please, explain to me what might have happened??? I am out of ideas.
Andrey.
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
Hi,
Im talking to Vaclav. The subject is "Please, help with SUBSCRIBE timeouts".. We were discussing this problem, and still cannot find any solution... Please, take a look... Im stuck there hopelessly.
On 12/14/05, Jan Janak jan@iptel.org wrote:
Could you make ngrep dumps on the server ? If SER replies with 408 that means it received the request and tried to forward it somewhere, but the dumps below do not show anything.
Do you have any record for sip:12345@sip.interlab.ait.ac.th in location table ?
Jan.
On 13-12-2005 22:01, Andrey Kouprianov wrote:
Hi,
I am having the same problem again.... SER just keeps on sending me back timeouts for SUBSCRIBES... The problem, as I described in previous emails, persists for any other presentity except myself.
Here's a part of ser.cfg:
. . . . . .
if(method=="SUBSCRIBE") { if (!www_authorize("sip.interlab.ait.ac.th", "subscriber")) { log(1, "Authentication for SUBSCRIBE"); www_challenge("sip.interlab.ait.ac.th", "0"); break; };
if(!lookup("location") ) { log(1, "No registered user found for SUBSCRIBE request"); sl_send_reply("404", "Not Found"); break; };
};
if(method=="NOTIFY") { if (!www_authorize("sip.interlab.ait.ac.th", "subscriber")) { log(1, "Authentication for SUBSCRIBE"); www_challenge("sip.interlab.ait.ac.th", "0"); break; };
if (!lookup("location")) { log(1, "No registered user found for NOTIFY request"); sl_send_reply("404", "Not Found"); break; };
};
if( !t_relay() ) { sl_reply_error(); };
. . . . . . . .
Here are the traces:
Message 1 from 203.159.32.39:5060 to 203.159.31.36:5060
SUBSCRIBE sip:12345@sip.interlab.ait.ac.th SIP/2.0 Call-ID: 7762edc6f3954c87c8b95a0270653250@203.159.32.39 CSeq: 1 SUBSCRIBE From: "Andrey Kuprianov" sip:andrey@sip.interlab.ait.ac.th;tag=15493888 To: sip:12345@sip.interlab.ait.ac.th Via: SIP/2.0/UDP 203.159.32.39:5060;branch=z9hG4bK3ad443c5b49de4b050bd2b028597a868 Max-Forwards: 70 Allow: REGISTER,INVITE,BYE,ACK,CANCEL,SUBSCRIBE,NOTIFY,MESSAGE User-Agent: IntERLab User Agent 1.0a Event: presence Expires: 600 Accept: application/pidf+xml,application/xpidf+xml,application/xvcresource+xml Contact: sip:andrey@203.159.32.39:5060 Content-Length: 0
Message 2 from 203.159.31.36:5060 to 203.159.32.39:5060
SIP/2.0 401 Unauthorized Call-ID: 7762edc6f3954c87c8b95a0270653250@203.159.32.39 CSeq: 1 SUBSCRIBE From: "Andrey Kuprianov" sip:andrey@sip.interlab.ait.ac.th;tag=15493888 To: sip:12345@sip.interlab.ait.ac.th;tag=1a5a85ff3e08e000f4c2527642cf14ac.5e75 Via: SIP/2.0/UDP 203.159.32.39:5060;branch=z9hG4bK3ad443c5b49de4b050bd2b028597a868 WWW-Authenticate: Digest realm="sip.interlab.ait.ac.th",nonce="439ee222efefefbb8cbb78e75d6d15b723a1e1d0" Server: Sip EXpress router (0.9.3 (i386/freebsd)) Warning: 392 203.159.31.36:5060 "Noisy feedback tells: pid=17754 req_src_ip=203.159.32.39 req_src_port=5060 in_uri=sip:12345@sip.interlab.ait.ac.th out_uri=sip:12345@sip.interlab.ait.ac.th via_cnt==1" Content-Length: 0
Message 3 from 203.159.32.39:5060 to 203.159.31.36:5060
SUBSCRIBE sip:12345@sip.interlab.ait.ac.th SIP/2.0 Call-ID: 7762edc6f3954c87c8b95a0270653250@203.159.32.39 CSeq: 2 SUBSCRIBE To: sip:12345@sip.interlab.ait.ac.th Via: SIP/2.0/UDP 203.159.32.39:5060;branch=z9hG4bK991c906a283ca5d57e8856c98097e81c Max-Forwards: 70 Allow: REGISTER,INVITE,BYE,ACK,CANCEL,SUBSCRIBE,NOTIFY,MESSAGE User-Agent: IntERLab User Agent 1.0a Event: presence Expires: 600 Accept: application/pidf+xml,application/xpidf+xml,application/xvcresource+xml Contact: sip:andrey@203.159.32.39:5060 Authorization: Digest username="andrey",realm="sip.interlab.ait.ac.th",nonce="439ee222efefefbb8cbb78e75d6d15b723a1e1d0",uri="sip:12345@sip.interlab.ait.ac.th",response="1c7fa7ceb1f654d0e2ea91c54823bb8d" From: "Andrey Kuprianov" sip:andrey@sip.interlab.ait.ac.th;tag=15493888 Content-Length: 0
Message 4 from 203.159.32.39:5060 to 203.159.31.36:5060
SUBSCRIBE sip:12345@sip.interlab.ait.ac.th SIP/2.0 Call-ID: 7762edc6f3954c87c8b95a0270653250@203.159.32.39 CSeq: 2 SUBSCRIBE To: sip:12345@sip.interlab.ait.ac.th Via: SIP/2.0/UDP 203.159.32.39:5060;branch=z9hG4bK991c906a283ca5d57e8856c98097e81c Max-Forwards: 70 Allow: REGISTER,INVITE,BYE,ACK,CANCEL,SUBSCRIBE,NOTIFY,MESSAGE User-Agent: IntERLab User Agent 1.0a Event: presence Expires: 600 Accept: application/pidf+xml,application/xpidf+xml,application/xvcresource+xml Contact: sip:andrey@203.159.32.39:5060 Authorization: Digest username="andrey",realm="sip.interlab.ait.ac.th",nonce="439ee222efefefbb8cbb78e75d6d15b723a1e1d0",uri="sip:12345@sip.interlab.ait.ac.th",response="1c7fa7ceb1f654d0e2ea91c54823bb8d" From: "Andrey Kuprianov" sip:andrey@sip.interlab.ait.ac.th;tag=15493888 Content-Length: 0
. . . . . .
And so it goes, until SER replies with Timeout.
Can you tell me what is wrong???
On 12/13/05, Andrey Kouprianov andrey.kouprianov@gmail.com wrote:
Hi,
I think the problem is solved... I forgot to mention that if I subscribed to myself, then it always worked... So, i plugged in the code for authentication, and it seemed to start working well for every other subscription. I also forgot that RFC metion, that it's a must to authenticate subscriptions. Is that what SER must do for subscriptions??? Is that the case?
Anyway, my SUBSCRIBE request is as follows:
SUBSCRIBE sip:12345@203.159.32.35:5060 SIP/2.0 Call-ID: 4c9d9cf6ff739599a9a3648001df9239@203.159.32.35 CSeq: 1 SUBSCRIBE From: "12345" sip:12345@sip.interlab.ait.ac.th;tag=32997440 To: sip:12345@sip.interlab.ait.ac.th Via: SIP/2.0/UDP 203.159.31.36;branch=0,SIP/2.0/UDP 203.159.32.35:5060;branch=z9 hG4bKb44ee5d83eb2b06d538a6152ca27914a Max-Forwards: 16 Allow: REGISTER,INVITE,BYE,ACK,CANCEL,SUBSCRIBE,NOTIFY,MESSAGE User-Agent: IntERLab User Agent 1.0a Event: presence Expires: 600 Accept: application/pidf+xml,application/xpidf+xml,application/xvcresource+xml Contact: sip:12345@203.159.32.35:5060 Content-Length: 0
After that the 408 Timeout was issued by SER...
On 12/13/05, Jan Janak jan@iptel.org wrote:
Could you post your SIP message dumps ?
Jan.
On 13-12-2005 15:03, Andrey Kouprianov wrote:
Hi,
Im using ser 0.9.3. The PA and Watcher are located on my UA, so basically my SUBSCRIBEs and NOTIFYs just need to be forwarded between clients.
Here's a part of ser.cfg that does the SUBSCRIBE and NOTIFY processing (please, note that I disabled the authentication for now):
. . . . . .
if(method=="SUBSCRIBE") { if(!lookup("location") ) { log(1, "No registered user found for SUBSCRIBE request"); sl_send_reply("404", "Not Found"); break; }; };
if(method=="NOTIFY") { if (!lookup("location")) { log(1, "No registered user found for NOTIFY request"); sl_send_reply("404", "Not Found"); break; }; };
if( !t_relay() ) { sl_reply_error(); };
. . . . . . . .
The problem is that only SOMETIMES SUIBSCRIBEs and NOTIFYs get through without any problem. However, MOST OF THE TIMES they get stuck in the server. The message log does not show any errors and tracesviewer tool shows only retransmissions for the issued requests. In the end SER replies with 408 Timeout response. I have tried to use forward(uri:host, uri:port) instead of t_relay(), but result is the same.
I have used eyeBeam to do the presence subscriptions, and the result is the same as with my UA...
Can you, please, explain to me what might have happened??? I am out of ideas.
Andrey.
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
So does SER forward the request somewhere ? If so then what is the Request-URI ? It would also help you you could disclose the 408 you are getting from SER.
Jan.
On 14-12-2005 16:43, Andrey Kouprianov wrote:
Hi,
Im talking to Vaclav. The subject is "Please, help with SUBSCRIBE timeouts".. We were discussing this problem, and still cannot find any solution... Please, take a look... Im stuck there hopelessly.
On 12/14/05, Jan Janak jan@iptel.org wrote:
Could you make ngrep dumps on the server ? If SER replies with 408 that means it received the request and tried to forward it somewhere, but the dumps below do not show anything.
Do you have any record for sip:12345@sip.interlab.ait.ac.th in location table ?
Jan.
On 13-12-2005 22:01, Andrey Kouprianov wrote:
Hi,
I am having the same problem again.... SER just keeps on sending me back timeouts for SUBSCRIBES... The problem, as I described in previous emails, persists for any other presentity except myself.
Here's a part of ser.cfg:
. . . . . .
if(method=="SUBSCRIBE") { if (!www_authorize("sip.interlab.ait.ac.th", "subscriber")) { log(1, "Authentication for SUBSCRIBE"); www_challenge("sip.interlab.ait.ac.th", "0"); break; };
if(!lookup("location") ) { log(1, "No registered user found for SUBSCRIBE request"); sl_send_reply("404", "Not Found"); break; };
};
if(method=="NOTIFY") { if (!www_authorize("sip.interlab.ait.ac.th", "subscriber")) { log(1, "Authentication for SUBSCRIBE"); www_challenge("sip.interlab.ait.ac.th", "0"); break; };
if (!lookup("location")) { log(1, "No registered user found for NOTIFY request"); sl_send_reply("404", "Not Found"); break; };
};
if( !t_relay() ) { sl_reply_error(); };
. . . . . . . .
Here are the traces:
Message 1 from 203.159.32.39:5060 to 203.159.31.36:5060
SUBSCRIBE sip:12345@sip.interlab.ait.ac.th SIP/2.0 Call-ID: 7762edc6f3954c87c8b95a0270653250@203.159.32.39 CSeq: 1 SUBSCRIBE From: "Andrey Kuprianov" sip:andrey@sip.interlab.ait.ac.th;tag=15493888 To: sip:12345@sip.interlab.ait.ac.th Via: SIP/2.0/UDP 203.159.32.39:5060;branch=z9hG4bK3ad443c5b49de4b050bd2b028597a868 Max-Forwards: 70 Allow: REGISTER,INVITE,BYE,ACK,CANCEL,SUBSCRIBE,NOTIFY,MESSAGE User-Agent: IntERLab User Agent 1.0a Event: presence Expires: 600 Accept: application/pidf+xml,application/xpidf+xml,application/xvcresource+xml Contact: sip:andrey@203.159.32.39:5060 Content-Length: 0
Message 2 from 203.159.31.36:5060 to 203.159.32.39:5060
SIP/2.0 401 Unauthorized Call-ID: 7762edc6f3954c87c8b95a0270653250@203.159.32.39 CSeq: 1 SUBSCRIBE From: "Andrey Kuprianov" sip:andrey@sip.interlab.ait.ac.th;tag=15493888 To: sip:12345@sip.interlab.ait.ac.th;tag=1a5a85ff3e08e000f4c2527642cf14ac.5e75 Via: SIP/2.0/UDP 203.159.32.39:5060;branch=z9hG4bK3ad443c5b49de4b050bd2b028597a868 WWW-Authenticate: Digest realm="sip.interlab.ait.ac.th",nonce="439ee222efefefbb8cbb78e75d6d15b723a1e1d0" Server: Sip EXpress router (0.9.3 (i386/freebsd)) Warning: 392 203.159.31.36:5060 "Noisy feedback tells: pid=17754 req_src_ip=203.159.32.39 req_src_port=5060 in_uri=sip:12345@sip.interlab.ait.ac.th out_uri=sip:12345@sip.interlab.ait.ac.th via_cnt==1" Content-Length: 0
Message 3 from 203.159.32.39:5060 to 203.159.31.36:5060
SUBSCRIBE sip:12345@sip.interlab.ait.ac.th SIP/2.0 Call-ID: 7762edc6f3954c87c8b95a0270653250@203.159.32.39 CSeq: 2 SUBSCRIBE To: sip:12345@sip.interlab.ait.ac.th Via: SIP/2.0/UDP 203.159.32.39:5060;branch=z9hG4bK991c906a283ca5d57e8856c98097e81c Max-Forwards: 70 Allow: REGISTER,INVITE,BYE,ACK,CANCEL,SUBSCRIBE,NOTIFY,MESSAGE User-Agent: IntERLab User Agent 1.0a Event: presence Expires: 600 Accept: application/pidf+xml,application/xpidf+xml,application/xvcresource+xml Contact: sip:andrey@203.159.32.39:5060 Authorization: Digest username="andrey",realm="sip.interlab.ait.ac.th",nonce="439ee222efefefbb8cbb78e75d6d15b723a1e1d0",uri="sip:12345@sip.interlab.ait.ac.th",response="1c7fa7ceb1f654d0e2ea91c54823bb8d" From: "Andrey Kuprianov" sip:andrey@sip.interlab.ait.ac.th;tag=15493888 Content-Length: 0
Message 4 from 203.159.32.39:5060 to 203.159.31.36:5060
SUBSCRIBE sip:12345@sip.interlab.ait.ac.th SIP/2.0 Call-ID: 7762edc6f3954c87c8b95a0270653250@203.159.32.39 CSeq: 2 SUBSCRIBE To: sip:12345@sip.interlab.ait.ac.th Via: SIP/2.0/UDP 203.159.32.39:5060;branch=z9hG4bK991c906a283ca5d57e8856c98097e81c Max-Forwards: 70 Allow: REGISTER,INVITE,BYE,ACK,CANCEL,SUBSCRIBE,NOTIFY,MESSAGE User-Agent: IntERLab User Agent 1.0a Event: presence Expires: 600 Accept: application/pidf+xml,application/xpidf+xml,application/xvcresource+xml Contact: sip:andrey@203.159.32.39:5060 Authorization: Digest username="andrey",realm="sip.interlab.ait.ac.th",nonce="439ee222efefefbb8cbb78e75d6d15b723a1e1d0",uri="sip:12345@sip.interlab.ait.ac.th",response="1c7fa7ceb1f654d0e2ea91c54823bb8d" From: "Andrey Kuprianov" sip:andrey@sip.interlab.ait.ac.th;tag=15493888 Content-Length: 0
. . . . . .
And so it goes, until SER replies with Timeout.
Can you tell me what is wrong???
On 12/13/05, Andrey Kouprianov andrey.kouprianov@gmail.com wrote:
Hi,
I think the problem is solved... I forgot to mention that if I subscribed to myself, then it always worked... So, i plugged in the code for authentication, and it seemed to start working well for every other subscription. I also forgot that RFC metion, that it's a must to authenticate subscriptions. Is that what SER must do for subscriptions??? Is that the case?
Anyway, my SUBSCRIBE request is as follows:
SUBSCRIBE sip:12345@203.159.32.35:5060 SIP/2.0 Call-ID: 4c9d9cf6ff739599a9a3648001df9239@203.159.32.35 CSeq: 1 SUBSCRIBE From: "12345" sip:12345@sip.interlab.ait.ac.th;tag=32997440 To: sip:12345@sip.interlab.ait.ac.th Via: SIP/2.0/UDP 203.159.31.36;branch=0,SIP/2.0/UDP 203.159.32.35:5060;branch=z9 hG4bKb44ee5d83eb2b06d538a6152ca27914a Max-Forwards: 16 Allow: REGISTER,INVITE,BYE,ACK,CANCEL,SUBSCRIBE,NOTIFY,MESSAGE User-Agent: IntERLab User Agent 1.0a Event: presence Expires: 600 Accept: application/pidf+xml,application/xpidf+xml,application/xvcresource+xml Contact: sip:12345@203.159.32.35:5060 Content-Length: 0
After that the 408 Timeout was issued by SER...
On 12/13/05, Jan Janak jan@iptel.org wrote:
Could you post your SIP message dumps ?
Jan.
On 13-12-2005 15:03, Andrey Kouprianov wrote:
Hi,
Im using ser 0.9.3. The PA and Watcher are located on my UA, so basically my SUBSCRIBEs and NOTIFYs just need to be forwarded between clients.
Here's a part of ser.cfg that does the SUBSCRIBE and NOTIFY processing (please, note that I disabled the authentication for now):
. . . . . .
if(method=="SUBSCRIBE") { if(!lookup("location") ) { log(1, "No registered user found for SUBSCRIBE request"); sl_send_reply("404", "Not Found"); break; }; };
if(method=="NOTIFY") { if (!lookup("location")) { log(1, "No registered user found for NOTIFY request"); sl_send_reply("404", "Not Found"); break; }; };
if( !t_relay() ) { sl_reply_error(); };
. . . . . . . .
The problem is that only SOMETIMES SUIBSCRIBEs and NOTIFYs get through without any problem. However, MOST OF THE TIMES they get stuck in the server. The message log does not show any errors and tracesviewer tool shows only retransmissions for the issued requests. In the end SER replies with 408 Timeout response. I have tried to use forward(uri:host, uri:port) instead of t_relay(), but result is the same.
I have used eyeBeam to do the presence subscriptions, and the result is the same as with my UA...
Can you, please, explain to me what might have happened??? I am out of ideas.
Andrey.
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
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
Yes, it does forward it to the remote UA (i posted the traces from the server under the mailing list subject that i mentioned to you in my previous mail).... and it seems that 408 is not generated by SER (it's not in the server traces).. seems like 408 comes from the remote UA itself...
And about uri... The original uri is: sip:12345@sip.interlab.ait.ac.th When SER processes it, the forwarded uri is: sip:12345@203.159.32.38:5060
On 12/14/05, Jan Janak jan@iptel.org wrote:
So does SER forward the request somewhere ? If so then what is the Request-URI ? It would also help you you could disclose the 408 you are getting from SER.
Jan.
On 14-12-2005 16:43, Andrey Kouprianov wrote:
Hi,
Im talking to Vaclav. The subject is "Please, help with SUBSCRIBE timeouts".. We were discussing this problem, and still cannot find any solution... Please, take a look... Im stuck there hopelessly.
On 12/14/05, Jan Janak jan@iptel.org wrote:
Could you make ngrep dumps on the server ? If SER replies with 408 that means it received the request and tried to forward it somewhere, but the dumps below do not show anything.
Do you have any record for sip:12345@sip.interlab.ait.ac.th in location table ?
Jan.
On 13-12-2005 22:01, Andrey Kouprianov wrote:
Hi,
I am having the same problem again.... SER just keeps on sending me back timeouts for SUBSCRIBES... The problem, as I described in previous emails, persists for any other presentity except myself.
Here's a part of ser.cfg:
. . . . . .
if(method=="SUBSCRIBE") { if (!www_authorize("sip.interlab.ait.ac.th", "subscriber")) { log(1, "Authentication for SUBSCRIBE"); www_challenge("sip.interlab.ait.ac.th", "0"); break; };
if(!lookup("location") ) { log(1, "No registered user found for SUBSCRIBE request"); sl_send_reply("404", "Not Found"); break; };
};
if(method=="NOTIFY") { if (!www_authorize("sip.interlab.ait.ac.th", "subscriber")) { log(1, "Authentication for SUBSCRIBE"); www_challenge("sip.interlab.ait.ac.th", "0"); break; };
if (!lookup("location")) { log(1, "No registered user found for NOTIFY request"); sl_send_reply("404", "Not Found"); break; };
};
if( !t_relay() ) { sl_reply_error(); };
. . . . . . . .
Here are the traces:
Message 1 from 203.159.32.39:5060 to 203.159.31.36:5060
SUBSCRIBE sip:12345@sip.interlab.ait.ac.th SIP/2.0 Call-ID: 7762edc6f3954c87c8b95a0270653250@203.159.32.39 CSeq: 1 SUBSCRIBE From: "Andrey Kuprianov" sip:andrey@sip.interlab.ait.ac.th;tag=15493888 To: sip:12345@sip.interlab.ait.ac.th Via: SIP/2.0/UDP 203.159.32.39:5060;branch=z9hG4bK3ad443c5b49de4b050bd2b028597a868 Max-Forwards: 70 Allow: REGISTER,INVITE,BYE,ACK,CANCEL,SUBSCRIBE,NOTIFY,MESSAGE User-Agent: IntERLab User Agent 1.0a Event: presence Expires: 600 Accept: application/pidf+xml,application/xpidf+xml,application/xvcresource+xml Contact: sip:andrey@203.159.32.39:5060 Content-Length: 0
Message 2 from 203.159.31.36:5060 to 203.159.32.39:5060
SIP/2.0 401 Unauthorized Call-ID: 7762edc6f3954c87c8b95a0270653250@203.159.32.39 CSeq: 1 SUBSCRIBE From: "Andrey Kuprianov" sip:andrey@sip.interlab.ait.ac.th;tag=15493888 To: sip:12345@sip.interlab.ait.ac.th;tag=1a5a85ff3e08e000f4c2527642cf14ac.5e75 Via: SIP/2.0/UDP 203.159.32.39:5060;branch=z9hG4bK3ad443c5b49de4b050bd2b028597a868 WWW-Authenticate: Digest realm="sip.interlab.ait.ac.th",nonce="439ee222efefefbb8cbb78e75d6d15b723a1e1d0" Server: Sip EXpress router (0.9.3 (i386/freebsd)) Warning: 392 203.159.31.36:5060 "Noisy feedback tells: pid=17754 req_src_ip=203.159.32.39 req_src_port=5060 in_uri=sip:12345@sip.interlab.ait.ac.th out_uri=sip:12345@sip.interlab.ait.ac.th via_cnt==1" Content-Length: 0
Message 3 from 203.159.32.39:5060 to 203.159.31.36:5060
SUBSCRIBE sip:12345@sip.interlab.ait.ac.th SIP/2.0 Call-ID: 7762edc6f3954c87c8b95a0270653250@203.159.32.39 CSeq: 2 SUBSCRIBE To: sip:12345@sip.interlab.ait.ac.th Via: SIP/2.0/UDP 203.159.32.39:5060;branch=z9hG4bK991c906a283ca5d57e8856c98097e81c Max-Forwards: 70 Allow: REGISTER,INVITE,BYE,ACK,CANCEL,SUBSCRIBE,NOTIFY,MESSAGE User-Agent: IntERLab User Agent 1.0a Event: presence Expires: 600 Accept: application/pidf+xml,application/xpidf+xml,application/xvcresource+xml Contact: sip:andrey@203.159.32.39:5060 Authorization: Digest username="andrey",realm="sip.interlab.ait.ac.th",nonce="439ee222efefefbb8cbb78e75d6d15b723a1e1d0",uri="sip:12345@sip.interlab.ait.ac.th",response="1c7fa7ceb1f654d0e2ea91c54823bb8d" From: "Andrey Kuprianov" sip:andrey@sip.interlab.ait.ac.th;tag=15493888 Content-Length: 0
Message 4 from 203.159.32.39:5060 to 203.159.31.36:5060
SUBSCRIBE sip:12345@sip.interlab.ait.ac.th SIP/2.0 Call-ID: 7762edc6f3954c87c8b95a0270653250@203.159.32.39 CSeq: 2 SUBSCRIBE To: sip:12345@sip.interlab.ait.ac.th Via: SIP/2.0/UDP 203.159.32.39:5060;branch=z9hG4bK991c906a283ca5d57e8856c98097e81c Max-Forwards: 70 Allow: REGISTER,INVITE,BYE,ACK,CANCEL,SUBSCRIBE,NOTIFY,MESSAGE User-Agent: IntERLab User Agent 1.0a Event: presence Expires: 600 Accept: application/pidf+xml,application/xpidf+xml,application/xvcresource+xml Contact: sip:andrey@203.159.32.39:5060 Authorization: Digest username="andrey",realm="sip.interlab.ait.ac.th",nonce="439ee222efefefbb8cbb78e75d6d15b723a1e1d0",uri="sip:12345@sip.interlab.ait.ac.th",response="1c7fa7ceb1f654d0e2ea91c54823bb8d" From: "Andrey Kuprianov" sip:andrey@sip.interlab.ait.ac.th;tag=15493888 Content-Length: 0
. . . . . .
And so it goes, until SER replies with Timeout.
Can you tell me what is wrong???
On 12/13/05, Andrey Kouprianov andrey.kouprianov@gmail.com wrote:
Hi,
I think the problem is solved... I forgot to mention that if I subscribed to myself, then it always worked... So, i plugged in the code for authentication, and it seemed to start working well for every other subscription. I also forgot that RFC metion, that it's a must to authenticate subscriptions. Is that what SER must do for subscriptions??? Is that the case?
Anyway, my SUBSCRIBE request is as follows:
SUBSCRIBE sip:12345@203.159.32.35:5060 SIP/2.0 Call-ID: 4c9d9cf6ff739599a9a3648001df9239@203.159.32.35 CSeq: 1 SUBSCRIBE From: "12345" sip:12345@sip.interlab.ait.ac.th;tag=32997440 To: sip:12345@sip.interlab.ait.ac.th Via: SIP/2.0/UDP 203.159.31.36;branch=0,SIP/2.0/UDP 203.159.32.35:5060;branch=z9 hG4bKb44ee5d83eb2b06d538a6152ca27914a Max-Forwards: 16 Allow: REGISTER,INVITE,BYE,ACK,CANCEL,SUBSCRIBE,NOTIFY,MESSAGE User-Agent: IntERLab User Agent 1.0a Event: presence Expires: 600 Accept: application/pidf+xml,application/xpidf+xml,application/xvcresource+xml Contact: sip:12345@203.159.32.35:5060 Content-Length: 0
After that the 408 Timeout was issued by SER...
On 12/13/05, Jan Janak jan@iptel.org wrote:
Could you post your SIP message dumps ?
Jan.
On 13-12-2005 15:03, Andrey Kouprianov wrote: > Hi, > > Im using ser 0.9.3. The PA and Watcher are located on my UA, so > basically my SUBSCRIBEs and NOTIFYs just need to be forwarded between > clients. > > Here's a part of ser.cfg that does the SUBSCRIBE and NOTIFY > processing (please, note that I disabled the authentication for now): > > . . . . . . > > if(method=="SUBSCRIBE") { > if(!lookup("location") ) { > log(1, "No registered user found for SUBSCRIBE request"); > sl_send_reply("404", "Not Found"); > break; > }; > }; > > if(method=="NOTIFY") { > if (!lookup("location")) { > log(1, "No registered user found for NOTIFY request"); > sl_send_reply("404", "Not Found"); > break; > }; > }; > > if( !t_relay() ) { > sl_reply_error(); > }; > > . . . . . . . . > > The problem is that only SOMETIMES SUIBSCRIBEs and NOTIFYs get > through without any problem. However, MOST OF THE TIMES they get stuck > in the server. The message log does not show any errors and > tracesviewer tool shows only retransmissions for the issued requests. > In the end SER replies with 408 Timeout response. I have tried to use > forward(uri:host, uri:port) instead of t_relay(), but result is the > same. > > I have used eyeBeam to do the presence subscriptions, and the result > is the same as with my UA... > > Can you, please, explain to me what might have happened??? I am out of ideas. > > Andrey. > > _______________________________________________ > 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
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers