<html>
  <head>
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Hello,<br>
    <br>
    it doesn't matter if there is a mix of transports. If the UA is
    mirroring the Record-Route headers in the response to the NOTIFY, it
    should work fine.<br>
    <br>
    Cheers,<br>
    Daniel<br>
    <br>
    <div class="moz-cite-prefix">On 11/03/15 21:40, Slava Bendersky
      wrote:<br>
    </div>
    <blockquote
cite="mid:2081313653.36594263.1426106424352.JavaMail.zimbra@skillsearch.ca"
      type="cite">
      <div style="font-family: lucida console,sans-serif; font-size:
        12pt; color: #000000">
        <div>Hello Daniel,<br>
        </div>
        <div>Is this matter that UDP and TCP transport in mix ?<br
            data-mce-bogus="1">
        </div>
        <div><br data-mce-bogus="1">
        </div>
        <div>Slava.<br data-mce-bogus="1">
        </div>
        <div><br>
        </div>
        <div><br>
        </div>
        <hr id="zwchr" data-marker="__DIVIDER__">
        <div data-marker="__HEADERS__"><b>From: </b>"Slava Bendersky"
          <a class="moz-txt-link-rfc2396E" href="mailto:volga629@networklab.ca"><volga629@networklab.ca></a><br>
          <b>To: </b><a class="moz-txt-link-abbreviated" href="mailto:miconda@gmail.com">miconda@gmail.com</a><br>
          <b>Cc: </b>"sr-users" <a class="moz-txt-link-rfc2396E" href="mailto:sr-users@lists.sip-router.org"><sr-users@lists.sip-router.org></a><br>
          <b>Sent: </b>Wednesday, March 11, 2015 4:21:39 PM<br>
          <b>Subject: </b>Re: [SR-Users] kamailio asterisk NOTIFY<br>
        </div>
        <div><br>
        </div>
        <div data-marker="__QUOTED_TEXT__">
          <div style="font-family: lucida console,sans-serif; font-size:
            12pt; color: #000000">
            <div>
              <div style="font-family: lucida console,sans-serif;
                font-size: 12pt; color: #000000">
                <div>Hello Daniel,<br>
                </div>
                <div>I have record route in WITHINDLG for NOTIFY, but it
                  not helped behaviour is the same it loosing route for
                  NOTIFY.<br>
                </div>
                <br>
                <br>
                <div>Slava.<br>
                </div>
                <br>
                <hr id="zwchr">
                <div><b>From: </b>"Daniel-Constantin Mierla"
                  <a class="moz-txt-link-rfc2396E" href="mailto:miconda@gmail.com"><miconda@gmail.com></a><br>
                  <b>To: </b>"Slava Bendersky"
                  <a class="moz-txt-link-rfc2396E" href="mailto:volga629@networklab.ca"><volga629@networklab.ca></a>, "sr-users"
                  <a class="moz-txt-link-rfc2396E" href="mailto:sr-users@lists.sip-router.org"><sr-users@lists.sip-router.org></a><br>
                  <b>Sent: </b>Wednesday, March 11, 2015 2:14:02 PM<br>
                  <b>Subject: </b>Re: [SR-Users] kamailio asterisk
                  NOTIFY<br>
                </div>
                <br>
                <div>Hello,<br>
                  <br>
                  you have to do record_route() for all NOTIFY requests
                  -- there are new specs requiring that (RFC 6665) and
                  perhaps asterisk is following them.<br>
                  <br>
                  If you look in the default kamailio.cfg for v4.2,
                  inside route[WITHINDLG], then you will see how it is
                  done.<br>
                  <br>
                  Cheers,<br>
                  Daniel<br>
                  <br>
                  <div class="moz-cite-prefix">On 11/03/15 14:22, Slava
                    Bendersky wrote:<br>
                  </div>
                  <blockquote
cite="mid:407545737.36476741.1426080157634.JavaMail.zimbra@skillsearch.ca">
                    <div style="font-family: lucida console,sans-serif;
                      font-size: 12pt; color: #000000">
                      <div>Hello Daniel,<br>
                      </div>
                      <div>Here fresh paste <br>
                      </div>
                      <br>
                      <div><a moz-do-not-send="true"
                          class="moz-txt-link-freetext"
                          href="http://fpaste.org/196616/42608006/"
                          target="_blank">http://fpaste.org/196616/42608006/</a><br>
                      </div>
                      <br>
                      <div>I see proper routing headers on SUBSCRIBE,
                        but then NOTIFY loose it.<br>
                      </div>
                      <br>
                      <div>Slava.<br>
                      </div>
                      <br>
                      <hr id="zwchr">
                      <div><b>From: </b>"Daniel-Constantin Mierla" <a
                          moz-do-not-send="true"
                          class="moz-txt-link-rfc2396E"
                          href="mailto:miconda@gmail.com"
                          target="_blank"><miconda@gmail.com></a><br>
                        <b>To: </b>"sr-users" <a
                          moz-do-not-send="true"
                          class="moz-txt-link-rfc2396E"
                          href="mailto:sr-users@lists.sip-router.org"
                          target="_blank"><sr-users@lists.sip-router.org></a><br>
                        <b>Sent: </b>Tuesday, March 10, 2015 5:31:51 PM<br>
                        <b>Subject: </b>Re: [SR-Users] kamailio
                        asterisk NOTIFY<br>
                      </div>
                      <br>
                      <div>Hello,<br>
                        <br>
                        fpaste link doesn't show anything.<br>
                        <br>
                        Can you check if the NOTIFY coming to Kamailio
                        has two Route headers?<br>
                        <br>
                        Cheers,<br>
                        Daniel<br>
                        <br>
                        <div class="moz-cite-prefix">On 10/03/15 18:44,
                          Slava Bendersky wrote:<br>
                        </div>
                        <blockquote
cite="mid:941404803.36162609.1426009495413.JavaMail.zimbra@skillsearch.ca">
                          <div style="font-family: lucida
                            console,sans-serif; font-size: 12pt; color:
                            #000000">
                            <div>Hello Everyone,<br>
                            </div>
                            <div>Having issue with NOTIFY, is not
                              forwarded to client properly.<br>
                            </div>
                            <br>
                            <div>asterisk ---> private kamailio
                              public ----> soft client<br>
                            </div>
                            <br>
                            <br>
                            <div>  <a moz-do-not-send="true"
                                class="moz-txt-link-freetext"
                                href="http://fpaste.org/196257/99948714/"
                                target="_blank">http://fpaste.org/196257/99948714/</a><br>
                            </div>
                            <br>
                            <div>I see kamailio trying connect always
                              with private IP to the client when NOTIFY
                              is come is in. Is this something to do
                              with
                              <pre>rr_advertise_address ?</pre>
                              Mar 10 13:44:23 canlvprx01 kamailio:
                              16(24971) ERROR: <core>
                              [tcp_main.c:4338]: tcpconn_main_timeout():
                              connect 192.168.88.246:5064 failed
                              (timeout)<br>
                              Mar 10 13:44:23 canlvprx01 kamailio:
                              16(24971) DEBUG: <core>
                              [tcp_main.c:4362]: tcpconn_main_timeout():
                              tcp_main: timeout for 0x7fbbb64e2800<br>
                              Mar 10 13:44:23 canlvprx01 kamailio:
                              16(24971) DEBUG: <core>
                              [io_wait.h:610]: io_watch_del(): DBG:
                              io_watch_del (0x9dbf00, 33, -1, 0x10)
                              fd_no=24 called<br>
                              Mar 10 13:44:23 canlvprx01 kamailio:
                              16(24971) DEBUG: <core>
                              [tcp_main.c:4320]: tcpconn_main_timeout():
                              tcp_main: entering timer for
                              0x7fbbb64eb6c0 (ticks=839577436,
                              timeout=839634956 (3595 s),
                              wr_timeout=839577436 (0 s)), write queue:
                              798 bytes<br>
                              Mar 10 13:44:23 canlvprx01 kamailio:
                              16(24971) ERROR: <core>
                              [tcp_main.c:4338]: tcpconn_main_timeout():
                              connect 192.168.88.246:5066 failed
                              (timeout)<br>
                              Mar 10 13:44:23 canlvprx01 kamailio:
                              16(24971) DEBUG: <core>
                              [tcp_main.c:4362]: tcpconn_main_timeout():
                              tcp_main: timeout for 0x7fbbb64eb6c0<br>
                              Mar 10 13:44:23 canlvprx01 kamailio:
                              16(24971) DEBUG: <core>
                              [io_wait.h:610]: io_watch_del(): DBG:
                              io_watch_del (0x9dbf00, 34, -1, 0x10)
                              fd_no=23 called<br>
                              Mar 10 13:44:42 canlvprx01 kamailio:
                              5(24960) DEBUG: tm [t_reply.c:1294]:
                              t_should_relay_response():
                              ->>>>>>>>>
                              T_code=0, new_code=408<br>
                              Mar 10 13:44:42 canlvprx01 kamailio:
                              5(24960) DEBUG: tm [t_reply.c:1812]:
                              relay_reply(): DEBUG: relay_reply:
                              branch=0, save=0, relay=0 icode=0<br>
                              Mar 10 13:44:42 canlvprx01 kamailio:
                              5(24960) DEBUG: <core>
                              [mem/shm_mem.c:111]: _shm_resize():
                              WARNING:vqm_resize: resize(0) called<br>
                              Mar 10 13:44:42 canlvprx01 kamailio:
                              5(24960) DEBUG: tm [t_reply.c:1294]:
                              t_should_relay_response():
                              ->>>>>>>>>
                              T_code=0, new_code=408<br>
                              Mar 10 13:44:42 canlvprx01 kamailio:
                              5(24960) DEBUG: tm [t_reply.c:1812]:
                              relay_reply(): DEBUG: relay_reply:
                              branch=0, save=0, relay=0 icode=0<br>
                            </div>
                            <br>
                            <div>I have in configuration in WITHINDLG<br>
                            </div>
                            <br>
                            <div>                        if
                              (is_method("NOTIFY")) {<br>
                                                              
                              record_route();<br>
                                                      }<br>
                            </div>
                            <br>
                            <div>and in NATDETECT<br>
                            </div>
                            <br>
                            <div>               
                              if(is_method("INVITE|SUBSCRIBE|UPDATE|NOTIFY"))
                              {<br>
                                                     
                              set_contact_alias();<br>
                                              }<br>
                            </div>
                            <br>
                            <div>Slava.<br>
                            </div>
                          </div>
                          <br>
                          <fieldset class="mimeAttachmentHeader"></fieldset>
                          <br>
                          <pre>_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:sr-users@lists.sip-router.org" target="_blank">sr-users@lists.sip-router.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users" target="_blank">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a>
</pre>
                        </blockquote>
                        <br>
                        <pre class="moz-signature">-- 
Daniel-Constantin Mierla
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://twitter.com/#%21/miconda" target="_blank">http://twitter.com/#!/miconda</a> - <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://www.linkedin.com/in/miconda" target="_blank">http://www.linkedin.com/in/miconda</a>
Kamailio World Conference, May 27-29, 2015
Berlin, Germany - <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://www.kamailioworld.com" target="_blank">http://www.kamailioworld.com</a>
</pre>
                        <br>
                        _______________________________________________<br>
                        SIP Express Router (SER) and Kamailio (OpenSER)
                        - sr-users mailing list<br>
                        <a moz-do-not-send="true"
                          class="moz-txt-link-abbreviated"
                          href="mailto:sr-users@lists.sip-router.org"
                          target="_blank">sr-users@lists.sip-router.org</a><br>
                        <a moz-do-not-send="true"
                          class="moz-txt-link-freetext"
                          href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users"
                          target="_blank">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a><br>
                      </div>
                    </div>
                  </blockquote>
                  <br>
                  <pre class="moz-signature">-- 
Daniel-Constantin Mierla
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://twitter.com/#%21/miconda" target="_blank">http://twitter.com/#!/miconda</a> - <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://www.linkedin.com/in/miconda" target="_blank">http://www.linkedin.com/in/miconda</a>
Kamailio World Conference, May 27-29, 2015
Berlin, Germany - <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://www.kamailioworld.com" target="_blank">http://www.kamailioworld.com</a>
</pre>
                </div>
              </div>
              <br>
            </div>
          </div>
          <br>
          _______________________________________________<br>
          SIP Express Router (SER) and Kamailio (OpenSER) - sr-users
          mailing list<br>
          <a class="moz-txt-link-abbreviated" href="mailto:sr-users@lists.sip-router.org">sr-users@lists.sip-router.org</a><br>
          <a class="moz-txt-link-freetext" href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a><br>
        </div>
      </div>
    </blockquote>
    <br>
    <pre class="moz-signature" cols="72">-- 
Daniel-Constantin Mierla
<a class="moz-txt-link-freetext" href="http://twitter.com/#!/miconda">http://twitter.com/#!/miconda</a> - <a class="moz-txt-link-freetext" href="http://www.linkedin.com/in/miconda">http://www.linkedin.com/in/miconda</a>
Kamailio World Conference, May 27-29, 2015
Berlin, Germany - <a class="moz-txt-link-freetext" href="http://www.kamailioworld.com">http://www.kamailioworld.com</a></pre>
  </body>
</html>