<div dir="ltr">Tristan,<div><br></div><div>Did not look deep but could likely a side effect to the following error representing over 50% of your log:</div><div><br></div><div>       ERROR: pv [pv_trans.c:1022]: tr_eval_uri(): invalid uri [0]<br></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature"><div dir="ltr"><span style="font-family:arial,sans-serif;background-color:rgb(255,255,255)"><span style="font-family:Arial"><div style="font-size:13px;color:rgb(119,119,119)">Regards,</div><div style="font-size:13px;color:rgb(119,119,119)"><br></div><div style="font-size:13px;color:rgb(119,119,119)">Lorenzo</div></span></span><span style="font-family:arial,sans-serif;background-color:rgb(255,255,255)"><span style="font-family:Arial"><div style="font-size:x-small"><br></div><div style="font-size:x-small"><br></div></span></span></div></div></div>
<br><div class="gmail_quote">On Wed, Aug 26, 2015 at 3:03 PM, Tristan Delsol <span dir="ltr"><<a href="mailto:tdelsol@qfast.nl" target="_blank">tdelsol@qfast.nl</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Hi Daniel,<br>
<br>
I'm hoping you're not fed up with this one. I did a debug on the proxy for this and I noticed that for some reason the proxy reads the Callee as "0". But I'm not sure why. I'm not really familiar with the debug log.<br>
I hope you can find some spare time to have a look anyways.<br>
On line 959 you can see the "No matching rewrite rules for '0' found".<br>
<br>
Thanks,<br>
Tristan<br>
<br>
On 2015-08-25 17:13, Tristan Delsol wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
I asked them a couple of days back, but it's not possible. They are<br>
flexible as most big telco's are.<br>
I will try and sell them the idea that I will use a separate analog<br>
line for faxing then or something.<br>
Not sure what else to try anymore.<br>
<br>
Tristan<br>
<br>
On 25-08-15 16:43, Daniel Grotti wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
Can you disable t38 in such a broken device ?<br>
<br>
<br>
--<br>
Daniel Grotti<br>
VoIP Engineer<br>
<br>
<br>
Sipwise GmbH<br>
Europaring F15 | 2345 Brunn am Gebirge, Austria | <a href="http://www.sipwise.com" rel="noreferrer" target="_blank">www.sipwise.com</a><br>
<br>
On 08/25/2015 04:40 PM, Tristan Delsol wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
Hi Daniel,<br>
<br>
If I send a 488 back it tries another re-invite with just g711 but then<br>
I get the 404 not found also. So that one is not working.<br>
Does spce check the request-uri? If so, then I can understand the 404<br>
because of the weird request-uri.<br>
<br>
<br>
<br>
On 25-08-15 16:35, Daniel Grotti wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
Hi,<br>
how is that possible ?<br>
Did you add a section in LB like ?<br>
<br>
if(is_method("INVITE") && uri =~ "^sip:ngcp-lb;tgrp.+@")<br>
{<br>
      sl_send_reply("488", "Not acceptable");<br>
      exit;<br>
}<br>
<br>
<br>
<br>
<br>
<br>
<br>
--<br>
Daniel Grotti<br>
VoIP Engineer<br>
<br>
<br>
Sipwise GmbH<br>
Europaring F15 | 2345 Brunn am Gebirge, Austria | <a href="http://www.sipwise.com" rel="noreferrer" target="_blank">www.sipwise.com</a><br>
<br>
On 08/25/2015 04:32 PM, Tristan Delsol wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
Just to be sure I reinstalled the whole box and configured it as basic<br>
as possible, but unfortunately still getting the 404 not found on the<br>
re-invite.<br>
Is there anything else I can try?<br>
<br>
Tristan<br>
<br>
On 24-08-15 11:55, Tristan Delsol wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
I tried the 488 from LB, but if I do that I still get the same 404 not<br>
found. So I send the 488, the telco ACKs it and then sends a new INVITE<br>
without T.38 but the same happens with this INVITE, which is the 404<br>
not<br>
found.<br>
<br>
I have a trace of that one also if you want.<br>
<br>
On 24-08-15 11:40, Daniel Grotti wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
Hi,<br>
something wrong in your rewriting patch, cause proxy receives:<br>
<br>
Call from PSTN -<br>
R=<a href="mailto:sip%3Angcp-lb@87.239.101.193" target="_blank">sip:ngcp-lb@87.239.101.193</a>:5060;ngcpct=7369703a3132372e302e302e313a35303830<br>
<br>
<br>
<br>
ID=1183523204412000183319@192.168.111.25_b2b-1<br>
<br>
<br>
I would suggest to do not rewrite, but just reject the re-invite with<br>
488 on LB if the RURI has that format.<br>
<br>
<br>
--<br>
Daniel Grotti<br>
VoIP Engineer<br>
<br>
<br>
Sipwise GmbH<br>
Europaring F15 | 2345 Brunn am Gebirge, Austria | <a href="http://www.sipwise.com" rel="noreferrer" target="_blank">www.sipwise.com</a><br>
<br>
On 08/24/2015 11:12 AM, Tristan Delsol wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
No problem. Attached.<br>
And thanks for the help.<br>
<br>
Tristan<br>
<br>
On 24-08-15 11:09, Daniel Grotti wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
would help to see LB an PROXY log.<br>
<br>
<br>
--<br>
Daniel Grotti<br>
VoIP Engineer<br>
<br>
<br>
Sipwise GmbH<br>
Europaring F15 | 2345 Brunn am Gebirge, Austria | <a href="http://www.sipwise.com" rel="noreferrer" target="_blank">www.sipwise.com</a><br>
<br>
On 08/24/2015 10:35 AM, Tristan Delsol wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
Daniel,<br>
<br>
I have no clue :)<br>
<br>
Here the re-invite before I rewrite the request-uri and the 404<br>
response:<br>
INVITE<br>
sip:ngcp-lb;tgrp=9752;trunk-context=ipic.imscore.net@87.239.101.193:5060;ngcpct=7369703a3132372e302e302e313a35303830<br>
<br>
<br>
<br>
<br>
SIP/2.0<br>
Via: SIP/2.0/UDP<br>
139.156.126.49:5060;branch=z9hG4bKfofomd006o71lno6s1i0.1<br>
Call-ID: 585966869312000201754@192.168.111.25_b2b-1<br>
From:<br>
<<a href="mailto:sip%3A%2B31306665648@ims.imscore.net" target="_blank">sip:+31306665648@ims.imscore.net</a>>;tag=SDemtl399-127.0.0.1alUtKGp-09752+1+a3000095+156d2c30<br>
<br>
<br>
<br>
<br>
<br>
To:<br>
<<a href="mailto:sip%3A%2B31756418049@192.168.111.25" target="_blank">sip:+31756418049@192.168.111.25</a>>;tag=3D534336-55D9A6A9000B9F71-7E3B2700<br>
<br>
<br>
<br>
CSeq: 98894742 INVITE<br>
Expires: 180<br>
Contact: <sip:<a href="tel:%2B31306665648" value="+31306665648" target="_blank">+31306665648</a>@<a href="http://139.156.126.49:5060" target="_blank">139.156.126.49:5060</a>;transport=udp><br>
Min-SE: 90<br>
Session-Expires: 7200;refresher=uac<br>
Supported: replaces, path, 100rel, timer<br>
Content-Length: 276<br>
Allow: INVITE, BYE, REGISTER, ACK, OPTIONS, CANCEL, SUBSCRIBE,<br>
NOTIFY,<br>
PRACK, INFO, REFER, UPDATE, PUBLISH, MESSAGE<br>
Max-Forwards: 69<br>
Content-Type: application/sdp<br>
User-Agent: Alcatel-Lucent 5060 MGC-8 9.2.0.4.0.11<br>
Route:<br>
<sip:87.239.101.193;r2=on;lr=on;ftag=3D534336-55D9A6A9000B9F71-7E3B2700;ngcplb=yes><br>
<br>
<br>
<br>
<br>
<br>
Route:<br>
<sip:127.0.0.1;r2=on;lr=on;ftag=3D534336-55D9A6A9000B9F71-7E3B2700;ngcplb=yes><br>
<br>
<br>
<br>
<br>
<br>
<br>
v=0<br>
o=- 3649316138 3649316139 IN IP4 139.156.126.49<br>
s=-<br>
c=IN IP4 139.156.126.49<br>
t=0 0<br>
m=image 23680 udptl t38<br>
a=T38FaxVersion:0<br>
a=T38MaxBitRate:14400<br>
a=T38FaxRateManagement:transferredTCF<br>
a=T38FaxMaxBuffer:72<br>
a=T38FaxMaxDatagram:316<br>
a=T38FaxUdpEC:t38UDPRedundancy<br>
<br>
<br>
SIP/2.0 404 Not Found<br>
Via: SIP/2.0/UDP<br>
139.156.126.49:5060;rport=5060;branch=z9hG4bKfofomd006o71lno6s1i0.1<br>
Call-ID: 585966869312000201754@192.168.111.25_b2b-1<br>
From:<br>
<<a href="mailto:sip%3A%2B31306665648@ims.imscore.net" target="_blank">sip:+31306665648@ims.imscore.net</a>>;tag=SDemtl399-127.0.0.1alUtKGp-09752+1+a3000095+156d2c30<br>
<br>
<br>
<br>
<br>
<br>
To:<br>
<<a href="mailto:sip%3A%2B31756418049@192.168.111.25" target="_blank">sip:+31756418049@192.168.111.25</a>>;tag=3D534336-55D9A6A9000B9F71-7E3B2700<br>
<br>
<br>
<br>
CSeq: 98894742 INVITE<br>
Server: Sipwise NGCP Proxy 3.X<br>
Content-Length: 0<br>
<br>
Tristan<br>
<br>
<br>
On 24-08-15 09:08, Daniel Grotti wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
Hi,<br>
how can you receive a 404 on a re-invite ?<br>
Does the re-invite have the From-tag and To-tag ?<br>
<br>
<br>
--<br>
Daniel Grotti<br>
VoIP Engineer<br>
<br>
<br>
Sipwise GmbH<br>
Europaring F15 | 2345 Brunn am Gebirge, Austria | <a href="http://www.sipwise.com" rel="noreferrer" target="_blank">www.sipwise.com</a><br>
<br>
On 08/24/2015 12:23 AM, Tristan Delsol wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
Checked a lot of things but I'm still getting a 404 not found<br>
from<br>
spce.<br>
I managed to change the request-uri from<br>
sip:ngcp-lb;tgrp=9752;trunk-context=ipic.imscore.net@87.239.101.193:5060;ngcpct=7369703a3132372e302e302e313a35303830<br>
<br>
<br>
<br>
<br>
<br>
to<br>
<a href="mailto:sip%3Angcp-lb@87.239.101.193" target="_blank">sip:ngcp-lb@87.239.101.193</a>:5060;ngcpct=7369703a3132372e302e302e313a35303830,<br>
<br>
<br>
<br>
<br>
<br>
but I'm still getting a 404 not found.<br>
Shouldn't this work?<br>
I mean the spce is sending this as Contact.<br>
<br>
Tristan<br>
<br>
On 2015-08-21 14:25, Daniel Grotti wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
Hi,<br>
yes something like:<br>
<br>
if(is_method("INVITE") && uri =~ "^sip:ngcp-lb;tgrp.+@")<br>
<br>
<br>
<br>
--<br>
Daniel Grotti<br>
VoIP Engineer<br>
<br>
<br>
Sipwise GmbH<br>
Europaring F15 | 2345 Brunn am Gebirge, Austria |<br>
<a href="http://www.sipwise.com" rel="noreferrer" target="_blank">www.sipwise.com</a><br>
<br>
On 08/20/2015 07:44 PM, Tristan Delsol wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
Hi Daniel,<br>
<br>
The only problem is actually that the telco sends this weird<br>
invite<br>
with<br>
the following request-uri:<br>
sip:ngcp-lb;tgrp=9752;trunk-context=ipic.imscore.net@87.239.101.193:5060;ngcpct=7369703a3132372e302e302e313a35303830<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
If I could maybe rewrite this to remove the<br>
";tgrp=9752;trunk-context=<a href="http://ipic.imscore.net" rel="noreferrer" target="_blank">ipic.imscore.net</a>" or send a 488<br>
then I<br>
should<br>
be good.<br>
<br>
Could I add something to<br>
/etc/ngcp-config/templates/etc/kamailio/proxy/proxy.cfg.customtt.tt2<br>
<br>
<br>
<br>
like<br>
if(is_method("INVITE") &&<br>
search("tgrp=9752;trunk-context=<a href="http://ipic.imscore.net" rel="noreferrer" target="_blank">ipic.imscore.net</a>"))<br>
{<br>
        sl_send_reply("488", "Not Acceptable Here");<br>
        exit;<br>
}<br>
<br>
Thanks,<br>
Tristan<br>
<br>
On 2015-08-20 16:15, Tristan Delsol wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
The reason is that the interconnect with our telco is tripping<br>
over<br>
our contact-header of ngcplb@<ip> only with T.38, because<br>
of the<br>
re-invite.<br>
They hide behind the fact that they have a spec for the<br>
interconnect<br>
that only wants phonenumber@<ip>or<dns> in the contact-header.<br>
<br>
<br>
<br>
On 20-08-15 16:05, Daniel Grotti wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
Hi,<br>
any reason for that ?<br>
The callee should reply 488, not the server.<br>
Anyway, I remember some old threasd about that:<br>
<a href="https://lists.sipwise.com/pipermail/spce-user/2014-June/006788.html" rel="noreferrer" target="_blank">https://lists.sipwise.com/pipermail/spce-user/2014-June/006788.html</a><br>
<br>
<br>
<br>
<br>
<br>
Maybe this could help.<br>
<br>
--<br>
Daniel Grotti<br>
VoIP Engineer<br>
<br>
<br>
Sipwise GmbH<br>
Europaring F15 | 2345 Brunn am Gebirge, Austria |<br>
<a href="http://www.sipwise.com" rel="noreferrer" target="_blank">www.sipwise.com</a><br>
<br>
On 08/20/2015 03:41 PM, Tristan Delsol wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
Back again on this :)<br>
<br>
One more thing. Would it be possible to disable T.38 support<br>
somehow. So<br>
that if the RE-INVITE comes in that we send back a 488?<br>
Or maybe I can set it up for certain subscriber numbers?<br>
<br>
Thanks,<br>
Tristan<br>
<br>
On 17-08-15 17:01, Tristan Delsol wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
Thanks for the info. I will experiment with that to see<br>
if it<br>
works.<br>
Then I will check if we would really want that or not.<br>
<br>
Tristan<br>
<br>
On 17-08-15 16:58, Andrew Pogrebennyk wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
On 08/17/2015 03:39 PM, Tristan Delsol wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
They state that they don't support that format for the<br>
contact<br>
header.<br>
They have it in the specs for the interconnect that the<br>
contact<br>
header<br>
can only contain the following:<br>
sip:+«ISN»@«ip-address/URL»:«port» with optional<br>
user=”phone”, so<br>
for<br>
example sip:<a href="tel:%2B31703434343" value="+31703434343" target="_blank">+31703434343</a>@domain.net:5060;user=”phone”.<br>
<br>
Where<br>
ISN: International Subscriber Number<br>
port: UDP portnumber;<br>
URL: Uniform Resource Locator: domain name;<br>
<br>
Is it possible I can adjust the contact header for this<br>
kind of<br>
request<br>
to keep the format as needed?<br>
</blockquote>
<br>
Unfortunately this is not something you can easily<br>
achieve,<br>
but if<br>
you<br>
have some understanding of kamailio config scripts you can<br>
try to<br>
modify<br>
/etc/ngcp-config/templates/etc/kamailio/lb/kamailio.cfg.tt2<br>
<br>
and disable the Contact masking completely, e.g.<br>
comment out<br>
all<br>
calls<br>
of ROUTE_MASK_CONTACT and ROUTE_UNMASK_CONTACT as a<br>
starting<br>
point.<br>
<br>
Then each side will receive the internal IP of b2b as<br>
Contact:<br>
sip:<a href="http://127.0.0.1:5080" rel="noreferrer" target="_blank">127.0.0.1:5080</a>, which exposes your topology a bit to<br>
outside<br>
but<br>
still doesn't break the protocol. But we are not<br>
sending the<br>
number part<br>
which might be a problem for them (they didn't say that<br>
the<br>
number<br>
part<br>
is optional). Sorry I can't help you out more at this<br>
time.<br>
<br>
Regards,<br>
Andrew<br>
<br>
</blockquote>
_______________________________________________<br>
Spce-user mailing list<br>
<a href="mailto:Spce-user@lists.sipwise.com" target="_blank">Spce-user@lists.sipwise.com</a><br>
<a href="https://lists.sipwise.com/listinfo/spce-user" rel="noreferrer" target="_blank">https://lists.sipwise.com/listinfo/spce-user</a><br>
</blockquote>
_______________________________________________<br>
Spce-user mailing list<br>
<a href="mailto:Spce-user@lists.sipwise.com" target="_blank">Spce-user@lists.sipwise.com</a><br>
<a href="https://lists.sipwise.com/listinfo/spce-user" rel="noreferrer" target="_blank">https://lists.sipwise.com/listinfo/spce-user</a><br>
</blockquote>
_______________________________________________<br>
Spce-user mailing list<br>
<a href="mailto:Spce-user@lists.sipwise.com" target="_blank">Spce-user@lists.sipwise.com</a><br>
<a href="https://lists.sipwise.com/listinfo/spce-user" rel="noreferrer" target="_blank">https://lists.sipwise.com/listinfo/spce-user</a><br>
<br>
</blockquote>
_______________________________________________<br>
Spce-user mailing list<br>
<a href="mailto:Spce-user@lists.sipwise.com" target="_blank">Spce-user@lists.sipwise.com</a><br>
<a href="https://lists.sipwise.com/listinfo/spce-user" rel="noreferrer" target="_blank">https://lists.sipwise.com/listinfo/spce-user</a><br>
</blockquote>
_______________________________________________<br>
Spce-user mailing list<br>
<a href="mailto:Spce-user@lists.sipwise.com" target="_blank">Spce-user@lists.sipwise.com</a><br>
<a href="https://lists.sipwise.com/listinfo/spce-user" rel="noreferrer" target="_blank">https://lists.sipwise.com/listinfo/spce-user</a><br>
</blockquote>
_______________________________________________<br>
Spce-user mailing list<br>
<a href="mailto:Spce-user@lists.sipwise.com" target="_blank">Spce-user@lists.sipwise.com</a><br>
<a href="https://lists.sipwise.com/listinfo/spce-user" rel="noreferrer" target="_blank">https://lists.sipwise.com/listinfo/spce-user</a><br>
</blockquote></blockquote></blockquote></blockquote></blockquote></blockquote></blockquote>
_______________________________________________<br>
Spce-user mailing list<br>
<a href="mailto:Spce-user@lists.sipwise.com" target="_blank">Spce-user@lists.sipwise.com</a><br>
<a href="https://lists.sipwise.com/listinfo/spce-user" rel="noreferrer" target="_blank">https://lists.sipwise.com/listinfo/spce-user</a><br>
</blockquote>
_______________________________________________<br>
Spce-user mailing list<br>
<a href="mailto:Spce-user@lists.sipwise.com" target="_blank">Spce-user@lists.sipwise.com</a><br>
<a href="https://lists.sipwise.com/listinfo/spce-user" rel="noreferrer" target="_blank">https://lists.sipwise.com/listinfo/spce-user</a><br>
</blockquote>
_______________________________________________<br>
Spce-user mailing list<br>
<a href="mailto:Spce-user@lists.sipwise.com" target="_blank">Spce-user@lists.sipwise.com</a><br>
<a href="https://lists.sipwise.com/listinfo/spce-user" rel="noreferrer" target="_blank">https://lists.sipwise.com/listinfo/spce-user</a><br>
<br>
</blockquote>
_______________________________________________<br>
Spce-user mailing list<br>
<a href="mailto:Spce-user@lists.sipwise.com" target="_blank">Spce-user@lists.sipwise.com</a><br>
<a href="https://lists.sipwise.com/listinfo/spce-user" rel="noreferrer" target="_blank">https://lists.sipwise.com/listinfo/spce-user</a><br>
</blockquote>
_______________________________________________<br>
Spce-user mailing list<br>
<a href="mailto:Spce-user@lists.sipwise.com" target="_blank">Spce-user@lists.sipwise.com</a><br>
<a href="https://lists.sipwise.com/listinfo/spce-user" rel="noreferrer" target="_blank">https://lists.sipwise.com/listinfo/spce-user</a><br>
<br>
</blockquote>
_______________________________________________<br>
Spce-user mailing list<br>
<a href="mailto:Spce-user@lists.sipwise.com" target="_blank">Spce-user@lists.sipwise.com</a><br>
<a href="https://lists.sipwise.com/listinfo/spce-user" rel="noreferrer" target="_blank">https://lists.sipwise.com/listinfo/spce-user</a></blockquote>
<br>_______________________________________________<br>
Spce-user mailing list<br>
<a href="mailto:Spce-user@lists.sipwise.com">Spce-user@lists.sipwise.com</a><br>
<a href="https://lists.sipwise.com/listinfo/spce-user" rel="noreferrer" target="_blank">https://lists.sipwise.com/listinfo/spce-user</a><br>
<br></blockquote></div><br></div></div>