<div dir="ltr">Problem is solved.<div><br></div><div>The problem was in wrong regeneration of headers in ACK requests (uac restore_mode parameter).</div><div>This parameter helps to modify From/To headers in all sequential requests and replies in the same way as it has been modified in initial invite.<br></div><div><br></div><div>The uac from/to replacement relies that parties keep the same from/to headers content.<br>The mechanism to replace A with B is to combine both and get the key X which is added in the record-route as parameter.<br>Then practically from A and X results B and from B and X results A. It's doing XOR over base64-encoded values.<br></div><div><br></div><div>And when endpoint or kamailio changes the mid dialog From or To URI, then XOR against the key produces wrong values.</div><div><br></div><div><br></div><div>So the solution was to change this:</div><div><div>modparam("uac","restore_mode","auto")</div><div>modparam("uac","restore_dlg",1)</div></div><div><br></div><div>To this one:</div><div><div>modparam("uac","restore_mode","none")</div><div>modparam("uac","restore_dlg",0)</div></div><div><br></div><div>This case doesn't mean that uac module works improperly, of course no.</div><div>This means, that this options can only be used in topologies that can admit such behavior.</div><div>In our case, kamailio changes $fU to internal numbers (before to send it to an internal agent) for consistent callerid presentation.</div><div><br></div><div>So be careful while using such options in your topologies.</div><div><br></div><div><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">2017-11-16 15:42 GMT+02:00 Donat Zenichev <span dir="ltr"><<a href="mailto:donat.zenichev@gmail.com" target="_blank">donat.zenichev@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><pre><font color="#000000"><span style="white-space:pre-wrap">Hi Daniel.
We are using now kamailio 4.4.6</span></font></pre><pre><font color="#000000"><span style="white-space:pre-wrap">"t</span></font>he latest release series should have a safety check.." does it mean stable 5.0.4 ?
Well it is a reasonable advice I think, we haven't tried this way, yet.
I thought about using uac + dialog module together, but this entails a lot of changes in common logic.
For that moment looks like disabling the restore_mode and restore_dlg parameters solved the problem.
So that, it is enough for me to keep calm. But further, I want to make an effort to turn on dialog/uac modules together.
Thanks for your answers.
I will continue this topic as soon as I will start to work with it.</pre><pre><font color="#000000"><span style="white-space:pre-wrap"><br></span></font></pre><pre><font color="#000000"><span style="white-space:pre-wrap">>Hello,
>
>it would be useful to know also the version of kamailio that is run
>there. The latest release series should have a safety check in order to
>prevent setting an invalid restored From/To URI.
>
>On the other hand, if the UA doesn't preserve the From/To, then it
>doesn't require to be unchanged, so the update (without auto restore) of
>the From/To can be done only for initial INVITE, when UA takes the
>caller/callee ids. For requests within the dialog, these headers can be
>left unchanged or changed to something like anonymous at anonymous.invalid
>
>The last option here, which is the safest, is to use dialog module
>together with uac, so uac module stores the From/To values inside the
>dialog and restores them from there, instead of relying on
>record-routing and the masking algorithm for values.
>
>Cheers,
>Daniel
>
>
</span></font><font color="#000000"><span style="white-space:pre-wrap">>>On 14.11.17 08:04, Julia Boudniatsky wrote:
>> Hello,
>>
>> It looks like headers "From" in initial INVITE and received message
>> are different.
>>
>> For example:
>> in INVITE : <sip:useragent7122 at kamailio_address:5068>>
>> in received message : <sip:useragent7122 at kamailio_address>>
>>
>> When you use header "From" transformation (I see Route with vsf),
>> restore may be correct only for exactly the same header "From".
>> Check may be port number is missing/added in received message header
>> "From".
>>
>> Best regards,
>> Julia
>>
>> On Mon, Nov 13, 2017 at 5:05 PM, Donat Zenichev
>> <donat.zenichev at <a href="http://gmail.com" target="_blank">gmail.com</a> <mailto:<a href="mailto:donat.zenichev" target="_blank">donat.zenichev</a> at <a href="http://gmail.com" target="_blank">gmail.com</a>>>>> wrote:
>>
>> Hi community.
>> We experience the problem with malformed messages.
>>
>> First of all, I want to say, that most of time kamailio works well
>> and nothing happens that can drop sessions.
>> But from time-to-time something changes (may be in the network)
>> and kamailio receives requests with malformed headers (To or From
>> hfs).
>>
>> The schema:
>> uplinks ->> kamailio <->> routing server (asterisk)
>>
>> Malformed messages were received only from asterisk server.
>> Sip debug on asterisk showed that messages were transmitted
>> correctly and headers were nice.
>> But kamailio obtains changed (broken) packets or perhaps can't
>> read them properly.
>>
>> How does it look like:
>> Nov 10 12:37:06 kamailio-name kamailio[965]: INFO: <script>>: Going
>> to NATMANAGE for BYE from sip:useragent7122 at kamailio_address:5068
>> (IP=wss:client_address:62881) -
>> R=sip:dialed_did_service at asterisk_address:50600
>> ID=<wbr>1b0044070de406153bf0e4b84d6bb7<wbr>93 at asterisk_address:50600
>> Nov 10 12:37:06 kamailio-name kamailio[965]: NOTICE: <script>>:
>> Relaying request to <null>> -
>> R=sip:dialed_did_service at asterisk_address:50600
>> ID=<wbr>1b0044070de406153bf0e4b84d6bb7<wbr>93 at asterisk_address:50600
>> Nov 10 12:37:06 kamailio-name kamailio[965]: ERROR: <core>>
>> [parser/parse_addr_spec.c:719]<wbr>: parse_addr_spec(): unexpected char
>> [<] in status 6: [<sip:useragent6] .
>> Nov 10 12:37:06 kamailio-name kamailio[965]: ERROR: <core>>
>> [parser/parse_from.c:75]: parse_from_header(): bad From header
>> [<sip:useragent6<+.w>>;tag=<wbr>jja7l45gd1]
>> Nov 10 12:37:06 kamailio-name kamailio[965]: ERROR: dialog
>> [dlg_cseq.c:89]: dlg_cseq_prepare_msg(): cannot parse FROM header
>> Nov 10 12:37:06 kamailio-name kamailio[937]: ERROR: <core>>
>> [parser/parse_addr_spec.c:719]<wbr>: parse_addr_spec(): unexpected char
>> [<] in status 6: [<sip:useragent6] .
>> Nov 10 12:37:06 kamailio-name kamailio[937]: ERROR: <core>>
>> [parser/parse_from.c:75]: parse_from_header(): bad From header
>> [<sip:useragent6<+.w>>;tag=<wbr>jja7l45gd1]
>> Nov 10 12:37:06 kamailio-name kamailio[937]: ERROR: dialog
>> [dlg_cseq.c:89]: dlg_cseq_prepare_msg(): cannot parse FROM header
>> Nov 10 12:37:06 kamailio-name kamailio[937]: ERROR: <core>>
>> [parser/parse_addr_spec.c:719]<wbr>: parse_addr_spec(): unexpected char
>> [<] in status 6: [<sip:useragent6] .
>> Nov 10 12:37:06 kamailio-name kamailio[937]: ERROR: <core>>
>> [parser/parse_from.c:75]: parse_from_header(): bad From header
>> [<sip:useragent6<+.w>>;tag=<wbr>jja7l45gd1]
>> Nov 10 12:37:06 kamailio-name kamailio[937]: ERROR: uac
>> [replace.c:783]: restore_uris_reply(): failed to find/parse FROM hdr
>> Nov 10 12:37:06 kamailio-name kamailio[937]: ERROR: <core>>
>> [parser/parse_addr_spec.c:719]<wbr>: parse_addr_spec(): unexpected char
>> [<] in status 6: [<sip:useragent6] .
>> Nov 10 12:37:06 kamailio-name kamailio[937]: ERROR: <core>>
>> [parser/parse_from.c:75]: parse_from_header(): bad From header
>> [<sip:useragent6<+.w>>;tag=<wbr>jja7l45gd1]
>> Nov 10 12:37:06 kamailio-name kamailio[937]: ERROR: pv
>> [pv_core.c:465]: pv_get_from_attr(): cannot parse From header
>> Nov 10 12:37:06 kamailio-name kamailio[937]: INFO: <script>>: Skip
>> manage DEVICE_STATE for BYE from <null>>
>> (IP=udp:asterisk_address:<wbr>50600) with (200 - OK) - R=<null>>
>> ID=<wbr>1b0044070de406153bf0e4b84d6bb7<wbr>93 at asterisk_address:50600
>> Nov 10 12:37:06 kamailio-name kamailio[937]: INFO: <script>>:
>> ------------------------------<wbr>------MANAGE BYE by
>> DEVICE_STATE_BYE_MANAGE route - 200 - OK M=BYE
>> IP=udp:asterisk_address:50600
>> ID=<wbr>1b0044070de406153bf0e4b84d6bb7<wbr>93 at asterisk_address:50600
>> Nov 10 12:37:06 kamailio-name kamailio[937]: ERROR: <core>>
>> [parser/parse_addr_spec.c:719]<wbr>: parse_addr_spec(): unexpected char
>> [<] in status 6: [<sip:useragent6] .
>> Nov 10 12:37:06 kamailio-name kamailio[937]: ERROR: <core>>
>> [parser/parse_from.c:75]: parse_from_header(): bad From header
>> [<sip:useragent6<+.w>>;tag=<wbr>jja7l45gd1]
>> Nov 10 12:37:06 kamailio-name kamailio[937]: ERROR: pv
>> [pv_core.c:465]: pv_get_from_attr(): cannot parse From header
>> Nov 10 12:37:06 kamailio-name kamailio[937]: ERROR: <core>>
>> [parser/parse_addr_spec.c:719]<wbr>: parse_addr_spec(): unexpected char
>> [<] in status 6: [<sip:useragent6] .
>> Nov 10 12:37:06 kamailio-name kamailio[937]: ERROR: <core>>
>> [parser/parse_from.c:75]: parse_from_header(): bad From header
>> [<sip:useragent6<+.w>>;tag=<wbr>jja7l45gd1]
>> Nov 10 12:37:06 kamailio-name kamailio[937]: ERROR: rtpengine
>> [rtpengine_funcs.c:331]: get_from_tag(): failed to parse From header
>> Nov 10 12:37:06 kamailio-name kamailio[937]: ERROR: rtpengine
>> [rtpengine.c:2252]: rtpp_function_call(): can't get From tag
>> Nov 10 12:37:06 kamailio-name kamailio[937]: ERROR: <core>>
>> [parser/parse_addr_spec.c:719]<wbr>: parse_addr_spec(): unexpected char
>> [<] in status 6: [<sip:useragent6] .
>> Nov 10 12:37:06 kamailio-name kamailio[937]: ERROR: <core>>
>> [parser/parse_from.c:75]: parse_from_header(): bad From header
>> [<sip:useragent6<+.w>>;tag=<wbr>jja7l45gd1]
>> Nov 10 12:37:06 kamailio-name kamailio[937]: ERROR: pv
>> [pv_core.c:465]: pv_get_from_attr(): cannot parse From header
>> Nov 10 12:37:06 kamailio-name kamailio[937]: ERROR: <core>>
>> [parser/parse_addr_spec.c:719]<wbr>: parse_addr_spec(): unexpected char
>> [<] in status 6: [<sip:useragent6] .
>> Nov 10 12:37:06 kamailio-name kamailio[937]: ERROR: <core>>
>> [parser/parse_from.c:75]: parse_from_header(): bad From header
>> [<sip:useragent6<+.w>>;tag=<wbr>jja7l45gd1]
>> Nov 10 12:37:06 kamailio-name kamailio[937]: ERROR: pv
>> [pv_core.c:465]: pv_get_from_attr(): cannot parse From header
>>
>> How the packet looks like:
>> ACK
>> sip:tt7etmau at bb0pd5t63b26.invalid;alias=<wbr>client_address~57573~6;<wbr>transport=ws
>> SIP/2.0
>> Via: SIP/2.0/UDP asterisk_address:50600;branch=<wbr>z9hG4bK117106ca;rport
>> Route:
>> <sip:kam2.domain.com:5068;nat=<wbr>yes;transport=udp;r2=on;ftag=<wbr>as06869a5d;lr=on;vsf=<wbr>AAAAAEZZSVVDVV1VRBlUUkUpFQxdVU<wbr>ZYXiRCHU1RQl1HRVNaXhhAQ3RuLnR3<wbr>aWxpby5jb20-;vst=<wbr>AAAAAAAAAAAAAAAAAAAAAAAfBwQRQE<wbr>8NBR9BChIFAwddCgADFEVDQlYudHdp<wbr>bGlvLmNvbQ--;did=b0c.7331>>,<<wbr>sip:<a href="http://kam2.callision.com:5068" target="_blank">kam2.callision.com:5068</a>
>> <<a href="http://kam2.callision.com:5068" target="_blank">http://kam2.callision.com:<wbr>5068</a>>>;nat=yes;transport=ws;<wbr>r2=on;ftag=as06869a5d;lr=on;<wbr>vsf=<wbr>AAAAAEZZSVVDVV1VRBlUUkUpFQxdVU<wbr>ZYXiRCHU1RQl1HRVNaXhhAQ3RuLnR3<wbr>aWxpby5jb20-;vst=<wbr>AAAAAAAAAAAAAAAAAAAAAAAfBwQRQE<wbr>8NBR9BChIFAwddCgADFEVDQlYudHdp<wbr>bGlvLmNvbQ--;did=b0c.7331>>
>> Max-Forwards: 70
>> From: "19172423539 <tel:%28917%29%20242-3539>>" <sip:19172423539
>> <tel:%28917%29%20242-3539>>@<wbr>asterisk_address:50600>>;tag=<wbr>as06869a5d
>> To: <sip:useragent7122 at <a href="http://10.0.1.18:5068" target="_blank">10.0.1.18:5068</a>
>> <<a href="http://sip:useragent7122@10.0.1.18:5068" target="_blank">http://sip:useragent7122@10.<wbr>0.1.18:5068</a>>>>>;tag=nmv7kmpau3
>> Contact: <sip:<a href="tel:(917)%20242-3539" value="+19172423539" target="_blank">19172423539</a>
>> <tel:%28917%29%20242-3539>>@<wbr>asterisk_address:50600>>
>> Call-ID: 629d5a132c194c536b5f5c1a2a3c6e<wbr>32 at asterisk_address:50600
>> CSeq: 102 ACK
>> User-Agent: asterisk PBX
>> Content-Length: 0
>>
>>
>> The transport is used to send messages between asterisk and
>> kamailio is TCP.
>> TCP configurations:
>> tcp_connection_lifetime=3604
>> tcp_accept_no_cl=yes
>> tcp_connect_timeout=5
>> tcp_send_timeout=5
>> tcp_rd_buf_size=16384
>> tcp_keepalive=yes
>> tcp_crlf_ping=yes
>> tcp_keepcnt=3
>> tcp_keepidle=30
>> tcp_keepintvl=15
>> tcp_max_connections=4096
>>
>> I found the idea, that we need to change following parameters:
>> modparam("uac","restore_mode",<wbr>"auto")
>> modparam("uac","restore_dlg",<wbr>1)
>>
>> to:
>> modparam("uac","restore_mode",<wbr>"none")
>> modparam("uac","restore_dlg",<wbr>0)
>>
>> I did that, now it looks like all is fine, but I think it can get
>> back.
>> Thanks in advance.
>>
>>
>>
>> --
>> --
>> BR, Donat Zenichev
>> Wnet VoIP team
>> Tel Ukraine: +380(44) 5-900-800
>> Tel USA: +164(67) 8-174-17
>> <a href="https://w-net.us/" target="_blank">https://w-net.us/</a> <<a href="http://wnet.ua" target="_blank">http://wnet.ua</a>>>
>>
>> ______________________________<wbr>_________________
>> Kamailio (SER) - Users Mailing List
>> sr-users at <a href="http://lists.kamailio.org" target="_blank">lists.kamailio.org</a> <mailto:<a href="mailto:sr-users" target="_blank">sr-users</a> at <a href="http://lists.kamailio.org" target="_blank">lists.kamailio.org</a>>>
>> <a href="https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users" target="_blank">https://lists.kamailio.org/<wbr>cgi-bin/mailman/listinfo/sr-<wbr>users</a>
>> <<a href="https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users" target="_blank">https://lists.kamailio.org/<wbr>cgi-bin/mailman/listinfo/sr-<wbr>users</a>>>
>>
>>
>>
>>
>> ______________________________<wbr>_________________
>> Kamailio (SER) - Users Mailing List
>> sr-users at <a href="http://lists.kamailio.org" target="_blank">lists.kamailio.org</a>
>> <a href="https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users" target="_blank">https://lists.kamailio.org/<wbr>cgi-bin/mailman/listinfo/sr-<wbr>users</a>
>>--
>Daniel-Constantin Mierla
><a href="http://www.twitter.com/miconda" target="_blank">www.twitter.com/miconda</a> -- <a href="http://www.linkedin.com/in/miconda" target="_blank">www.linkedin.com/in/miconda</a>
>Kamailio Advanced Training, Nov 13-15, 2017, in Berlin - <a href="http://www.asipto.com" target="_blank">www.asipto.com</a>
>Kamailio World Conference - <a href="http://www.kamailioworld.com" target="_blank">www.kamailioworld.com</a>
</span></font></pre><div><br></div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">2017-11-13 17:05 GMT+02:00 Donat Zenichev <span dir="ltr"><<a href="mailto:donat.zenichev@gmail.com" target="_blank">donat.zenichev@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Hi community.</div><div>We experience the problem with malformed messages.</div><div><br></div><div>First of all, I want to say, that most of time kamailio works well and nothing happens that can drop sessions.</div><div>But from time-to-time something changes (may be in the network) and kamailio receives requests with malformed headers (To or From hfs).</div><div><br></div><div>The schema:</div><div>uplinks -> kamailio <-> routing server (asterisk)</div><div><br></div><div>Malformed messages were received only from asterisk server.<br>Sip debug on asterisk showed that messages were transmitted correctly and headers were nice.</div><div>But kamailio obtains changed (broken) packets or perhaps can't read them properly.</div><div><br></div><div>How does it look like:</div><div><div>Nov 10 12:37:06 kamailio-name kamailio[965]: INFO: <script>: Going to NATMANAGE for BYE from sip:useragent7122@kamailio_add<wbr>ress:5068 (IP=wss:client_address:62881) - R=sip:dialed_did_service@aster<wbr>isk_address:50600 ID=1b0044070de406153bf0e4b84d6<wbr>bb793@asterisk_address:50600</div><div>Nov 10 12:37:06 kamailio-name kamailio[965]: NOTICE: <script>: Relaying request to <null> - R=sip:dialed_did_service@aster<wbr>isk_address:50600 ID=1b0044070de406153bf0e4b84d6<wbr>bb793@asterisk_address:50600</div><div>Nov 10 12:37:06 kamailio-name kamailio[965]: ERROR: <core> [parser/parse_addr_spec.c:719]<wbr>: parse_addr_spec(): unexpected char [<] in status 6: [<sip:useragent6] .</div><div>Nov 10 12:37:06 kamailio-name kamailio[965]: ERROR: <core> [parser/parse_from.c:75]: parse_from_header(): bad From header [<sip:useragent6<+.w>;tag=jja7<wbr>l45gd1]</div><div>Nov 10 12:37:06 kamailio-name kamailio[965]: ERROR: dialog [dlg_cseq.c:89]: dlg_cseq_prepare_msg(): cannot parse FROM header</div><div>Nov 10 12:37:06 kamailio-name kamailio[937]: ERROR: <core> [parser/parse_addr_spec.c:719]<wbr>: parse_addr_spec(): unexpected char [<] in status 6: [<sip:useragent6] .</div><div>Nov 10 12:37:06 kamailio-name kamailio[937]: ERROR: <core> [parser/parse_from.c:75]: parse_from_header(): bad From header [<sip:useragent6<+.w>;tag=jja7<wbr>l45gd1]</div><div>Nov 10 12:37:06 kamailio-name kamailio[937]: ERROR: dialog [dlg_cseq.c:89]: dlg_cseq_prepare_msg(): cannot parse FROM header</div><div>Nov 10 12:37:06 kamailio-name kamailio[937]: ERROR: <core> [parser/parse_addr_spec.c:719]<wbr>: parse_addr_spec(): unexpected char [<] in status 6: [<sip:useragent6] .</div><div>Nov 10 12:37:06 kamailio-name kamailio[937]: ERROR: <core> [parser/parse_from.c:75]: parse_from_header(): bad From header [<sip:useragent6<+.w>;tag=jja7<wbr>l45gd1]</div><div>Nov 10 12:37:06 kamailio-name kamailio[937]: ERROR: uac [replace.c:783]: restore_uris_reply(): failed to find/parse FROM hdr</div><div>Nov 10 12:37:06 kamailio-name kamailio[937]: ERROR: <core> [parser/parse_addr_spec.c:719]<wbr>: parse_addr_spec(): unexpected char [<] in status 6: [<sip:useragent6] .</div><div>Nov 10 12:37:06 kamailio-name kamailio[937]: ERROR: <core> [parser/parse_from.c:75]: parse_from_header(): bad From header [<sip:useragent6<+.w>;tag=jja7<wbr>l45gd1]</div><div>Nov 10 12:37:06 kamailio-name kamailio[937]: ERROR: pv [pv_core.c:465]: pv_get_from_attr(): cannot parse >From header</div><div>Nov 10 12:37:06 kamailio-name kamailio[937]: INFO: <script>: Skip manage DEVICE_STATE for BYE from <null> (IP=udp:asterisk_address:50600<wbr>) with (200 - OK) - R=<null> ID=1b0044070de406153bf0e4b84d6<wbr>bb793@asterisk_address:50600</div><div>Nov 10 12:37:06 kamailio-name kamailio[937]: INFO: <script>: ------------------------------<wbr>------MANAGE BYE by DEVICE_STATE_BYE_MANAGE route - 200 - OK M=BYE IP=udp:asterisk_address:50600 ID=1b0044070de406153bf0e4b84d6<wbr>bb793@asterisk_address:50600</div><div>Nov 10 12:37:06 kamailio-name kamailio[937]: ERROR: <core> [parser/parse_addr_spec.c:719]<wbr>: parse_addr_spec(): unexpected char [<] in status 6: [<sip:useragent6] .</div><div>Nov 10 12:37:06 kamailio-name kamailio[937]: ERROR: <core> [parser/parse_from.c:75]: parse_from_header(): bad From header [<sip:useragent6<+.w>;tag=jja7<wbr>l45gd1]</div><div>Nov 10 12:37:06 kamailio-name kamailio[937]: ERROR: pv [pv_core.c:465]: pv_get_from_attr(): cannot parse From header</div><div>Nov 10 12:37:06 kamailio-name kamailio[937]: ERROR: <core> [parser/parse_addr_spec.c:719]<wbr>: parse_addr_spec(): unexpected char [<] in status 6: [<sip:useragent6] .</div><div>Nov 10 12:37:06 kamailio-name kamailio[937]: ERROR: <core> [parser/parse_from.c:75]: parse_from_header(): bad From header [<sip:useragent6<+.w>;tag=jja7<wbr>l45gd1]</div><div>Nov 10 12:37:06 kamailio-name kamailio[937]: ERROR: rtpengine [rtpengine_funcs.c:331]: get_from_tag(): failed to parse From header</div><div>Nov 10 12:37:06 kamailio-name kamailio[937]: ERROR: rtpengine [rtpengine.c:2252]: rtpp_function_call(): can't get From tag</div><div>Nov 10 12:37:06 kamailio-name kamailio[937]: ERROR: <core> [parser/parse_addr_spec.c:719]<wbr>: parse_addr_spec(): unexpected char [<] in status 6: [<sip:useragent6] .</div><div>Nov 10 12:37:06 kamailio-name kamailio[937]: ERROR: <core> [parser/parse_from.c:75]: parse_from_header(): bad From header [<sip:useragent6<+.w>;tag=jja7<wbr>l45gd1]</div><div>Nov 10 12:37:06 kamailio-name kamailio[937]: ERROR: pv [pv_core.c:465]: pv_get_from_attr(): cannot parse From header</div><div>Nov 10 12:37:06 kamailio-name kamailio[937]: ERROR: <core> [parser/parse_addr_spec.c:719]<wbr>: parse_addr_spec(): unexpected char [<] in status 6: [<sip:useragent6] .</div><div>Nov 10 12:37:06 kamailio-name kamailio[937]: ERROR: <core> [parser/parse_from.c:75]: parse_from_header(): bad From header [<sip:useragent6<+.w>;tag=jja7<wbr>l45gd1]</div><div>Nov 10 12:37:06 kamailio-name kamailio[937]: ERROR: pv [pv_core.c:465]: pv_get_from_attr(): cannot parse From header<br><br>How the packet looks like:<br><div>ACK sip:tt7etmau@bb0pd5t63b26.inva<wbr>lid;alias=client_address~57573<wbr>~6;transport=ws SIP/2.0</div><div>Via: SIP/2.0/UDP asterisk_address:50600;branch=<wbr>z9hG4bK117106ca;rport</div><div>Route: <sip:kam2.domain.com:5068;nat=<wbr>yes;transport=udp;r2=on;ftag=a<wbr>s06869a5d;lr=on;vsf=AAAAAEZZSV<wbr>VDVV1VRBlUUkUpFQxdVUZYXiRCHU1R<wbr>Ql1HRVNaXhhAQ3RuLnR3aWxpby5jb2<wbr>0-;vst=AAAAAAAAAAAAAAAAAAAAAAA<wbr>fBwQRQE8NBR9BChIFAwddCgADFEVDQ<wbr>lYudHdpbGlvLmNvbQ--;did=b0c.<wbr>7331>,<sip:<a href="http://kam2.callision.com:5068" target="_blank">kam2.callision.com:<wbr>5068</a>;nat=yes;transport=ws;r2=<wbr>on;ftag=as06869a5d;lr=on;vsf=A<wbr>AAAAEZZSVVDVV1VRBlUUkUpFQxdVUZ<wbr>YXiRCHU1RQl1HRVNaXhhAQ3RuLnR3a<wbr>Wxpby5jb20-;vst=AAAAAAAAAAAAAA<wbr>AAAAAAAAAfBwQRQE8NBR9BChIFAwdd<wbr>CgADFEVDQlYudHdpbGlvLmNvbQ--;<wbr>did=b0c.7331></div><div>Max-Forwards: 70</div><div>From: "<a href="tel:(917)%20242-3539" value="+19172423539" target="_blank">19172423539</a>" <sip:<a href="tel:(917)%20242-3539" value="+19172423539" target="_blank">19172423539</a>@asterisk_addr<wbr>ess:50600>;tag=as06869a5d</div><div>To: <<a href="http://sip:useragent7122@10.0.1.18:5068" target="_blank">sip:useragent7122@10.0.1.18:5<wbr>068</a>>;tag=nmv7kmpau3</div><div>Contact: <sip:<a href="tel:(917)%20242-3539" value="+19172423539" target="_blank">19172423539</a>@asterisk_addr<wbr>ess:50600></div><div>Call-ID: 629d5a132c194c536b5f5c1a2a3c6e<wbr>32@asterisk_address:50600</div><div>CSeq: 102 ACK</div><div>User-Agent: asterisk PBX</div><div>Content-Length: 0</div><br><br>The transport is used to send messages between asterisk and kamailio is TCP.</div></div><div>TCP configurations:</div><div><div>tcp_connection_lifetime=3604</div><div>tcp_accept_no_cl=yes</div><div>tcp_connect_timeout=5</div><div>tcp_send_timeout=5</div><div>tcp_rd_buf_size=16384</div><div>tcp_keepalive=yes</div><div>tcp_crlf_ping=yes</div><div>tcp_keepcnt=3</div><div>tcp_keepidle=30</div><div>tcp_keepintvl=15</div><div>tcp_max_connections=4096 </div></div><div><br></div><div>I found the idea, that we need to change following parameters:<br><div>modparam("uac","restore_mode",<wbr>"auto")</div><div>modparam("uac","restore_dlg",1<wbr>)<br><br>to:<br><div>modparam("uac","restore_mode",<wbr>"none")</div><div>modparam("uac","restore_dlg",0<wbr>)<br><br>I did that, now it looks like all is fine, but I think it can get back.</div></div></div><div>Thanks in advance.</div><span class="m_-3281789307149543554HOEnZb"><font color="#888888"><div><br></div><br clear="all"><div><br></div>-- <br><div class="m_-3281789307149543554m_7513552613212225379gmail_signature"><div dir="ltr"><div><div dir="ltr"><font style="background-color:rgb(255,255,255)" color="#0b5394">-- <br>BR, Donat Zenichev
<br>Wnet VoIP team<br>Tel Ukraine: +380(44) 5-900-800
<br>Tel USA: +164(67) 8-174-17<br><a href="http://wnet.ua" target="_blank">https://w-net.us/</a></font></div></div></div></div>
</font></span></div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="m_-3281789307149543554gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><font style="background-color:rgb(255,255,255)" color="#0b5394">-- <br>BR, Donat Zenichev
<br>Wnet VoIP team<br>Tel Ukraine: +380(44) 5-900-800
<br>Tel USA: +164(67) 8-174-17<br><a href="http://wnet.ua" target="_blank">https://w-net.us/</a></font></div></div></div></div>
</div>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><font style="background-color:rgb(255,255,255)" color="#0b5394">-- <br>BR, Donat Zenichev
<br>Wnet VoIP team<br>Tel Ukraine: +380(44) 5-900-800
<br>Tel USA: +164(67) 8-174-17<br><a href="http://wnet.ua" target="_blank">https://w-net.us/</a></font></div></div></div></div>
</div>