<div dir="ltr"><div><div><div><div><div>Hi Jason,<br></div>I understood it, the issue here is that i was trying to use ims_qos module in a non IMS network and my frontend component isn't the Kamailio server.<br><br></div>But now I understood that the requirement is having this component in the frontend of network in order to have the correct information from UE.<br><br></div>Once again, thank you all to make it more clear to me.<br><br></div>BR<br></div>José<br></div><div class="gmail_extra"><br><div class="gmail_quote">2016-04-28 10:16 GMT+01:00 Jason Penton <span dir="ltr"><<a href="mailto:jason.penton@smilecoms.com" target="_blank">jason.penton@smilecoms.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">Hi José<div><br></div><div>Ivailo is correct here, you need to have p-cscf *be* the SBC or at least sit in front of one if it is not the SBC. If not you will effectively be sending "junk" to the PCRF and it will be impossible for it to signal the correct setup of bearers between UE and P-CSCF/SBC.</div><div><br></div><div>Then, re. youre questions around usrloc. The current pre-requisites of binding to usrloc and dialog are for the following reasons:</div><div><br></div><div>1. if signalling bearer is removed by network, typically QCI 5 bearer (for whatever reason) viz ASR - then:</div><div>a) tear down all active calls related to contact (requires dialog_ng binding)</div><div>b) unregister contact (network initiated) (requires usrloc binding)</div><div><br></div><div>2. if media bearer is removed by network (typically QCI 1 and / or 2) - then:</div><div>a) terminate active call (requires dialog_ng binding)</div><div><br></div><div>So, for ims_qos to correctly do what it is meant to do, it <b>has</b> to bind to the ims_usrloc... I hope this helps make sense of it all a little more</div><div><br></div><div>Cheers</div><span class="HOEnZb"><font color="#888888"><div>Jason</div></font></span></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Apr 28, 2016 at 12:22 AM, Ivailo Dobrev <span dir="ltr"><<a href="mailto:ivailod@telera.eu" target="_blank">ivailod@telera.eu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
Hi Jose,<br>
<br>
Framed IP or some king of hashing over IP/identitiy/APN... is used
from PCRF for session binding. If I understand question right the
short answer is that reservation from PCRF is made by
Media-Component-Description not by framed IP address. In your
architecture if Kamailio instance that serves Rx do not have real UE
IP address (and real SDP media addresses) it cannot send proper info
to PCRF. You should put Kamailio in front of SBC...<br>
<br>
BR,<br>
Ivo<div><div><br>
<br>
<div>On 04/28/2016 12:28 AM, José Seabra
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">Hi,
<div>Updating my last email, I noticed that the
AVP framed_ip_address is also containing the IP address of SDP
C field, so in my case that I have a SBC in front of my
Kamailio doing NAT, the SDP address will be the IP of the SBC,
in order that PCRF will try reserve bandwidth in the SBC.</div>
<div><br>
</div>
<div>What we can do in these cases?</div>
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra">Thank you for your support</div>
<div class="gmail_extra">BR</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">2016-04-27 10:52 GMT+01:00 José
Seabra <span dir="ltr"><<a href="mailto:joseseabra4@gmail.com" target="_blank">joseseabra4@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>
<div>Hi Jason,<br>
</div>
<div>What could be the impact of using both modules
(usrloc and ims_usrloc_pcscf)?<br>
<br>
One of the impacts that I can see is the Shared
memory, it will consume more shared memory because
will save the AOR twice in memory, one in usrloc and
the other in ims_usrloc_pcscf, is that right?<br>
<br>
<div>
<div>Another Doubt that I have:<br>
<br>
</div>
At this moment I'm only using the function
rx_aar, (I'm not using ims_qos with register sip
messages), and when kamailio sends an AAR to PCRF,
the AVP "Flow-Description" contains the IP address
of received host, that is a kamailio server acting
as loadbalancer, not the Terminal IP address.<br>
<br>
So I'm obliged to use RX on registrar messages in
order to have the AOR of the SIP Terminal on the
AVP "Flow-Description"? Or can I manipulate it in
an easy way?<br>
<br>
<br>
</div>
<br>
</div>
</div>
<div>Anyway I'm facing an issue when PCRF is sending an
Abort-Session Request after the call is established,
Kamailio stops working with the following Log
messages:<br>
<br>
<br>
36(21757) DEBUG: cdp [receiver.c:1083]:
receive_message(): receive_message(): [<a href="http://alb-pcrf.rx.example.com" target="_blank">alb-pcrf.rx.example.com</a>] Recv
msg 274<br>
36(21757) DEBUG: cdp [peerstatemachine.c:92]:
sm_process(): sm_process(): Peer <a href="http://alb-pcrf.rx.example.com" target="_blank">alb-pcrf.rx.example.com</a>
State I_Open Event I_Rcv_Message<br>
36(21757) DEBUG: cdp [session.c:305]:
cdp_get_session(): called get session with id <a href="http://proxy1.sw.example.com" target="_blank">proxy1.sw.example.com</a>;2463925226;1
and hash 39<br>
36(21757) DEBUG: cdp [session.c:308]:
cdp_get_session(): looking for |<a href="http://proxy1.sw.example.com" target="_blank">proxy1.sw.example.com</a>;2463925226;1|
in |<a href="http://proxy1.sw.example.com" target="_blank">proxy1.sw.example.com</a>;2463925226;1|<br>
36(21757) DEBUG: ims_qos [mod.c:301]:
callback_for_cdp_session(): callback_for_cdp
session(): called with event 5 and session id [<a href="http://proxy1.sw.example.com" target="_blank">proxy1.sw.example.com</a>;2463925226;1]<br>
36(21757) DEBUG: ims_qos [cdpeventprocessor.c:113]:
new_cdp_cb_event(): Creating new event for rx session
[<a href="http://proxy1.sw.example.com" target="_blank">proxy1.sw.example.com</a>;2463925226;1]<br>
36(21757) INFO: cdp [authstatemachine.c:271]:
auth_client_statefull_sm_process(): after callback of
event 5<br>
36(21757) INFO: cdp [authstatemachine.c:733]:
Send_ASA(): Send_ASA(): sending ASA<br>
36(21757) INFO: cdp [authstatemachine.c:758]:
Send_ASA(): sending ASA to peer alb-pcrf<br>
36(21757) DEBUG: cdp [diameter_msg.c:83]:
AAABuildMsgBuffer(): AAABuildMsgBuffer(): len=172<br>
39(21770) DEBUG: ims_qos [cdpeventprocessor.c:209]:
cdp_cb_event_process(): processing event [5]<br>
39(21770) DEBUG: ims_qos [cdpeventprocessor.c:221]:
cdp_cb_event_process(): Received notification of ASR
from transport plane or CDP timeout for CDP session
with Rx session ID: [<a href="http://proxy1.sw.example.com" target="_blank">proxy1.sw.example.com</a>;2463925226;1]
and associated contact [] and domain []<br>
39(21770) DEBUG: ims_qos [cdpeventprocessor.c:228]:
cdp_cb_event_process(): This is a media bearer session
session39(21770) DEBUG: ims_qos
[cdpeventprocessor.c:316]: free_cdp_cb_event():
Freeing cdpb CB event structure<br>
39(21770) DEBUG: ims_qos [cdpeventprocessor.c:318]:
free_cdp_cb_event(): about to free string from cdp CB
event [<a href="http://proxy1.sw.example.com" target="_blank">proxy1.sw.example.com</a>;2463925226;1]<br>
0(21693) ALERT: <core> [main.c:739]:
handle_sigs(): child process 21757 exited by a signal
11<br>
0(21693) ALERT: <core> [main.c:742]:
handle_sigs(): core was not generated<br>
0(21693) INFO: <core> [main.c:754]:
handle_sigs(): terminating due to SIGCHLD<br>
0(21693) DEBUG: <core> [main.c:756]:
handle_sigs(): terminating due to SIGCHLD<br>
69(21816) INFO: <core> [main.c:809]: sig_usr():
signal 15 received<br>
.<br>
.<br>
.<br>
<br>
</div>
<br>
<div>Thank you<br>
<br>
</div>
<div>Best Regards<span><font color="#888888"><br>
</font></span></div>
<span><font color="#888888">
<div>José Seabra<br>
</div>
<span style="color:rgb(0,0,0);background-color:rgb(254,254,238)"><br>
</span></font></span></div>
<div>
<div>
<div class="gmail_extra"><br>
<div class="gmail_quote">2016-04-25 13:27 GMT+01:00
Jason Penton <span dir="ltr"><<a href="mailto:jason.penton@smilecoms.com" target="_blank"></a><a href="mailto:jason.penton@smilecoms.com" target="_blank">jason.penton@smilecoms.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">Hi José,
<div><br>
</div>
<div>Unfortunately you have to use the
ims_usrloc_pcscf as there are extra extra
data fields that are required in the case of
IMS registrations. Perhaps what you can do
is run with both usrloc backends. I know
that we made the restriction that you could
only use one but I as soon as I get a chance
I will see if it's possible for ims modules
to bind specifically to the ims_usrloc_*
module as well as allow you to run "other"
code that bind to other usrloc backends.</div>
<div><br>
</div>
<div>Cheers</div>
<span><font color="#888888">
<div>Jason</div>
</font></span></div>
<div>
<div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Sun, Apr 24,
2016 at 11:30 PM, José Seabra <span dir="ltr"><<a href="mailto:joseseabra4@gmail.com" target="_blank"></a><a href="mailto:joseseabra4@gmail.com" target="_blank">joseseabra4@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">Hi all,
<div>Once again, thank you all for
the Help.</div>
<div><br>
</div>
<div>I have one last question, can I
use the function <span style="color:rgb(0,0,0);background-color:rgb(254,254,238)">Rx_AAR_Register
without save the usr location
information on </span><font color="#000000">ims_usrloc_pcscf?
that is because I'm already
using the usrloc module with
dmq_usrloc.</font></div>
<div><font color="#000000"><br>
</font></div>
<div><font color="#000000">I know
that ims_usrloc_pcscf is a
dependency of ims_qos, but the
doubt here is if I don't use
the </font><span style="color:rgb(0,0,0);background-color:rgb(254,254,238)">ims_registrar_pcscf,
the usrloc_pcscf won't be used
to store usr location? And the
ims_qos will works correctly?</span></div>
<div><span style="color:rgb(0,0,0);background-color:rgb(254,254,238)"><br>
</span></div>
<div><span style="color:rgb(0,0,0);background-color:rgb(254,254,238)">BR</span></div>
<span><font color="#888888">
<div><span style="color:rgb(0,0,0);background-color:rgb(254,254,238)">José
Seabra</span></div>
<div><br>
</div>
</font></span></div>
<div>
<div>
<div class="gmail_extra"><br>
<div class="gmail_quote">2016-04-22
23:46 GMT+01:00 Ivailo Dobrev
<span dir="ltr"><<a href="mailto:ivailod@telera.eu" target="_blank"></a><a href="mailto:ivailod@telera.eu" target="_blank">ivailod@telera.eu</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"> Hi Jason,<br>
<br>
It is always better when
code "guru" shares his
opinion :)<br>
<br>
Cheers gents !
<div>
<div><br>
<br>
<br>
<div>On 04/23/2016
01:35 AM, Jason
Penton wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">Hi
gents,
<div><br>
</div>
<div>we do not
support the
preliminary
service
information. So
for now you can
only call Rx_AAR
when you have
SDP in the
replies. So for
VoLTE
(preconditions),
for example you
can call on 183
SP whilst using
plain SIP you
will have to
call on the
first reply you
get that has SDP
(either 183SP or
200OK).</div>
<div><br>
</div>
<div>HTH</div>
<div><br>
</div>
<div>Cheers</div>
<div>Jason </div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On
Fri, Apr 22,
2016 at 11:11
PM, Ivailo
Dobrev <span dir="ltr"><<a href="mailto:ivailod@telera.eu" target="_blank"></a><a href="mailto:ivailod@telera.eu" target="_blank">ivailod@telera.eu</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
Yes you send
both direction
media
information to
the PCRF but
when reply is
received in
precondition
state.
<div>
<div><br>
<br>
<div>On
04/23/2016
12:03 AM, José
Seabra wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">Hello
Ivailo and <span style="font-size:12.8px">Franz,</span>
<div><span style="font-size:12.8px"><br>
</span></div>
<div><span style="font-size:12.8px">Thank
you for your
clarifications.</span></div>
<div><span style="font-size:12.8px"><br>
</span></div>
<div><span style="font-size:12.8px">Well
sending an AAR
when receive a
reply makes
all sense, but
ims_qos must
send the SDP
information
from the
Initial Invite
and also from
183 ringing or
200Ok, Am I
correct?</span></div>
<div><span style="font-size:12.8px"><br>
</span></div>
<div><span style="font-size:12.8px">Because
PCRF needs to
know the
session
parameters
from Initial
Initial INVITE
and the reply
to it.</span></div>
<div><span style="font-size:12.8px"><br>
</span></div>
<div><span style="font-size:12.8px">The
PCRF is
a proprietary solution. </span></div>
<div><span style="font-size:12.8px"><br>
</span></div>
<div><span style="font-size:12.8px">Thank
you</span></div>
<div><span style="font-size:12.8px">BR</span></div>
<div><span style="font-size:12.8px">José
Seabra</span></div>
<div><span style="font-size:12.8px"><br>
</span></div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">2016-04-22
21:54
GMT+01:00
Ivailo Dobrev
<span dir="ltr"><<a href="mailto:ivailod@telera.eu" target="_blank"></a><a href="mailto:ivailod@telera.eu" target="_blank">ivailod@telera.eu</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
Hi Franz,<br>
<br>
There no real
OS PCRF.
Yota/Telexir
use to had
some free VM
image that is
OK for test.
You can search
about
FreePCRF. It
is a little
tricky to
configure it
but ... I made
for my tests a
really dummy
one based on
FreeDIAMETER.
Generally
speaking PCRF
is the "brain"
of the network
and you should
understand and
design things
well there. I
have
experience
also w/
commercial
PCRFs and
there is no
real answer
yes this is a
right way of
making
something.<br>
<br>
Cheers,<br>
<br>
Ivo
<div>
<div><br>
<br>
On 04/22/2016
11:09 PM,
Franz Edler
wrote:<br>
</div>
</div>
<blockquote type="cite">
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Hi </span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif" lang="DE">José,</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif" lang="DE"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif" lang="EN-US">in
principle it
is possible to
send an AAR
after
receiving the
request. In
this case the
Service-Info-Status
AVP is set to
PRELIMINARY
SERVICE
INFORMATION.</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif" lang="EN-US">More
efficient is
it to wait
until SDP
answer is
received and
then the
Service-Info-Status
AVP is set to
FINAL_SERVICE_INFORMATION.</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif" lang="EN-US"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif" lang="EN-US">I
don’t know if
both methods
are covered in
ims_qos
module.</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif" lang="EN-US"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif" lang="EN-US">BTW:
which PCRF are
you using? Is
there some
open source
PCRF
available?</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif" lang="EN-US"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif" lang="EN-US">BR
</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif" lang="EN-US">Franz</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif" lang="EN-US"></span></p>
<p class="MsoNormal"><a name="m_-2314813183173972637_m_-8795717174675138278_m_-9216171539801978707_m_2368407585857785675_m_-319018792623189699_m_8658665282185897518_m_-4830481951054555584_m_5226943923647200882__MailEndCompose"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif" lang="EN-US"> </span></a></p>
<span></span>
<div style="border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt">
<div>
<div style="border:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif" lang="DE">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif" lang="DE">
sr-users [<a href="mailto:sr-users-bounces@lists.sip-router.org" target="_blank"></a><a href="mailto:sr-users-bounces@lists.sip-router.org" target="_blank">mailto:sr-users-bounces@lists.sip-router.org</a>]
<b>On Behalf
Of </b>José
Seabra<br>
<b>Sent:</b>
Friday, April
22, 2016 3:58
PM<br>
<b>To:</b>
Kamailio (SER)
- Users
Mailing List <a href="mailto:sr-users@lists.sip-router.org" target="_blank"></a><a href="mailto:sr-users@lists.sip-router.org" target="_blank"><sr-users@lists.sip-router.org></a><br>
<b>Subject:</b>
[SR-Users]
Kamailio
IMS_QOS</span></p>
</div>
</div>
<p class="MsoNormal"> </p>
<div>
<div>
<div>
<div>
<p class="MsoNormal">Hello
There,<br>
<br>
I'm trying
using the
ims_qos module
with PCRF for
QOS, but I'm
facing some
issues.<br>
<br>
When kamailio
receives an
initial invite
(originator),
it will
execute the
function -
"Rx_AAR("ORIG_SESSION_AAR","orig","",-1)",
but the PCRF
is not
contacted and
i see the
following
messages:<br>
<br>
5(12153)
DEBUG:
<script>:
Diameter: Orig
authorizing
media via Rx<br>
5(12153)
DEBUG: ims_qos
[mod.c:609]:
w_rx_aar():
Looking for
route block
[ORIG_SESSION_AAR]<br>
5(12153)
DEBUG: ims_qos
[mod.c:621]:
w_rx_aar(): Rx
AAR called<br>
5(12153)
DEBUG: ims_qos
[mod.c:1345]:
create_return_code():
Creating
return code of
[-2] for
aar_return_code<br>
5(12153)
DEBUG: ims_qos
[mod.c:1354]:
create_return_code():
created AVP
successfully :
[aar_return_code]<br>
5(12153)
DEBUG: ims_qos
[mod.c:627]:
w_rx_aar():
Can't do AAR
for call
session in
request.<br>
<br clear="all">
</p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt">Why kamailio says that I Can't do AAR for
call session
in request? I
have looked
into source
code and I
found that the
condition that
is blocking
the
communication
with PCRF is:<br>
<br>
<br>
<br>
<br>
<br>
//We don't
ever do AAR on
request for
calling
scenario...<br>
if
(msg->first_line.type
!= SIP_REPLY)
{<br>
LM_DBG("Can't
do AAR for
call session
in
request\n");<br>
return
result;<br>
}</p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt">Anyone can help me understand why it is
happening? why
it can't
proceed if
isn't a reply?</p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt">Thank you for your support</p>
<div>
<p class="MsoNormal">BR</p>
</div>
<div>
<div>
<div>
<div>
<p class="MsoNormal">--
</p>
<div>
<div>
<p class="MsoNormal">José
Seabra</p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<br>
<fieldset></fieldset>
<br>
</div>
</div>
<span>
<pre>_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
<a href="mailto:sr-users@lists.sip-router.org" target="_blank">sr-users@lists.sip-router.org</a>
<a 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>
</span></blockquote>
<br>
</div>
<br>
_______________________________________________<br>
SIP Express
Router (SER)
and Kamailio
(OpenSER) -
sr-users
mailing list<br>
<a href="mailto:sr-users@lists.sip-router.org" target="_blank"></a><a href="mailto:sr-users@lists.sip-router.org" target="_blank">sr-users@lists.sip-router.org</a><br>
<a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users" rel="noreferrer" target="_blank"></a><a 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>
<br>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
<div>Cumprimentos
<div>José
Seabra</div>
</div>
</div>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
<a href="mailto:sr-users@lists.sip-router.org" target="_blank">sr-users@lists.sip-router.org</a>
<a 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>
</div>
</div>
</div>
<br>
_______________________________________________<br>
SIP Express
Router (SER)
and Kamailio
(OpenSER) -
sr-users
mailing list<br>
<a href="mailto:sr-users@lists.sip-router.org" target="_blank"></a><a href="mailto:sr-users@lists.sip-router.org" target="_blank">sr-users@lists.sip-router.org</a><br>
<a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users" rel="noreferrer" target="_blank"></a><a 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>
<br>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
<div>
<div dir="ltr">
<div>
<div dir="ltr">
<div>
<div dir="ltr">
<div>
<table style="width:450pt" cellpadding="0" cellspacing="0" border="0" width="600">
<tbody>
<tr>
<td style="padding:0cm" valign="top"><br>
</td>
</tr>
</tbody>
</table>
<table style="font-family:monospace" cellpadding="0" cellspacing="0" border="0" width="320px">
<tbody>
<tr>
<td style="font-family:Arial,sans-serif;font-size:16px;color:rgb(117,179,67);line-height:18px;padding-left:15px;padding-top:10px"><b>Jason
Penton</b></td>
</tr>
<tr>
<td style="font-family:Arial,sans-serif;font-size:16px;color:rgb(117,179,67);line-height:18px;padding-left:15px;padding-top:10px"><b>Senior
Manager:
Applications
and Services</b></td>
</tr>
<tr>
<td style="font-family:Arial,sans-serif;font-size:16px;color:rgb(134,145,154);line-height:18px;padding-left:15px;padding-top:10px"><b>Smile
Communications
Pty (Ltd)</b></td>
</tr>
<tr>
<td>
<table cellpadding="0" cellspacing="0" width="100%">
<tbody>
<tr>
<td style="font-family:Arial,sans-serif;font-size:16px;color:rgb(134,145,154);line-height:18px;padding-left:15px;padding-top:10px" width="27%"><b>Voice:<br>
<br>
Mobile:</b></td>
<td style="font-family:Arial,sans-serif;font-size:16px;color:rgb(134,145,154);line-height:18px;padding-left:10px;padding-top:10px" width="73%"><span>+234
(0) 702 000
000 7</span><br>
<br>
<a href="tel:%2B27%20%280%29%2083%20283%207000" value="+27832837000" target="_blank">+27
(0) 83 283
7000</a></td>
</tr>
<tr>
<td style="font-family:Arial,sans-serif;font-size:16px;color:rgb(134,145,154);line-height:18px;padding-left:15px;padding-top:10px"><b>Skype:</b></td>
<td style="font-family:Arial,sans-serif;font-size:16px;color:rgb(134,145,154);line-height:18px;padding-left:10px;padding-top:10px">jason.barry.penton</td>
</tr>
</tbody>
</table>
</td>
</tr>
<tr>
<td style="font-family:Arial,sans-serif;font-size:16px;color:rgb(117,179,67);line-height:18px;padding-left:15px;padding-top:10px"><a href="mailto:jason.penton@smilecoms.com" target="_blank"></a><a href="mailto:jason.penton@smilecoms.com" target="_blank">jason.penton@smilecoms.com</a></td>
</tr>
<tr>
<td style="font-family:Arial,sans-serif;font-size:16px;color:rgb(117,179,67);line-height:18px;padding-left:15px;padding-top:10px"><a href="http://www.smilecoms.com" target="_blank"></a><a href="http://www.smilecoms.com" target="_blank">www.smilecoms.com</a><br>
<img src="http://196.33.227.129/%7Esmlcoms/sigs/pty/images/smile_signature_07_09.jpg" height="144" width="420"><br>
</td>
</tr>
</tbody>
</table>
</div>
<br>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<br>
<span><font color="#888888">
<pre>This email is subject to the disclaimer of Smile Communications at <a href="http://www.smilecoms.com/home/email-disclaimer/" target="_blank">http://www.smilecoms.com/home/email-disclaimer/</a></pre>
</font></span>
<fieldset></fieldset>
<pre>_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
<a href="mailto:sr-users@lists.sip-router.org" target="_blank">sr-users@lists.sip-router.org</a>
<a 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>
</div>
</div>
</div>
<br>
_______________________________________________<br>
SIP Express Router (SER) and
Kamailio (OpenSER) -
sr-users mailing list<br>
<a href="mailto:sr-users@lists.sip-router.org" target="_blank">sr-users@lists.sip-router.org</a><br>
<a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users" rel="noreferrer" target="_blank">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a><br>
<br>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
<div>Cumprimentos
<div>José Seabra</div>
</div>
</div>
</div>
</div>
<br>
_______________________________________________<br>
SIP Express Router (SER) and Kamailio
(OpenSER) - sr-users mailing list<br>
<a href="mailto:sr-users@lists.sip-router.org" target="_blank">sr-users@lists.sip-router.org</a><br>
<a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users" rel="noreferrer" target="_blank">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a><br>
<br>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
<div>
<div dir="ltr">
<div>
<div dir="ltr">
<div>
<div dir="ltr">
<div>
<table style="width:450pt" cellpadding="0" cellspacing="0" border="0" width="600">
<tbody>
<tr>
<td style="padding:0cm" valign="top"><br>
</td>
</tr>
</tbody>
</table>
<table style="font-family:monospace" cellpadding="0" cellspacing="0" border="0" width="320px">
<tbody>
<tr>
<td style="font-family:Arial,sans-serif;font-size:16px;color:rgb(117,179,67);line-height:18px;padding-left:15px;padding-top:10px"><b>Jason
Penton</b></td>
</tr>
<tr>
<td style="font-family:Arial,sans-serif;font-size:16px;color:rgb(117,179,67);line-height:18px;padding-left:15px;padding-top:10px"><b>Senior
Manager:
Applications and
Services</b></td>
</tr>
<tr>
<td style="font-family:Arial,sans-serif;font-size:16px;color:rgb(134,145,154);line-height:18px;padding-left:15px;padding-top:10px"><b>Smile
Communications Pty
(Ltd)</b></td>
</tr>
<tr>
<td>
<table cellpadding="0" cellspacing="0" width="100%">
<tbody>
<tr>
<td style="font-family:Arial,sans-serif;font-size:16px;color:rgb(134,145,154);line-height:18px;padding-left:15px;padding-top:10px" width="27%"><b>Voice:<br>
<br>
Mobile:</b></td>
<td style="font-family:Arial,sans-serif;font-size:16px;color:rgb(134,145,154);line-height:18px;padding-left:10px;padding-top:10px" width="73%"><span>+234
(0) 702 000
000 7</span><br>
<br>
<a href="tel:%2B27%20%280%29%2083%20283%207000" value="+27832837000" target="_blank">+27
(0) 83 283
7000</a></td>
</tr>
<tr>
<td style="font-family:Arial,sans-serif;font-size:16px;color:rgb(134,145,154);line-height:18px;padding-left:15px;padding-top:10px"><b>Skype:</b></td>
<td style="font-family:Arial,sans-serif;font-size:16px;color:rgb(134,145,154);line-height:18px;padding-left:10px;padding-top:10px">jason.barry.penton</td>
</tr>
</tbody>
</table>
</td>
</tr>
<tr>
<td style="font-family:Arial,sans-serif;font-size:16px;color:rgb(117,179,67);line-height:18px;padding-left:15px;padding-top:10px"><a href="mailto:name.surname@smilecoms.com" style="font-family:Arial;color:rgb(117,179,67);text-decoration:none" target="_blank"></a><a href="mailto:jason.penton@smilecoms.com" target="_blank">jason.penton@smilecoms.com</a></td>
</tr>
<tr>
<td style="font-family:Arial,sans-serif;font-size:16px;color:rgb(117,179,67);line-height:18px;padding-left:15px;padding-top:10px"><a href="http://www.smilecoms.com/" style="font-family:Arial;color:rgb(117,179,67)" target="_blank"></a><a href="http://www.smilecoms.com" target="_blank">www.smilecoms.com</a><br>
<img src="http://196.33.227.129/%7Esmlcoms/sigs/pty/images/smile_signature_07_09.jpg" height="144" width="420"><br>
</td>
</tr>
</tbody>
</table>
</div>
<br>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<br>
<span><font color="#888888">
<pre>This email is subject to the disclaimer of Smile Communications at <a href="http://www.smilecoms.com/home/email-disclaimer/" target="_blank">http://www.smilecoms.com/home/email-disclaimer/</a></pre>
</font></span></div>
</div>
<br>
_______________________________________________<br>
SIP Express Router (SER) and Kamailio (OpenSER)
- sr-users mailing list<br>
<a href="mailto:sr-users@lists.sip-router.org" target="_blank">sr-users@lists.sip-router.org</a><br>
<a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users" rel="noreferrer" target="_blank">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a><br>
<br>
</blockquote>
</div>
<br>
<br clear="all">
<br>
-- <br>
<div>Cumprimentos
<div>José Seabra</div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
<div>Cumprimentos
<div>José Seabra</div>
</div>
</div>
</div>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
<a href="mailto:sr-users@lists.sip-router.org" target="_blank">sr-users@lists.sip-router.org</a>
<a 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>
</div></div></div>
<br>_______________________________________________<br>
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list<br>
<a href="mailto:sr-users@lists.sip-router.org" target="_blank">sr-users@lists.sip-router.org</a><br>
<a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users" rel="noreferrer" target="_blank">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><table style="width:450pt" cellpadding="0" cellspacing="0" border="0" width="600"><tbody><tr><td style="padding:0cm" valign="top"><p></p></td></tr></tbody></table><table style="font-family:monospace" cellpadding="0" cellspacing="0" border="0" width="320px"><tbody><tr><td style="font-family:Arial,sans-serif;font-size:16px;color:rgb(117,179,67);line-height:18px;padding-left:15px;padding-top:10px"><b>Jason Penton</b></td></tr><tr><td style="font-family:Arial,sans-serif;font-size:16px;color:rgb(117,179,67);line-height:18px;padding-left:15px;padding-top:10px"><b>Senior Manager: Applications and Services</b></td></tr><tr><td style="font-family:Arial,sans-serif;font-size:16px;color:rgb(134,145,154);line-height:18px;padding-left:15px;padding-top:10px"><b>Smile Communications Pty (Ltd)</b></td></tr><tr><td><table cellpadding="0" cellspacing="0" width="100%"><tbody><tr><td style="font-family:Arial,sans-serif;font-size:16px;color:rgb(134,145,154);line-height:18px;padding-left:15px;padding-top:10px" width="27%"><b>Voice:<br><br>Mobile:</b></td><td style="font-family:Arial,sans-serif;font-size:16px;color:rgb(134,145,154);line-height:18px;padding-left:10px;padding-top:10px" width="73%"><span>+234 (0) 702 000 000 7</span><br><br><a href="tel:%2B27%20%280%29%2083%20283%207000" value="+27832837000" target="_blank">+27 (0) 83 283 7000</a></td></tr><tr><td style="font-family:Arial,sans-serif;font-size:16px;color:rgb(134,145,154);line-height:18px;padding-left:15px;padding-top:10px"><b>Skype:</b></td><td style="font-family:Arial,sans-serif;font-size:16px;color:rgb(134,145,154);line-height:18px;padding-left:10px;padding-top:10px">jason.barry.penton</td></tr></tbody></table></td></tr><tr><td style="font-family:Arial,sans-serif;font-size:16px;color:rgb(117,179,67);line-height:18px;padding-left:15px;padding-top:10px"><a href="mailto:name.surname@smilecoms.com" style="font-family:Arial;color:rgb(117,179,67);text-decoration:none" target="_blank">jason.penton@smilecoms.com</a></td></tr><tr><td style="font-family:Arial,sans-serif;font-size:16px;color:rgb(117,179,67);line-height:18px;padding-left:15px;padding-top:10px"><a href="http://www.smilecoms.com/" style="font-family:Arial;color:rgb(117,179,67)" target="_blank">www.smilecoms.com</a><br><img src="http://196.33.227.129/~smlcoms/sigs/pty/images/smile_signature_07_09.jpg" height="144" width="420"><br></td></tr></tbody></table></div><br></div></div></div></div></div></div>
</div>
<br>
<span><font color="#888888"><pre>This email is subject to the disclaimer of Smile Communications at <a href="http://www.smilecoms.com/home/email-disclaimer/" target="_blank">http://www.smilecoms.com/home/email-disclaimer/</a><a href="http://www.smilecoms.com/disclaimer" target="_blank"></a></pre></font></span></div></div><br>_______________________________________________<br>
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list<br>
<a href="mailto:sr-users@lists.sip-router.org">sr-users@lists.sip-router.org</a><br>
<a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users" rel="noreferrer" target="_blank">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature">Cumprimentos<div>José Seabra</div></div>
</div>