THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#295 - UAC generates messages with a NULL body which failes in SANITY module check
User who did this - oren avraham (orenav)
----------
Thanks !
i've added the \r\n and it seems to work now...
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=295#comment901
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#295 - UAC generates messages with a NULL body which failes in SANITY module check
User who did this - Daniel-Constantin Mierla (miconda)
----------
Content-Type is not needed. I just added to have hdrs set, which now gives a hint of what might be the problem in your side, with this line:
$uac_req(hdrs) = $sht(websocket=>$si:$sp:hdrs);
Be sure $sht(websocket=>$si:$sp:hdrs) is ending in "\r\n", because must be in full header format: "Name: body\r\n"
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=295#comment900
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#295 - UAC generates messages with a NULL body which failes in SANITY module check
User who did this - oren avraham (orenav)
----------
I mean, when the body is empty, it is ok not to provide the content type header.
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=295#comment899
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#295 - UAC generates messages with a NULL body which failes in SANITY module check
User who did this - oren avraham (orenav)
----------
As you asked:
U 2013/05/27 00:25:52.090319 10.0.0.4:5060 -> 10.0.0.4:5060
REGISTER sip:oren@10.0.0.4 SIP/2.0.
Via: SIP/2.0/UDP 10.0.0.4;branch=z9hG4bKdf2a.37a13ec2.0.
To: sip:oren@10.0.0.4.
From: sip:oren@10.0.0.4;tag=ea1fc35981b38c23d4118e13e0c2a171-ffc8.
CSeq: 10 REGISTER.
Call-ID: 3f3dfd38-17008(a)10.0.0.4.
Max-Forwards: 70.
Content-Length: 0.
User-Agent: kamailio (4.0.1 (i386/linux)).
Contact: "Seller"<sip:oren@df7jal23ls0d.invalid;rtcweb-breaker=no;transport=ws>;expires=0;click2call=no.
I found the problem: because i dont provied the content-type header it happens. when i add it, like in your example, the problem is solved.
BUT acording to the RFC it is OK not to provide the Content-Type header....
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=295#comment898
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#295 - UAC generates messages with a NULL body which failes in SANITY module check
User who did this - Daniel-Constantin Mierla (miconda)
----------
I did a test with:
$uac_req(method)="REGISTER";
$uac_req(ruri) = "sip:testb@127.0.0.1:5090";
$uac_req(turi) = "sip:testb@127.0.0.1";
$uac_req(furi) = "sip:testa@127.0.0.1";
$uac_req(hdrs) = "Content-Type: text/plain\r\n";
uac_req_send();
and the result is ok:
REGISTER sip:testb@127.0.0.1:5090 SIP/2.0.
Via: SIP/2.0/UDP 127.0.0.1;branch=z9hG4bK8443.08598b30000000000000000000000000.0.
To: <sip:testb@127.0.0.1>.
From: <sip:testa@127.0.0.1>;tag=533cb9e91f4b999cf76861cbb9ed54ed-8f53.
CSeq: 10 REGISTER.
Call-ID: 5193b50938528bb9-25802(a)127.0.0.1.
Max-Forwards: 70.
Content-Length: 0.
User-Agent: kamailio (4.1.0-dev6 (x86_64/darwin)).
Content-Type: text/plain.
.
Provide a ngrep output of what you get, that's what I asked.
----------
More information can be found at the following URL:
https://sip-router.org/tracker/index.php?do=details&task_id=295#comment897
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.