<html><body><div style="font-family: lucida console,sans-serif; font-size: 12pt; color: #000000"><div>Hello Daniel,<br></div><div>Look like transactions are not match when it send reply for NOTIFY. I think it should reuse connection.<br data-mce-bogus="1"></div><div>Here SDP output where cseq are match and asterisk does retransmissions until time out.<br data-mce-bogus="1"></div><div>Also I wonder where Path route is reused I see %* instead ; as delimiter between transport and port.<br data-mce-bogus="1"></div><div><br data-mce-bogus="1"></div><div><br data-mce-bogus="1"></div><div>Retransmitting #8 (NAT) to 10.18.130.46:5060:<br>NOTIFY sip:191@192.168.88.246:5062;transport=tcp SIP/2.0<br>Via: SIP/2.0/UDP 10.18.130.51:5060;branch=z9hG4bK6939f20d;rport<br>Max-Forwards: 70<br>Route: <sip:inbound@10.18.130.46;lr;received=sip:client_public_ip:5062%3Btransport%3Dtcp><br>From: "canlpbx02" <sip:canlpbx02@10.18.130.51>;tag=as4b212049<br>To: <sip:191@192.168.88.246:5062;transport=tcp><br>Contact: <sip:canlpbx02@10.18.130.51:5060><br>Call-ID: 14c7c8cc7335adf60f2be634132d3b2f@10.18.130.51:5060<br>CSeq: 102 NOTIFY<br>User-Agent: FPBX-12.0.43(12.8.1)<br>Event: message-summary<br>Content-Type: application/simple-message-summary<br>Content-Length: 89<br><br>Messages-Waiting: yes<br>Message-Account: sip:*97@10.18.130.51<br>Voice-Message: 24/0 (0/0)<br><br>---<br>Retransmitting #9 (NAT) to 10.18.130.46:5060:<br>NOTIFY sip:191@192.168.88.246:5062;transport=tcp SIP/2.0<br>Via: SIP/2.0/UDP 10.18.130.51:5060;branch=z9hG4bK6939f20d;rport<br>Max-Forwards: 70<br>Route: <sip:inbound@10.18.130.46;lr;received=sip:99.251.238.38:5062%3Btransport%3Dtcp> <span data-mce-style="color: #ff0000;" style="color: rgb(255, 0, 0);">right here</span><br>From: "canlpbx02" <sip:canlpbx02@10.18.130.51>;tag=as4b212049<br>To: <sip:191@192.168.88.246:5062;transport=tcp><br>Contact: <sip:canlpbx02@10.18.130.51:5060><br>Call-ID: 14c7c8cc7335adf60f2be634132d3b2f@10.18.130.51:5060<br>CSeq: 102 NOTIFY<br>User-Agent: FPBX-12.0.43(12.8.1)<br>Event: message-summary<br>Content-Type: application/simple-message-summary<br>Content-Length: 89<br><br>Messages-Waiting: yes<br>Message-Account: sip:*97@10.18.130.51<br>Voice-Message: 24/0 (0/0)<br><br>---<br><br><--- SIP read from UDP:10.18.130.46:5060 ---><br>SIP/2.0 408 Request Timeout<br>Via: SIP/2.0/UDP 10.18.130.51:5060;branch=z9hG4bK6939f20d;rport=5060;received=10.18.130.51<br>From: "canlpbx02" <sip:canlpbx02@10.18.130.51>;tag=as4b212049<br>To: <sip:191@192.168.88.246:5062;transport=tcp>;tag=dc299d9ac16f3377ac0b8dfa22eaf0a6-2fe2<br>Call-ID: 14c7c8cc7335adf60f2be634132d3b2f@10.18.130.51:5060<br>CSeq: 102 NOTIFY<br>Server: kamailio (4.2.3 (x86_64/linux))<br>Content-Length: 0<br><br><-------------><br></div><div><br></div><div>Mar 23 08:45:47 canlvprx01 /usr/sbin/kamailio[20143]: ERROR: <core> [tcp_main.c:4338]: tcpconn_main_timeout(): connect client_pub_ip:5063 failed (timeout)</div><div><br data-mce-bogus="1"></div><div><br data-mce-bogus="1"></div><div>Slava.<br data-mce-bogus="1"></div><hr id="zwchr" data-marker="__DIVIDER__"><div data-marker="__HEADERS__"><b>From: </b>"Daniel-Constantin Mierla" <miconda@gmail.com><br><b>To: </b>"Slava Bendersky" <volga629@networklab.ca><br><b>Cc: </b>"sr-users" <sr-users@lists.sip-router.org><br><b>Sent: </b>Monday, March 23, 2015 4:21:47 AM<br><b>Subject: </b>Re: [SR-Users] kamailio asterisk NOTIFY<br></div><div><br></div><div data-marker="__QUOTED_TEXT__">Hello,<br>
<br>
as you can see the 408 is for another request, because the cseq is
103. The first one has cseq 102, but has no Record-Route header,
which is mandated by new RFCs.<br>
<br>
In kamailio, if you added in request_route when handling the NOTIFY,
you can try to add record route via reply_route if the client is not
keeping it in reply, kind of following fix:<br>
<br>
reply_route {<br>
if(is_method("NOTIFY")) {<br>
if(!is_present_hf("Record-Route")) {<br>
insert_hf("Record-Route:
<<a class="moz-txt-link-freetext" href="sip:yourserverip:port;transport=...\r\n" target="_blank">sip:yourserverip:port;transport=...\r\n</a>");<br>
}<br>
}<br>
<br>
Cheers,<br>
Daniel<br>
<br>
<div class="moz-cite-prefix">On 22/03/15 18:11, Slava Bendersky
wrote:<br>
</div>
<blockquote cite="mid:836087699.41149767.1427044280781.JavaMail.zimbra@skillsearch.ca">
<div style="font-family: lucida console,sans-serif; font-size:
12pt; color: #000000">
<div>Hello Daniel,<br>
</div>
<div>I still can't understand clearly why when asterisk send
NOTIFY to client through kamailio it coming back with with
408. I <br>
</div>
<div>I tried different case event change Contact:, but no luck
can't I see what the issue all routes in first SUBSCRIBE looks
ok . </div>
<div>Any though or help will be really appreciate.</div>
<div><br>
</div>
<div>This what I see on asterisk debug<br>
</div>
<div><br>
Reliably Transmitting (NAT) to 10.18.130.46:5060:<br>
NOTIFY <a class="moz-txt-link-freetext" href="sip:102@192.168.88.243:5068;alias=client_pub_ip~5068~2" target="_blank">sip:102@192.168.88.243:5068;alias=client_pub_ip~5068~2</a>
SIP/2.0<br>
Via: SIP/2.0/UDP 10.18.130.51:5060;branch=z9hG4bK5dd3f266<br>
Max-Forwards: 70<br>
Route:
<a class="moz-txt-link-rfc2396E" href="sip:10.18.130.46:5060;lr=on;ftag=3b27a2a409;nat=yes" target="_blank"><sip:10.18.130.46:5060;lr=on;ftag=3b27a2a409;nat=yes></a>
--->Kamailio route<br>
From: "canlpbx02"
<a class="moz-txt-link-rfc2396E" href="sip:canlpbx02@10.18.130.51" target="_blank"><sip:canlpbx02@10.18.130.51></a>;tag=as56402f92<br>
To:
<a class="moz-txt-link-rfc2396E" href="sip:102@192.168.88.243:5068;alias=client_pub_ip~5068~2" target="_blank"><sip:102@192.168.88.243:5068;alias=client_pub_ip~5068~2></a>;tag=3b27a2a409<br>
Contact: <a class="moz-txt-link-rfc2396E" href="sip:canlpbx02@10.18.130.51:5060" target="_blank"><sip:canlpbx02@10.18.130.51:5060></a><br>
Call-ID: b1edde040d695988<br>
CSeq: 102 NOTIFY<br>
User-Agent: FPBX-12.0.43(12.8.1)<br>
Event: message-summary<br>
Content-Type: application/simple-message-summary<br>
Subscription-State: active<br>
Content-Length: 88<br>
<br>
Messages-Waiting: yes<br>
Message-Account: <a class="moz-txt-link-freetext" href="sip:*97@10.18.130.51" target="_blank">sip:*97@10.18.130.51</a><br>
Voice-Message: 5/0 (0/0)<br>
<br>
---<br>
<br>
<--- SIP read from UDP:10.18.130.46:5060 ---><br>
SIP/2.0 200 OK<br>
Via: SIP/2.0/UDP
10.18.130.51:5060;rport=5060;branch=z9hG4bK5dd3f266<br>
From: "canlpbx02"
<a class="moz-txt-link-rfc2396E" href="sip:canlpbx02@10.18.130.51" target="_blank"><sip:canlpbx02@10.18.130.51></a>;tag=as56402f92<br>
To:
<a class="moz-txt-link-rfc2396E" href="sip:102@192.168.88.243:5068;alias=client_pub_ip~5068~2" target="_blank"><sip:102@192.168.88.243:5068;alias=client_pub_ip~5068~2></a>;tag=3b27a2a409<br>
Call-ID: b1edde040d695988<br>
CSeq: 102 NOTIFY<br>
Allow: ACK, BYE, CANCEL, INVITE, MESSAGE, NOTIFY, OPTIONS,
REFER, SUBSCRIBE, UPDATE<br>
Server: Media5-fone/4.1.6.3283 Android/5.1<br>
Supported: eventlist, replaces, timer<br>
Content-Length: 0<br>
<br>
<-------------><br>
--- (10 headers 0 lines) ---<br>
<br>
<--- SIP read from UDP:10.18.130.46:5060 ---><br>
SIP/2.0 408 Request Timeout<br>
Via: SIP/2.0/UDP
10.18.130.51:5060;branch=z9hG4bK6386387f;rport=5060<br>
From: "canlpbx02"
<a class="moz-txt-link-rfc2396E" href="sip:canlpbx02@10.18.130.51" target="_blank"><sip:canlpbx02@10.18.130.51></a>;tag=as00936a6d<br>
To:
<a class="moz-txt-link-rfc2396E" href="sip:102@192.168.88.243:5066;alias=client_pub_ip~5066~2" target="_blank"><sip:102@192.168.88.243:5066;alias=client_pub_ip~5066~2></a>;tag=a3aea18741<br>
Call-ID: 5a66b87a618d1042<br>
CSeq: 103 NOTIFY<br>
Server: kamailio (4.2.3 (x86_64/linux))<br>
Content-Length: 0<br>
<br>
<-------------><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div>Slava.<br>
</div>
<div><br>
</div>
<hr id="zwchr">
<div><b>From: </b>"Daniel-Constantin
Mierla" <a class="moz-txt-link-rfc2396E" href="mailto:miconda@gmail.com" target="_blank"><miconda@gmail.com></a><br>
<b>To: </b>"Slava Bendersky" <a class="moz-txt-link-rfc2396E" href="mailto:volga629@networklab.ca" target="_blank"><volga629@networklab.ca></a>,
"sr-users" <a 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>Friday, March 13, 2015 1:28:33 PM<br>
<b>Subject: </b>Re: [SR-Users] kamailio asterisk NOTIFY<br>
</div>
<br>
<div>Hello,<br>
<br>
that function might be in textopsx module.<br>
<br>
Cheers,<br>
Daniel<br>
<br>
<div class="moz-cite-prefix">On 13/03/15 14:25, Slava
Bendersky wrote:<br>
</div>
<blockquote cite="mid:1734594061.37294583.1426253140580.JavaMail.zimbra@skillsearch.ca">
<div style="font-family: lucida console,sans-serif;
font-size: 12pt; color: #000000">
<div>Hello Daniel,<br>
</div>
<div>Where possible find updated version of options for
textops.</div>
<div><br>
</div>
<div>[sr_module.c:701]: find_mod_export_record():
find_export_record: <remove_hf_value> not found</div>
<div><br>
</div>
<div>Specially Record-Route manipulation.<br>
</div>
<div><br>
</div>
<div>Slava.<br>
</div>
<div><br>
</div>
<hr id="zwchr">
<div><b>From: </b>"Slava Bendersky" <a class="moz-txt-link-rfc2396E" href="mailto:volga629@networklab.ca" target="_blank"><volga629@networklab.ca></a><br>
<b>To: </b><a class="moz-txt-link-abbreviated" href="mailto:miconda@gmail.com" target="_blank">miconda@gmail.com</a><br>
<b>Cc: </b>"sr-users" <a 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>Friday, March 13, 2015 8:54:26 AM<br>
<b>Subject: </b>Re: [SR-Users] kamailio asterisk NOTIFY<br>
</div>
<br>
<div>
<div style="font-family: lucida console,sans-serif;
font-size: 12pt; color: #000000">
<div>Hello Daniel,<br>
</div>
<div>Here paste for first SUBSCRIBE.<br>
</div>
<br>
<div><a class="moz-txt-link-freetext" href="http://fpaste.org/197545/25118514/" target="_blank">http://fpaste.org/197545/25118514/</a><br>
</div>
<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" target="_blank"><miconda@gmail.com></a><br>
<b>To: </b>"Slava Bendersky" <a class="moz-txt-link-rfc2396E" href="mailto:volga629@networklab.ca" target="_blank"><volga629@networklab.ca></a><br>
<b>Cc: </b>"sr-users" <a 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>Thursday, March 12, 2015 5:09:17 AM<br>
<b>Subject: </b>Re: [SR-Users] kamailio asterisk
NOTIFY<br>
</div>
<br>
<div>Hello,<br>
<br>
can you get the sip traffic from the network (from
the first subscribe of this presence dialog)? It
will help to see the Route set.<br>
<br>
Cheers,<br>
Daniel<br>
<br>
<div class="moz-cite-prefix">On 12/03/15 00:36,
Slava Bendersky wrote:<br>
</div>
<blockquote cite="mid:951809989.36641443.1426116981670.JavaMail.zimbra@skillsearch.ca">
<div style="font-family: lucida
console,sans-serif; font-size: 12pt; color:
#000000">
<div>Hello Daniel,<br>
</div>
<div>Here debug of the notify which failing.
Look like transaction miss match<br>
</div>
<br>
<div><a class="moz-txt-link-freetext" href="http://fpaste.org/196896/61168591/" target="_blank">http://fpaste.org/196896/61168591/</a><br>
</div>
<br>
<div>Slava.<br>
</div>
<br>
<br>
<hr id="zwchr">
<div><b>From: </b>"Daniel-Constantin Mierla" <a class="moz-txt-link-rfc2396E" href="mailto:miconda@gmail.com" target="_blank"><miconda@gmail.com></a><br>
<b>To: </b>"Slava Bendersky" <a class="moz-txt-link-rfc2396E" href="mailto:volga629@networklab.ca" target="_blank"><volga629@networklab.ca></a>,
"sr-users" <a 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>Wednesday, March 11, 2015
5:44:05 PM<br>
<b>Subject: </b>Re: [SR-Users] kamailio
asterisk NOTIFY<br>
</div>
<br>
<div>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">
<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>
</div>
<br>
<div>Slava.<br>
</div>
<br>
<br>
<hr id="zwchr">
<div><b>From: </b>"Slava Bendersky" <a class="moz-txt-link-rfc2396E" href="mailto:volga629@networklab.ca" target="_blank"><volga629@networklab.ca></a><br>
<b>To: </b><a class="moz-txt-link-abbreviated" href="mailto:miconda@gmail.com" target="_blank">miconda@gmail.com</a><br>
<b>Cc: </b>"sr-users" <a 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>Wednesday, March 11, 2015
4:21:39 PM<br>
<b>Subject: </b>Re: [SR-Users] kamailio
asterisk NOTIFY<br>
</div>
<br>
<div>
<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" target="_blank"><miconda@gmail.com></a><br>
<b>To: </b>"Slava Bendersky" <a class="moz-txt-link-rfc2396E" href="mailto:volga629@networklab.ca" target="_blank"><volga629@networklab.ca></a>,
"sr-users" <a 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>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 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 class="moz-txt-link-rfc2396E" href="mailto:miconda@gmail.com" target="_blank"><miconda@gmail.com></a><br>
<b>To: </b>"sr-users" <a 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 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 class="moz-txt-link-abbreviated" href="mailto:sr-users@lists.sip-router.org" target="_blank">sr-users@lists.sip-router.org</a>
<a 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 class="moz-txt-link-freetext" href="http://twitter.com/#%21/miconda" target="_blank">http://twitter.com/#!/miconda</a> - <a 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 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 class="moz-txt-link-abbreviated" href="mailto:sr-users@lists.sip-router.org" target="_blank">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" 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 class="moz-txt-link-freetext" href="http://twitter.com/#%21/miconda" target="_blank">http://twitter.com/#!/miconda</a> - <a 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 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" target="_blank">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" 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 class="moz-txt-link-freetext" href="http://twitter.com/#%21/miconda" target="_blank">http://twitter.com/#!/miconda</a> - <a 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 class="moz-txt-link-freetext" href="http://www.kamailioworld.com" target="_blank">http://www.kamailioworld.com</a>
</pre>
<br>
</div>
</div>
</blockquote>
<br>
<pre class="moz-signature">--
Daniel-Constantin Mierla
<a class="moz-txt-link-freetext" href="http://twitter.com/#%21/miconda" target="_blank">http://twitter.com/#!/miconda</a> - <a 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 class="moz-txt-link-freetext" href="http://www.kamailioworld.com" target="_blank">http://www.kamailioworld.com</a>
</pre>
<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" target="_blank">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" 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 class="moz-txt-link-freetext" href="http://twitter.com/#%21/miconda" target="_blank">http://twitter.com/#!/miconda</a> - <a 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 class="moz-txt-link-freetext" href="http://www.kamailioworld.com" target="_blank">http://www.kamailioworld.com</a>
</pre>
<br>
</div>
</div>
</blockquote>
<br>
<pre class="moz-signature">--
Daniel-Constantin Mierla
<a class="moz-txt-link-freetext" href="http://twitter.com/#!/miconda" target="_blank">http://twitter.com/#!/miconda</a> - <a 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 class="moz-txt-link-freetext" href="http://www.kamailioworld.com" target="_blank">http://www.kamailioworld.com</a><br data-mce-bogus="1"></pre><br></div></div></body></html>