[OpenSIPS-Users] t_uac_dlg command through mi_datagram socket gives 400 bad headers

[Husnain Taseer]

Hi,

I have got hint from ctd.sh script and modified my string as per the string
being used in that script for INVITE. After modification I am getting error
Content-Type missing. The string is now as follows:

message=""":t_uac_dlg:
MESSAGE
sip:212897645 at 192.168.1.20
.
.
"From: <sip:212897554 at 192.168.1.20>\\r\\nTo:
<sip:212897645 at 192.168.1.20>\\r\\nContent-Type:
text/plain\\r\\np-identifier: Local_Socket_V1.0\\r\\n
"
"Hi
"
"""

​The debug logs for mi_datagram module are as follows:
​
Mar  6 16:01:53 VoIPDevSys opensips[26600]:
DBG:mi_datagram:identify_command: the command starts here:
t_uac_dlg:#012MESSAGE#012sip:212897645 at 192.168.1.20#012.#012.#012"
From: <sip:212897554 at 192.168.1.20>\r\nTo:
<sip:212897645 at 192.168.1.20>\r\nContent-Type:
text/plain\r\np-identifier: Local_Socket_V1.0\r\n#012"#012"Hi#012"
Mar  6 16:01:53 VoIPDevSys opensips[26600]:
DBG:mi_datagram:identify_command: the command is t_uac_dlg
Mar  6 16:01:53 VoIPDevSys opensips[26600]:
DBG:mi_datagram:identify_command: dtgram->len is 195
Mar  6 16:01:53 VoIPDevSys opensips[26600]:
DBG:mi_datagram:identify_command: dtgram->len is 183
Mar  6 16:01:53 VoIPDevSys opensips[26600]:
DBG:mi_datagram:mi_datagram_server: we have a valid command
Mar  6 16:01:53 VoIPDevSys opensips[26600]:
DBG:mi_datagram:mi_datagram_server: after identifing the command, the
received datagram is MESSAGE#012sip:212897645 at 192.168.1.20#012.#012.#012"From:
<sip:212897554 at 192.168.1.20>\r\nTo:
<sip:212897645 at 192.168.1.20>\r\nContent-Type:
text/plain\r\np-identifier: Local_Socket_V1.0\r\n#012"#012"Hi#012"

Mar  6 16:01:53 VoIPDevSys opensips[26600]:
DBG:mi_datagram:mi_datagram_parse_tree: adding node <> ; val <From: <
sip:212897554 at 192.168.1.20>\r\nTo:
<sip:212897645 at 192.168.1.20>\r\nContent-Type:
text/plain\r\np-identifier: Local_Socket_V1.0\r\n#012>
Mar  6 16:01:53 VoIPDevSys opensips[26600]:
DBG:mi_datagram:mi_datagram_parse_tree: the remaining datagram has 7 bytes
Mar  6 16:01:53 VoIPDevSys opensips[26600]:
DBG:mi_datagram:mi_datagram_parse_node: the remaining datagram to be parsed
is #012"Hi#012"#012 and 7 in length
Mar  6 16:01:53 VoIPDevSys opensips[26600]:
DBG:mi_datagram:mi_datagram_parse_node: we have a  quoted value, "Hi#012"
Mar  6 16:01:53 VoIPDevSys opensips[26600]:
DBG:mi_datagram:mi_datagram_parse_node: " found p is "
Mar  6 16:01:53 VoIPDevSys opensips[26600]:
DBG:mi_datagram:mi_datagram_parse_node: we have reached the end of attr
value, p is "
Mar  6 16:01:53 VoIPDevSys opensips[26600]:
DBG:mi_datagram:mi_datagram_parse_node: attr value <Hi#012> found
Mar  6 16:01:53 VoIPDevSys opensips[26600]:
DBG:mi_datagram:mi_datagram_parse_node: line ended properly case1
Mar  6 16:01:53 VoIPDevSys opensips[26600]:
DBG:mi_datagram:mi_datagram_parse_node: 1 data->len is 7
Mar  6 16:01:53 VoIPDevSys opensips[26600]:
DBG:mi_datagram:mi_datagram_parse_node: 2 data->len is 1
Mar  6 16:01:53 VoIPDevSys opensips[26600]:
DBG:mi_datagram:mi_datagram_parse_tree: adding node <> ; val <Hi#012>
Mar  6 16:01:53 VoIPDevSys opensips[26600]:
DBG:mi_datagram:mi_datagram_parse_tree: the remaining datagram has 1 bytes
Mar  6 16:01:53 VoIPDevSys opensips[26600]:
DBG:mi_datagram:mi_datagram_parse_node: the remaining datagram to be parsed
is #012 and 1 in length
Mar  6 16:01:53 VoIPDevSys opensips[26600]:
DBG:mi_datagram:mi_datagram_server: done parsing the mi tree
Mar  6 16:01:53 VoIPDevSys opensips[26600]:
DBG:mi_datagram:mi_datagram_server: command process (t_uac_dlg)succeded
Mar  6 16:01:53 VoIPDevSys opensips[26600]:
DBG:mi_datagram:mi_datagram_server: the response: 400 Content-Type
missin#012 has been sent in 24 octets

​From above logs I can see that Content-Type is present in the request but
still I am getting this error and opensips is sending back 400 Content-Type
missin#012​. The above logs are not complete if you need complete logs I
can give you on pastebin.


Regards,
*Husnain Taseer*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20170306/e98bf5d2/attachment.html>