[Spce-user] No rewrite on T.38 INVITE

Sun Aug 16 09:36:45 EDT 2015

I see where things are going bad.
The MP112 sends an ACK in response to the 200 OK and in the ACK the to 
address is 
sip:ngcp-lb at 87.239.101.193:5060;ngcpct=7369703a3132372e302e302e313a353038303b707278726f7574653d31 
SIP/2.0.
The forwarded ACK of the SPCE is then send with a Contact 
<sip:ngcp-lb at 87.239.101.193:5060;ngcpct=7369703a3132372e302e302e313a35303830>.
Then the RE-INVITE has a destination of ngcp-lb which is not a 
subscriber ofcourse.

Tristan

On 2015-08-15 20:01, Tristan Delsol wrote:
> In the previous mail I said that I changed it, to not send the +
> anymore but still the same issue.
>  I find it a weird one also.
>  Maybe some more lowlevel debugging would show where its failing. But
> I'm no expert on the spce.
> 
> On August 15, 2015 7:16:22 PM GMT+02:00, Matthew Ogden
> <matthew at tenacit.net> wrote:
> 
>> Hi Tristan,
>> 
>> I want to say, its the other way around compared to your suspicion.
>> Its sending the Re-INVITE to you without a +
>> 
>> There are others on this list who are probably more skilled at
>> looking at the issue.
>> 
>> The proxy log seems to show no knowledge of the re-invite, make the
>> LB log has some more info for you?
>> 
>> On 15 August 2015 at 17:41, Tristan Delsol <tdelsol at qfast.nl> wrote:
>> Indeed. I got it off to quick.
>> I agree about using t.38 but I need to support the fallback for the
>> interconnect,
>> that's why I'm testing this.
>> 
>> Attached the full pcap.
>> 
>> Tristan
>> 
>> On 2015-08-15 16:55, Matthew Ogden wrote:
>> Hi
>> 
>> Possibly some data is missing? I dont see the reinvite, or any BYEs
>> to
>> end the call.
>> 
>> Also, if your upstream supports T38, its a no-brainer to use it, it
>> will be far more reliable. (But lets first focus on getting the
>> whole
>> call).
>> 
>> See here:
>> 
>> On 15 August 2015 at 15:49, Tristan Delsol <tdelsol at qfast.nl>
>> wrote:
>> 
>> Matthew,
>> 
>> Find attached, pcap of the setup.
>> I'm using an audiocodes MP112 and have T.38 disabled on the MP112
>> as I want it to fallback to passthrough.
>> 
>> Thanks
>> 
>> On 2015-08-15 14:57, Matthew Ogden wrote:
>> 
>> might be easier with a pcap of the call to see whats going on
>> 
>> On 15 August 2015 at 14:09, Tristan Delsol <tdelsol at qfast.nl>
>> wrote:
>> 
>> Well I removed the + sign for the outgoing fax but that doesn't
>> seem
>> to be the issue.
>> For some reason the RE-INVITE for T.38 does not get through.
>> 
>> Here the ngcp-logs for the setup.
>> 
>> (spce|kamailio-proxy.log) Aug 15 14:00:13 [6519]: NOTICE: <script>:
>> Call to SIP Peering - R=sip:31306665648 at 87.239.101.193;user=phone
>> ID=1729768205212000211650 at 192.168.111.25
>> (spce|kamailio-proxy.log) Aug 15 14:00:13 [6519]: NOTICE: <script>:
>> Load gws matching calling part 'sip:31756418049 at 87.239.101.193' and
>> called user '31306665648' and called part
>> 'sip:31306665648 at 87.239.101.193;user=phone' -
>> R=sip:31306665648 at 87.239.101.193;user=phone
>> ID=1729768205212000211650 at 192.168.111.25
>> (spce|kamailio-proxy.log) Aug 15 14:00:13 [6519]: NOTICE: <script>:
>> Setting acc source-leg for uuid
>> 'c453f9be-74d4-47e6-931d-a18f29fef700':
>> 
>> 
> 'c453f9be-74d4-47e6-931d-a18f29fef700|31756418049|87.239.101.193|31756418049|||7|||0|call|192.168.111.25|1439640013.867047|||||||||||'
>> 
>> - R=sip:31306665648 at ims.imscore.net
>> ID=1729768205212000211650 at 192.168.111.25
>> (spce|kamailio-proxy.log) Aug 15 14:00:13 [6519]: NOTICE: <script>:
>> Setting acc destination-leg for uuid '0':
>> '0|||0|0306665648|0|31306665648|ims.imscore.net [1] [1]
>> 
>> [2]|31306665648|87.239.101.193|2|||||||||||' -
>> 
>> R=sip:31306665648 at ims.imscore.net
>> ID=1729768205212000211650 at 192.168.111.25
>> (spce|kamailio-proxy.log) Aug 15 14:00:13 [6519]: ERROR: dispatcher
>> [dispatch.c:1247]: ds_get_index(): destination set [50] not found
>> (spce|kamailio-proxy.log) Aug 15 14:00:13 [6519]: ERROR: dispatcher
>> [dispatch.c:1625]: ds_select_dst(): destination set [50] not found
>> (spce|kamailio-proxy.log) Aug 15 14:00:13 [6519]: WARNING:
>> <script>: Failed to load dispatcher entries for lb using did '50',
>> use first lb found in network.yml -
>> R=sip:31306665648 at ims.imscore.net
>> ID=1729768205212000211650 at 192.168.111.25
>> (spce|kamailio-proxy.log) Aug 15 14:00:13 [6519]: NOTICE: <script>:
>> Setting caller_cli_userprov/caller_domain_userprov
>> '31756418049 at 192.168.111.25' for upn -
>> R=sip:31306665648 at ims.imscore.net
>> ID=1729768205212000211650 at 192.168.111.25
>> (spce|kamailio-proxy.log) Aug 15 14:00:13 [6519]: NOTICE: <script>:
>> Setting From to '<sip:31756418049 at 192.168.111.25>' -
>> R=sip:31306665648 at ims.imscore.net
>> ID=1729768205212000211650 at 192.168.111.25
>> (spce|kamailio-proxy.log) Aug 15 14:00:13 [6519]: NOTICE: <script>:
>> Setting caller_cli_netprov/caller_domain_netprov
>> '31756418049 at 87.239.101.193' for npn -
>> R=sip:31306665648 at ims.imscore.net
>> ID=1729768205212000211650 at 192.168.111.25
>> (spce|kamailio-proxy.log) Aug 15 14:00:13 [6519]: NOTICE: <script>:
>> Setting PAI to '<sip:31756418049 at 87.239.101.193>' -
>> R=sip:31306665648 at ims.imscore.net
>> ID=1729768205212000211650 at 192.168.111.25
>> (spce|kamailio-proxy.log) Aug 15 14:00:13 [6519]: NOTICE: <script>:
>> Rewriting called party '31306665648' to '+31306665648 [2] [2] [3]'
>> -
>> R=sip:31306665648 at ims.imscore.net
>> ID=1729768205212000211650 at 192.168.111.25
>> (spce|kamailio-proxy.log) Aug 15 14:00:13 [6519]: NOTICE: <script>:
>> Setting P-Called-Party-ID '<sip:+31306665648 at ims.imscore.net>' -
>> R=sip:+31306665648 at ims.imscore.net
>> ID=1729768205212000211650 at 192.168.111.25
>> (spce|kamailio-proxy.log) Aug 15 14:00:13 [6519]: NOTICE: <script>:
>> Setting 'sip:139.156.126.49:5060 [3] [3] [4]' taken from D-URI as
>> next
>> hop
>> after lb for PSTN call - R=sip:+31306665648 at ims.imscore.net
>> ID=1729768205212000211650 at 192.168.111.25
>> (spce|kamailio-proxy.log) Aug 15 14:00:13 [6519]: NOTICE: <script>:
>> Appending P-D-URI
>> 
>> 
> 'sip:127.0.0.1:5060;received='sip:139.156.126.49:5060;lr;transport=udp''
>> - R=sip:+31306665648 at ims.imscore.net
>> ID=1729768205212000211650 at 192.168.111.25
>> (spce|kamailio-proxy.log) Aug 15 14:00:13 [6519]: NOTICE: <script>:
>> Forcing request via B2BUA 'sip:127.0.0.1:5080 [4] [4] [5]' -
>> R=sip:+31306665648 at ims.imscore.net
>> ID=1729768205212000211650 at 192.168.111.25
>> (spce|kamailio-proxy.log) Aug 15 14:00:13 [6519]: NOTICE: <script>:
>> Request leaving server, D-URI='sip:127.0.0.1:5080 [4] [4] [5]' -
>> R=sip:+31306665648 at ims.imscore.net
>> ID=1729768205212000211650 at 192.168.111.25
>> (spce|kamailio-proxy.log) Aug 15 14:00:13 [6521]: NOTICE: <script>:
>> NAT-Reply - S=100 - Connecting M=INVITE IP=192.168.111.25:5060 [5]
>> [5]
>> [6]
>> (127.0.0.1:5080 [4] [4] [5])
>> ID=1729768205212000211650 at 192.168.111.25
>> (spce|kamailio-proxy.log) Aug 15 14:00:14 [6518]: NOTICE: <script>:
>> NAT-Reply - S=183 - Session Progress M=INVITE
>> IP=192.168.111.25:5060 [5] [5]
>> [6] (127.0.0.1:5080 [4] [4] [5])
>> ID=1729768205212000211650 at 192.168.111.25
>> (spce|kamailio-proxy.log) Aug 15 14:00:21 [6523]: NOTICE: <script>:
>> NAT-Reply - S=200 - OK M=INVITE IP=192.168.111.25:5060 [5] [5] [6]
>> (127.0.0.1:5080 [4] [4] [5])
>> ID=1729768205212000211650 at 192.168.111.25
>> (spce|kamailio-proxy.log) Aug 15 14:00:21 [6524]: NOTICE: <script>:
>> New request on proxy - M=ACK R=sip:127.0.0.1:5080;prxroute=1
>> F=sip:31756418049 at 192.168.111.25
>> T=sip:0306665648 at 87.239.101.193;user=phone IP=192.168.111.25:5060
>> [5]
>> [5]
>> [6] (127.0.0.1:5060 [6] [6] [7])
>> ID=1729768205212000211650 at 192.168.111.25
>> (spce|kamailio-proxy.log) Aug 15 14:00:27 [6522]: NOTICE: <script>:
>> New request on proxy - M=INVITE
>> 
>> 
> R=sip:127.0.0.1;r2=on;lr=on;ftag=434A31C2-55CF29CD000D42FC-5A3BD700;ngcplb=yes
>> F=sip:+31306665648 at ims.imscore.net T=sip:31756418049 at 192.168.111.25
>> IP=139.156.126.49:5060 [3] [3] [4] (127.0.0.1:5060 [6] [6] [7])
>> ID=1729768205212000211650 at 192.168.111.25_b2b-1
>> (spce|kamailio-proxy.log) Aug 15 14:00:27 [6522]: NOTICE: <script>:
>> Call from PSTN -
>> 
>> 
> R=sip:127.0.0.1;r2=on;lr=on;ftag=434A31C2-55CF29CD000D42FC-5A3BD700;ngcplb=yes
>> ID=1729768205212000211650 at 192.168.111.25_b2b-1
>> (spce|kamailio-proxy.log) Aug 15 14:00:27 [6522]: NOTICE: <script>:
>> User-Provided CLI '+31306665648 [2] [2] [3]' taken from From-User -
>> 
>> 
> R=sip:127.0.0.1;r2=on;lr=on;ftag=434A31C2-55CF29CD000D42FC-5A3BD700;ngcplb=yes
>> ID=1729768205212000211650 at 192.168.111.25_b2b-1
>> (spce|kamailio-proxy.log) Aug 15 14:00:27 [6522]: NOTICE: <script>:
>> Network-Provided CLI '+31306665648 [2] [2] [3]' taken from
>> From-User -
>> 
>> 
> R=sip:127.0.0.1;r2=on;lr=on;ftag=434A31C2-55CF29CD000D42FC-5A3BD700;ngcplb=yes
>> ID=1729768205212000211650 at 192.168.111.25_b2b-1
>> (spce|kamailio-proxy.log) Aug 15 14:00:27 [6522]: NOTICE: <script>:
>> Setting '+31306665648 at ims.imscore.net' as initiating user-provided
>> CLI -
>> 
>> 
> R=sip:127.0.0.1;r2=on;lr=on;ftag=434A31C2-55CF29CD000D42FC-5A3BD700;ngcplb=yes
>> ID=1729768205212000211650 at 192.168.111.25_b2b-1
>> (spce|kamailio-proxy.log) Aug 15 14:00:27 [6522]: NOTICE: <script>:
>> Setting '+31306665648 at ims.imscore.net' as initiating
>> network-provided CLI -
>> 
>> 
> R=sip:127.0.0.1;r2=on;lr=on;ftag=434A31C2-55CF29CD000D42FC-5A3BD700;ngcplb=yes
>> ID=1729768205212000211650 at 192.168.111.25_b2b-1
>> (spce|kamailio-proxy.log) Aug 15 14:00:27 [6522]: NOTICE: <script>:
>> Callee is not local -
>> 
>> 
> R=sip:127.0.0.1;r2=on;lr=on;ftag=434A31C2-55CF29CD000D42FC-5A3BD700;ngcplb=yes
>> ID=1729768205212000211650 at 192.168.111.25_b2b-1
>> (spce|kamailio-proxy.log) Aug 15 14:00:27 [6522]: NOTICE: <script>:
>> Call to unknown user -
>> 
>> 
> R=sip:127.0.0.1;r2=on;lr=on;ftag=434A31C2-55CF29CD000D42FC-5A3BD700;ngcplb=yes
>> ID=1729768205212000211650 at 192.168.111.25_b2b-1
>> (spce|kamailio-proxy.log) Aug 15 14:00:27 [6522]: NOTICE: <script>:
>> Setting acc source-leg for uuid '0': '0|+31306665648 [2] [2]
>> 
>> [3]|139.156.126.49|+31306665648 [2]
>> [2]|||0|||0|call|139.156.126.49|1439640027.462624|||||||||||'
>> -
>> 
>> 
> R=sip:127.0.0.1;r2=on;lr=on;ftag=434A31C2-55CF29CD000D42FC-5A3BD700;ngcplb=yes
>> ID=1729768205212000211650 at 192.168.111.25_b2b-1
>> (spce|kamailio-proxy.log) Aug 15 14:00:27 [6522]: NOTICE: <script>:
>> Setting acc destination-leg for uuid '0':
>> '0|||0|<null>|0|<null>|127.0.0.1|<null>|127.0.0.1|2|||||||||||' -
>> 
>> 
> R=sip:127.0.0.1;r2=on;lr=on;ftag=434A31C2-55CF29CD000D42FC-5A3BD700;ngcplb=yes
>> ID=1729768205212000211650 at 192.168.111.25_b2b-1
>> (spce|kamailio-proxy.log) Aug 15 14:00:27 [6519]: NOTICE: <script>:
>> New request on proxy - M=ACK
>> 
>> 
> R=sip:ngcp-lb;tgrp=9752;trunk-context=ipic.imscore.net at 87.239.101.193:5060;ngcpct=7369703a3132372e302e302e313a35303830
>> F=sip:+31306665648 at ims.imscore.net T=sip:31756418049 at 192.168.111.25
>> IP=139.156.126.49:5060 [3] [3] [4] (127.0.0.1:5060 [6] [6] [7])
>> ID=1729768205212000211650 at 192.168.111.25_b2b-1
>> (spce|kamailio-proxy.log) Aug 15 14:00:27 [6521]: NOTICE: <script>:
>> New request on proxy - M=BYE
>> 
>> 
> R=sip:127.0.0.1;r2=on;lr=on;ftag=434A31C2-55CF29CD000D42FC-5A3BD700;ngcplb=yes
>> F=sip:+31306665648 at ims.imscore.net T=sip:31756418049 at 192.168.111.25
>> IP=139.156.126.49:5060 [3] [3] [4] (127.0.0.1:5060 [6] [6] [7])
>> ID=1729768205212000211650 at 192.168.111.25_b2b-1
>> (spce|kamailio-proxy.log) Aug 15 14:00:31 [6523]: NOTICE: <script>:
>> New request on proxy - M=BYE
>> 
>> 
> R=sip:127.0.0.1;r2=on;lr=on;ftag=434A31C2-55CF29CD000D42FC-5A3BD700;ngcplb=yes
>> F=sip:+31306665648 at ims.imscore.net T=sip:31756418049 at 192.168.111.25
>> IP=139.156.126.49:5060 [3] [3] [4] (127.0.0.1:5060 [6] [6] [7])
>> ID=1729768205212000211650 at 192.168.111.25_b2b-1
>> (spce|kamailio-proxy.log) Aug 15 14:00:35 [6520]: NOTICE: <script>:
>> New request on proxy - M=BYE
>> 
>> 
> R=sip:127.0.0.1;r2=on;lr=on;ftag=434A31C2-55CF29CD000D42FC-5A3BD700;ngcplb=yes
>> F=sip:+31306665648 at ims.imscore.net T=sip:31756418049 at 192.168.111.25
>> IP=139.156.126.49:5060 [3] [3] [4] (127.0.0.1:5060 [6] [6] [7])
>> ID=1729768205212000211650 at 192.168.111.25_b2b-1
>> (spce|kamailio-proxy.log) Aug 15 14:00:37 [6522]: NOTICE: <script>:
>> New request on proxy - M=BYE R=sip:127.0.0.1:5080;prxroute=1
>> F=sip:31756418049 at 192.168.111.25
>> T=sip:0306665648 at 87.239.101.193;user=phone IP=192.168.111.25:5060
>> [5]
>> [5]
>> [6] (127.0.0.1:5060 [6] [6] [7])
>> ID=1729768205212000211650 at 192.168.111.25
>> (spce|kamailio-proxy.log) Aug 15 14:00:37 [6519]: NOTICE: <script>:
>> NAT-Reply - S=200 - OK M=BYE IP=192.168.111.25:5060 [5] [5] [6]
>> (127.0.0.1:5080 [4] [4] [5])
>> ID=1729768205212000211650 at 192.168.111.25
>> (spce|kamailio-proxy.log) Aug 15 14:00:39 [6521]: NOTICE: <script>:
>> New request on proxy - M=BYE
>> 
>> 
> R=sip:127.0.0.1;r2=on;lr=on;ftag=434A31C2-55CF29CD000D42FC-5A3BD700;ngcplb=yes
>> F=sip:+31306665648 at ims.imscore.net T=sip:31756418049 at 192.168.111.25
>> IP=139.156.126.49:5060 [3] [3] [4] (127.0.0.1:5060 [6] [6] [7])
>> ID=1729768205212000211650 at 192.168.111.25_b2b-1
>> (spce|kamailio-proxy.log) Aug 15 14:00:43 [6524]: NOTICE: <script>:
>> New request on proxy - M=BYE
>> 
>> 
> R=sip:127.0.0.1;r2=on;lr=on;ftag=434A31C2-55CF29CD000D42FC-5A3BD700;ngcplb=yes
>> F=sip:+31306665648 at ims.imscore.net T=sip:31756418049 at 192.168.111.25
>> IP=139.156.126.49:5060 [3] [3] [4] (127.0.0.1:5060 [6] [6] [7])
>> ID=1729768205212000211650 at 192.168.111.25_b2b-1
>> (spce|kamailio-proxy.log) Aug 15 14:00:47 [6523]: NOTICE: <script>:
>> New request on proxy - M=BYE
>> 
>> 
> R=sip:127.0.0.1;r2=on;lr=on;ftag=434A31C2-55CF29CD000D42FC-5A3BD700;ngcplb=yes
>> F=sip:+31306665648 at ims.imscore.net T=sip:31756418049 at 192.168.111.25
>> IP=139.156.126.49:5060 [3] [3] [4] (127.0.0.1:5060 [6] [6] [7])
>> ID=1729768205212000211650 at 192.168.111.25_b2b-1
>> (spce|kamailio-proxy.log) Aug 15 14:00:51 [6517]: NOTICE: <script>:
>> New request on proxy - M=BYE
>> 
>> 
> R=sip:127.0.0.1;r2=on;lr=on;ftag=434A31C2-55CF29CD000D42FC-5A3BD700;ngcplb=yes
>> F=sip:+31306665648 at ims.imscore.net T=sip:31756418049 at 192.168.111.25
>> IP=139.156.126.49:5060 [3] [3] [4] (127.0.0.1:5060 [6] [6] [7])
>> 
>> ID=1729768205212000211650 at 192.168.111.25_b2b-1
>> 
>> Tristan
>> 
>> On 2015-08-14 10:55, Tristan Delsol wrote:
>> 
>> Hi All,
>> 
>> I'm currently testing an interconnect with a telco and ran in to
>> an
>> issue with faxing.
>> I have two SIP trunks to the telco. One for incoming calls and
>> for
>> outgoing calls.
>> I have rewrite rule sets from removing + sign for incoming calls
>> and
>> rewrite rule sets for adding + sign for outgoing calls
>> 
>> When I start a fax from behind the SPCE out to the telco
>> everything
>> goes normal, until I get an INVITE from the telco to switch to
>> T.38.
>> The INVITE comes in but no rewrite is done on the number which
>> leaves
>> the + sign in front of the e164 number and SPCE doesn't recognize
>> as a
>> subscriber so the whole fax is cancelled.
>> 
>> Any idea how I can solve this one?
>> 
>> Thanks,
>> Tristan
>> _______________________________________________
>> Spce-user mailing list
>> Spce-user at lists.sipwise.com
>> https://lists.sipwise.com/listinfo/spce-user [7] [7] [1]
>> _______________________________________________
>> Spce-user mailing list
>> Spce-user at lists.sipwise.com
>> https://lists.sipwise.com/listinfo/spce-user [7] [7] [1]
>> 
>> --
>> 
>> MATTHEW OGDEN
>> 
>> Management
>> 
>> TenacIT
>> 
>> STRATEGIC IT CONSULTING • ADVANCED NETWORKING • VIRTUALISATION
>> 
>> CUSTOM DEVELOPMENT • HOSTING • SYSPRO SUPPORT • MS
>> LICENSING
>> 
>> National Tel: 041 10 10 100 | Cell: 084 205 4445 | Email:
>> matthew at tenacit.net
>> 
>> CT Tel: 021 201 0333 | Skype Name: matthew.ogden | Web:
>> http://www.tenacit.net [8] [8] [8]
>> 
>> Links:
>> ------
>> [1] https://lists.sipwise.com/listinfo/spce-user [7] [7]
>> [2] http://ims.imscore.net [1] [1]
>> [3] tel:%2B31306665648
>> [4] http://139.156.126.49:5060 [3] [3]
>> [5] http://127.0.0.1:5080 [4] [4]
>> [6] http://192.168.111.25:5060 [5] [5]
>> [7] http://127.0.0.1:5060 [6] [6]
>> [8] http://www.tenacit.net/ [9] [9]
>> 
>> --
>> 
>> MATTHEW OGDEN
>> 
>> Management
>> 
>> TenacIT
>> 
>> STRATEGIC IT CONSULTING • ADVANCED NETWORKING • VIRTUALISATION
>> 
>> CUSTOM DEVELOPMENT • HOSTING • SYSPRO SUPPORT • MS LICENSING
>> 
>> National Tel: 041 10 10 100 | Cell: 084 205 4445 | Email:
>> matthew at tenacit.net
>> 
>> CT Tel: 021 201 0333 | Skype Name: matthew.ogden | Web:
>> http://www.tenacit.net [8] [9]
>> 
>> Links:
>> ------
>> [1] http://ims.imscore.net [1]
>> [2] tel:%2B31306665648
>> [3] http://139.156.126.49:5060 [3]
>> [4] http://127.0.0.1:5080 [4]
>> [5] http://192.168.111.25:5060 [5]
>> [6] http://127.0.0.1:5060 [6]
>> [7] https://lists.sipwise.com/listinfo/spce-user [7]
>> [8] http://www.tenacit.net [8]
>> [9] http://www.tenacit.net/ [9]
> 
> --
> 
> MATTHEW OGDEN
> 
> Management
> 
> TenacIT
> 
> STRATEGIC IT CONSULTING • ADVANCED NETWORKING • VIRTUALISATION
> 
> CUSTOM DEVELOPMENT • HOSTING • SYSPRO SUPPORT  • MS LICENSING
> 
> National Tel: 041 10 10 100 | Cell: 084 205 4445 | Email:
> matthew at tenacit.net
> 
> CT Tel: 021 201 0333 | Skype Name: matthew.ogden | Web:
> http://www.tenacit.net [9]
> 
> 
> 
> Links:
> ------
> [1] http://ims.imscore.net
> [2] tel:%2B31306665648
> [3] http://139.156.126.49:5060
> [4] http://127.0.0.1:5080
> [5] http://192.168.111.25:5060
> [6] http://127.0.0.1:5060
> [7] https://lists.sipwise.com/listinfo/spce-user
> [8] http://www.tenacit.net
> [9] http://www.tenacit.net/
> 
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user