Hello,

the headers have to be terminated in \r\n. In a shell script for click to dial, here is the used form:

cat > $FIFO <<EOF
:t_uac_dlg:$name
INVITE
$URI
.
.
"`printf "${FIXED_DLG}To: <$URI>\r\nCSeq: $CSEQ INVITE\r\nContent-Type: application/sdp\r\n"`
"
"`printf "v=0\r\no=click-to-dial 0 0 IN IP4 0.0.0.0\r\ns=session\r\nc=IN IP4 0.0.0.0\r\nb=CT:1000\r\nt=0 0\r\nm=audio 9 RTP/AVP 8 0\r\na=rtpmap:8 PCMA/8000\r\na=rtpmap:0 PCMU/8000\r\n"`
"

EOF

Cheers,
Daniel


On 12/16/11 10:02 AM, Sammy Govind wrote:
Hello list,

I'm using Kamailio 3.2 and am trying to send a SIP request from fifo to kamailio using below format.

#kamctl fifo t_uac_dlg MESSAGE sip:103@ mydomain.org  . . "From: 101@mydomain.org To: 103@mydomain.org Contact: mydomain.org Content-Type: text/plain; charset=UTF-8" "INVITE"

But I see this reply from Kamctl

database engine 'MYSQL' loaded
Control engine 'FIFO' loaded
entering fifo_cmd t_uac_dlg INVITE sip:103@ mydomain.org  . . From: 101@ mydomain.org  To: 103@ mydomain.org  Contact:  mydomain.org  Content-Type: text/plain; charset=UTF-8 INVITE
400 Bad headers
FIFO command was:
:t_uac_dlg:openser_receiver_25561
INVITE
sip:103@mydomain.org
.
.
From: 101@ mydomain.org  To: 103@ mydomain.org  Contact:  mydomain.org  Content-Type: text/plain; charset=UTF-8
INVITE



And in log file I see this output:

Dec 16 00:57:46 Kamailio3 /usr/local/sbin/kamailio[24541]: ERROR: <core> [parser/msg_parser.c:275]: ERROR: get_hdr_field: bad body for <From: 101@mydomain.org  To: 103@ mydomain.org  Contact:  mydomain.org  Content-Type: text/plain; charset=UTF-8INVITE#012>(4)
Dec 16 00:57:46 Kamailio3 /usr/local/sbin/kamailio[24541]: INFO: <core> [parser/msg_parser.c:353]: ERROR: bad header field [From: 101@mydomain.o]


Can anyone help..


Regards,
Sammy




_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

-- 
Daniel-Constantin Mierla -- http://www.asipto.com
http://linkedin.com/in/miconda -- http://twitter.com/miconda