From alexander at schrego.com  Mon Feb  1 02:29:28 2016
From: alexander at schrego.com (Alexander Topolanek)
Date: Mon, 1 Feb 2016 08:29:28 +0100
Subject: [Spce-user] How to reset the invoice count
Message-ID: <56AF0958.1050904@schrego.com>

Hello,

Invoices generated by the web interface have an increasing serial 
number, If I need to change that serial number or reset it to start from 
1 how would I do that.
Can I truncate the table billing.invoices for that?

kind regards

-- 
Alexander Topolanek
System engineer



From vseva at sipwise.com  Mon Feb  1 04:27:31 2016
From: vseva at sipwise.com (Victor Seva)
Date: Mon, 1 Feb 2016 10:27:31 +0100
Subject: [Spce-user] New sip:provider CE mr4.2.1 is now available
In-Reply-To: <013701d15c76$b9618f50$2c24adf0$@telematica.at>
References: <56AB780C.8060705@sipwise.com>
 <013701d15c76$b9618f50$2c24adf0$@telematica.at>
Message-ID: <56AF2503.3040107@sipwise.com>

On 01/31/2016 11:28 PM, Matthias Hohl wrote:
> After starting the installation, the installation stops cause the directory ".ssh" is not available on the server.
> The ".ssh" directory must be created manually before I could run ngcp-upgrade again.


Thanks for your report!
-- 
Victor Seva
Software Engineer

Phone: +43(0)1 301 2029
Email: vseva at sipwise.com
Website: www.sipwise.com

Particulars according Austrian Companies Code paragraph 14
"Sipwise GmbH? - Europaring F15 ? 2345 Brunn am Gebirge
FN:305595f, Commercial Court Vienna, ATU64002206

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20160201/79fdc61a/attachment.asc>

From alutay at sipwise.com  Mon Feb  1 05:27:47 2016
From: alutay at sipwise.com (Alex Lutay)
Date: Mon, 1 Feb 2016 11:27:47 +0100
Subject: [Spce-user] Rings once, then disconnects!
In-Reply-To: <DB5PR06MB1557AB8F343FE2DD1C4AC44FBEDE0@DB5PR06MB1557.eurprd06.prod.outlook.com>
References: <DB5PR06MB1557AB8F343FE2DD1C4AC44FBEDE0@DB5PR06MB1557.eurprd06.prod.outlook.com>
Message-ID: <56AF3323.3090101@sipwise.com>

Dear William,

As I can see on picture SPCE received "500 - Server Internal Error"
from your Carrier, so there is nothing we can tell you here.

Please ask your Carrier about the reason of internal server error here.

On 02/01/2016 03:08 AM, William Hilsum wrote:
[...skipped...]
> I?ve tried to do diagnostics ? I selected both legs of the call and made
> a quick picture: http://i.imgur.com/PzJF0Y5.jpg
[...skipped...]
> Feb  1 02:55:45 masterpbx1 (local7.notice) proxy[3350]: NOTICE:
> <script>: NAT-Reply - S=500 - Server Internal Error M=INVITE
> IP=**MY-HOME-IP**:56805 (127.0.0.1:5080)
> ID=ZTdlYmYwY2I2MmExZThkYmY1MTIxZGJmOGQyOWQ4ZmM. UA='<null>'
[...skipped...]

-- 
Alex Lutay



From matthias.hohl at telematica.at  Mon Feb  1 05:38:44 2016
From: matthias.hohl at telematica.at (Matthias Hohl)
Date: Mon, 1 Feb 2016 11:38:44 +0100 (CET)
Subject: [Spce-user] Upgrade to 4.2.1 causes in a cronjob failure
Message-ID: <027e01d15cdc$b940fea0$2bc2fbe0$@telematica.at>

Hello,

 

I get this error per mail everytime when the fraud auto lock is running as
cron.

 

What does this mean? An how can I solve it?

 

Thanks.

 

 

 

 

Cron <root at spce> if /usr/sbin/ngcp-check_active -q; then
/usr/sbin/ngcp-fraud-auto-lock; fi

 

Smartmatch is experimental at /usr/share/perl5/Sipwise/Provisioning.pm line
1122.
Use of my $_ is experimental at /usr/share/perl5/Sipwise/Provisioning.pm
line 1146.
defined(@array) is deprecated at /usr/share/perl5/PDF/Reuse.pm line 993.
(Maybe you should just omit the defined()?)
defined(@array) is deprecated at /usr/share/perl5/PDF/Reuse.pm line 993.
(Maybe you should just omit the defined()?)
Smartmatch is experimental at
/usr/share/perl5/Sipwise/Provisioning/Voip/DB.pm line 748.
given is experimental at /usr/share/perl5/Sipwise/Provisioning/Voip.pm line
6629.
when is experimental at /usr/share/perl5/Sipwise/Provisioning/Voip.pm line
6630.
when is experimental at /usr/share/perl5/Sipwise/Provisioning/Voip.pm line
6634.
Smartmatch is experimental at /usr/share/perl5/Sipwise/Provisioning/Voip.pm
line 6992.
Smartmatch is experimental at /usr/share/perl5/Sipwise/Provisioning/Voip.pm
line 7047.
Smartmatch is experimental at /usr/share/perl5/Sipwise/Provisioning/Voip.pm
line 7236.
Smartmatch is experimental at /usr/share/perl5/Sipwise/Provisioning/Voip.pm
line 7236.
Smartmatch is experimental at /usr/share/perl5/Sipwise/Provisioning/Voip.pm
line 7240.
Smartmatch is experimental at /usr/share/perl5/Sipwise/Provisioning/Voip.pm
line 7240.
Smartmatch is experimental at /usr/share/perl5/Sipwise/Provisioning/Voip.pm
line 7244.
Smartmatch is experimental at /usr/share/perl5/Sipwise/Provisioning/Voip.pm
line 7244.
Smartmatch is experimental at /usr/share/perl5/Sipwise/Provisioning/Voip.pm
line 7248.
Smartmatch is experimental at /usr/share/perl5/Sipwise/Provisioning/Voip.pm
line 7248.
Smartmatch is experimental at /usr/share/perl5/Sipwise/Provisioning/Voip.pm
line 7252.
Smartmatch is experimental at /usr/share/perl5/Sipwise/Provisioning/Voip.pm
line 7252.
Use of my $_ is experimental at
/usr/share/perl5/Sipwise/Provisioning/Voip.pm line 7259.

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20160201/3b7a244f/attachment.html>

From vseva at sipwise.com  Mon Feb  1 06:03:54 2016
From: vseva at sipwise.com (Victor Seva)
Date: Mon, 1 Feb 2016 12:03:54 +0100
Subject: [Spce-user] New sip:provider CE mr4.2.1 is now available
In-Reply-To: <56AF2503.3040107@sipwise.com>
References: <56AB780C.8060705@sipwise.com>
 <013701d15c76$b9618f50$2c24adf0$@telematica.at>
 <56AF2503.3040107@sipwise.com>
Message-ID: <56AF3B9A.6000706@sipwise.com>

On 02/01/2016 10:27 AM, Victor Seva wrote:
> On 01/31/2016 11:28 PM, Matthias Hohl wrote:
>> After starting the installation, the installation stops cause the directory ".ssh" is not available on the server.
>> The ".ssh" directory must be created manually before I could run ngcp-upgrade again.
> 
> 
> Thanks for your report!

Fix released!

ngcp-support (0.3.1.2+0~mr4.2.1.2) unstable; urgency=medium

  [ Victor Seva ]
  * [acc3ed6] MT#17647 ngcp-support-access: assert ${HOME}/.ssh exists

  [ Sipwise Jenkins Builder ]

 -- Sipwise Jenkins Builder <jenkins at sipwise.com>  Mon, 01 Feb 2016
11:30:32 +0100

-- 
Victor Seva
Software Engineer

Phone: +43(0)1 301 2029
Email: vseva at sipwise.com
Website: www.sipwise.com

Particulars according Austrian Companies Code paragraph 14
"Sipwise GmbH? - Europaring F15 ? 2345 Brunn am Gebirge
FN:305595f, Commercial Court Vienna, ATU64002206

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20160201/3500160b/attachment.asc>

From William at ezpcltd.com  Mon Feb  1 06:37:56 2016
From: William at ezpcltd.com (William Hilsum)
Date: Mon, 1 Feb 2016 11:37:56 +0000
Subject: [Spce-user] Rings once, then disconnects!
In-Reply-To: <56AF3323.3090101@sipwise.com>
References: <DB5PR06MB1557AB8F343FE2DD1C4AC44FBEDE0@DB5PR06MB1557.eurprd06.prod.outlook.com>
 <56AF3323.3090101@sipwise.com>
Message-ID: <DB5PR06MB15571F52E939DC8818644634BEDE0@DB5PR06MB1557.eurprd06.prod.outlook.com>

Hi,

I've been working on this overnight and made a bit more progress... and, it is a weird one!

I saw the Sipwise Ios App and I thought I would give it a go...

I made calls fine without issue!

It looks like the issue is then related to the softphone (I was using 3CX) doing something dodgy and/or Sipwise not removing/changing the headers.

I'm really unsure how to proceed here, but, I am guessing I just have a lot of trial and error ahead of me.

William

-----Original Message-----
From: Spce-user [mailto:spce-user-bounces at lists.sipwise.com] On Behalf Of Alex Lutay
Sent: 01 February 2016 10:28
To: spce-user at lists.sipwise.com
Subject: Re: [Spce-user] Rings once, then disconnects!

Dear William,

As I can see on picture SPCE received "500 - Server Internal Error"
from your Carrier, so there is nothing we can tell you here.

Please ask your Carrier about the reason of internal server error here.

On 02/01/2016 03:08 AM, William Hilsum wrote:
[...skipped...]
> I've tried to do diagnostics - I selected both legs of the call and 
> made a quick picture: http://i.imgur.com/PzJF0Y5.jpg
[...skipped...]
> Feb  1 02:55:45 masterpbx1 (local7.notice) proxy[3350]: NOTICE:
> <script>: NAT-Reply - S=500 - Server Internal Error M=INVITE
> IP=**MY-HOME-IP**:56805 (127.0.0.1:5080) 
> ID=ZTdlYmYwY2I2MmExZThkYmY1MTIxZGJmOGQyOWQ4ZmM. UA='<null>'
[...skipped...]

--
Alex Lutay

_______________________________________________
Spce-user mailing list
Spce-user at lists.sipwise.com
https://lists.sipwise.com/listinfo/spce-user


From j.feugne at prisnets.ch  Mon Feb  1 08:41:08 2016
From: j.feugne at prisnets.ch (=?UTF-8?Q?Jephth=C3=A9_Feugn=C3=A9?=)
Date: Mon, 1 Feb 2016 14:41:08 +0100
Subject: [Spce-user] No sound with outbound call
In-Reply-To: <CAD7smbgDKAQGN=Kr6uksNGrS960RyO3rta7uxThMkOZsbxo1Dg@mail.gmail.com>
References: <abf698f63423a025abf6efeee49764d4@prisnets.ch>
 <CAD7smbgDKAQGN=Kr6uksNGrS960RyO3rta7uxThMkOZsbxo1Dg@mail.gmail.com>
Message-ID: <013701d15cf6$3502c820$9f085860$@prisnets.ch>

Hello Marco,

Sorry to come back to you so late with the information you ask related to my problem in subject.

Here is what I have with the command you gave me:

77.72.169.131 is my Voip provider that is Voicetrading

84.xxx.xxx.xxx My sipwise NGCP VM instance that I?ve just upgrade to 4.2.1

Still no way to have the destination phone ringing.

 

13:32:51.232177 IP 213.55.176.206.3357 > 84.xxx.xxx.xxx.5060: Flags [.], ack 1125, win 16931, options [nop,nop,TS val 15666394 ecr 5685786], length 0

13:32:51.240915 IP 77.72.169.131.5060 > 84.xxx.xxx.xxx.5060: SIP, length: 813

13:32:51.241693 IP 84.xxx.xxx.xxx.5060 > 77.72.169.131.5060: SIP, length: 642

13:32:51.242006 IP 84.xxx.xxx.xxx.5060 > 77.72.169.131.5060: SIP, length: 1436

13:32:51.261239 IP 77.72.169.131.5060 > 84.xxx.xxx.xxx.5060: SIP, length: 813

13:32:51.261911 IP 84.xxx.xxx.xxx.5060 > 77.72.169.131.5060: SIP, length: 642

13:32:51.268555 IP 84.xxx.xxx.xxx.5060 > 213.55.176.206.3357: Flags [P.], seq 1125:1882, ack 2333, win 1452, options [nop,nop,TS val 5685805 ecr 15666394], length 757

13:32:51.325414 IP 213.55.176.206.3357 > 84.xxx.xxx.xxx.5060: Flags [.], ack 1882, win 16931, options [nop,nop,TS val 15666402 ecr 5685805], length 0

13:32:51.392226 IP 213.55.176.206.3357 > 84.xxx.xxx.xxx.5060: Flags [P.], seq 2333:2615, ack 1882, win 16931, options [nop,nop,TS val 15666408 ecr 5685805], length 282

13:32:51.428393 IP 84.xxx.xxx.xxx.5060 > 213.55.176.206.3357: Flags [.], ack 2615, win 1452, options [nop,nop,TS val 5685845 ecr 15666408], length 0

13:32:51.492618 IP 213.55.176.206.3357 > 84.xxx.xxx.xxx.5060: Flags [P.], seq 2615:3508, ack 1882, win 16931, options [nop,nop,TS val 15666417 ecr 5685845], length 893

13:32:51.492632 IP 84.xxx.xxx.xxx.5060 > 213.55.176.206.3357: Flags [.], ack 3508, win 1452, options [nop,nop,TS val 5685861 ecr 15666417], length 0

13:32:51.493556 IP 84.xxx.xxx.xxx.5060 > 213.55.176.206.3357: Flags [P.], seq 1882:2202, ack 3508, win 1452, options [nop,nop,TS val 5685861 ecr 15666417], length 320

13:32:51.498452 IP 84.xxx.xxx.xxx.5060 > 213.55.176.206.3357: Flags [P.], seq 2202:2683, ack 3508, win 1452, options [nop,nop,TS val 5685862 ecr 15666417], length 481

13:32:51.545170 IP 213.55.176.206.3357 > 84.xxx.xxx.xxx.5060: Flags [.], ack 2202, win 16931, options [nop,nop,TS val 15666424 ecr 5685861], length 0

13:32:51.545172 IP 213.55.176.206.3357 > 84.xxx.xxx.xxx.5060: Flags [.], ack 2683, win 16931, options [nop,nop,TS val 15666424 ecr 5685862], length 0

13:32:51.632516 IP 213.55.176.206.3357 > 84.xxx.xxx.xxx.5060: Flags [P.], seq 3508:3831, ack 2683, win 16931, options [nop,nop,TS val 15666432 ecr 5685862], length 323

13:32:51.672526 IP 84.xxx.xxx.xxx.5060 > 213.55.176.206.3357: Flags [.], ack 3831, win 1452, options [nop,nop,TS val 5685906 ecr 15666432], length 0

13:32:51.740698 IP 213.55.176.206.3357 > 84.xxx.xxx.xxx.5060: Flags [P.], seq 3831:4946, ack 2683, win 16931, options [nop,nop,TS val 15666441 ecr 5685906], length 1115

13:32:51.740711 IP 84.xxx.xxx.xxx.5060 > 213.55.176.206.3357: Flags [.], ack 4946, win 1452, options [nop,nop,TS val 5685923 ecr 15666441], length 0

13:32:51.741405 IP 84.xxx.xxx.xxx.5060 > 213.55.176.206.3357: Flags [P.], seq 2683:3004, ack 4946, win 1452, options [nop,nop,TS val 5685923 ecr 15666441], length 321

13:32:51.765479 IP 84.xxx.xxx.xxx.5060 > 77.72.169.129.5060: SIP, length: 1236

13:32:51.784621 IP 77.72.169.131.5060 > 84.xxx.xxx.xxx.5060: SIP, length: 813

13:32:51.785055 IP 213.55.176.206.3357 > 84.xxx.xxx.xxx.5060: Flags [.], ack 3004, win 16931, options [nop,nop,TS val 15666448 ecr 5685923], length 0

13:32:51.785187 IP 84.xxx.xxx.xxx.5060 > 77.72.169.129.5060: SIP, length: 642

13:32:51.785920 IP 84.xxx.xxx.xxx.5060 > 77.72.169.129.5060: SIP, length: 1436

13:32:51.805014 IP 77.72.169.131.5060 > 84.xxx.xxx.xxx.5060: SIP, length: 813

13:32:51.805610 IP 84.xxx.xxx.xxx.5060 > 77.72.169.129.5060: SIP, length: 642

13:32:51.812729 IP 84.xxx.xxx.xxx.5060 > 213.55.176.206.3357: Flags [P.], seq 3004:3761, ack 4946, win 1452, options [nop,nop,TS val 5685941 ecr 15666448], length 757

13:32:51.865097 IP 213.55.176.206.3357 > 84.xxx.xxx.xxx.5060: Flags [.], ack 3761, win 16931, options [nop,nop,TS val 15666456 ecr 5685941], length 0

13:32:51.952443 IP 213.55.176.206.3357 > 84.xxx.xxx.xxx.5060: Flags [P.], seq 4946:5228, ack 3761, win 16931, options [nop,nop,TS val 15666463 ecr 5685941], length 282

13:32:51.992428 IP 84.xxx.xxx.xxx.5060 > 213.55.176.206.3357: Flags [.], ack 5228, win 1452, options [nop,nop,TS val 5685986 ecr 15666463], length 0

13:32:55.460605 IP 84.xxx.xxx.xxx.5060 > 10.3.30.42.5080: SIP, length: 822

13:32:55.461871 IP 10.3.30.42.5080 > 84.xxx.xxx.xxx.5060: SIP, length: 1078

13:32:59.675499 IP 41.216.232.18.5060 > 84.xxx.xxx.xxx.5060: SIP, length: 3

13:33:11.603205 IP 84.xxx.xxx.xxx.5060 > 213.55.176.206.3357: Flags [P.], seq 3761:4458, ack 5228, win 1452, options [nop,nop,TS val 5690888 ecr 15666463], length 697

13:33:11.645161 IP 213.55.176.206.3357 > 84.xxx.xxx.xxx.5060: Flags [.], ack 4458, win 16931, options [nop,nop,TS val 15668435 ecr 5690888], length 0

13:33:11.792554 IP 213.55.176.206.3357 > 84.xxx.xxx.xxx.5060: Flags [P.], seq 5228:5649, ack 4458, win 16931, options [nop,nop,TS val 15668448 ecr 5690888], length 421

13:33:11.792566 IP 84.xxx.xxx.xxx.5060 > 213.55.176.206.3357: Flags [.], ack 5649, win 1452, options [nop,nop,TS val 5690936 ecr 15668448], length 0

13:33:11.845101 IP 213.55.176.206.3357 > 84.xxx.xxx.xxx.5060: Flags [P.], seq 5649:5653, ack 4458, win 16931, options [nop,nop,TS val 15668454 ecr 5690936], length 4

13:33:11.845121 IP 84.xxx.xxx.xxx.5060 > 213.55.176.206.3357: Flags [.], ack 5653, win 1452, options [nop,nop,TS val 5690949 ecr 15668454], length 0

13:33:11.845151 IP 84.xxx.xxx.xxx.5060 > 213.55.176.206.3357: Flags [P.], seq 4458:4460, ack 5653, win 1452, options [nop,nop,TS val 5690949 ecr 15668454], length 2

13:33:11.900125 IP 213.55.176.206.3357 > 84.xxx.xxx.xxx.5060: Flags [.], ack 4460, win 16931, options [nop,nop,TS val 15668459 ecr 5690949], length 0

Thank you for helping

Regards,

Jeph

 

 

 

_____

Prisnets SA.

Office:   +41 22 501 70 70 / Fax : +41 22 501 70 67

Direct line : +41 22 508 72 70

Mobile:  +41 78 728 92 97

Email:      <mailto:j.feugne at prisnets.ch> j.feugne at prisnets.ch

Skype:   jephtech - Twitter:  @prisnet_ch

 <http://www.prisnets.ch/> http://www.prisnets.ch
Prisnet Telecommunications SA.  Route de Saint-Julien 184 A, 1228 Plan-Les-Ouates CH.

 

De : Marco Teixeira [mailto:admin at marcoteixeira.com] 
Envoy? : samedi, 2 janvier 2016 16:55
? : j.feugne at prisnets.ch
Cc : spce-user at lists.sipwise.com
Objet : Re: [Spce-user] No sound with outbound call

 

Hi,

 

On a security side note, don't forget to replace your, and your peer's, real IP address before posting on public mailling lists.

 

About your issue, Can you tell that INVITE packet size ?

Try to grep it out of a tcpdump:

"tcpdump port 5060 -nnn | grep YOUR_PEER_IP_HERE"

 

?(apt-get install tcpdump, if you need)?




 

---

Marco

---

 

 

On Sat, Jan 2, 2016 at 7:56 AM, <j.feugne at prisnets.ch <mailto:j.feugne at prisnets.ch> > wrote:

hello,
I'm just starting with Sipwise and I've setup a VM running version mr4.1.1 CE.
I have followed the instructions of the manual and all subscribers can call each others.
I also setup a sip peer to voicetrading, and here is waht I have withthe command line ngrep sip on my vm while placing and outband call:
NB, voicetrading is expecting for premium rate all number to be leading with 00000 (5 zero)

U  <http://84.253.60.150:5060> 84.253.60.150:5060 ->  <http://77.72.169.129:5060> 77.72.169.129:5060
  INVITE  <sip:0000041227312221 at 77.72.169.129:5060;transport=udp> sip:0000041227312221 at 77.72.169.129:5060;transport=udp SIP/2.0..Record-Route: < <sip:84.253.60.150;r2=on;%0b %20lr=on;ftag=2AF8D981-568781960002DB55-51003700;ngcplb=yes> sip:84.253.60.150;r2=on;
  lr=on;ftag=2AF8D981-568781960002DB55-51003700;ngcplb=yes>..Record-Route: < <sip:127.0.0.1;r2=on;lr=on;ftag=2AF8%0b %20D981-568781960002DB55-51003700;ngcplb=yes> sip:127.0.0.1;r2=on;lr=on;ftag=2AF8
  D981-568781960002DB55-51003700;ngcplb=yes>..Via: SIP/2.0/UDP 84.253.60.150;branch=z9hG4bK603f.7793d5b01aaccef
  36467f073399c00c2.0..Via: SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;branch=z9hG4bKVg2PkaeG;rport=5080..Fr
  om: < <mailto:sip%3A41225017070 at prisnets.adoovoice.com> sip:41225017070 at prisnets.adoovoice.com>;tag=2AF8D981-568781960002DB55-51003700..To: <sip:000004122731222
   <mailto:1 at 77.72.169.129> 1 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: scRGTP71RF5cdeju0O0qmw.._b2b-1..Max-Forwards: 69..Allow: INVITE,
  ACK, CANCEL, BYE, NOTIFY, MESSAGE, OPTIONS, SUBSCRIBE..Supported: replaces, norefersub, extended-refer, outbo
  und, path, X-cisco-serviceuri..P-Asserted-Identity: < <mailto:sip%3A41225017070 at prisnets.adoovoice.com> sip:41225017070 at prisnets.adoovoice.com>..Authorization:
  Digest username="", realm=" <http://prisnets.adoovoice.com> prisnets.adoovoice.com", nonce="4087963395", uri=" <mailto:sip%3A0000041227312221 at 77.72.169.1> sip:0000041227312221 at 77.72.169.1
  29:5060;transport=udp", response="c2fb4cd3a1235efd35e99190aedc45c2", algorithm=MD5..Content-Type: application
  /sdp..Content-Length: 322..Contact: < <mailto:sip%3Angcp-lb at 84.253.60.150> sip:ngcp-lb at 84.253.60.150:5060;ngcpct=7369703a3132372e302e302e313a353038
  30>....v=0..o=Zoiper 0 0 IN IP4 84.253.60.150..s=Zoiper..c=IN IP4 84.253.60.150..t=0 0..m=audio 32468 RTP/AVP
   3 0 8 18 101..a=rtpmap:3 GSM/8000..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:18 G729/8000..a=fmtp
  :18 annexb=no..a=rtpmap:101 telephone-event/8000..a=fmtp:101 0-16..a=sendrecv..a=rtcp:32469..a=direction:both
  ..


After almost 1 minute with no ringing sound nor answer the call hang up.

Can someone please help me point out where the problem is comming and how I can solve it?

Thank you

Jephth? Feugn?
_______________________________________________
Spce-user mailing list
Spce-user at lists.sipwise.com <mailto:Spce-user at lists.sipwise.com> 
https://lists.sipwise.com/listinfo/spce-user

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20160201/fd176adc/attachment.html>

From alexander at schrego.com  Mon Feb  1 08:46:47 2016
From: alexander at schrego.com (Alexander Topolanek)
Date: Mon, 1 Feb 2016 14:46:47 +0100
Subject: [Spce-user] upgrading to 4.2.1 fails on nonexistent old packages
Message-ID: <56AF61C7.7010307@schrego.com>

The uprade process fails when it tries to purge a nonexistant package:

2016-02-01 14:30:11: [23/36] Step '2.8/handle_apt_install_ngcp' has been 
executed already, continuing with the next step...
2016-02-01 14:30:11: [24/36] Running: 
/usr/share/ngcp-upgrade/steps/mr4.2/fix_purge_old_packages
Reading package lists... 0%
... Done^M
^MBuilding dependency tree...
... Done^M
E: Unable to locate package linux-headers-2.6-amd64
E: Couldn't find any package by regex 'linux-headers-2.6-amd64'
ERROR: the step 'mr4.2/fix_purge_old_packages' failed, upgrade aborted!
Please fix the root of the issue and restart 'ngcp-upgrade'

I*ve manually purged what can be purged and then commented out some 
lines in /usr/share/ngcp-upgrade/steps/mr4.2/fix_purge_old_packages.
After that the upgrade completed

kind regards

-- 
Alexander Topolanek
System engineer



From alutay at sipwise.com  Mon Feb  1 09:54:45 2016
From: alutay at sipwise.com (Alex Lutay)
Date: Mon, 1 Feb 2016 15:54:45 +0100
Subject: [Spce-user] upgrading to 4.2.1 fails on nonexistent old packages
In-Reply-To: <56AF61C7.7010307@schrego.com>
References: <56AF61C7.7010307@schrego.com>
Message-ID: <56AF71B5.7080702@sipwise.com>

Dear Alexander,

Thank you for the report here, internal ticket is MT#17665
should be fixed and hotfixed in mr4.2.1 shortly.

On 02/01/2016 02:46 PM, Alexander Topolanek wrote:
> The uprade process fails when it tries to purge a nonexistant package:
> 
> 2016-02-01 14:30:11: [23/36] Step '2.8/handle_apt_install_ngcp' has been
> executed already, continuing with the next step...
> 2016-02-01 14:30:11: [24/36] Running:
> /usr/share/ngcp-upgrade/steps/mr4.2/fix_purge_old_packages
> Reading package lists... 0%
> ... Done^M
> ^MBuilding dependency tree...
> ... Done^M
> E: Unable to locate package linux-headers-2.6-amd64
> E: Couldn't find any package by regex 'linux-headers-2.6-amd64'
> ERROR: the step 'mr4.2/fix_purge_old_packages' failed, upgrade aborted!
> Please fix the root of the issue and restart 'ngcp-upgrade'
> 
> I*ve manually purged what can be purged and then commented out some
> lines in /usr/share/ngcp-upgrade/steps/mr4.2/fix_purge_old_packages.
> After that the upgrade completed

-- 
Alex Lutay


From agranig at sipwise.com  Mon Feb  1 11:33:03 2016
From: agranig at sipwise.com (Andreas Granig)
Date: Mon, 1 Feb 2016 17:33:03 +0100
Subject: [Spce-user] Rings once, then disconnects!
In-Reply-To: <DB5PR06MB15571F52E939DC8818644634BEDE0@DB5PR06MB1557.eurprd06.prod.outlook.com>
References: <DB5PR06MB1557AB8F343FE2DD1C4AC44FBEDE0@DB5PR06MB1557.eurprd06.prod.outlook.com>
 <56AF3323.3090101@sipwise.com>
 <DB5PR06MB15571F52E939DC8818644634BEDE0@DB5PR06MB1557.eurprd06.prod.outlook.com>
Message-ID: <56AF88BF.1020002@sipwise.com>

Hi William,

Maybe your peering partner doesn't like the SDP body (specifically the
list of codecs) or something.

Try to limit the list of codecs on your 3CX to G711 as a start. Maybe
also the SIP message (the 500 from your carrier) contains a header
providing more details. From a SIP signaling perspective, there is a
B2BUA in the SPCE, so the outbound message should be *somewhat* equal
all the time no matter what client you're using, but then again the SDP
is passed through more or less as-is, which could be a starting point
for trouble-shooting.

Anyways, your carrier should be able to explain the reason why they're
sending a 500 reply.

Andreas

On 02/01/2016 12:37 PM, William Hilsum wrote:
> Hi,
> 
> I've been working on this overnight and made a bit more progress... and, it is a weird one!
> 
> I saw the Sipwise Ios App and I thought I would give it a go...
> 
> I made calls fine without issue!
> 
> It looks like the issue is then related to the softphone (I was using 3CX) doing something dodgy and/or Sipwise not removing/changing the headers.
> 
> I'm really unsure how to proceed here, but, I am guessing I just have a lot of trial and error ahead of me.
> 
> William
> 
> -----Original Message-----
> From: Spce-user [mailto:spce-user-bounces at lists.sipwise.com] On Behalf Of Alex Lutay
> Sent: 01 February 2016 10:28
> To: spce-user at lists.sipwise.com
> Subject: Re: [Spce-user] Rings once, then disconnects!
> 
> Dear William,
> 
> As I can see on picture SPCE received "500 - Server Internal Error"
> from your Carrier, so there is nothing we can tell you here.
> 
> Please ask your Carrier about the reason of internal server error here.
> 
> On 02/01/2016 03:08 AM, William Hilsum wrote:
> [...skipped...]
>> I've tried to do diagnostics - I selected both legs of the call and 
>> made a quick picture: http://i.imgur.com/PzJF0Y5.jpg
> [...skipped...]
>> Feb  1 02:55:45 masterpbx1 (local7.notice) proxy[3350]: NOTICE:
>> <script>: NAT-Reply - S=500 - Server Internal Error M=INVITE
>> IP=**MY-HOME-IP**:56805 (127.0.0.1:5080) 
>> ID=ZTdlYmYwY2I2MmExZThkYmY1MTIxZGJmOGQyOWQ4ZmM. UA='<null>'
> [...skipped...]
> 
> --
> Alex Lutay
> 
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
> 


From alutay at sipwise.com  Mon Feb  1 11:52:21 2016
From: alutay at sipwise.com (Alex Lutay)
Date: Mon, 1 Feb 2016 17:52:21 +0100
Subject: [Spce-user] upgrading to 4.2.1 fails on nonexistent old packages
In-Reply-To: <56AF71B5.7080702@sipwise.com>
References: <56AF61C7.7010307@schrego.com> <56AF71B5.7080702@sipwise.com>
Message-ID: <56AF8D45.6080307@sipwise.com>

Fixed.

The step "/usr/share/ngcp-upgrade/steps/mr4.2/fix_purge_old_packages"
should care about the list of installed packages before purging
unnecessary. Released hotfix for mr4.2.1 already.

On 02/01/2016 03:54 PM, Alex Lutay wrote:
> Thank you for the report here, internal ticket is MT#17665
> should be fixed and hotfixed in mr4.2.1 shortly.
> 
> On 02/01/2016 02:46 PM, Alexander Topolanek wrote:
>> The uprade process fails when it tries to purge a nonexistant package:
>>
>> 2016-02-01 14:30:11: [23/36] Step '2.8/handle_apt_install_ngcp' has been
>> executed already, continuing with the next step...
>> 2016-02-01 14:30:11: [24/36] Running:
>> /usr/share/ngcp-upgrade/steps/mr4.2/fix_purge_old_packages
>> Reading package lists... 0%
>> ... Done^M
>> ^MBuilding dependency tree...
>> ... Done^M
>> E: Unable to locate package linux-headers-2.6-amd64
>> E: Couldn't find any package by regex 'linux-headers-2.6-amd64'
>> ERROR: the step 'mr4.2/fix_purge_old_packages' failed, upgrade aborted!
>> Please fix the root of the issue and restart 'ngcp-upgrade'
>>
>> I*ve manually purged what can be purged and then commented out some
>> lines in /usr/share/ngcp-upgrade/steps/mr4.2/fix_purge_old_packages.
>> After that the upgrade completed

-- 
Alex Lutay


From William at ezpcltd.com  Mon Feb  1 19:03:15 2016
From: William at ezpcltd.com (William Hilsum)
Date: Tue, 2 Feb 2016 00:03:15 +0000
Subject: [Spce-user] Rings once, then disconnects!
In-Reply-To: <56AF88BF.1020002@sipwise.com>
References: <DB5PR06MB1557AB8F343FE2DD1C4AC44FBEDE0@DB5PR06MB1557.eurprd06.prod.outlook.com>
 <56AF3323.3090101@sipwise.com>
 <DB5PR06MB15571F52E939DC8818644634BEDE0@DB5PR06MB1557.eurprd06.prod.outlook.com>
 <56AF88BF.1020002@sipwise.com>
Message-ID: <DB5PR06MB15573307ABE294694E402401BEDF0@DB5PR06MB1557.eurprd06.prod.outlook.com>

Hi

This is now solved... The moment I unticked "allow video" on the softphone, it worked as expected. 

These additional lines in the "invite (SDP) packet" from Sipwise to the carrier platform break the connection:

m=video 32562 RTP/AVP 34
c=IN IP4 <PBX-IP>
a=rtpmap:34 H263/90000
a=fmtp:34 QCIF=1;CIF=1;SQCIF=1;CIF4=1
a=sendrecv
a=rtcp:32563
a=direction:both

so...

1. Is there anyway to disable voice/these headers being sent on a per carrier basis? 
2. Is this a case of the carrier not following spec? (should it be ignored if they don't support video?)
3. is it just a broken softphone? (if it is, this is the first problem I've had with it)
 Or something else?!

I still don't get how one single ring goes out! I can't say I am an expert at all on this, but, this is certainly a new one for me!

Thanks for your help Andreas and Alex.

William

-----Original Message-----
From: Spce-user [mailto:spce-user-bounces at lists.sipwise.com] On Behalf Of Andreas Granig
Sent: 01 February 2016 16:33
To: spce-user at lists.sipwise.com
Subject: Re: [Spce-user] Rings once, then disconnects!

Hi William,

Maybe your peering partner doesn't like the SDP body (specifically the list of codecs) or something.

Try to limit the list of codecs on your 3CX to G711 as a start. Maybe also the SIP message (the 500 from your carrier) contains a header providing more details. From a SIP signaling perspective, there is a B2BUA in the SPCE, so the outbound message should be *somewhat* equal all the time no matter what client you're using, but then again the SDP is passed through more or less as-is, which could be a starting point for trouble-shooting.

Anyways, your carrier should be able to explain the reason why they're sending a 500 reply.

Andreas

On 02/01/2016 12:37 PM, William Hilsum wrote:
> Hi,
> 
> I've been working on this overnight and made a bit more progress... and, it is a weird one!
> 
> I saw the Sipwise Ios App and I thought I would give it a go...
> 
> I made calls fine without issue!
> 
> It looks like the issue is then related to the softphone (I was using 3CX) doing something dodgy and/or Sipwise not removing/changing the headers.
> 
> I'm really unsure how to proceed here, but, I am guessing I just have a lot of trial and error ahead of me.
> 
> William
> 
> -----Original Message-----
> From: Spce-user [mailto:spce-user-bounces at lists.sipwise.com] On Behalf 
> Of Alex Lutay
> Sent: 01 February 2016 10:28
> To: spce-user at lists.sipwise.com
> Subject: Re: [Spce-user] Rings once, then disconnects!
> 
> Dear William,
> 
> As I can see on picture SPCE received "500 - Server Internal Error"
> from your Carrier, so there is nothing we can tell you here.
> 
> Please ask your Carrier about the reason of internal server error here.
> 
> On 02/01/2016 03:08 AM, William Hilsum wrote:
> [...skipped...]
>> I've tried to do diagnostics - I selected both legs of the call and 
>> made a quick picture: http://i.imgur.com/PzJF0Y5.jpg
> [...skipped...]
>> Feb  1 02:55:45 masterpbx1 (local7.notice) proxy[3350]: NOTICE:
>> <script>: NAT-Reply - S=500 - Server Internal Error M=INVITE
>> IP=**MY-HOME-IP**:56805 (127.0.0.1:5080) 
>> ID=ZTdlYmYwY2I2MmExZThkYmY1MTIxZGJmOGQyOWQ4ZmM. UA='<null>'
> [...skipped...]
> 
> --
> Alex Lutay
> 
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
> 
_______________________________________________
Spce-user mailing list
Spce-user at lists.sipwise.com
https://lists.sipwise.com/listinfo/spce-user


From alutay at sipwise.com  Tue Feb  2 03:24:19 2016
From: alutay at sipwise.com (Alex Lutay)
Date: Tue, 2 Feb 2016 09:24:19 +0100
Subject: [Spce-user] Rings once, then disconnects!
In-Reply-To: <DB5PR06MB15573307ABE294694E402401BEDF0@DB5PR06MB1557.eurprd06.prod.outlook.com>
References: <DB5PR06MB1557AB8F343FE2DD1C4AC44FBEDE0@DB5PR06MB1557.eurprd06.prod.outlook.com>
 <56AF3323.3090101@sipwise.com>
 <DB5PR06MB15571F52E939DC8818644634BEDE0@DB5PR06MB1557.eurprd06.prod.outlook.com>
 <56AF88BF.1020002@sipwise.com>
 <DB5PR06MB15573307ABE294694E402401BEDF0@DB5PR06MB1557.eurprd06.prod.outlook.com>
Message-ID: <56B067B3.4030606@sipwise.com>

Dear William,

Check incoming invite from softphone to Sipwise,
I am strongly believe you will find the same part there.

Sipwise doesn't change SDP part a lot, mainly it is replacing IP
(I believe you have replaced '<PBX-IP>' in SDP part manually, otherwise
it is an error) and limit list of codecs if necessary (turned off by
default).

You can also try to make a call from your softphone through your
Carrier directly and compare invite sent by softphone and Sipwise.

On the first look I do not see anything which can cause 500 on carrier
side here. Was the correct IPv4/IPv6 in <PBX-IP> ?

On 02/02/2016 01:03 AM, William Hilsum wrote:
> These additional lines in the "invite (SDP) packet" from Sipwise to the carrier platform break the connection:
> 
> m=video 32562 RTP/AVP 34
> c=IN IP4 <PBX-IP>
> a=rtpmap:34 H263/90000
> a=fmtp:34 QCIF=1;CIF=1;SQCIF=1;CIF4=1
> a=sendrecv
> a=rtcp:32563
> a=direction:both

-- 
Alexander Lutay
Head of Quality Assurance
Sipwise GmbH, Campus 21/Europaring F15
AT-2345 Brunn am Gebirge

Office: +43(0)13012036
Email: alutay at sipwise.com
Website: http://www.sipwise.com


From js at dacor.de  Tue Feb  2 07:52:17 2016
From: js at dacor.de (Julian Seifert)
Date: Tue, 2 Feb 2016 12:52:17 +0000
Subject: [Spce-user] trunk configuration
Message-ID: <07F41140D7F60847B76E3730B2ADCA6995F35C30@exchange.suecdacor.local>

Hi,

I'm currently working on building a sample configuration for a sip trunk
on which we can base our future trunk-setups.

I'm not 100% sure if I approach it correctly so please be gentle and what I actually want to know
is "how do you configure a sip trunk for a customer on sipwise the proper way?"

The pbx in our case is for example askozia which essentially is a asterisk
based solution afaik.
The askozia trunk configuration is quite straight forward and works with a variety of sip providers.

As we are now entering the business ourselves we'd like to configure our sipwise appropriately
to provide trunks.
We want to allow the trunkuser to dialout with DDIs (so "CLIP no screening")
In this example we want to provide the customer with a block of 100 numbers where 
there is a "centralnumber", commonly its the -0. 

I'm basing this example on the following number: 499561404956
We would like to be able to use 499561404956-0 to -99 as DDIs.

Currently I'm using a subscriber setup with the following specific settings.

- Primary number: 499561404956
- No Aliases
- extended dialing mode, send dialed number with extension (so calls using a DDI will reach the pbx)
- extension_in_npn (to set the ddi in outgoing calls as npn - if I understand the option properly)
- allowed_clis to "*" (or to 499561404956* to restrict the allowed CLIs to basenumber and DDIs?)
- e164_to_uri (unsure about this)
- would it be necessary to add all DDIs as aliases? (which is something we would like to avoid)

so - is this approach completely wrong? 
Is the regular approach to implement a trunk different?
Is there a "best practice" approach? 

Please share your knowledge/opinion/wisdom and if I used some terms in the wrong way please forgive my ignorance.

kind regards,

  Julian

From kim.philby at gmx.com  Tue Feb  2 15:44:09 2016
From: kim.philby at gmx.com (Kim Philby)
Date: Tue, 2 Feb 2016 21:44:09 +0100
Subject: [Spce-user] Manual delete of subscribers
Message-ID: <trinity-94d7bd6b-7ba1-4bb9-a692-aa20dc6dd8a2-1454445849737@3capp-mailcom-bs13>

An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20160202/572f5be3/attachment.html>

From me at nevian.org  Thu Feb  4 10:50:50 2016
From: me at nevian.org (Serge S. Yuriev)
Date: Thu, 4 Feb 2016 18:50:50 +0300
Subject: [Spce-user] Number cleanup
In-Reply-To: <9428FDFA-A738-42C3-AC1F-83092E021A9C@nevian.org>
References: <9428FDFA-A738-42C3-AC1F-83092E021A9C@nevian.org>
Message-ID: <56B3735A.3030201@nevian.org>

Hi,

Anyone?

On 21/01/16 13:39, Serge Yuriev wrote:
> Hello,
>
> I try to construct rewrite rule to remove any non-digits numbers from destination.
> In sed this is simple as /[^0-9]//g
> But I have no idea how to do it here :(

-- 
Serge S. Yuriev
Lead VoIP engineer



From j_e_vargas at live.com  Thu Feb  4 13:38:25 2016
From: j_e_vargas at live.com (Jose E. Vargas B.)
Date: Thu, 4 Feb 2016 10:38:25 -0800
Subject: [Spce-user] bruteforcing sip credentials attack
In-Reply-To: <07F41140D7F60847B76E3730B2ADCA6995F35C30@exchange.suecdacor.local>
References: <07F41140D7F60847B76E3730B2ADCA6995F35C30@exchange.suecdacor.local>
Message-ID: <BLU436-SMTP260D4059BD5534FFF946A8EBCD10@phx.gbl>

Hello,

Just have a quick and probably easy question for the SP community. I am experimenting with the server and keep getting the entire day the following attack:

016/02/04 19:20:16.673827 188.138.33.14:5071 -> yy.yy.yy.yy:5060
INVITE sip:901141445209482 at xx.xx.xx.xx SIP/2.0
To: 901141445209482<sip:901141445209482 at xx.xx.xx.xx>
From: 0550<sip:0550 at xx.xx.xx.xx>;tag=67a87716
Via: SIP/2.0/UDP 188.138.33.14:5071;branch=z9hG4bK-6f67d7e24b4ac8a25f3d76106be4cb74;rport
Call-ID: 6f67d7e24b4ac8a25f3d76106be4cb74
CSeq: 1 INVITE
Contact: <sip:0550 at 188.138.33.14:5071>
Max-Forwards: 70
Allow: INVITE, ACK, CANCEL, BYE
User-Agent: sipcli/v1.8
Content-Type: application/sdp
Content-Length: 281

v=0
o=sipcli-Session 691746334 738426574 IN IP4 188.138.33.14
s=sipcli
c=IN IP4 188.138.33.14
t=0 0
m=audio 5073 RTP/AVP 18 0 8 101
a=fmtp:101 0-15
a=rtpmap:18 G729/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=ptime:20
a=sendrecv


I guess it is a funny group/folk trying to get unauthorized access to the server by sending multiple SIP invites with different accounts and possible free phone calls ;)  The problem is that SPCE won?t detect it as his attempts are spared in time.  Would like to get your guidance about blocking the entire IP or domain to SCPCE server. Could you please comment on how you deal with this type of attack?

Jose 

PS: 
    BTW - making changes to config.yml (failed _auth)?) didn?t help  
    Offending IP:  188.138.33.14


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20160204/7587fc9a/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 1776 bytes
Desc: not available
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20160204/7587fc9a/attachment.p7s>

From rabs at dimension-virtual.com  Thu Feb  4 13:52:20 2016
From: rabs at dimension-virtual.com (=?utf-8?B?UmHDumw=?= Alexis Betancor Santana)
Date: Thu, 4 Feb 2016 19:52:20 +0100 (CET)
Subject: [Spce-user] bruteforcing sip credentials attack
In-Reply-To: <BLU436-SMTP260D4059BD5534FFF946A8EBCD10@phx.gbl>
References: <07F41140D7F60847B76E3730B2ADCA6995F35C30@exchange.suecdacor.local>
 <BLU436-SMTP260D4059BD5534FFF946A8EBCD10@phx.gbl>
Message-ID: <1047616280.316778.1454611940266.JavaMail.zimbra@dimension-virtual.com>

Easy ... 

291a292,298 
> ## filtering by UA : blacklist 
> if(is_method("REGISTER|INVITE|OPTIONS") && ($ua =~ "friendly-scanner" || $ua =~ "sipvicious" || $ua =~ "^sipcli.+")) 
> { 
> xlog("L_WARN", "Request rejected, malicious UA='$ua' from IP=$si - [% logreq_init -%]\n"); 
> exit; 
> } 
> 

Patch applied over the lb/kamailio.cfg.tt2 ... so create a .cusomtt.tt2 

> De: "Jose E. Vargas B." <j_e_vargas at live.com>
> Para: spce-user at lists.sipwise.com
> Enviados: Jueves, 4 de Febrero 2016 18:38:25
> Asunto: [Spce-user] bruteforcing sip credentials attack

> Hello,

> Just have a quick and probably easy question for the SP community. I am
> experimenting with the server and keep getting the entire day the following
> attack:

> 016/02/04 19:20:16.673827 188.138.33.14:5071 -> yy.yy.yy.yy:5060
> INVITE sip:901141445209482 at xx.xx.xx.xx SIP/2.0
> To: 901141445209482< sip:901141445209482 at xx.xx.xx.xx >
> From: 0550< sip:0550 at xx.xx.xx.xx >;tag=67a87716
> Via: SIP/2.0/UDP
> 188.138.33.14:5071;branch=z9hG4bK-6f67d7e24b4ac8a25f3d76106be4cb74;rport
> Call-ID: 6f67d7e24b4ac8a25f3d76106be4cb74
> CSeq: 1 INVITE
> Contact: < sip:0550 at 188.138.33.14:5071 >
> Max-Forwards: 70
> Allow: INVITE, ACK, CANCEL, BYE
> User-Agent: sipcli/v1.8
> Content-Type: application/sdp
> Content-Length: 281

> v=0
> o=sipcli-Session 691746334 738426574 IN IP4 188.138.33.14
> s=sipcli
> c=IN IP4 188.138.33.14
> t=0 0
> m=audio 5073 RTP/AVP 18 0 8 101
> a=fmtp:101 0-15
> a=rtpmap:18 G729/8000
> a=rtpmap:0 PCMU/8000
> a=rtpmap:8 PCMA/8000
> a=rtpmap:101 telephone-event/8000
> a=ptime:20
> a=sendrecv

> I guess it is a funny group/folk trying to get unauthorized access to the server
> by sending multiple SIP invites with different accounts and possible free phone
> calls ;) The problem is that SPCE won?t detect it as his attempts are spared in
> time. Would like to get your guidance about blocking the entire IP or domain to
> SCPCE server. Could you please comment on how you deal with this type of
> attack?

> Jose

> PS:
> BTW - making changes to config.yml (failed _auth)?) didn?t help
> Offending IP: 188.138.33.14

> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20160204/cdb504d7/attachment.html>

From dgrotti at sipwise.com  Thu Feb  4 14:03:52 2016
From: dgrotti at sipwise.com (Daniel Grotti)
Date: Thu, 04 Feb 2016 20:03:52 +0100
Subject: [Spce-user] bruteforcing sip credentials attack
In-Reply-To: <BLU436-SMTP260D4059BD5534FFF946A8EBCD10@phx.gbl>
Message-ID: <46812e2e-1a1d-4c80-847e-d34d4f4d544e@email.android.com>

Hi,
Hope it will help and maybe give you some hints:

https://www.linkedin.com/pulse/securing-your-ngcp-against-sip-attacks-daniel-grotti?forceNoSplash=true


Daniel


On Feb 4, 2016 7:38 PM, "Jose E. Vargas B." <j_e_vargas at live.com> wrote:
>
> Hello,
>
> Just have a quick and probably easy question for the SP community. I am experimenting with the server and keep getting the entire day the following attack:
>
> 016/02/04 19:20:16.673827 188.138.33.14:5071 -> yy.yy.yy.yy:5060
> INVITE sip:901141445209482 at xx.xx.xx.xx SIP/2.0
> To: 901141445209482<sip:901141445209482 at xx.xx.xx.xx>
> From: 0550<sip:0550 at xx.xx.xx.xx>;tag=67a87716
> Via: SIP/2.0/UDP 188.138.33.14:5071;branch=z9hG4bK-6f67d7e24b4ac8a25f3d76106be4cb74;rport
> Call-ID: 6f67d7e24b4ac8a25f3d76106be4cb74
> CSeq: 1 INVITE
> Contact: <sip:0550 at 188.138.33.14:5071>
> Max-Forwards: 70
> Allow: INVITE, ACK, CANCEL, BYE
> User-Agent: sipcli/v1.8
> Content-Type: application/sdp
> Content-Length: 281
>
> v=0
> o=sipcli-Session 691746334 738426574 IN IP4 188.138.33.14
> s=sipcli
> c=IN IP4 188.138.33.14
> t=0 0
> m=audio 5073 RTP/AVP 18 0 8 101
> a=fmtp:101 0-15
> a=rtpmap:18 G729/8000
> a=rtpmap:0 PCMU/8000
> a=rtpmap:8 PCMA/8000
> a=rtpmap:101 telephone-event/8000
> a=ptime:20
> a=sendrecv
>
>
> I guess it is a funny group/folk trying to get unauthorized access to the server by sending multiple SIP invites with different accounts and possible free phone calls ;) ?The problem is that SPCE won?t detect it as his attempts are spared in time. ?Would like to get your guidance about blocking the entire IP or domain to SCPCE server. Could you please comment on how you deal with this type of attack?
>
> Jose?
>
> PS:?
> ? ? BTW - making changes to config.yml (failed _auth)?) didn?t help ?
> ? ? Offending IP: ?188.138.33.14
>
>

From mstorck at voipgate.com  Thu Feb  4 18:51:09 2016
From: mstorck at voipgate.com (Marc Storck)
Date: Thu, 4 Feb 2016 23:51:09 +0000
Subject: [Spce-user] MCID App issue
In-Reply-To: <9F7472F0-1DCE-41BD-BBFB-B3726276D01E@voipgate.com>
References: <464D53E5-C98C-4B05-9D53-63A3224442CF@voipgate.com>
 <1EA4E174-98A5-4DDF-A346-1191DDACD7E8@sipwise.com>,
 <9F7472F0-1DCE-41BD-BBFB-B3726276D01E@voipgate.com>
Message-ID: <42E0F0207938744EB3DA31C28FC221CF0136A41BA1@LCEXMBX02.cmsad.local>

I just upgraded to mr4.2.1.

I followed the steps described in the documentation. My system was almost good, I was only missing the audio file in the sound set.

However the problem persists:

Feb  5 00:42:38 cusax (local7.notice) proxy[3552]: NOTICE: <script>: New request on proxy - M=INVITE R=sip:*57 at sld.tld;user=phone F=sip:johndoe at sld.tld T=sip:*57 at sld.tld;user=phone IP=11.22.33.44:5732 (127.0.0.1:5060) ID=2639378387 at 11_22_33_44 UA='N510 IP PRO/42.210.00.000.000'
Feb  5 00:42:38 cusax (local7.notice) proxy[3552]: NOTICE: <script>: User-Provided CLI 'johndoe' taken from From-User - R=sip:*57 at sld.tld;user=phone ID=2639378387 at 11_22_33_44 UA='N510 IP PRO/42.210.00.000.000'
Feb  5 00:42:38 cusax (local7.notice) proxy[3552]: NOTICE: <script>: User-provided CLI 'johndoe' rejected, using network-provided CLI '898910001201001' - R=sip:*57 at sld.tld;user=phone ID=2639378387 at 11_22_33_44 UA='N510 IP PRO/42.210.00.000.000'
Feb  5 00:42:38 cusax (local7.notice) proxy[3552]: NOTICE: <script>: Setting '898910001201001 at sld.tld' as initiating user-provided CLI - R=sip:*57 at sld.tld;user=phone ID=2639378387 at 11_22_33_44 UA='N510 IP PRO/42.210.00.000.000'
Feb  5 00:42:38 cusax (local7.notice) proxy[3552]: NOTICE: <script>: Setting '898910001201001 at sld.tld' as initiating network-provided CLI - R=sip:*57 at sld.tld;user=phone ID=2639378387 at 11_22_33_44 UA='N510 IP PRO/42.210.00.000.000'
Feb  5 00:42:38 cusax (local7.notice) proxy[3552]: NOTICE: <script>: Rewriting called party '*57' to 'malicious_call' - R=sip:*57 at sld.tld;user=phone ID=2639378387 at 11_22_33_44 UA='N510 IP PRO/42.210.00.000.000'
Feb  5 00:42:38 cusax (local7.err) proxy[3552]: ERROR: app_lua [app_lua_api.c:680]: app_lua_run(): error executing: del_dlg_profile (err: 2)
Feb  5 00:42:38 cusax (local7.err) proxy[3552]: ERROR: app_lua [app_lua_api.c:682]: app_lua_run(): error from Lua: /etc/kamailio/proxy/dlgcnt.lua:101: can't restore callid from $dlg_var(lua_dlg_callid): is null
Feb  5 00:42:38 cusax (local7.err) proxy[3552]: ERROR: <script>: Failed to decrease redis counters - R=sip:you at kamailio.org ID=123 UA='<null>'
Feb  5 00:42:38 cusax (local7.notice) proxy[3552]: NOTICE: <script>: New request on proxy - M=ACK R=sip:*57 at sld.tld;user=phone F=sip:johndoe at sld.tld T=sip:*57 at sld.tld;user=phone IP=11.22.33.44:5732 (127.0.0.1:5060) ID=2639378387 at 11_22_33_44 UA='N510 IP PRO/42.210.00.000.000'

Does anybody have an idea what might be the missing part?

Regards,

Marc

________________________________________
From: Marc Storck
Sent: Friday, October 30, 2015 17:49
To: Kirill Solomko
Cc: spce-user at lists.sipwise.com
Subject: Re: [Spce-user] MCID App issue

So I set

store_recentcalls: ?yes'

followed by running

ngcpcfg apply

but the result is still quite the same:

Oct 30 17:45:08 cusax proxy[514]: NOTICE: <script>: Rewriting called party '*57' to 'malicious_call' - R=sip:*57 at sld.tld ID=OWU3ZmFiMDY5ZGE4ZGJkODE4ODdlMDhjMzg1MWFkYzc UA='Bria iOS release 3.4.4 stamp 31657'
Oct 30 17:45:08 cusax proxy[514]: ERROR: app_lua [app_lua_api.c:680]: app_lua_run(): error executing: del_dlg_profile (err: 2)
Oct 30 17:45:08 cusax proxy[514]: ERROR: app_lua [app_lua_api.c:682]: app_lua_run(): error from Lua: /etc/kamailio/proxy/dlgcnt.lua:101: can't restore callid from $dlg_var(lua_dlg_callid): is null
Oct 30 17:45:08 cusax proxy[514]: ERROR: <script>: Failed to decrease redis counters - R=sip:you at kamailio.org ID=123 UA='<null>'

Regards,

Marc

> On 30 Oct 2015, at 17:42, Kirill Solomko <ksolomko at sipwise.com> wrote:
>
> Hi Mark,
>
> You should also enable ?recent calls? support in config.yml
>
> kamailio:
>  proxy:
>    store_recentcalls: ?yes'
>
>> On 30 Oct 2015, at 17:24, Marc Storck <mstorck at voipgate.com> wrote:
>>
>> Good evening,
>>
>> I?m having this problem with the MCID app:
>>
>> Oct 30 17:21:34 cusax proxy[23526]: NOTICE: <script>: Rewriting called party '*57' to 'malicious_call' - R=sip:*57 at sld.tld ID=YmE5NDYzOWMyMWE2NWY0MjE3YTMwYWRkMDVkMjcwOWI UA='Bria iOS release 3.4.4 stamp 31657'
>> Oct 30 17:21:34 cusax proxy[23526]: ERROR: app_lua [app_lua_api.c:680]: app_lua_run(): error executing: del_dlg_profile (err: 2)
>> Oct 30 17:21:34 cusax proxy[23526]: ERROR: app_lua [app_lua_api.c:682]: app_lua_run(): error from Lua: /etc/kamailio/proxy/dlgcnt.lua:101: can't restore callid from $dlg_var(lua_dlg_callid): is null
>> Oct 30 17:21:34 cusax proxy[23526]: ERROR: <script>: Failed to decrease redis counters - R=sip:you at kamailio.org ID=123 UA='<null>?
>>
>> I activated the MCID app in config.yml, are there any further changes required?
>>
>> Regards,
>>
>> Marc
>> _______________________________________________
>> Spce-user mailing list
>> Spce-user at lists.sipwise.com
>> https://lists.sipwise.com/listinfo/spce-user
>
> Kind regards,
> Kirill



From William at ezpcltd.com  Fri Feb  5 01:40:48 2016
From: William at ezpcltd.com (William Hilsum)
Date: Fri, 5 Feb 2016 06:40:48 +0000
Subject: [Spce-user] Rings once, then disconnects!
In-Reply-To: <56B067B3.4030606@sipwise.com>
References: <DB5PR06MB1557AB8F343FE2DD1C4AC44FBEDE0@DB5PR06MB1557.eurprd06.prod.outlook.com>
 <56AF3323.3090101@sipwise.com>
 <DB5PR06MB15571F52E939DC8818644634BEDE0@DB5PR06MB1557.eurprd06.prod.outlook.com>
 <56AF88BF.1020002@sipwise.com>
 <DB5PR06MB15573307ABE294694E402401BEDF0@DB5PR06MB1557.eurprd06.prod.outlook.com>
 <56B067B3.4030606@sipwise.com>
Message-ID: <DB5PR06MB1557E9176F0A2FCED9233799BED20@DB5PR06MB1557.eurprd06.prod.outlook.com>

Hi Alex,

Apologies - I think I'm unintentionally being confusing!

This is not a problem as such with Sipwise - it is the sip client with the option "Allow video calls" that when turned on, it automatically causes my upstream carrier to reject the call (after a single ring, which is just weird...)

Anyway, I have another PBX here where on a per carrier basis, I have the option "Disable video calls". When this is ticked, it basically strips out all relevant headers such as what caused my calls on Sipwise to fail.

So my question really is, after finding out the issue here, is there anyway I can get Sipwise to strip out these headers to avoid similar issues? I have not tested, but, I am guessing if anyone has a VOIP videophone, they may have the same issue as the softphone wasn't actually trying to establish a video stream, it was just saying it was video compatible in the header.

Thanks,

William

-----Original Message-----
From: Spce-user [mailto:spce-user-bounces at lists.sipwise.com] On Behalf Of Alex Lutay
Sent: 02 February 2016 08:24
To: spce-user at lists.sipwise.com
Subject: Re: [Spce-user] Rings once, then disconnects!

Dear William,

Check incoming invite from softphone to Sipwise, I am strongly believe you will find the same part there.

Sipwise doesn't change SDP part a lot, mainly it is replacing IP (I believe you have replaced '<PBX-IP>' in SDP part manually, otherwise it is an error) and limit list of codecs if necessary (turned off by default).

You can also try to make a call from your softphone through your Carrier directly and compare invite sent by softphone and Sipwise.

On the first look I do not see anything which can cause 500 on carrier side here. Was the correct IPv4/IPv6 in <PBX-IP> ?

On 02/02/2016 01:03 AM, William Hilsum wrote:
> These additional lines in the "invite (SDP) packet" from Sipwise to the carrier platform break the connection:
> 
> m=video 32562 RTP/AVP 34
> c=IN IP4 <PBX-IP>
> a=rtpmap:34 H263/90000
> a=fmtp:34 QCIF=1;CIF=1;SQCIF=1;CIF4=1
> a=sendrecv
> a=rtcp:32563
> a=direction:both

--
Alexander Lutay
Head of Quality Assurance
Sipwise GmbH, Campus 21/Europaring F15
AT-2345 Brunn am Gebirge

Office: +43(0)13012036
Email: alutay at sipwise.com
Website: http://www.sipwise.com
_______________________________________________
Spce-user mailing list
Spce-user at lists.sipwise.com
https://lists.sipwise.com/listinfo/spce-user


From dgrotti at sipwise.com  Fri Feb  5 01:58:59 2016
From: dgrotti at sipwise.com (Daniel Grotti)
Date: Fri, 05 Feb 2016 07:58:59 +0100
Subject: [Spce-user] MCID App issue
In-Reply-To: <42E0F0207938744EB3DA31C28FC221CF0136A41BA1@LCEXMBX02.cmsad.local>
Message-ID: <634d081a-8463-4965-abbb-a282d8f21695@email.android.com>

Hi Marc,
Did you flag the subscriber preferences MCID ? It should be in the Internal section.
You should enable MCID there otherwise it won't work.

Daniel

On Feb 5, 2016 12:51 AM, Marc Storck <mstorck at voipgate.com> wrote:
>
> I just upgraded to mr4.2.1. 
>
> I followed the steps described in the documentation. My system was almost good, I was only missing the audio file in the sound set. 
>
> However the problem persists: 
>
> Feb? 5 00:42:38 cusax (local7.notice) proxy[3552]: NOTICE: <script>: New request on proxy - M=INVITE R=sip:*57 at sld.tld;user=phone F=sip:johndoe at sld.tld T=sip:*57 at sld.tld;user=phone IP=11.22.33.44:5732 (127.0.0.1:5060) ID=2639378387 at 11_22_33_44 UA='N510 IP PRO/42.210.00.000.000' 
> Feb? 5 00:42:38 cusax (local7.notice) proxy[3552]: NOTICE: <script>: User-Provided CLI 'johndoe' taken from From-User - R=sip:*57 at sld.tld;user=phone ID=2639378387 at 11_22_33_44 UA='N510 IP PRO/42.210.00.000.000' 
> Feb? 5 00:42:38 cusax (local7.notice) proxy[3552]: NOTICE: <script>: User-provided CLI 'johndoe' rejected, using network-provided CLI '898910001201001' - R=sip:*57 at sld.tld;user=phone ID=2639378387 at 11_22_33_44 UA='N510 IP PRO/42.210.00.000.000' 
> Feb? 5 00:42:38 cusax (local7.notice) proxy[3552]: NOTICE: <script>: Setting '898910001201001 at sld.tld' as initiating user-provided CLI - R=sip:*57 at sld.tld;user=phone ID=2639378387 at 11_22_33_44 UA='N510 IP PRO/42.210.00.000.000' 
> Feb? 5 00:42:38 cusax (local7.notice) proxy[3552]: NOTICE: <script>: Setting '898910001201001 at sld.tld' as initiating network-provided CLI - R=sip:*57 at sld.tld;user=phone ID=2639378387 at 11_22_33_44 UA='N510 IP PRO/42.210.00.000.000' 
> Feb? 5 00:42:38 cusax (local7.notice) proxy[3552]: NOTICE: <script>: Rewriting called party '*57' to 'malicious_call' - R=sip:*57 at sld.tld;user=phone ID=2639378387 at 11_22_33_44 UA='N510 IP PRO/42.210.00.000.000' 
> Feb? 5 00:42:38 cusax (local7.err) proxy[3552]: ERROR: app_lua [app_lua_api.c:680]: app_lua_run(): error executing: del_dlg_profile (err: 2) 
> Feb? 5 00:42:38 cusax (local7.err) proxy[3552]: ERROR: app_lua [app_lua_api.c:682]: app_lua_run(): error from Lua: /etc/kamailio/proxy/dlgcnt.lua:101: can't restore callid from $dlg_var(lua_dlg_callid): is null 
> Feb? 5 00:42:38 cusax (local7.err) proxy[3552]: ERROR: <script>: Failed to decrease redis counters - R=sip:you at kamailio.org ID=123 UA='<null>' 
> Feb? 5 00:42:38 cusax (local7.notice) proxy[3552]: NOTICE: <script>: New request on proxy - M=ACK R=sip:*57 at sld.tld;user=phone F=sip:johndoe at sld.tld T=sip:*57 at sld.tld;user=phone IP=11.22.33.44:5732 (127.0.0.1:5060) ID=2639378387 at 11_22_33_44 UA='N510 IP PRO/42.210.00.000.000' 
>
> Does anybody have an idea what might be the missing part? 
>
> Regards, 
>
> Marc 
>
> ________________________________________ 
> From: Marc Storck 
> Sent: Friday, October 30, 2015 17:49 
> To: Kirill Solomko 
> Cc: spce-user at lists.sipwise.com 
> Subject: Re: [Spce-user] MCID App issue 
>
> So I set 
>
> store_recentcalls: ?yes' 
>
> followed by running 
>
> ngcpcfg apply 
>
> but the result is still quite the same: 
>
> Oct 30 17:45:08 cusax proxy[514]: NOTICE: <script>: Rewriting called party '*57' to 'malicious_call' - R=sip:*57 at sld.tld ID=OWU3ZmFiMDY5ZGE4ZGJkODE4ODdlMDhjMzg1MWFkYzc UA='Bria iOS release 3.4.4 stamp 31657' 
> Oct 30 17:45:08 cusax proxy[514]: ERROR: app_lua [app_lua_api.c:680]: app_lua_run(): error executing: del_dlg_profile (err: 2) 
> Oct 30 17:45:08 cusax proxy[514]: ERROR: app_lua [app_lua_api.c:682]: app_lua_run(): error from Lua: /etc/kamailio/proxy/dlgcnt.lua:101: can't restore callid from $dlg_var(lua_dlg_callid): is null 
> Oct 30 17:45:08 cusax proxy[514]: ERROR: <script>: Failed to decrease redis counters - R=sip:you at kamailio.org ID=123 UA='<null>' 
>
> Regards, 
>
> Marc 
>
> > On 30 Oct 2015, at 17:42, Kirill Solomko <ksolomko at sipwise.com> wrote: 
> > 
> > Hi Mark, 
> > 
> > You should also enable ?recent calls? support in config.yml 
> > 
> > kamailio: 
> >? proxy: 
> >??? store_recentcalls: ?yes' 
> > 
> >> On 30 Oct 2015, at 17:24, Marc Storck <mstorck at voipgate.com> wrote: 
> >> 
> >> Good evening, 
> >> 
> >> I?m having this problem with the MCID app: 
> >> 
> >> Oct 30 17:21:34 cusax proxy[23526]: NOTICE: <script>: Rewriting called party '*57' to 'malicious_call' - R=sip:*57 at sld.tld ID=YmE5NDYzOWMyMWE2NWY0MjE3YTMwYWRkMDVkMjcwOWI UA='Bria iOS release 3.4.4 stamp 31657' 
> >> Oct 30 17:21:34 cusax proxy[23526]: ERROR: app_lua [app_lua_api.c:680]: app_lua_run(): error executing: del_dlg_profile (err: 2) 
> >> Oct 30 17:21:34 cusax proxy[23526]: ERROR: app_lua [app_lua_api.c:682]: app_lua_run(): error from Lua: /etc/kamailio/proxy/dlgcnt.lua:101: can't restore callid from $dlg_var(lua_dlg_callid): is null 
> >> Oct 30 17:21:34 cusax proxy[23526]: ERROR: <script>: Failed to decrease redis counters - R=sip:you at kamailio.org ID=123 UA='<null>? 
> >> 
> >> I activated the MCID app in config.yml, are there any further changes required? 
> >> 
> >> Regards, 
> >> 
> >> Marc 
> >> _______________________________________________ 
> >> Spce-user mailing list 
> >> Spce-user at lists.sipwise.com 
> >> https://lists.sipwise.com/listinfo/spce-user 
> > 
> > Kind regards, 
> > Kirill 
>
> _______________________________________________ 
> Spce-user mailing list 
> Spce-user at lists.sipwise.com 
> https://lists.sipwise.com/listinfo/spce-user 

From j_e_vargas at live.com  Fri Feb  5 03:21:08 2016
From: j_e_vargas at live.com (Jose E. Vargas B.)
Date: Fri, 5 Feb 2016 00:21:08 -0800
Subject: [Spce-user] bruteforcing sip credentials attack
In-Reply-To: <46812e2e-1a1d-4c80-847e-d34d4f4d544e@email.android.com>
References: <46812e2e-1a1d-4c80-847e-d34d4f4d544e@email.android.com>
Message-ID: <BLU436-SMTP14785083FBDB23E415E1FEDBCD20@phx.gbl>

Thanks for your help Daniel, Alexis and George. Problem is solved now!
Jose

> On Feb 4, 2016, at 11:03 AM, Daniel Grotti <dgrotti at sipwise.com> wrote:
> 
> Hi,
> Hope it will help and maybe give you some hints:
> 
> https://www.linkedin.com/pulse/securing-your-ngcp-against-sip-attacks-daniel-grotti?forceNoSplash=true
> 
> 
> Daniel
> 
> 
> On Feb 4, 2016 7:38 PM, "Jose E. Vargas B." <j_e_vargas at live.com> wrote:
>> 
>> Hello,
>> 
>> Just have a quick and probably easy question for the SP community. I am experimenting with the server and keep getting the entire day the following attack:
>> 
>> 016/02/04 19:20:16.673827 188.138.33.14:5071 -> yy.yy.yy.yy:5060
>> INVITE sip:901141445209482 at xx.xx.xx.xx SIP/2.0
>> To: 901141445209482<sip:901141445209482 at xx.xx.xx.xx>
>> From: 0550<sip:0550 at xx.xx.xx.xx>;tag=67a87716
>> Via: SIP/2.0/UDP 188.138.33.14:5071;branch=z9hG4bK-6f67d7e24b4ac8a25f3d76106be4cb74;rport
>> Call-ID: 6f67d7e24b4ac8a25f3d76106be4cb74
>> CSeq: 1 INVITE
>> Contact: <sip:0550 at 188.138.33.14:5071>
>> Max-Forwards: 70
>> Allow: INVITE, ACK, CANCEL, BYE
>> User-Agent: sipcli/v1.8
>> Content-Type: application/sdp
>> Content-Length: 281
>> 
>> v=0
>> o=sipcli-Session 691746334 738426574 IN IP4 188.138.33.14
>> s=sipcli
>> c=IN IP4 188.138.33.14
>> t=0 0
>> m=audio 5073 RTP/AVP 18 0 8 101
>> a=fmtp:101 0-15
>> a=rtpmap:18 G729/8000
>> a=rtpmap:0 PCMU/8000
>> a=rtpmap:8 PCMA/8000
>> a=rtpmap:101 telephone-event/8000
>> a=ptime:20
>> a=sendrecv
>> 
>> 
>> I guess it is a funny group/folk trying to get unauthorized access to the server by sending multiple SIP invites with different accounts and possible free phone calls ;)  The problem is that SPCE won?t detect it as his attempts are spared in time.  Would like to get your guidance about blocking the entire IP or domain to SCPCE server. Could you please comment on how you deal with this type of attack?
>> 
>> Jose 
>> 
>> PS: 
>>     BTW - making changes to config.yml (failed _auth)?) didn?t help  
>>     Offending IP:  188.138.33.14
>> 
>> 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 1776 bytes
Desc: not available
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20160205/1b48eec3/attachment.p7s>

From mstorck at voipgate.com  Fri Feb  5 04:36:24 2016
From: mstorck at voipgate.com (Marc Storck)
Date: Fri, 5 Feb 2016 09:36:24 +0000
Subject: [Spce-user] MCID App issue
In-Reply-To: <634d081a-8463-4965-abbb-a282d8f21695@email.android.com>
References: <634d081a-8463-4965-abbb-a282d8f21695@email.android.com>
Message-ID: <2970CB78-9A94-41AB-8E04-63CC51B6C992@voipgate.com>

Hello Daniel,

That step is missing in the documentation.

I?ll test tonight.

Regards,

Marc Storck


> On 05 Feb 2016, at 07:58, Daniel Grotti <dgrotti at sipwise.com> wrote:
> 
> Hi Marc,
> Did you flag the subscriber preferences MCID ? It should be in the Internal section.
> You should enable MCID there otherwise it won't work.
> 
> Daniel
> 
> On Feb 5, 2016 12:51 AM, Marc Storck <mstorck at voipgate.com> wrote:
>> 
>> I just upgraded to mr4.2.1.
>> 
>> I followed the steps described in the documentation. My system was almost good, I was only missing the audio file in the sound set.
>> 
>> However the problem persists:
>> 
>> Feb  5 00:42:38 cusax (local7.notice) proxy[3552]: NOTICE: <script>: New request on proxy - M=INVITE R=sip:*57 at sld.tld;user=phone F=sip:johndoe at sld.tld T=sip:*57 at sld.tld;user=phone IP=11.22.33.44:5732 (127.0.0.1:5060) ID=2639378387 at 11_22_33_44 UA='N510 IP PRO/42.210.00.000.000'
>> Feb  5 00:42:38 cusax (local7.notice) proxy[3552]: NOTICE: <script>: User-Provided CLI 'johndoe' taken from From-User - R=sip:*57 at sld.tld;user=phone ID=2639378387 at 11_22_33_44 UA='N510 IP PRO/42.210.00.000.000'
>> Feb  5 00:42:38 cusax (local7.notice) proxy[3552]: NOTICE: <script>: User-provided CLI 'johndoe' rejected, using network-provided CLI '898910001201001' - R=sip:*57 at sld.tld;user=phone ID=2639378387 at 11_22_33_44 UA='N510 IP PRO/42.210.00.000.000'
>> Feb  5 00:42:38 cusax (local7.notice) proxy[3552]: NOTICE: <script>: Setting '898910001201001 at sld.tld' as initiating user-provided CLI - R=sip:*57 at sld.tld;user=phone ID=2639378387 at 11_22_33_44 UA='N510 IP PRO/42.210.00.000.000'
>> Feb  5 00:42:38 cusax (local7.notice) proxy[3552]: NOTICE: <script>: Setting '898910001201001 at sld.tld' as initiating network-provided CLI - R=sip:*57 at sld.tld;user=phone ID=2639378387 at 11_22_33_44 UA='N510 IP PRO/42.210.00.000.000'
>> Feb  5 00:42:38 cusax (local7.notice) proxy[3552]: NOTICE: <script>: Rewriting called party '*57' to 'malicious_call' - R=sip:*57 at sld.tld;user=phone ID=2639378387 at 11_22_33_44 UA='N510 IP PRO/42.210.00.000.000'
>> Feb  5 00:42:38 cusax (local7.err) proxy[3552]: ERROR: app_lua [app_lua_api.c:680]: app_lua_run(): error executing: del_dlg_profile (err: 2)
>> Feb  5 00:42:38 cusax (local7.err) proxy[3552]: ERROR: app_lua [app_lua_api.c:682]: app_lua_run(): error from Lua: /etc/kamailio/proxy/dlgcnt.lua:101: can't restore callid from $dlg_var(lua_dlg_callid): is null
>> Feb  5 00:42:38 cusax (local7.err) proxy[3552]: ERROR: <script>: Failed to decrease redis counters - R=sip:you at kamailio.org ID=123 UA='<null>'
>> Feb  5 00:42:38 cusax (local7.notice) proxy[3552]: NOTICE: <script>: New request on proxy - M=ACK R=sip:*57 at sld.tld;user=phone F=sip:johndoe at sld.tld T=sip:*57 at sld.tld;user=phone IP=11.22.33.44:5732 (127.0.0.1:5060) ID=2639378387 at 11_22_33_44 UA='N510 IP PRO/42.210.00.000.000'
>> 
>> Does anybody have an idea what might be the missing part?
>> 
>> Regards,
>> 
>> Marc
>> 
>> ________________________________________
>> From: Marc Storck
>> Sent: Friday, October 30, 2015 17:49
>> To: Kirill Solomko
>> Cc: spce-user at lists.sipwise.com
>> Subject: Re: [Spce-user] MCID App issue
>> 
>> So I set
>> 
>> store_recentcalls: ?yes'
>> 
>> followed by running
>> 
>> ngcpcfg apply
>> 
>> but the result is still quite the same:
>> 
>> Oct 30 17:45:08 cusax proxy[514]: NOTICE: <script>: Rewriting called party '*57' to 'malicious_call' - R=sip:*57 at sld.tld ID=OWU3ZmFiMDY5ZGE4ZGJkODE4ODdlMDhjMzg1MWFkYzc UA='Bria iOS release 3.4.4 stamp 31657'
>> Oct 30 17:45:08 cusax proxy[514]: ERROR: app_lua [app_lua_api.c:680]: app_lua_run(): error executing: del_dlg_profile (err: 2)
>> Oct 30 17:45:08 cusax proxy[514]: ERROR: app_lua [app_lua_api.c:682]: app_lua_run(): error from Lua: /etc/kamailio/proxy/dlgcnt.lua:101: can't restore callid from $dlg_var(lua_dlg_callid): is null
>> Oct 30 17:45:08 cusax proxy[514]: ERROR: <script>: Failed to decrease redis counters - R=sip:you at kamailio.org ID=123 UA='<null>'
>> 
>> Regards,
>> 
>> Marc
>> 
>>> On 30 Oct 2015, at 17:42, Kirill Solomko <ksolomko at sipwise.com> wrote:
>>> 
>>> Hi Mark,
>>> 
>>> You should also enable ?recent calls? support in config.yml
>>> 
>>> kamailio:
>>>   proxy:
>>>     store_recentcalls: ?yes'
>>> 
>>>> On 30 Oct 2015, at 17:24, Marc Storck <mstorck at voipgate.com> wrote:
>>>> 
>>>> Good evening,
>>>> 
>>>> I?m having this problem with the MCID app:
>>>> 
>>>> Oct 30 17:21:34 cusax proxy[23526]: NOTICE: <script>: Rewriting called party '*57' to 'malicious_call' - R=sip:*57 at sld.tld ID=YmE5NDYzOWMyMWE2NWY0MjE3YTMwYWRkMDVkMjcwOWI UA='Bria iOS release 3.4.4 stamp 31657'
>>>> Oct 30 17:21:34 cusax proxy[23526]: ERROR: app_lua [app_lua_api.c:680]: app_lua_run(): error executing: del_dlg_profile (err: 2)
>>>> Oct 30 17:21:34 cusax proxy[23526]: ERROR: app_lua [app_lua_api.c:682]: app_lua_run(): error from Lua: /etc/kamailio/proxy/dlgcnt.lua:101: can't restore callid from $dlg_var(lua_dlg_callid): is null
>>>> Oct 30 17:21:34 cusax proxy[23526]: ERROR: <script>: Failed to decrease redis counters - R=sip:you at kamailio.org ID=123 UA='<null>?
>>>> 
>>>> I activated the MCID app in config.yml, are there any further changes required?
>>>> 
>>>> Regards,
>>>> 
>>>> Marc
>>>> _______________________________________________
>>>> Spce-user mailing list
>>>> Spce-user at lists.sipwise.com
>>>> https://lists.sipwise.com/listinfo/spce-user
>>> 
>>> Kind regards,
>>> Kirill
>> 
>> _______________________________________________
>> Spce-user mailing list
>> Spce-user at lists.sipwise.com
>> https://lists.sipwise.com/listinfo/spce-user

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 841 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20160205/cc27e9e1/attachment.asc>

From dgrotti at sipwise.com  Fri Feb  5 04:42:38 2016
From: dgrotti at sipwise.com (Daniel Grotti)
Date: Fri, 5 Feb 2016 10:42:38 +0100
Subject: [Spce-user] MCID App issue
In-Reply-To: <2970CB78-9A94-41AB-8E04-63CC51B6C992@voipgate.com>
References: <634d081a-8463-4965-abbb-a282d8f21695@email.android.com>
 <2970CB78-9A94-41AB-8E04-63CC51B6C992@voipgate.com>
Message-ID: <56B46E8E.8030906@sipwise.com>

Hi Marc,
it's part of mr4.2.1 documentation.
I introduced it when we noticed that was missing.

thanks.

*Daniel Grotti *
Head of Customer Support

Sipwise GmbH <http://www.sipwise.com> , Campus 21/Europaring F15
AT-2345 Brunn am Gebirge

Phone: +43(0)1 301 2032 <callto:+4313012032>
Email: dgrotti at sipwise.com <mailto:dgrotti at sipwise.com>
Website: www.sipwise.com <http://www.sipwise.com>

Particulars according Austrian Companies Code paragraph 14
"Sipwise GmbH" - Europaring F15 - 2345 Brunn am Gebirge
FN:305595f, Commercial Court Vienna, ATU64002206

On 02/05/2016 10:36 AM, Marc Storck wrote:
> Hello Daniel,
>
> That step is missing in the documentation.
>
> I?ll test tonight.
>
> Regards,
>
> Marc Storck
>
>
>> On 05 Feb 2016, at 07:58, Daniel Grotti <dgrotti at sipwise.com> wrote:
>>
>> Hi Marc,
>> Did you flag the subscriber preferences MCID ? It should be in the Internal section.
>> You should enable MCID there otherwise it won't work.
>>
>> Daniel
>>
>> On Feb 5, 2016 12:51 AM, Marc Storck <mstorck at voipgate.com> wrote:
>>> I just upgraded to mr4.2.1.
>>>
>>> I followed the steps described in the documentation. My system was almost good, I was only missing the audio file in the sound set.
>>>
>>> However the problem persists:
>>>
>>> Feb  5 00:42:38 cusax (local7.notice) proxy[3552]: NOTICE: <script>: New request on proxy - M=INVITE R=sip:*57 at sld.tld;user=phone F=sip:johndoe at sld.tld T=sip:*57 at sld.tld;user=phone IP=11.22.33.44:5732 (127.0.0.1:5060) ID=2639378387 at 11_22_33_44 UA='N510 IP PRO/42.210.00.000.000'
>>> Feb  5 00:42:38 cusax (local7.notice) proxy[3552]: NOTICE: <script>: User-Provided CLI 'johndoe' taken from From-User - R=sip:*57 at sld.tld;user=phone ID=2639378387 at 11_22_33_44 UA='N510 IP PRO/42.210.00.000.000'
>>> Feb  5 00:42:38 cusax (local7.notice) proxy[3552]: NOTICE: <script>: User-provided CLI 'johndoe' rejected, using network-provided CLI '898910001201001' - R=sip:*57 at sld.tld;user=phone ID=2639378387 at 11_22_33_44 UA='N510 IP PRO/42.210.00.000.000'
>>> Feb  5 00:42:38 cusax (local7.notice) proxy[3552]: NOTICE: <script>: Setting '898910001201001 at sld.tld' as initiating user-provided CLI - R=sip:*57 at sld.tld;user=phone ID=2639378387 at 11_22_33_44 UA='N510 IP PRO/42.210.00.000.000'
>>> Feb  5 00:42:38 cusax (local7.notice) proxy[3552]: NOTICE: <script>: Setting '898910001201001 at sld.tld' as initiating network-provided CLI - R=sip:*57 at sld.tld;user=phone ID=2639378387 at 11_22_33_44 UA='N510 IP PRO/42.210.00.000.000'
>>> Feb  5 00:42:38 cusax (local7.notice) proxy[3552]: NOTICE: <script>: Rewriting called party '*57' to 'malicious_call' - R=sip:*57 at sld.tld;user=phone ID=2639378387 at 11_22_33_44 UA='N510 IP PRO/42.210.00.000.000'
>>> Feb  5 00:42:38 cusax (local7.err) proxy[3552]: ERROR: app_lua [app_lua_api.c:680]: app_lua_run(): error executing: del_dlg_profile (err: 2)
>>> Feb  5 00:42:38 cusax (local7.err) proxy[3552]: ERROR: app_lua [app_lua_api.c:682]: app_lua_run(): error from Lua: /etc/kamailio/proxy/dlgcnt.lua:101: can't restore callid from $dlg_var(lua_dlg_callid): is null
>>> Feb  5 00:42:38 cusax (local7.err) proxy[3552]: ERROR: <script>: Failed to decrease redis counters - R=sip:you at kamailio.org ID=123 UA='<null>'
>>> Feb  5 00:42:38 cusax (local7.notice) proxy[3552]: NOTICE: <script>: New request on proxy - M=ACK R=sip:*57 at sld.tld;user=phone F=sip:johndoe at sld.tld T=sip:*57 at sld.tld;user=phone IP=11.22.33.44:5732 (127.0.0.1:5060) ID=2639378387 at 11_22_33_44 UA='N510 IP PRO/42.210.00.000.000'
>>>
>>> Does anybody have an idea what might be the missing part?
>>>
>>> Regards,
>>>
>>> Marc
>>>
>>> ________________________________________
>>> From: Marc Storck
>>> Sent: Friday, October 30, 2015 17:49
>>> To: Kirill Solomko
>>> Cc: spce-user at lists.sipwise.com
>>> Subject: Re: [Spce-user] MCID App issue
>>>
>>> So I set
>>>
>>> store_recentcalls: ?yes'
>>>
>>> followed by running
>>>
>>> ngcpcfg apply
>>>
>>> but the result is still quite the same:
>>>
>>> Oct 30 17:45:08 cusax proxy[514]: NOTICE: <script>: Rewriting called party '*57' to 'malicious_call' - R=sip:*57 at sld.tld ID=OWU3ZmFiMDY5ZGE4ZGJkODE4ODdlMDhjMzg1MWFkYzc UA='Bria iOS release 3.4.4 stamp 31657'
>>> Oct 30 17:45:08 cusax proxy[514]: ERROR: app_lua [app_lua_api.c:680]: app_lua_run(): error executing: del_dlg_profile (err: 2)
>>> Oct 30 17:45:08 cusax proxy[514]: ERROR: app_lua [app_lua_api.c:682]: app_lua_run(): error from Lua: /etc/kamailio/proxy/dlgcnt.lua:101: can't restore callid from $dlg_var(lua_dlg_callid): is null
>>> Oct 30 17:45:08 cusax proxy[514]: ERROR: <script>: Failed to decrease redis counters - R=sip:you at kamailio.org ID=123 UA='<null>'
>>>
>>> Regards,
>>>
>>> Marc
>>>
>>>> On 30 Oct 2015, at 17:42, Kirill Solomko <ksolomko at sipwise.com> wrote:
>>>>
>>>> Hi Mark,
>>>>
>>>> You should also enable ?recent calls? support in config.yml
>>>>
>>>> kamailio:
>>>>    proxy:
>>>>      store_recentcalls: ?yes'
>>>>
>>>>> On 30 Oct 2015, at 17:24, Marc Storck <mstorck at voipgate.com> wrote:
>>>>>
>>>>> Good evening,
>>>>>
>>>>> I?m having this problem with the MCID app:
>>>>>
>>>>> Oct 30 17:21:34 cusax proxy[23526]: NOTICE: <script>: Rewriting called party '*57' to 'malicious_call' - R=sip:*57 at sld.tld ID=YmE5NDYzOWMyMWE2NWY0MjE3YTMwYWRkMDVkMjcwOWI UA='Bria iOS release 3.4.4 stamp 31657'
>>>>> Oct 30 17:21:34 cusax proxy[23526]: ERROR: app_lua [app_lua_api.c:680]: app_lua_run(): error executing: del_dlg_profile (err: 2)
>>>>> Oct 30 17:21:34 cusax proxy[23526]: ERROR: app_lua [app_lua_api.c:682]: app_lua_run(): error from Lua: /etc/kamailio/proxy/dlgcnt.lua:101: can't restore callid from $dlg_var(lua_dlg_callid): is null
>>>>> Oct 30 17:21:34 cusax proxy[23526]: ERROR: <script>: Failed to decrease redis counters - R=sip:you at kamailio.org ID=123 UA='<null>?
>>>>>
>>>>> I activated the MCID app in config.yml, are there any further changes required?
>>>>>
>>>>> Regards,
>>>>>
>>>>> Marc
>>>>> _______________________________________________
>>>>> Spce-user mailing list
>>>>> Spce-user at lists.sipwise.com
>>>>> https://lists.sipwise.com/listinfo/spce-user
>>>> Kind regards,
>>>> Kirill
>>> _______________________________________________
>>> Spce-user mailing list
>>> Spce-user at lists.sipwise.com
>>> https://lists.sipwise.com/listinfo/spce-user

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20160205/e0f4cb80/attachment.html>

From j.feugne at prisnets.ch  Fri Feb  5 06:57:27 2016
From: j.feugne at prisnets.ch (=?UTF-8?Q?Jephth=c3=a9_Feugn=c3=a9?=)
Date: Fri, 5 Feb 2016 12:57:27 +0100
Subject: [Spce-user]  trunk to voicetrading configuration
In-Reply-To: <56B46E8E.8030906@sipwise.com>
References: <634d081a-8463-4965-abbb-a282d8f21695@email.android.com>
 <2970CB78-9A94-41AB-8E04-63CC51B6C992@voipgate.com>
 <56B46E8E.8030906@sipwise.com>
Message-ID: <56B48E27.2080804@prisnets.ch>

Hello,
I've been trying for weeks to have my trunk to voicetrading working with 
no success. I also tried a sip trunk to my GSM gateway with the same 
result. No ringing to the calle side, and no sound no ringing tone by 
the caller side.

Can some one please can help me solve this problem?

Here is what I have during call with the command "ngrep sip" executed on 
the sipwise CE 4.2.1  server. Voicetrading is  expecting for premium 
route on their side, the number to be perpended with "00000", 
xx.xx.xx.250 is the IP address of my sipwise CE 4.2.1 server:



U xx.xx.xx.250:5060 -> 77.72.169.129:5060
   ACK sip:0000041227312221 at 77.72.169.129:5060;transport=udp 
SIP/2.0..Max-Forwards: 70..Record-Route: 
<sip:xx.xx.xx.250;r2=on;lr=on;ftag=3F73B03A-56B489EF00017901-870F0700;ngcplb=yes
   >..Record-Route: 
<sip:127.0.0.1;r2=on;lr=on;ftag=3F73B03A-56B489EF00017901-870F0700;ngcplb=yes>..Via: 
SIP/2.0/UDP 
xx.xx.xx.250;branch=z9hG4bK705f.3ceafc99ad73ca726fe67f2c96efb4ea.
   0..Via: SIP/2.0/UDP 
127.0.0.1:5080;received=127.0.0.1;branch=z9hG4bKqqDKvalZ;rport=5080..From: 
"41225017070" 
<sip:41225017070 at sip.adoovoice.com>;tag=3F73B03A-56B489EF00017901-870F0
   700..To: <sip:0000041227312221 at 77.72.169.129>..Call-ID: 
f3e84a2c-469f-1234-1eae-00163ee0653c_b2b-1..CSeq: 10 
ACK..Content-Length: 0....
#
U xx.xx.xx.250:5060 -> 77.72.169.129:5060
   INVITE sip:0000041227312221 at 77.72.169.129:5060;transport=udp 
SIP/2.0..Record-Route: 
<sip:xx.xx.xx.250;r2=on;lr=on;ftag=3F73B03A-56B489EF00017901-870F0700;ngcplb=yes>..Record-Route
   : 
<sip:127.0.0.1;r2=on;lr=on;ftag=3F73B03A-56B489EF00017901-870F0700;ngcplb=yes>..Via: 
SIP/2.0/UDP 
xx.xx.xx.250;branch=z9hG4bK805f.3b9fffb768d5164c476e3f831eb033fc.0..Via: 
SIP/2.0
   /UDP 
127.0.0.1:5080;received=127.0.0.1;branch=z9hG4bKx0gPrabm;rport=5080..From: 
"41225017070" 
<sip:41225017070 at sip.adoovoice.com>;tag=3F73B03A-56B489EF00017901-870F0700..To: 
<sip:0
   000041227312221 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 
f3e84a2c-469f-1234-1eae-00163ee0653c_b2b-1..Max-Forwards: 69..Allow: 
INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, UPDATE, R
   EGISTER, NOTIFY..Supported: path, replaces..P-Asserted-Identity: 
<sip:41225017070 at sip.adoovoice.com>..Authorization: Digest 
username="pbxprisnet", realm="sip.adoovoice.com", nonce=
   "99066203", 
uri="sip:0000041227312221 at 77.72.169.129:5060;transport=udp", 
response="e3fda1ac2871a94ed7b781e0f69741d0", 
algorithm=MD5..Content-Type: application/sdp..Content-Length:
   326..Contact: 
<sip:ngcp-lb at xx.xx.xx.250:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=FreeSWITCH 
1454642405 1454642406 IN IP4 xx.xx.xx.253..s=FreeSWITCH..c=IN IP4 8
   4.253.60.153..t=0 0..m=audio 29962 RTP/AVP 8 9 0 3 101 13..a=rtpmap:8 
PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:0 PCMU/8000..a=rtpmap:3 
GSM/8000..a=rtpmap:101 telephone-event/8000.
   .a=fmtp:101 0-16..a=sendrecv..a=ptime:20..a=direction:both..
################################
U xx.xx.xx.250:5060 -> 77.72.169.129:5060
   INVITE sip:0000041227312221 at 77.72.169.129:5060;transport=udp 
SIP/2.0..Record-Route: 
<sip:xx.xx.xx.250;r2=on;lr=on;ftag=3F73B03A-56B489EF00017901-870F0700;ngcplb=yes>..Record-Route
   : 
<sip:127.0.0.1;r2=on;lr=on;ftag=3F73B03A-56B489EF00017901-870F0700;ngcplb=yes>..Via: 
SIP/2.0/UDP 
xx.xx.xx.250;branch=z9hG4bK805f.3b9fffb768d5164c476e3f831eb033fc.0..Via: 
SIP/2.0
   /UDP 
127.0.0.1:5080;received=127.0.0.1;branch=z9hG4bKx0gPrabm;rport=5080..From: 
"41225017070" 
<sip:41225017070 at sip.adoovoice.com>;tag=3F73B03A-56B489EF00017901-870F0700..To: 
<sip:0
   000041227312221 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 
f3e84a2c-469f-1234-1eae-00163ee0653c_b2b-1..Max-Forwards: 69..Allow: 
INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, UPDATE, R
   EGISTER, NOTIFY..Supported: path, replaces..P-Asserted-Identity: 
<sip:41225017070 at sip.adoovoice.com>..Authorization: Digest 
username="pbxprisnet", realm="sip.adoovoice.com", nonce=
   "99066203", 
uri="sip:0000041227312221 at 77.72.169.129:5060;transport=udp", 
response="e3fda1ac2871a94ed7b781e0f69741d0", 
algorithm=MD5..Content-Type: application/sdp..Content-Length:
   326..Contact: 
<sip:ngcp-lb at xx.xx.xx.250:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=FreeSWITCH 
1454642405 1454642406 IN IP4 xx.xx.xx.253..s=FreeSWITCH..c=IN IP4 8
   4.253.60.153..t=0 0..m=audio 29962 RTP/AVP 8 9 0 3 101 13..a=rtpmap:8 
PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:0 PCMU/8000..a=rtpmap:3 
GSM/8000..a=rtpmap:101 telephone-event/8000.
   .a=fmtp:101 0-16..a=sendrecv..a=ptime:20..a=direction:both..
#############################
U xx.xx.xx.250:5060 -> 77.72.169.129:5060
   INVITE sip:0000041227312221 at 77.72.169.129:5060;transport=udp 
SIP/2.0..Record-Route: 
<sip:xx.xx.xx.250;r2=on;lr=on;ftag=3F73B03A-56B489EF00017901-870F0700;ngcplb=yes>..Record-Route
   : 
<sip:127.0.0.1;r2=on;lr=on;ftag=3F73B03A-56B489EF00017901-870F0700;ngcplb=yes>..Via: 
SIP/2.0/UDP 
xx.xx.xx.250;branch=z9hG4bK805f.3b9fffb768d5164c476e3f831eb033fc.0..Via: 
SIP/2.0
   /UDP 
127.0.0.1:5080;received=127.0.0.1;branch=z9hG4bKx0gPrabm;rport=5080..From: 
"41225017070" 
<sip:41225017070 at sip.adoovoice.com>;tag=3F73B03A-56B489EF00017901-870F0700..To: 
<sip:0
   000041227312221 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 
f3e84a2c-469f-1234-1eae-00163ee0653c_b2b-1..Max-Forwards: 69..Allow: 
INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, UPDATE, R
   EGISTER, NOTIFY..Supported: path, replaces..P-Asserted-Identity: 
<sip:41225017070 at sip.adoovoice.com>..Authorization: Digest 
username="pbxprisnet", realm="sip.adoovoice.com", nonce=
   "99066203", 
uri="sip:0000041227312221 at 77.72.169.129:5060;transport=udp", 
response="e3fda1ac2871a94ed7b781e0f69741d0", 
algorithm=MD5..Content-Type: application/sdp..Content-Length:
   326..Contact: 
<sip:ngcp-lb at xx.xx.xx.250:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=FreeSWITCH 
1454642405 1454642406 IN IP4 xx.xx.xx.253..s=FreeSWITCH..c=IN IP4 8
   4.253.60.153..t=0 0..m=audio 29962 RTP/AVP 8 9 0 3 101 13..a=rtpmap:8 
PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:0 PCMU/8000..a=rtpmap:3 
GSM/8000..a=rtpmap:101 telephone-event/8000.
   .a=fmtp:101 0-16..a=sendrecv..a=ptime:20..a=direction:both..
###################################################
U xx.xx.xx.250:5060 -> 77.72.169.129:5060
   INVITE sip:0000041227312221 at 77.72.169.129:5060;transport=udp 
SIP/2.0..Record-Route: 
<sip:xx.xx.xx.250;r2=on;lr=on;ftag=3F73B03A-56B489EF00017901-870F0700;ngcplb=yes>..Record-Route
   : 
<sip:127.0.0.1;r2=on;lr=on;ftag=3F73B03A-56B489EF00017901-870F0700;ngcplb=yes>..Via: 
SIP/2.0/UDP 
xx.xx.xx.250;branch=z9hG4bK805f.3b9fffb768d5164c476e3f831eb033fc.0..Via: 
SIP/2.0
   /UDP 
127.0.0.1:5080;received=127.0.0.1;branch=z9hG4bKx0gPrabm;rport=5080..From: 
"41225017070" 
<sip:41225017070 at sip.adoovoice.com>;tag=3F73B03A-56B489EF00017901-870F0700..To: 
<sip:0
   000041227312221 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 
f3e84a2c-469f-1234-1eae-00163ee0653c_b2b-1..Max-Forwards: 69..Allow: 
INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, UPDATE, R
   EGISTER, NOTIFY..Supported: path, replaces..P-Asserted-Identity: 
<sip:41225017070 at sip.adoovoice.com>..Authorization: Digest 
username="pbxprisnet", realm="sip.adoovoice.com", nonce=
   "99066203", 
uri="sip:0000041227312221 at 77.72.169.129:5060;transport=udp", 
response="e3fda1ac2871a94ed7b781e0f69741d0", 
algorithm=MD5..Content-Type: application/sdp..Content-Length:
   326..Contact: 
<sip:ngcp-lb at xx.xx.xx.250:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=FreeSWITCH 
1454642405 1454642406 IN IP4 xx.xx.xx.253..s=FreeSWITCH..c=IN IP4 8
   4.253.60.153..t=0 0..m=audio 29962 RTP/AVP 8 9 0 3 101 13..a=rtpmap:8 
PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:0 PCMU/8000..a=rtpmap:3 
GSM/8000..a=rtpmap:101 telephone-event/8000.
   .a=fmtp:101 0-16..a=sendrecv..a=ptime:20..a=direction:both..
######


Thank you for your contributions

Jephth? Feugn?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20160205/47dd82c2/attachment.html>

From manwe at sipdoc.net  Fri Feb  5 07:07:38 2016
From: manwe at sipdoc.net (Jon Bonilla (Manwe))
Date: Fri, 5 Feb 2016 13:07:38 +0100
Subject: [Spce-user] trunk to voicetrading configuration
In-Reply-To: <56B48E27.2080804@prisnets.ch>
References: <634d081a-8463-4965-abbb-a282d8f21695@email.android.com>
 <2970CB78-9A94-41AB-8E04-63CC51B6C992@voipgate.com>
 <56B46E8E.8030906@sipwise.com> <56B48E27.2080804@prisnets.ch>
Message-ID: <20160205130738.49281a29@multivac>

El Fri, 5 Feb 2016 12:57:27 +0100
Jephth? Feugn? <j.feugne at prisnets.ch> escribi?:

> Hello,
> I've been trying for weeks to have my trunk to voicetrading working with 
> no success. I also tried a sip trunk to my GSM gateway with the same 
> result. No ringing to the calle side, and no sound no ringing tone by 
> the caller side.
> 
> Can some one please can help me solve this problem?
> 
> Here is what I have during call with the command "ngrep sip" executed on 
> the sipwise CE 4.2.1  server. Voicetrading is  expecting for premium 
> route on their side, the number to be perpended with "00000", 
> xx.xx.xx.250 is the IP address of my sipwise CE 4.2.1 server:
> 
> 
>

Please, do not answer mails to create a new thread. Press the "new mail" button.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: Firma digital OpenPGP
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20160205/fd55d046/attachment.sig>

From j.feugne at prisnets.ch  Fri Feb  5 09:59:13 2016
From: j.feugne at prisnets.ch (=?UTF-8?Q?Jephth=c3=a9_Feugn=c3=a9?=)
Date: Fri, 5 Feb 2016 15:59:13 +0100
Subject: [Spce-user] Trunk to voicetrading configuration
Message-ID: <56B4B8C1.5060203@prisnets.ch>

Hello,
I've been trying for weeks to have my trunk to voicetrading working with no success. I also tried a sip trunk to my GSM gateway with the same
result. No ringing to the calle side, and no sound no ringing tone by the caller side.

Can some one please can help me solve this problem?

Here is what I have during call with the command "ngrep sip" executed on the sipwise CE 4.2.1  server. Voicetrading is  expecting for premium
route on their side, the number to be perpended with "00000", xx.xx.xx.250 is the IP address of my sipwise CE 4.2.1 server:


XX.XX.XX.250:5060 -> 77.72.169.129:5060
   INVITE sip:00492271993120 at 77.72.169.129:5060;transport=udp SIP/2.0..Record-Route: <sip:XX.XX.XX.250;r2=on;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Record-Route: <sip:127.0.0.1;r2=on
   ;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Via: SIP/2.0/UDP XX.XX.XX.250;branch=z9hG4bKd906.5531f5d10bd0fe3667091afe519d5f94.0..Via: SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;bra
   nch=z9hG4bKZ7GCaaKk;rport=5080..From: "41225017077" <sip:41225017077 at sip.adoovoice.com>;tag=0F8733E5-56B4B7B700066935-870F0700..To: <sip:00492271993120 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 222572
   206 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, PUBLISH, UPDATE, MESSAGE..Supported: replaces,100rel..P-Asserted-Identity: <sip:
   41225017077 at sip.adoovoice.com>..Authorization: Digest username="pbxprisnet", realm="sip.adoovoice.com", nonce="2231175255", uri="sip:00492271993120 at 77.72.169.129:5060;transport=udp", response="dac6cac
   8d25100ee03560bab867ba1be", algorithm=MD5..Content-Type: application/sdp..Content-Length: 265..Contact: <sip:ngcp-lb at XX.XX.XX.250:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=- 20036 2
   0036 IN IP4 10.164.124.97..s=SDP data..c=IN IP4 213.55.176.206..t=0 0..m=audio 11852 RTP/AVP 0 8 9 101..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:101 telephone-event/8
   000..a=sendrecv..a=ptime:20..a=direction:active..
#####################
U XX.XX.XX.250:5060 -> 77.72.169.129:5060
   INVITE sip:00492271993120 at 77.72.169.129:5060;transport=udp SIP/2.0..Record-Route: <sip:XX.XX.XX.250;r2=on;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Record-Route: <sip:127.0.0.1;r2=on
   ;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Via: SIP/2.0/UDP XX.XX.XX.250;branch=z9hG4bKd906.5531f5d10bd0fe3667091afe519d5f94.0..Via: SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;bra
   nch=z9hG4bKZ7GCaaKk;rport=5080..From: "41225017077" <sip:41225017077 at sip.adoovoice.com>;tag=0F8733E5-56B4B7B700066935-870F0700..To: <sip:00492271993120 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 222572
   206 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, PUBLISH, UPDATE, MESSAGE..Supported: replaces,100rel..P-Asserted-Identity: <sip:
   41225017077 at sip.adoovoice.com>..Authorization: Digest username="pbxprisnet", realm="sip.adoovoice.com", nonce="2231175255", uri="sip:00492271993120 at 77.72.169.129:5060;transport=udp", response="dac6cac
   8d25100ee03560bab867ba1be", algorithm=MD5..Content-Type: application/sdp..Content-Length: 265..Contact: <sip:ngcp-lb at XX.XX.XX.250:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=- 20036 2
   0036 IN IP4 10.164.124.97..s=SDP data..c=IN IP4 213.55.176.206..t=0 0..m=audio 11852 RTP/AVP 0 8 9 101..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:101 telephone-event/8
   000..a=sendrecv..a=ptime:20..a=direction:active..
#######################
U XX.XX.XX.250:5060 -> 77.72.169.129:5060
   INVITE sip:00492271993120 at 77.72.169.129:5060;transport=udp SIP/2.0..Record-Route: <sip:XX.XX.XX.250;r2=on;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Record-Route: <sip:127.0.0.1;r2=on
   ;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Via: SIP/2.0/UDP XX.XX.XX.250;branch=z9hG4bKd906.5531f5d10bd0fe3667091afe519d5f94.0..Via: SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;bra
   nch=z9hG4bKZ7GCaaKk;rport=5080..From: "41225017077" <sip:41225017077 at sip.adoovoice.com>;tag=0F8733E5-56B4B7B700066935-870F0700..To: <sip:00492271993120 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 222572
   206 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, PUBLISH, UPDATE, MESSAGE..Supported: replaces,100rel..P-Asserted-Identity: <sip:
   41225017077 at sip.adoovoice.com>..Authorization: Digest username="pbxprisnet", realm="sip.adoovoice.com", nonce="2231175255", uri="sip:00492271993120 at 77.72.169.129:5060;transport=udp", response="dac6cac
   8d25100ee03560bab867ba1be", algorithm=MD5..Content-Type: application/sdp..Content-Length: 265..Contact: <sip:ngcp-lb at XX.XX.XX.250:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=- 20036 2
   0036 IN IP4 10.164.124.97..s=SDP data..c=IN IP4 213.55.176.206..t=0 0..m=audio 11852 RTP/AVP 0 8 9 101..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:101 telephone-event/8
   000..a=sendrecv..a=ptime:20..a=direction:active..
#########################################
U XX.XX.XX.250:5060 -> 77.72.169.129:5060
   INVITE sip:00492271993120 at 77.72.169.129:5060;transport=udp SIP/2.0..Record-Route: <sip:XX.XX.XX.250;r2=on;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Record-Route: <sip:127.0.0.1;r2=on
   ;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Via: SIP/2.0/UDP XX.XX.XX.250;branch=z9hG4bKd906.5531f5d10bd0fe3667091afe519d5f94.0..Via: SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;bra
   nch=z9hG4bKZ7GCaaKk;rport=5080..From: "41225017077" <sip:41225017077 at sip.adoovoice.com>;tag=0F8733E5-56B4B7B700066935-870F0700..To: <sip:00492271993120 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 222572
   206 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, PUBLISH, UPDATE, MESSAGE..Supported: replaces,100rel..P-Asserted-Identity: <sip:
   41225017077 at sip.adoovoice.com>..Authorization: Digest username="pbxprisnet", realm="sip.adoovoice.com", nonce="2231175255", uri="sip:00492271993120 at 77.72.169.129:5060;transport=udp", response="dac6cac
   8d25100ee03560bab867ba1be", algorithm=MD5..Content-Type: application/sdp..Content-Length: 265..Contact: <sip:ngcp-lb at XX.XX.XX.250:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=- 20036 2
   0036 IN IP4 10.164.124.97..s=SDP data..c=IN IP4 213.55.176.206..t=0 0..m=audio 11852 RTP/AVP 0 8 9 101..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:101 telephone-event/8
   000..a=sendrecv..a=ptime:20..a=direction:active..
#################################################################################
U XX.XX.XX.250:5060 -> 77.72.169.129:5060
   INVITE sip:00492271993120 at 77.72.169.129:5060;transport=udp SIP/2.0..Record-Route: <sip:XX.XX.XX.250;r2=on;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Record-Route: <sip:127.0.0.1;r2=on
   ;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Via: SIP/2.0/UDP XX.XX.XX.250;branch=z9hG4bKd906.5531f5d10bd0fe3667091afe519d5f94.0..Via: SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;bra
   nch=z9hG4bKZ7GCaaKk;rport=5080..From: "41225017077" <sip:41225017077 at sip.adoovoice.com>;tag=0F8733E5-56B4B7B700066935-870F0700..To: <sip:00492271993120 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 222572
   206 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, PUBLISH, UPDATE, MESSAGE..Supported: replaces,100rel..P-Asserted-Identity: <sip:
   41225017077 at sip.adoovoice.com>..Authorization: Digest username="pbxprisnet", realm="sip.adoovoice.com", nonce="2231175255", uri="sip:00492271993120 at 77.72.169.129:5060;transport=udp", response="dac6cac
   8d25100ee03560bab867ba1be", algorithm=MD5..Content-Type: application/sdp..Content-Length: 265..Contact: <sip:ngcp-lb at XX.XX.XX.250:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=- 20036 2
   0036 IN IP4 10.164.124.97..s=SDP data..c=IN IP4 213.55.176.206..t=0 0..m=audio 11852 RTP/AVP 0 8 9 101..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:101 telephone-event/8
   000..a=sendrecv..a=ptime:20..a=direction:active..
############################################################################

Thank you for your help

Jephth? Feugn?



From mstorck at voipgate.com  Fri Feb  5 11:10:49 2016
From: mstorck at voipgate.com (Marc Storck)
Date: Fri, 5 Feb 2016 16:10:49 +0000
Subject: [Spce-user] MCID App issue
In-Reply-To: <56B46E8E.8030906@sipwise.com>
References: <634d081a-8463-4965-abbb-a282d8f21695@email.android.com>
 <2970CB78-9A94-41AB-8E04-63CC51B6C992@voipgate.com>
 <56B46E8E.8030906@sipwise.com>
Message-ID: <0DDF2E9C-9CDF-44A4-BF8C-FE17DE1EEF53@voipgate.com>

Great :-D

so please apply

:%s/is/was/g

to my last mail.

Regards,

Marc Storck


> On 05 Feb 2016, at 10:42, Daniel Grotti <dgrotti at sipwise.com> wrote:
> 
> Hi Marc,
> it's part of mr4.2.1 documentation.
> I introduced it when we noticed that was missing.
> 
> thanks.
> 
> DANIEL GROTTI
> Head of Customer Support
> Sipwise GmbH  <http://www.sipwise.com/>, Campus 21/Europaring F15
> AT-2345 Brunn am Gebirge
> 
> Phone:  +43(0)1 301 2032  <callto:+4313012032>
> Email:  dgrotti at sipwise.com  <mailto:dgrotti at sipwise.com>
> Website:  www.sipwise.com <http://www.sipwise.com/>
> Particulars according Austrian Companies Code paragraph 14
> "Sipwise GmbH" - Europaring F15 - 2345 Brunn am Gebirge
> FN:305595f, Commercial Court Vienna, ATU64002206
> 
> On 02/05/2016 10:36 AM, Marc Storck wrote:
>> Hello Daniel,
>> 
>> That step is missing in the documentation.
>> 
>> I?ll test tonight.
>> 
>> Regards,
>> 
>> Marc Storck
>> 
>> 
>>> On 05 Feb 2016, at 07:58, Daniel Grotti <dgrotti at sipwise.com> <mailto:dgrotti at sipwise.com> wrote:
>>> 
>>> Hi Marc,
>>> Did you flag the subscriber preferences MCID ? It should be in the Internal section.
>>> You should enable MCID there otherwise it won't work.
>>> 
>>> Daniel
>>> 
>>> On Feb 5, 2016 12:51 AM, Marc Storck <mstorck at voipgate.com> <mailto:mstorck at voipgate.com> wrote:
>>>> I just upgraded to mr4.2.1.
>>>> 
>>>> I followed the steps described in the documentation. My system was almost good, I was only missing the audio file in the sound set.
>>>> 
>>>> However the problem persists:
>>>> 
>>>> Feb  5 00:42:38 cusax (local7.notice) proxy[3552]: NOTICE: <script>: New request on proxy - M=INVITE R=sip:*57 at sld.tld;user=phone <mailto:R=sip:*57 at sld.tld;user=phone> F=sip:johndoe at sld.tld <mailto:F=sip:johndoe at sld.tld> T=sip:*57 at sld.tld;user=phone <mailto:T=sip:*57 at sld.tld;user=phone> IP=11.22.33.44:5732 (127.0.0.1:5060) ID=2639378387 at 11_22_33_44 UA='N510 IP PRO/42.210.00.000.000'
>>>> Feb  5 00:42:38 cusax (local7.notice) proxy[3552]: NOTICE: <script>: User-Provided CLI 'johndoe' taken from From-User - R=sip:*57 at sld.tld;user=phone <mailto:R=sip:*57 at sld.tld;user=phone> ID=2639378387 at 11_22_33_44 UA='N510 IP PRO/42.210.00.000.000'
>>>> Feb  5 00:42:38 cusax (local7.notice) proxy[3552]: NOTICE: <script>: User-provided CLI 'johndoe' rejected, using network-provided CLI '898910001201001' - R=sip:*57 at sld.tld;user=phone <mailto:R=sip:*57 at sld.tld;user=phone> ID=2639378387 at 11_22_33_44 UA='N510 IP PRO/42.210.00.000.000'
>>>> Feb  5 00:42:38 cusax (local7.notice) proxy[3552]: NOTICE: <script>: Setting '898910001201001 at sld.tld <mailto:898910001201001 at sld.tld>' as initiating user-provided CLI - R=sip:*57 at sld.tld;user=phone <mailto:R=sip:*57 at sld.tld;user=phone> ID=2639378387 at 11_22_33_44 UA='N510 IP PRO/42.210.00.000.000'
>>>> Feb  5 00:42:38 cusax (local7.notice) proxy[3552]: NOTICE: <script>: Setting '898910001201001 at sld.tld <mailto:898910001201001 at sld.tld>' as initiating network-provided CLI - R=sip:*57 at sld.tld;user=phone <mailto:R=sip:*57 at sld.tld;user=phone> ID=2639378387 at 11_22_33_44 UA='N510 IP PRO/42.210.00.000.000'
>>>> Feb  5 00:42:38 cusax (local7.notice) proxy[3552]: NOTICE: <script>: Rewriting called party '*57' to 'malicious_call' - R=sip:*57 at sld.tld;user=phone <mailto:R=sip:*57 at sld.tld;user=phone> ID=2639378387 at 11_22_33_44 UA='N510 IP PRO/42.210.00.000.000'
>>>> Feb  5 00:42:38 cusax (local7.err) proxy[3552]: ERROR: app_lua [app_lua_api.c:680]: app_lua_run(): error executing: del_dlg_profile (err: 2)
>>>> Feb  5 00:42:38 cusax (local7.err) proxy[3552]: ERROR: app_lua [app_lua_api.c:682]: app_lua_run(): error from Lua: /etc/kamailio/proxy/dlgcnt.lua:101: can't restore callid from $dlg_var(lua_dlg_callid): is null
>>>> Feb  5 00:42:38 cusax (local7.err) proxy[3552]: ERROR: <script>: Failed to decrease redis counters - R=sip:you at kamailio.org <mailto:R=sip:you at kamailio.org> ID=123 UA='<null>'
>>>> Feb  5 00:42:38 cusax (local7.notice) proxy[3552]: NOTICE: <script>: New request on proxy - M=ACK R=sip:*57 at sld.tld;user=phone <mailto:R=sip:*57 at sld.tld;user=phone> F=sip:johndoe at sld.tld <mailto:F=sip:johndoe at sld.tld> T=sip:*57 at sld.tld;user=phone <mailto:T=sip:*57 at sld.tld;user=phone> IP=11.22.33.44:5732 (127.0.0.1:5060) ID=2639378387 at 11_22_33_44 UA='N510 IP PRO/42.210.00.000.000'
>>>> 
>>>> Does anybody have an idea what might be the missing part?
>>>> 
>>>> Regards,
>>>> 
>>>> Marc
>>>> 
>>>> ________________________________________
>>>> From: Marc Storck
>>>> Sent: Friday, October 30, 2015 17:49
>>>> To: Kirill Solomko
>>>> Cc: spce-user at lists.sipwise.com <mailto:spce-user at lists.sipwise.com>
>>>> Subject: Re: [Spce-user] MCID App issue
>>>> 
>>>> So I set
>>>> 
>>>> store_recentcalls: ?yes'
>>>> 
>>>> followed by running
>>>> 
>>>> ngcpcfg apply
>>>> 
>>>> but the result is still quite the same:
>>>> 
>>>> Oct 30 17:45:08 cusax proxy[514]: NOTICE: <script>: Rewriting called party '*57' to 'malicious_call' - R=sip:*57 at sld.tld <mailto:R=sip:*57 at sld.tld> ID=OWU3ZmFiMDY5ZGE4ZGJkODE4ODdlMDhjMzg1MWFkYzc UA='Bria iOS release 3.4.4 stamp 31657'
>>>> Oct 30 17:45:08 cusax proxy[514]: ERROR: app_lua [app_lua_api.c:680]: app_lua_run(): error executing: del_dlg_profile (err: 2)
>>>> Oct 30 17:45:08 cusax proxy[514]: ERROR: app_lua [app_lua_api.c:682]: app_lua_run(): error from Lua: /etc/kamailio/proxy/dlgcnt.lua:101: can't restore callid from $dlg_var(lua_dlg_callid): is null
>>>> Oct 30 17:45:08 cusax proxy[514]: ERROR: <script>: Failed to decrease redis counters - R=sip:you at kamailio.org <mailto:R=sip:you at kamailio.org> ID=123 UA='<null>'
>>>> 
>>>> Regards,
>>>> 
>>>> Marc
>>>> 
>>>>> On 30 Oct 2015, at 17:42, Kirill Solomko <ksolomko at sipwise.com> <mailto:ksolomko at sipwise.com> wrote:
>>>>> 
>>>>> Hi Mark,
>>>>> 
>>>>> You should also enable ?recent calls? support in config.yml
>>>>> 
>>>>> kamailio:
>>>>>   proxy:
>>>>>     store_recentcalls: ?yes'
>>>>> 
>>>>>> On 30 Oct 2015, at 17:24, Marc Storck <mstorck at voipgate.com> <mailto:mstorck at voipgate.com> wrote:
>>>>>> 
>>>>>> Good evening,
>>>>>> 
>>>>>> I?m having this problem with the MCID app:
>>>>>> 
>>>>>> Oct 30 17:21:34 cusax proxy[23526]: NOTICE: <script>: Rewriting called party '*57' to 'malicious_call' - R=sip:*57 at sld.tld <mailto:R=sip:*57 at sld.tld> ID=YmE5NDYzOWMyMWE2NWY0MjE3YTMwYWRkMDVkMjcwOWI UA='Bria iOS release 3.4.4 stamp 31657'
>>>>>> Oct 30 17:21:34 cusax proxy[23526]: ERROR: app_lua [app_lua_api.c:680]: app_lua_run(): error executing: del_dlg_profile (err: 2)
>>>>>> Oct 30 17:21:34 cusax proxy[23526]: ERROR: app_lua [app_lua_api.c:682]: app_lua_run(): error from Lua: /etc/kamailio/proxy/dlgcnt.lua:101: can't restore callid from $dlg_var(lua_dlg_callid): is null
>>>>>> Oct 30 17:21:34 cusax proxy[23526]: ERROR: <script>: Failed to decrease redis counters - R=sip:you at kamailio.org <mailto:R=sip:you at kamailio.org> ID=123 UA='<null>?
>>>>>> 
>>>>>> I activated the MCID app in config.yml, are there any further changes required?
>>>>>> 
>>>>>> Regards,
>>>>>> 
>>>>>> Marc
>>>>>> _______________________________________________
>>>>>> Spce-user mailing list
>>>>>> Spce-user at lists.sipwise.com <mailto:Spce-user at lists.sipwise.com>
>>>>>> https://lists.sipwise.com/listinfo/spce-user <https://lists.sipwise.com/listinfo/spce-user>
>>>>> Kind regards,
>>>>> Kirill
>>>> _______________________________________________
>>>> Spce-user mailing list
>>>> Spce-user at lists.sipwise.com <mailto:Spce-user at lists.sipwise.com>
>>>> https://lists.sipwise.com/listinfo/spce-user <https://lists.sipwise.com/listinfo/spce-user>
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20160205/88976a35/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 841 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20160205/88976a35/attachment.asc>

From agranig at sipwise.com  Fri Feb  5 11:12:01 2016
From: agranig at sipwise.com (Andreas Granig)
Date: Fri, 5 Feb 2016 17:12:01 +0100
Subject: [Spce-user] Trunk to voicetrading configuration
In-Reply-To: <56B4B8C1.5060203@prisnets.ch>
References: <56B4B8C1.5060203@prisnets.ch>
Message-ID: <56B4C9D1.1090008@sipwise.com>

Hi,

>From the trace you provided, it seems your request just times out, as
there is no reply at all from your peer. No idea if they do this because
you're not sending the 00000 prefix you mentioned.

Create a new rewrite rule set and put a rule like "^(.+)$" => "00000\1"
into the outbound callee rule and assign this rule set in the peer
preferences of your configured peering server.

Please read carefully the handbook provided with the CE installation,
specifically the configuration of peerings and peering rules.

Andreas

On 02/05/2016 03:59 PM, Jephth? Feugn? wrote:
> Hello,
> I've been trying for weeks to have my trunk to voicetrading working with
> no success. I also tried a sip trunk to my GSM gateway with the same
> result. No ringing to the calle side, and no sound no ringing tone by
> the caller side.
> 
> Can some one please can help me solve this problem?
> 
> Here is what I have during call with the command "ngrep sip" executed on
> the sipwise CE 4.2.1  server. Voicetrading is  expecting for premium
> route on their side, the number to be perpended with "00000",
> xx.xx.xx.250 is the IP address of my sipwise CE 4.2.1 server:
> 
> 
> XX.XX.XX.250:5060 -> 77.72.169.129:5060
>   INVITE sip:00492271993120 at 77.72.169.129:5060;transport=udp
> SIP/2.0..Record-Route:
> <sip:XX.XX.XX.250;r2=on;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Record-Route:
> <sip:127.0.0.1;r2=on
>   ;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Via:
> SIP/2.0/UDP
> XX.XX.XX.250;branch=z9hG4bKd906.5531f5d10bd0fe3667091afe519d5f94.0..Via:
> SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;bra
>   nch=z9hG4bKZ7GCaaKk;rport=5080..From: "41225017077"
> <sip:41225017077 at sip.adoovoice.com>;tag=0F8733E5-56B4B7B700066935-870F0700..To:
> <sip:00492271993120 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 222572
>   206 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE, PRACK, ACK,
> BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, PUBLISH, UPDATE,
> MESSAGE..Supported: replaces,100rel..P-Asserted-Identity: <sip:
>   41225017077 at sip.adoovoice.com>..Authorization: Digest
> username="pbxprisnet", realm="sip.adoovoice.com", nonce="2231175255",
> uri="sip:00492271993120 at 77.72.169.129:5060;transport=udp",
> response="dac6cac
>   8d25100ee03560bab867ba1be", algorithm=MD5..Content-Type:
> application/sdp..Content-Length: 265..Contact:
> <sip:ngcp-lb at XX.XX.XX.250:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=-
> 20036 2
>   0036 IN IP4 10.164.124.97..s=SDP data..c=IN IP4 213.55.176.206..t=0
> 0..m=audio 11852 RTP/AVP 0 8 9 101..a=rtpmap:0 PCMU/8000..a=rtpmap:8
> PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:101 telephone-event/8
>   000..a=sendrecv..a=ptime:20..a=direction:active..
> #####################
> U XX.XX.XX.250:5060 -> 77.72.169.129:5060
>   INVITE sip:00492271993120 at 77.72.169.129:5060;transport=udp
> SIP/2.0..Record-Route:
> <sip:XX.XX.XX.250;r2=on;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Record-Route:
> <sip:127.0.0.1;r2=on
>   ;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Via:
> SIP/2.0/UDP
> XX.XX.XX.250;branch=z9hG4bKd906.5531f5d10bd0fe3667091afe519d5f94.0..Via:
> SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;bra
>   nch=z9hG4bKZ7GCaaKk;rport=5080..From: "41225017077"
> <sip:41225017077 at sip.adoovoice.com>;tag=0F8733E5-56B4B7B700066935-870F0700..To:
> <sip:00492271993120 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 222572
>   206 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE, PRACK, ACK,
> BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, PUBLISH, UPDATE,
> MESSAGE..Supported: replaces,100rel..P-Asserted-Identity: <sip:
>   41225017077 at sip.adoovoice.com>..Authorization: Digest
> username="pbxprisnet", realm="sip.adoovoice.com", nonce="2231175255",
> uri="sip:00492271993120 at 77.72.169.129:5060;transport=udp",
> response="dac6cac
>   8d25100ee03560bab867ba1be", algorithm=MD5..Content-Type:
> application/sdp..Content-Length: 265..Contact:
> <sip:ngcp-lb at XX.XX.XX.250:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=-
> 20036 2
>   0036 IN IP4 10.164.124.97..s=SDP data..c=IN IP4 213.55.176.206..t=0
> 0..m=audio 11852 RTP/AVP 0 8 9 101..a=rtpmap:0 PCMU/8000..a=rtpmap:8
> PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:101 telephone-event/8
>   000..a=sendrecv..a=ptime:20..a=direction:active..
> #######################
> U XX.XX.XX.250:5060 -> 77.72.169.129:5060
>   INVITE sip:00492271993120 at 77.72.169.129:5060;transport=udp
> SIP/2.0..Record-Route:
> <sip:XX.XX.XX.250;r2=on;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Record-Route:
> <sip:127.0.0.1;r2=on
>   ;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Via:
> SIP/2.0/UDP
> XX.XX.XX.250;branch=z9hG4bKd906.5531f5d10bd0fe3667091afe519d5f94.0..Via:
> SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;bra
>   nch=z9hG4bKZ7GCaaKk;rport=5080..From: "41225017077"
> <sip:41225017077 at sip.adoovoice.com>;tag=0F8733E5-56B4B7B700066935-870F0700..To:
> <sip:00492271993120 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 222572
>   206 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE, PRACK, ACK,
> BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, PUBLISH, UPDATE,
> MESSAGE..Supported: replaces,100rel..P-Asserted-Identity: <sip:
>   41225017077 at sip.adoovoice.com>..Authorization: Digest
> username="pbxprisnet", realm="sip.adoovoice.com", nonce="2231175255",
> uri="sip:00492271993120 at 77.72.169.129:5060;transport=udp",
> response="dac6cac
>   8d25100ee03560bab867ba1be", algorithm=MD5..Content-Type:
> application/sdp..Content-Length: 265..Contact:
> <sip:ngcp-lb at XX.XX.XX.250:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=-
> 20036 2
>   0036 IN IP4 10.164.124.97..s=SDP data..c=IN IP4 213.55.176.206..t=0
> 0..m=audio 11852 RTP/AVP 0 8 9 101..a=rtpmap:0 PCMU/8000..a=rtpmap:8
> PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:101 telephone-event/8
>   000..a=sendrecv..a=ptime:20..a=direction:active..
> #########################################
> U XX.XX.XX.250:5060 -> 77.72.169.129:5060
>   INVITE sip:00492271993120 at 77.72.169.129:5060;transport=udp
> SIP/2.0..Record-Route:
> <sip:XX.XX.XX.250;r2=on;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Record-Route:
> <sip:127.0.0.1;r2=on
>   ;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Via:
> SIP/2.0/UDP
> XX.XX.XX.250;branch=z9hG4bKd906.5531f5d10bd0fe3667091afe519d5f94.0..Via:
> SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;bra
>   nch=z9hG4bKZ7GCaaKk;rport=5080..From: "41225017077"
> <sip:41225017077 at sip.adoovoice.com>;tag=0F8733E5-56B4B7B700066935-870F0700..To:
> <sip:00492271993120 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 222572
>   206 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE, PRACK, ACK,
> BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, PUBLISH, UPDATE,
> MESSAGE..Supported: replaces,100rel..P-Asserted-Identity: <sip:
>   41225017077 at sip.adoovoice.com>..Authorization: Digest
> username="pbxprisnet", realm="sip.adoovoice.com", nonce="2231175255",
> uri="sip:00492271993120 at 77.72.169.129:5060;transport=udp",
> response="dac6cac
>   8d25100ee03560bab867ba1be", algorithm=MD5..Content-Type:
> application/sdp..Content-Length: 265..Contact:
> <sip:ngcp-lb at XX.XX.XX.250:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=-
> 20036 2
>   0036 IN IP4 10.164.124.97..s=SDP data..c=IN IP4 213.55.176.206..t=0
> 0..m=audio 11852 RTP/AVP 0 8 9 101..a=rtpmap:0 PCMU/8000..a=rtpmap:8
> PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:101 telephone-event/8
>   000..a=sendrecv..a=ptime:20..a=direction:active..
> #################################################################################
> 
> U XX.XX.XX.250:5060 -> 77.72.169.129:5060
>   INVITE sip:00492271993120 at 77.72.169.129:5060;transport=udp
> SIP/2.0..Record-Route:
> <sip:XX.XX.XX.250;r2=on;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Record-Route:
> <sip:127.0.0.1;r2=on
>   ;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Via:
> SIP/2.0/UDP
> XX.XX.XX.250;branch=z9hG4bKd906.5531f5d10bd0fe3667091afe519d5f94.0..Via:
> SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;bra
>   nch=z9hG4bKZ7GCaaKk;rport=5080..From: "41225017077"
> <sip:41225017077 at sip.adoovoice.com>;tag=0F8733E5-56B4B7B700066935-870F0700..To:
> <sip:00492271993120 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 222572
>   206 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE, PRACK, ACK,
> BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, PUBLISH, UPDATE,
> MESSAGE..Supported: replaces,100rel..P-Asserted-Identity: <sip:
>   41225017077 at sip.adoovoice.com>..Authorization: Digest
> username="pbxprisnet", realm="sip.adoovoice.com", nonce="2231175255",
> uri="sip:00492271993120 at 77.72.169.129:5060;transport=udp",
> response="dac6cac
>   8d25100ee03560bab867ba1be", algorithm=MD5..Content-Type:
> application/sdp..Content-Length: 265..Contact:
> <sip:ngcp-lb at XX.XX.XX.250:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=-
> 20036 2
>   0036 IN IP4 10.164.124.97..s=SDP data..c=IN IP4 213.55.176.206..t=0
> 0..m=audio 11852 RTP/AVP 0 8 9 101..a=rtpmap:0 PCMU/8000..a=rtpmap:8
> PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:101 telephone-event/8
>   000..a=sendrecv..a=ptime:20..a=direction:active..
> ############################################################################
> 
> 
> Thank you for your help
> 
> Jephth? Feugn?
> 
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user


From dgrotti at sipwise.com  Fri Feb  5 11:15:41 2016
From: dgrotti at sipwise.com (Daniel Grotti)
Date: Fri, 05 Feb 2016 17:15:41 +0100
Subject: [Spce-user] MCID App issue
In-Reply-To: <0DDF2E9C-9CDF-44A4-BF8C-FE17DE1EEF53@voipgate.com>
Message-ID: <deb9b9dc-af14-4fa5-882c-9ca6097ed06d@email.android.com>

An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20160205/b64c93c8/attachment.html>

From me at nevian.org  Fri Feb  5 13:09:54 2016
From: me at nevian.org (Serge Yuriev)
Date: Fri, 5 Feb 2016 21:09:54 +0300
Subject: [Spce-user] Trunk to voicetrading configuration
In-Reply-To: <56B4B8C1.5060203@prisnets.ch>
References: <56B4B8C1.5060203@prisnets.ch>
Message-ID: <C0EFEFFE-2D76-4177-A2AB-72ECE0151145@nevian.org>

Hello,

You said you can't use your GSM-gw also..
Looks like firewall issue to me.
Are you able to just ping your destinations and back?

-- 
Wbr, Serge via mobile

05.02.2016, 17:59, "Jephth? Feugn?" <j.feugne at prisnets.ch>:
> 
> Hello,
> I've been trying for weeks to have my trunk to voicetrading working with no success. I also tried a sip trunk to my GSM gateway with the same
> result. No ringing to the calle side, and no sound no ringing tone by the caller side.
> 
> Can some one please can help me solve this problem?
> 
> Here is what I have during call with the command "ngrep sip" executed on the sipwise CE 4.2.1 server. Voicetrading is expecting for premium
> route on their side, the number to be perpended with "00000", xx.xx.xx.250 is the IP address of my sipwise CE 4.2.1 server:
> 
> 
> XX.XX.XX.250:5060 -> 77.72.169.129:5060
>    INVITE sip:00492271993120 at 77.72.169.129:5060;transport=udp SIP/2.0..Record-Route: <sip:XX.XX.XX.250;r2=on;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Record-Route: <sip:127.0.0.1;r2=on
>    ;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Via: SIP/2.0/UDP XX.XX.XX.250;branch=z9hG4bKd906.5531f5d10bd0fe3667091afe519d5f94.0..Via: SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;bra
>    nch=z9hG4bKZ7GCaaKk;rport=5080..From: "41225017077" <sip:41225017077 at sip.adoovoice.com>;tag=0F8733E5-56B4B7B700066935-870F0700..To: <sip:00492271993120 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 222572
>    206 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, PUBLISH, UPDATE, MESSAGE..Supported: replaces,100rel..P-Asserted-Identity: <sip:
>    41225017077 at sip.adoovoice.com>..Authorization: Digest username="pbxprisnet", realm="sip.adoovoice.com", nonce="2231175255", uri="sip:00492271993120 at 77.72.169.129:5060;transport=udp", response="dac6cac
>    8d25100ee03560bab867ba1be", algorithm=MD5..Content-Type: application/sdp..Content-Length: 265..Contact: <sip:ngcp-lb at XX.XX.XX.250:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=- 20036 2
>    0036 IN IP4 10.164.124.97..s=SDP data..c=IN IP4 213.55.176.206..t=0 0..m=audio 11852 RTP/AVP 0 8 9 101..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:101 telephone-event/8
>    000..a=sendrecv..a=ptime:20..a=direction:active..
> #####################
> U XX.XX.XX.250:5060 -> 77.72.169.129:5060
>    INVITE sip:00492271993120 at 77.72.169.129:5060;transport=udp SIP/2.0..Record-Route: <sip:XX.XX.XX.250;r2=on;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Record-Route: <sip:127.0.0.1;r2=on
>    ;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Via: SIP/2.0/UDP XX.XX.XX.250;branch=z9hG4bKd906.5531f5d10bd0fe3667091afe519d5f94.0..Via: SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;bra
>    nch=z9hG4bKZ7GCaaKk;rport=5080..From: "41225017077" <sip:41225017077 at sip.adoovoice.com>;tag=0F8733E5-56B4B7B700066935-870F0700..To: <sip:00492271993120 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 222572
>    206 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, PUBLISH, UPDATE, MESSAGE..Supported: replaces,100rel..P-Asserted-Identity: <sip:
>    41225017077 at sip.adoovoice.com>..Authorization: Digest username="pbxprisnet", realm="sip.adoovoice.com", nonce="2231175255", uri="sip:00492271993120 at 77.72.169.129:5060;transport=udp", response="dac6cac
>    8d25100ee03560bab867ba1be", algorithm=MD5..Content-Type: application/sdp..Content-Length: 265..Contact: <sip:ngcp-lb at XX.XX.XX.250:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=- 20036 2
>    0036 IN IP4 10.164.124.97..s=SDP data..c=IN IP4 213.55.176.206..t=0 0..m=audio 11852 RTP/AVP 0 8 9 101..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:101 telephone-event/8
>    000..a=sendrecv..a=ptime:20..a=direction:active..
> #######################
> U XX.XX.XX.250:5060 -> 77.72.169.129:5060
>    INVITE sip:00492271993120 at 77.72.169.129:5060;transport=udp SIP/2.0..Record-Route: <sip:XX.XX.XX.250;r2=on;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Record-Route: <sip:127.0.0.1;r2=on
>    ;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Via: SIP/2.0/UDP XX.XX.XX.250;branch=z9hG4bKd906.5531f5d10bd0fe3667091afe519d5f94.0..Via: SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;bra
>    nch=z9hG4bKZ7GCaaKk;rport=5080..From: "41225017077" <sip:41225017077 at sip.adoovoice.com>;tag=0F8733E5-56B4B7B700066935-870F0700..To: <sip:00492271993120 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 222572
>    206 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, PUBLISH, UPDATE, MESSAGE..Supported: replaces,100rel..P-Asserted-Identity: <sip:
>    41225017077 at sip.adoovoice.com>..Authorization: Digest username="pbxprisnet", realm="sip.adoovoice.com", nonce="2231175255", uri="sip:00492271993120 at 77.72.169.129:5060;transport=udp", response="dac6cac
>    8d25100ee03560bab867ba1be", algorithm=MD5..Content-Type: application/sdp..Content-Length: 265..Contact: <sip:ngcp-lb at XX.XX.XX.250:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=- 20036 2
>    0036 IN IP4 10.164.124.97..s=SDP data..c=IN IP4 213.55.176.206..t=0 0..m=audio 11852 RTP/AVP 0 8 9 101..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:101 telephone-event/8
>    000..a=sendrecv..a=ptime:20..a=direction:active..
> #########################################
> U XX.XX.XX.250:5060 -> 77.72.169.129:5060
>    INVITE sip:00492271993120 at 77.72.169.129:5060;transport=udp SIP/2.0..Record-Route: <sip:XX.XX.XX.250;r2=on;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Record-Route: <sip:127.0.0.1;r2=on
>    ;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Via: SIP/2.0/UDP XX.XX.XX.250;branch=z9hG4bKd906.5531f5d10bd0fe3667091afe519d5f94.0..Via: SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;bra
>    nch=z9hG4bKZ7GCaaKk;rport=5080..From: "41225017077" <sip:41225017077 at sip.adoovoice.com>;tag=0F8733E5-56B4B7B700066935-870F0700..To: <sip:00492271993120 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 222572
>    206 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, PUBLISH, UPDATE, MESSAGE..Supported: replaces,100rel..P-Asserted-Identity: <sip:
>    41225017077 at sip.adoovoice.com>..Authorization: Digest username="pbxprisnet", realm="sip.adoovoice.com", nonce="2231175255", uri="sip:00492271993120 at 77.72.169.129:5060;transport=udp", response="dac6cac
>    8d25100ee03560bab867ba1be", algorithm=MD5..Content-Type: application/sdp..Content-Length: 265..Contact: <sip:ngcp-lb at XX.XX.XX.250:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=- 20036 2
>    0036 IN IP4 10.164.124.97..s=SDP data..c=IN IP4 213.55.176.206..t=0 0..m=audio 11852 RTP/AVP 0 8 9 101..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:101 telephone-event/8
>    000..a=sendrecv..a=ptime:20..a=direction:active..
> #################################################################################
> U XX.XX.XX.250:5060 -> 77.72.169.129:5060
>    INVITE sip:00492271993120 at 77.72.169.129:5060;transport=udp SIP/2.0..Record-Route: <sip:XX.XX.XX.250;r2=on;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Record-Route: <sip:127.0.0.1;r2=on
>    ;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Via: SIP/2.0/UDP XX.XX.XX.250;branch=z9hG4bKd906.5531f5d10bd0fe3667091afe519d5f94.0..Via: SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;bra
>    nch=z9hG4bKZ7GCaaKk;rport=5080..From: "41225017077" <sip:41225017077 at sip.adoovoice.com>;tag=0F8733E5-56B4B7B700066935-870F0700..To: <sip:00492271993120 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 222572
>    206 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, PUBLISH, UPDATE, MESSAGE..Supported: replaces,100rel..P-Asserted-Identity: <sip:
>    41225017077 at sip.adoovoice.com>..Authorization: Digest username="pbxprisnet", realm="sip.adoovoice.com", nonce="2231175255", uri="sip:00492271993120 at 77.72.169.129:5060;transport=udp", response="dac6cac
>    8d25100ee03560bab867ba1be", algorithm=MD5..Content-Type: application/sdp..Content-Length: 265..Contact: <sip:ngcp-lb at XX.XX.XX.250:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=- 20036 2
>    0036 IN IP4 10.164.124.97..s=SDP data..c=IN IP4 213.55.176.206..t=0 0..m=audio 11852 RTP/AVP 0 8 9 101..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:101 telephone-event/8
>    000..a=sendrecv..a=ptime:20..a=direction:active..
> ############################################################################
> 
> Thank you for your help
> 
> Jephth? Feugn?
> 
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
> 


From j.feugne at prisnets.ch  Fri Feb  5 13:15:12 2016
From: j.feugne at prisnets.ch (=?UTF-8?Q?Jephth=c3=a9_Feugn=c3=a9?=)
Date: Fri, 5 Feb 2016 19:15:12 +0100
Subject: [Spce-user] Trunk to voicetrading configuration
In-Reply-To: <56B4C9D1.1090008@sipwise.com>
References: <56B4B8C1.5060203@prisnets.ch> <56B4C9D1.1090008@sipwise.com>
Message-ID: <56B4E6B0.5090307@prisnets.ch>

Hi,
Thank you for your reply. I unfortunately disable one of my rewrite rule 
by the time I made the call. I Cross check the rules once more and here 
is the result when I place call. still no ring both on the caller and 
callee  side:


        U xx.xx.xx.2:5060 -> 77.72.169.129:5060
                   INVITE
        sip:0000041227312221 at 77.72.169.129:5060;transport=udp
        SIP/2.0..Record-Route:
        <sip:xx.xx.xx.2;r2=on;lr=on;ftag=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>..Record-Route:
        <sip:127.0.0.1;r2=
        on;lr=on;ftag=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>..Via:
        SIP/2.0/UDP
        xx.xx.xx.2;branch=z9hG4bKe854.61a0e861a7f1d69a32327173a5932390.0..Via:
        SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;b
        ranch=z9hG4bKtn6UJa1a;rport=5080..From: "41225017077"
        <sip:41225017077 at sip.adoovoice.com>;tag=16EE36B8-56B4E5C400006FEF-86FEF700..To:
        <sip:0000041227312221 at 77.72.169.129>..CSeq: 10 INVITE..Call-ID: 50
        4974996 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE,
        PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE,
        PUBLISH, UPDATE, MESSAGE..Supported:
        replaces,100rel..P-Asserted-Identity: <
        sip:41225017077 at sip.adoovoice.com>..Content-Type:
        application/sdp..Content-Length: 265..Contact:
        <sip:ngcp-lb at xx.xx.xx.2:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=-
        20054 20054 IN
                    IP4 10.164.124.97..s=SDP data..c=IN IP4
        213.55.176.206..t=0 0..m=audio 11888 RTP/AVP 0 8 9
        101..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:9
        G722/8000..a=rtpmap:101 telephone-event/8000..a=
        sendrecv..a=ptime:20..a=direction:active..
                 ##
                 U 77.72.169.129:5060 -> xx.xx.xx.2:5060
                   SIP/2.0 401 Unauthorized..Via: SIP/2.0/UDP
        xx.xx.xx.2:5060;branch=z9hG4bKe854.61a0e861a7f1d69a32327173a5932390.0..Via:
        SIP/2.0/UDP
        127.0.0.1:5080;received=127.0.0.1;branch=z9hG4bKtn6UJa1a;rport=508
                   0..From: "41225017077"
        <sip:41225017077 at sip.adoovoice.com>;tag=16EE36B8-56B4E5C400006FEF-86FEF700..To:
        <sip:0000041227312221 at 77.72.169.129>..Contact:
        sip:0000041227312221 at 77.72.169.129:5060..Call-ID:
        504974996 at 10.20.12.202_b2b-1..CSeq: 10 INVITE..Server: (Very
        nice Sip Registrar/Proxy Server)..Allow:
        ACK,BYE,CANCEL,INVITE,REGISTER,OPTIONS,INFO,MESSAGE..Record-route:
        <sip:xx.xx.xx.2;r2=on;lr;fta
        g=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>,<sip:127.0.0.1;r2=on;lr;ftag=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>..WWW-Authenticate:
        Digest realm="sip.adoovoice.com",nonce="2242964208",algo
                   rithm=MD5..Content-Length: 0....
                 #
                 U xx.xx.xx.2:5060 -> 77.72.169.129:5060
                   ACK
        sip:0000041227312221 at 77.72.169.129:5060;transport=udp
        SIP/2.0..Max-Forwards: 70..Record-Route:
        <sip:xx.xx.xx.2;r2=on;lr=on;ftag=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>..Record-Route:
        <si
        p:127.0.0.1;r2=on;lr=on;ftag=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>..Via:
        SIP/2.0/UDP
        xx.xx.xx.2;branch=z9hG4bKe854.61a0e861a7f1d69a32327173a5932390.0..Via:
        SIP/2.0/UDP 127.0.0.1:5080;recei
        ved=127.0.0.1;branch=z9hG4bKtn6UJa1a;rport=5080..From:
        "41225017077"
        <sip:41225017077 at sip.adoovoice.com>;tag=16EE36B8-56B4E5C400006FEF-86FEF700..To:
        <sip:0000041227312221 at 77.72.169.129>..Call-ID: 5049
        74996 at 10.20.12.202_b2b-1..CSeq: 10 ACK..Content-Length: 0....
                 #
                 U xx.xx.xx.2:5060 -> 77.72.169.129:5060
                   INVITE
        sip:0000041227312221 at 77.72.169.129:5060;transport=udp
        SIP/2.0..Record-Route:
        <sip:xx.xx.xx.2;r2=on;lr=on;ftag=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>..Record-Route:
        <sip:127.0.0.1;r2=
        on;lr=on;ftag=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>..Via:
        SIP/2.0/UDP
        xx.xx.xx.2;branch=z9hG4bKf854.44da301080c743aeec10ba45573ba2e4.0..Via:
        SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;b
        ranch=z9hG4bKkKgwgaE0;rport=5080..From: "41225017077"
        <sip:41225017077 at sip.adoovoice.com>;tag=16EE36B8-56B4E5C400006FEF-86FEF700..To:
        <sip:0000041227312221 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 50
        4974996 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE,
        PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE,
        PUBLISH, UPDATE, MESSAGE..Supported:
        replaces,100rel..P-Asserted-Identity: <
        sip:41225017077 at sip.adoovoice.com>..Authorization: Digest
        username="pbxprisnet", realm="sip.adoovoice.com",
        nonce="2242964208",
        uri="sip:0000041227312221 at 77.72.169.129:5060;transport=udp",
        response="9
        53a2ba986e16d9d2c3564149681dd58", algorithm=MD5..Content-Type:
        application/sdp..Content-Length: 265..Contact:
        <sip:ngcp-lb at xx.xx.xx.2:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=-
        2
                   0054 20054 IN IP4 10.164.124.97..s=SDP data..c=IN IP4
        213.55.176.206..t=0 0..m=audio 11888 RTP/AVP 0 8 9
        101..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:9
        G722/8000..a=rtpmap:101 telephone-e
        vent/8000..a=sendrecv..a=ptime:20..a=direction:active..
                 ########################
                 U xx.xx.xx.2:5060 -> 77.72.169.129:5060
                   INVITE
        sip:0000041227312221 at 77.72.169.129:5060;transport=udp
        SIP/2.0..Record-Route:
        <sip:xx.xx.xx.2;r2=on;lr=on;ftag=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>..Record-Route:
        <sip:127.0.0.1;r2=
        on;lr=on;ftag=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>..Via:
        SIP/2.0/UDP
        xx.xx.xx.2;branch=z9hG4bKf854.44da301080c743aeec10ba45573ba2e4.0..Via:
        SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;b
        ranch=z9hG4bKkKgwgaE0;rport=5080..From: "41225017077"
        <sip:41225017077 at sip.adoovoice.com>;tag=16EE36B8-56B4E5C400006FEF-86FEF700..To:
        <sip:0000041227312221 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 50
        4974996 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE,
        PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE,
        PUBLISH, UPDATE, MESSAGE..Supported:
        replaces,100rel..P-Asserted-Identity: <
        sip:41225017077 at sip.adoovoice.com>..Authorization: Digest
        username="pbxprisnet", realm="sip.adoovoice.com",
        nonce="2242964208",
        uri="sip:0000041227312221 at 77.72.169.129:5060;transport=udp",
        response="9
        53a2ba986e16d9d2c3564149681dd58", algorithm=MD5..Content-Type:
        application/sdp..Content-Length: 265..Contact:
        <sip:ngcp-lb at xx.xx.xx.2:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=-
        2
                   0054 20054 IN IP4 10.164.124.97..s=SDP data..c=IN IP4
        213.55.176.206..t=0 0..m=audio 11888 RTP/AVP 0 8 9
        101..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:9
        G722/8000..a=rtpmap:101 telephone-e
        vent/8000..a=sendrecv..a=ptime:20..a=direction:active..
                 #########################
                 U xx.xx.xx.2:5060 -> 77.72.169.129:5060
                   INVITE
        sip:0000041227312221 at 77.72.169.129:5060;transport=udp
        SIP/2.0..Record-Route:
        <sip:xx.xx.xx.2;r2=on;lr=on;ftag=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>..Record-Route:
        <sip:127.0.0.1;r2=
        on;lr=on;ftag=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>..Via:
        SIP/2.0/UDP
        xx.xx.xx.2;branch=z9hG4bKf854.44da301080c743aeec10ba45573ba2e4.0..Via:
        SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;b
        ranch=z9hG4bKkKgwgaE0;rport=5080..From: "41225017077"
        <sip:41225017077 at sip.adoovoice.com>;tag=16EE36B8-56B4E5C400006FEF-86FEF700..To:
        <sip:0000041227312221 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 50
        4974996 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE,
        PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE,
        PUBLISH, UPDATE, MESSAGE..Supported:
        replaces,100rel..P-Asserted-Identity: <
        sip:41225017077 at sip.adoovoice.com>..Authorization: Digest
        username="pbxprisnet", realm="sip.adoovoice.com",
        nonce="2242964208",
        uri="sip:0000041227312221 at 77.72.169.129:5060;transport=udp",
        response="9
        53a2ba986e16d9d2c3564149681dd58", algorithm=MD5..Content-Type:
        application/sdp..Content-Length: 265..Contact:
        <sip:ngcp-lb at xx.xx.xx.2:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=-
        2
                   0054 20054 IN IP4 10.164.124.97..s=SDP data..c=IN IP4
        213.55.176.206..t=0 0..m=audio 11888 RTP/AVP 0 8 9
        101..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:9
        G722/8000..a=rtpmap:101 telephone-e
        vent/8000..a=sendrecv..a=ptime:20..a=direction:active..
        #############################################
                 U xx.xx.xx.2:5060 -> 77.72.169.129:5060
                   INVITE
        sip:0000041227312221 at 77.72.169.129:5060;transport=udp
        SIP/2.0..Record-Route:
        <sip:xx.xx.xx.2;r2=on;lr=on;ftag=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>..Record-Route:
        <sip:127.0.0.1;r2=
        on;lr=on;ftag=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>..Via:
        SIP/2.0/UDP
        xx.xx.xx.2;branch=z9hG4bKf854.44da301080c743aeec10ba45573ba2e4.0..Via:
        SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;b
        ranch=z9hG4bKkKgwgaE0;rport=5080..From: "41225017077"
        <sip:41225017077 at sip.adoovoice.com>;tag=16EE36B8-56B4E5C400006FEF-86FEF700..To:
        <sip:0000041227312221 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 50
        4974996 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE,
        PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE,
        PUBLISH, UPDATE, MESSAGE..Supported:
        replaces,100rel..P-Asserted-Identity: <
        sip:41225017077 at sip.adoovoice.com>..Authorization: Digest
        username="pbxprisnet", realm="sip.adoovoice.com",
        nonce="2242964208",
        uri="sip:0000041227312221 at 77.72.169.129:5060;transport=udp",
        response="9
        53a2ba986e16d9d2c3564149681dd58", algorithm=MD5..Content-Type:
        application/sdp..Content-Length: 265..Contact:
        <sip:ngcp-lb at xx.xx.xx.2:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=-
        2
                   0054 20054 IN IP4 10.164.124.97..s=SDP data..c=IN IP4
        213.55.176.206..t=0 0..m=audio 11888 RTP/AVP 0 8 9
        101..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:9
        G722/8000..a=rtpmap:101 telephone-e
        vent/8000..a=sendrecv..a=ptime:20..a=direction:active..
        #################################################################################
                 U xx.xx.xx.2:5060 -> 77.72.169.129:5060
                   INVITE
        sip:0000041227312221 at 77.72.169.129:5060;transport=udp
        SIP/2.0..Record-Route:
        <sip:xx.xx.xx.2;r2=on;lr=on;ftag=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>..Record-Route:
        <sip:127.0.0.1;r2=
        on;lr=on;ftag=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>..Via:
        SIP/2.0/UDP
        xx.xx.xx.2;branch=z9hG4bKf854.44da301080c743aeec10ba45573ba2e4.0..Via:
        SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;b
        ranch=z9hG4bKkKgwgaE0;rport=5080..From: "41225017077"
        <sip:41225017077 at sip.adoovoice.com>;tag=16EE36B8-56B4E5C400006FEF-86FEF700..To:
        <sip:0000041227312221 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 50
        4974996 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE,
        PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE,
        PUBLISH, UPDATE, MESSAGE..Supported:
        replaces,100rel..P-Asserted-Identity: <
        sip:41225017077 at sip.adoovoice.com>..Authorization: Digest
        username="pbxprisnet", realm="sip.adoovoice.com",
        nonce="2242964208",
        uri="sip:0000041227312221 at 77.72.169.129:5060;transport=udp",
        response="9
        53a2ba986e16d9d2c3564149681dd58", algorithm=MD5..Content-Type:
        application/sdp..Content-Length: 265..Contact:
        <sip:ngcp-lb at xx.xx.xx.2:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=-
        2
                   0054 20054 IN IP4 10.164.124.97..s=SDP data..c=IN IP4
        213.55.176.206..t=0 0..m=audio 11888 RTP/AVP 0 8 9
        101..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:9
        G722/8000..a=rtpmap:101 telephone-e
        vent/8000..a=sendrecv..a=ptime:20..a=direction:active..
        ################################################################################################
                 T 213.55.176.206:31002 -> xx.xx.xx.2:5060 [AP]
                   CANCEL sip:0227312221 at sip.adoovoice.com:5060
        SIP/2.0..Via: SIP/2.0/TCP
        10.20.12.202:5063;branch=z9hG4bK2530177975..From: "balmer"
        <sip:balmer at sip.adoovoice.com>;tag=801761386..To:
        <sip:0227312221 at sip.
                   adoovoice.com>..Call-ID:
        504974996 at 10.20.12.202..CSeq: 2 CANCEL..Max-Forwards:
        70..User-Agent: Yealink SIP-W52P 25.73.0.40..Content-Length: 0....
                 #



Le 05. 02. 16 17:12, Andreas Granig a ?crit :
> Hi,
>
>  From the trace you provided, it seems your request just times out, as
> there is no reply at all from your peer. No idea if they do this because
> you're not sending the 00000 prefix you mentioned.
>
> Create a new rewrite rule set and put a rule like "^(.+)$" => "00000\1"
> into the outbound callee rule and assign this rule set in the peer
> preferences of your configured peering server.
>
> Please read carefully the handbook provided with the CE installation,
> specifically the configuration of peerings and peering rules.
>
> Andreas
>
> On 02/05/2016 03:59 PM, Jephth? Feugn? wrote:
>> Hello,
>> I've been trying for weeks to have my trunk to voicetrading working with
>> no success. I also tried a sip trunk to my GSM gateway with the same
>> result. No ringing to the calle side, and no sound no ringing tone by
>> the caller side.
>>
>> Can some one please can help me solve this problem?
>>
>> Here is what I have during call with the command "ngrep sip" executed on
>> the sipwise CE 4.2.1  server. Voicetrading is  expecting for premium
>> route on their side, the number to be perpended with "00000",
>> xx.xx.xx.250 is the IP address of my sipwise CE 4.2.1 server:
>>
>>
>> XX.XX.XX.250:5060 -> 77.72.169.129:5060
>>    INVITE sip:00492271993120 at 77.72.169.129:5060;transport=udp
>> SIP/2.0..Record-Route:
>> <sip:XX.XX.XX.250;r2=on;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Record-Route:
>> <sip:127.0.0.1;r2=on
>>    ;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Via:
>> SIP/2.0/UDP
>> XX.XX.XX.250;branch=z9hG4bKd906.5531f5d10bd0fe3667091afe519d5f94.0..Via:
>> SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;bra
>>    nch=z9hG4bKZ7GCaaKk;rport=5080..From: "41225017077"
>> <sip:41225017077 at sip.adoovoice.com>;tag=0F8733E5-56B4B7B700066935-870F0700..To:
>> <sip:00492271993120 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 222572
>>    206 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE, PRACK, ACK,
>> BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, PUBLISH, UPDATE,
>> MESSAGE..Supported: replaces,100rel..P-Asserted-Identity: <sip:
>>    41225017077 at sip.adoovoice.com>..Authorization: Digest
>> username="pbxprisnet", realm="sip.adoovoice.com", nonce="2231175255",
>> uri="sip:00492271993120 at 77.72.169.129:5060;transport=udp",
>> response="dac6cac
>>    8d25100ee03560bab867ba1be", algorithm=MD5..Content-Type:
>> application/sdp..Content-Length: 265..Contact:
>> <sip:ngcp-lb at XX.XX.XX.250:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=-
>> 20036 2
>>    0036 IN IP4 10.164.124.97..s=SDP data..c=IN IP4 213.55.176.206..t=0
>> 0..m=audio 11852 RTP/AVP 0 8 9 101..a=rtpmap:0 PCMU/8000..a=rtpmap:8
>> PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:101 telephone-event/8
>>    000..a=sendrecv..a=ptime:20..a=direction:active..
>> #####################
>> U XX.XX.XX.250:5060 -> 77.72.169.129:5060
>>    INVITE sip:00492271993120 at 77.72.169.129:5060;transport=udp
>> SIP/2.0..Record-Route:
>> <sip:XX.XX.XX.250;r2=on;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Record-Route:
>> <sip:127.0.0.1;r2=on
>>    ;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Via:
>> SIP/2.0/UDP
>> XX.XX.XX.250;branch=z9hG4bKd906.5531f5d10bd0fe3667091afe519d5f94.0..Via:
>> SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;bra
>>    nch=z9hG4bKZ7GCaaKk;rport=5080..From: "41225017077"
>> <sip:41225017077 at sip.adoovoice.com>;tag=0F8733E5-56B4B7B700066935-870F0700..To:
>> <sip:00492271993120 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 222572
>>    206 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE, PRACK, ACK,
>> BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, PUBLISH, UPDATE,
>> MESSAGE..Supported: replaces,100rel..P-Asserted-Identity: <sip:
>>    41225017077 at sip.adoovoice.com>..Authorization: Digest
>> username="pbxprisnet", realm="sip.adoovoice.com", nonce="2231175255",
>> uri="sip:00492271993120 at 77.72.169.129:5060;transport=udp",
>> response="dac6cac
>>    8d25100ee03560bab867ba1be", algorithm=MD5..Content-Type:
>> application/sdp..Content-Length: 265..Contact:
>> <sip:ngcp-lb at XX.XX.XX.250:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=-
>> 20036 2
>>    0036 IN IP4 10.164.124.97..s=SDP data..c=IN IP4 213.55.176.206..t=0
>> 0..m=audio 11852 RTP/AVP 0 8 9 101..a=rtpmap:0 PCMU/8000..a=rtpmap:8
>> PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:101 telephone-event/8
>>    000..a=sendrecv..a=ptime:20..a=direction:active..
>> #######################
>> U XX.XX.XX.250:5060 -> 77.72.169.129:5060
>>    INVITE sip:00492271993120 at 77.72.169.129:5060;transport=udp
>> SIP/2.0..Record-Route:
>> <sip:XX.XX.XX.250;r2=on;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Record-Route:
>> <sip:127.0.0.1;r2=on
>>    ;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Via:
>> SIP/2.0/UDP
>> XX.XX.XX.250;branch=z9hG4bKd906.5531f5d10bd0fe3667091afe519d5f94.0..Via:
>> SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;bra
>>    nch=z9hG4bKZ7GCaaKk;rport=5080..From: "41225017077"
>> <sip:41225017077 at sip.adoovoice.com>;tag=0F8733E5-56B4B7B700066935-870F0700..To:
>> <sip:00492271993120 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 222572
>>    206 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE, PRACK, ACK,
>> BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, PUBLISH, UPDATE,
>> MESSAGE..Supported: replaces,100rel..P-Asserted-Identity: <sip:
>>    41225017077 at sip.adoovoice.com>..Authorization: Digest
>> username="pbxprisnet", realm="sip.adoovoice.com", nonce="2231175255",
>> uri="sip:00492271993120 at 77.72.169.129:5060;transport=udp",
>> response="dac6cac
>>    8d25100ee03560bab867ba1be", algorithm=MD5..Content-Type:
>> application/sdp..Content-Length: 265..Contact:
>> <sip:ngcp-lb at XX.XX.XX.250:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=-
>> 20036 2
>>    0036 IN IP4 10.164.124.97..s=SDP data..c=IN IP4 213.55.176.206..t=0
>> 0..m=audio 11852 RTP/AVP 0 8 9 101..a=rtpmap:0 PCMU/8000..a=rtpmap:8
>> PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:101 telephone-event/8
>>    000..a=sendrecv..a=ptime:20..a=direction:active..
>> #########################################
>> U XX.XX.XX.250:5060 -> 77.72.169.129:5060
>>    INVITE sip:00492271993120 at 77.72.169.129:5060;transport=udp
>> SIP/2.0..Record-Route:
>> <sip:XX.XX.XX.250;r2=on;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Record-Route:
>> <sip:127.0.0.1;r2=on
>>    ;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Via:
>> SIP/2.0/UDP
>> XX.XX.XX.250;branch=z9hG4bKd906.5531f5d10bd0fe3667091afe519d5f94.0..Via:
>> SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;bra
>>    nch=z9hG4bKZ7GCaaKk;rport=5080..From: "41225017077"
>> <sip:41225017077 at sip.adoovoice.com>;tag=0F8733E5-56B4B7B700066935-870F0700..To:
>> <sip:00492271993120 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 222572
>>    206 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE, PRACK, ACK,
>> BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, PUBLISH, UPDATE,
>> MESSAGE..Supported: replaces,100rel..P-Asserted-Identity: <sip:
>>    41225017077 at sip.adoovoice.com>..Authorization: Digest
>> username="pbxprisnet", realm="sip.adoovoice.com", nonce="2231175255",
>> uri="sip:00492271993120 at 77.72.169.129:5060;transport=udp",
>> response="dac6cac
>>    8d25100ee03560bab867ba1be", algorithm=MD5..Content-Type:
>> application/sdp..Content-Length: 265..Contact:
>> <sip:ngcp-lb at XX.XX.XX.250:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=-
>> 20036 2
>>    0036 IN IP4 10.164.124.97..s=SDP data..c=IN IP4 213.55.176.206..t=0
>> 0..m=audio 11852 RTP/AVP 0 8 9 101..a=rtpmap:0 PCMU/8000..a=rtpmap:8
>> PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:101 telephone-event/8
>>    000..a=sendrecv..a=ptime:20..a=direction:active..
>> #################################################################################
>>
>> U XX.XX.XX.250:5060 -> 77.72.169.129:5060
>>    INVITE sip:00492271993120 at 77.72.169.129:5060;transport=udp
>> SIP/2.0..Record-Route:
>> <sip:XX.XX.XX.250;r2=on;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Record-Route:
>> <sip:127.0.0.1;r2=on
>>    ;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Via:
>> SIP/2.0/UDP
>> XX.XX.XX.250;branch=z9hG4bKd906.5531f5d10bd0fe3667091afe519d5f94.0..Via:
>> SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;bra
>>    nch=z9hG4bKZ7GCaaKk;rport=5080..From: "41225017077"
>> <sip:41225017077 at sip.adoovoice.com>;tag=0F8733E5-56B4B7B700066935-870F0700..To:
>> <sip:00492271993120 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 222572
>>    206 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE, PRACK, ACK,
>> BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, PUBLISH, UPDATE,
>> MESSAGE..Supported: replaces,100rel..P-Asserted-Identity: <sip:
>>    41225017077 at sip.adoovoice.com>..Authorization: Digest
>> username="pbxprisnet", realm="sip.adoovoice.com", nonce="2231175255",
>> uri="sip:00492271993120 at 77.72.169.129:5060;transport=udp",
>> response="dac6cac
>>    8d25100ee03560bab867ba1be", algorithm=MD5..Content-Type:
>> application/sdp..Content-Length: 265..Contact:
>> <sip:ngcp-lb at XX.XX.XX.250:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=-
>> 20036 2
>>    0036 IN IP4 10.164.124.97..s=SDP data..c=IN IP4 213.55.176.206..t=0
>> 0..m=audio 11852 RTP/AVP 0 8 9 101..a=rtpmap:0 PCMU/8000..a=rtpmap:8
>> PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:101 telephone-event/8
>>    000..a=sendrecv..a=ptime:20..a=direction:active..
>> ############################################################################
>>
>>
>> Thank you for your help
>>
>> Jephth? Feugn?
>>
>> _______________________________________________
>> Spce-user mailing list
>> Spce-user at lists.sipwise.com
>> https://lists.sipwise.com/listinfo/spce-user
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20160205/346e9f8c/attachment.html>

From me at nevian.org  Fri Feb  5 13:39:32 2016
From: me at nevian.org (Serge Yuriev)
Date: Fri, 5 Feb 2016 21:39:32 +0300
Subject: [Spce-user] Trunk to voicetrading configuration
In-Reply-To: <56B4E6B0.5090307@prisnets.ch>
References: <56B4E6B0.5090307@prisnets.ch> <56B4B8C1.5060203@prisnets.ch>
 <56B4C9D1.1090008@sipwise.com>
Message-ID: <EA2E104E-D65F-4872-A38A-801C9103418C@nevian.org>

Hi,

Who is 213.55.176.206? Is this someone you should proxy before passing upstream? Maybe your provider filters such requests?

-- 
Wbr, Serge via mobile

05.02.2016, 21:15, "Jephth? Feugn?" <j.feugne at prisnets.ch>:
> 
> Hi,
> Thank you for your reply. I unfortunately disable one of my rewrite rule by the time I made the call. I Cross check the rules once more and here is the result when I place call. still no ring both on the caller and callee  side:
> 
> 
>>>         U xx.xx.xx.2:5060 -> 77.72.169.129:5060
>>>           INVITE sip:0000041227312221 at 77.72.169.129:5060;transport=udp SIP/2.0..Record-Route: <sip:xx.xx.xx.2;r2=on;lr=on;ftag=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>..Record-Route: <sip:127.0.0.1;r2=
>>>           on;lr=on;ftag=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>..Via: SIP/2.0/UDP xx.xx.xx.2;branch=z9hG4bKe854.61a0e861a7f1d69a32327173a5932390.0..Via: SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;b
>>>           ranch=z9hG4bKtn6UJa1a;rport=5080..From: "41225017077" <sip:41225017077 at sip.adoovoice.com>;tag=16EE36B8-56B4E5C400006FEF-86FEF700..To: <sip:0000041227312221 at 77.72.169.129>..CSeq: 10 INVITE..Call-ID: 50
>>>           4974996 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, PUBLISH, UPDATE, MESSAGE..Supported: replaces,100rel..P-Asserted-Identity: <
>>>           sip:41225017077 at sip.adoovoice.com>..Content-Type: application/sdp..Content-Length: 265..Contact: <sip:ngcp-lb at xx.xx.xx.2:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=- 20054 20054 IN
>>>            IP4 10.164.124.97..s=SDP data..c=IN IP4 213.55.176.206..t=0 0..m=audio 11888 RTP/AVP 0 8 9 101..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:101 telephone-event/8000..a=
>>>           sendrecv..a=ptime:20..a=direction:active..                                                                                                                                                             
>>>         ##
>>>         U 77.72.169.129:5060 -> xx.xx.xx.2:5060
>>>           SIP/2.0 401 Unauthorized..Via: SIP/2.0/UDP xx.xx.xx.2:5060;branch=z9hG4bKe854.61a0e861a7f1d69a32327173a5932390.0..Via: SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;branch=z9hG4bKtn6UJa1a;rport=508
>>>           0..From: "41225017077" <sip:41225017077 at sip.adoovoice.com>;tag=16EE36B8-56B4E5C400006FEF-86FEF700..To: <sip:0000041227312221 at 77.72.169.129>..Contact: sip:0000041227312221 at 77.72.169.129:5060..Call-ID:
>>>           504974996 at 10.20.12.202_b2b-1..CSeq: 10 INVITE..Server: (Very nice Sip Registrar/Proxy Server)..Allow: ACK,BYE,CANCEL,INVITE,REGISTER,OPTIONS,INFO,MESSAGE..Record-route: <sip:xx.xx.xx.2;r2=on;lr;fta
>>>           g=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>,<sip:127.0.0.1;r2=on;lr;ftag=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>..WWW-Authenticate: Digest realm="sip.adoovoice.com",nonce="2242964208",algo
>>>           rithm=MD5..Content-Length: 0....                                                                                                                                                                       
>>>         #
>>>         U xx.xx.xx.2:5060 -> 77.72.169.129:5060
>>>           ACK sip:0000041227312221 at 77.72.169.129:5060;transport=udp SIP/2.0..Max-Forwards: 70..Record-Route: <sip:xx.xx.xx.2;r2=on;lr=on;ftag=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>..Record-Route: <si
>>>           p:127.0.0.1;r2=on;lr=on;ftag=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>..Via: SIP/2.0/UDP xx.xx.xx.2;branch=z9hG4bKe854.61a0e861a7f1d69a32327173a5932390.0..Via: SIP/2.0/UDP 127.0.0.1:5080;recei
>>>           ved=127.0.0.1;branch=z9hG4bKtn6UJa1a;rport=5080..From: "41225017077" <sip:41225017077 at sip.adoovoice.com>;tag=16EE36B8-56B4E5C400006FEF-86FEF700..To: <sip:0000041227312221 at 77.72.169.129>..Call-ID: 5049
>>>           74996 at 10.20.12.202_b2b-1..CSeq: 10 ACK..Content-Length: 0....                                                                                                                                          
>>>         #
>>>         U xx.xx.xx.2:5060 -> 77.72.169.129:5060
>>>           INVITE sip:0000041227312221 at 77.72.169.129:5060;transport=udp SIP/2.0..Record-Route: <sip:xx.xx.xx.2;r2=on;lr=on;ftag=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>..Record-Route: <sip:127.0.0.1;r2=
>>>           on;lr=on;ftag=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>..Via: SIP/2.0/UDP xx.xx.xx.2;branch=z9hG4bKf854.44da301080c743aeec10ba45573ba2e4.0..Via: SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;b
>>>           ranch=z9hG4bKkKgwgaE0;rport=5080..From: "41225017077" <sip:41225017077 at sip.adoovoice.com>;tag=16EE36B8-56B4E5C400006FEF-86FEF700..To: <sip:0000041227312221 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 50
>>>           4974996 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, PUBLISH, UPDATE, MESSAGE..Supported: replaces,100rel..P-Asserted-Identity: <
>>>           sip:41225017077 at sip.adoovoice.com>..Authorization: Digest username="pbxprisnet", realm="sip.adoovoice.com", nonce="2242964208", uri="sip:0000041227312221 at 77.72.169.129:5060;transport=udp", response="9
>>>           53a2ba986e16d9d2c3564149681dd58", algorithm=MD5..Content-Type: application/sdp..Content-Length: 265..Contact: <sip:ngcp-lb at xx.xx.xx.2:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=- 2
>>>           0054 20054 IN IP4 10.164.124.97..s=SDP data..c=IN IP4 213.55.176.206..t=0 0..m=audio 11888 RTP/AVP 0 8 9 101..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:101 telephone-e
>>>           vent/8000..a=sendrecv..a=ptime:20..a=direction:active..                                                                                                                                                
>>>         ########################
>>>         U xx.xx.xx.2:5060 -> 77.72.169.129:5060
>>>           INVITE sip:0000041227312221 at 77.72.169.129:5060;transport=udp SIP/2.0..Record-Route: <sip:xx.xx.xx.2;r2=on;lr=on;ftag=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>..Record-Route: <sip:127.0.0.1;r2=
>>>           on;lr=on;ftag=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>..Via: SIP/2.0/UDP xx.xx.xx.2;branch=z9hG4bKf854.44da301080c743aeec10ba45573ba2e4.0..Via: SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;b
>>>           ranch=z9hG4bKkKgwgaE0;rport=5080..From: "41225017077" <sip:41225017077 at sip.adoovoice.com>;tag=16EE36B8-56B4E5C400006FEF-86FEF700..To: <sip:0000041227312221 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 50
>>>           4974996 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, PUBLISH, UPDATE, MESSAGE..Supported: replaces,100rel..P-Asserted-Identity: <
>>>           sip:41225017077 at sip.adoovoice.com>..Authorization: Digest username="pbxprisnet", realm="sip.adoovoice.com", nonce="2242964208", uri="sip:0000041227312221 at 77.72.169.129:5060;transport=udp", response="9
>>>           53a2ba986e16d9d2c3564149681dd58", algorithm=MD5..Content-Type: application/sdp..Content-Length: 265..Contact: <sip:ngcp-lb at xx.xx.xx.2:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=- 2
>>>           0054 20054 IN IP4 10.164.124.97..s=SDP data..c=IN IP4 213.55.176.206..t=0 0..m=audio 11888 RTP/AVP 0 8 9 101..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:101 telephone-e
>>>           vent/8000..a=sendrecv..a=ptime:20..a=direction:active..                                                                                                                                                
>>>         #########################
>>>         U xx.xx.xx.2:5060 -> 77.72.169.129:5060
>>>           INVITE sip:0000041227312221 at 77.72.169.129:5060;transport=udp SIP/2.0..Record-Route: <sip:xx.xx.xx.2;r2=on;lr=on;ftag=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>..Record-Route: <sip:127.0.0.1;r2=
>>>           on;lr=on;ftag=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>..Via: SIP/2.0/UDP xx.xx.xx.2;branch=z9hG4bKf854.44da301080c743aeec10ba45573ba2e4.0..Via: SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;b
>>>           ranch=z9hG4bKkKgwgaE0;rport=5080..From: "41225017077" <sip:41225017077 at sip.adoovoice.com>;tag=16EE36B8-56B4E5C400006FEF-86FEF700..To: <sip:0000041227312221 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 50
>>>           4974996 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, PUBLISH, UPDATE, MESSAGE..Supported: replaces,100rel..P-Asserted-Identity: <
>>>           sip:41225017077 at sip.adoovoice.com>..Authorization: Digest username="pbxprisnet", realm="sip.adoovoice.com", nonce="2242964208", uri="sip:0000041227312221 at 77.72.169.129:5060;transport=udp", response="9
>>>           53a2ba986e16d9d2c3564149681dd58", algorithm=MD5..Content-Type: application/sdp..Content-Length: 265..Contact: <sip:ngcp-lb at xx.xx.xx.2:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=- 2
>>>           0054 20054 IN IP4 10.164.124.97..s=SDP data..c=IN IP4 213.55.176.206..t=0 0..m=audio 11888 RTP/AVP 0 8 9 101..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:101 telephone-e
>>>           vent/8000..a=sendrecv..a=ptime:20..a=direction:active..                                                                                                                                                
>>>         #############################################
>>>         U xx.xx.xx.2:5060 -> 77.72.169.129:5060
>>>           INVITE sip:0000041227312221 at 77.72.169.129:5060;transport=udp SIP/2.0..Record-Route: <sip:xx.xx.xx.2;r2=on;lr=on;ftag=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>..Record-Route: <sip:127.0.0.1;r2=
>>>           on;lr=on;ftag=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>..Via: SIP/2.0/UDP xx.xx.xx.2;branch=z9hG4bKf854.44da301080c743aeec10ba45573ba2e4.0..Via: SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;b
>>>           ranch=z9hG4bKkKgwgaE0;rport=5080..From: "41225017077" <sip:41225017077 at sip.adoovoice.com>;tag=16EE36B8-56B4E5C400006FEF-86FEF700..To: <sip:0000041227312221 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 50
>>>           4974996 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, PUBLISH, UPDATE, MESSAGE..Supported: replaces,100rel..P-Asserted-Identity: <
>>>           sip:41225017077 at sip.adoovoice.com>..Authorization: Digest username="pbxprisnet", realm="sip.adoovoice.com", nonce="2242964208", uri="sip:0000041227312221 at 77.72.169.129:5060;transport=udp", response="9
>>>           53a2ba986e16d9d2c3564149681dd58", algorithm=MD5..Content-Type: application/sdp..Content-Length: 265..Contact: <sip:ngcp-lb at xx.xx.xx.2:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=- 2
>>>           0054 20054 IN IP4 10.164.124.97..s=SDP data..c=IN IP4 213.55.176.206..t=0 0..m=audio 11888 RTP/AVP 0 8 9 101..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:101 telephone-e
>>>           vent/8000..a=sendrecv..a=ptime:20..a=direction:active..                                                                                                                                                
>>>         #################################################################################
>>>         U xx.xx.xx.2:5060 -> 77.72.169.129:5060
>>>           INVITE sip:0000041227312221 at 77.72.169.129:5060;transport=udp SIP/2.0..Record-Route: <sip:xx.xx.xx.2;r2=on;lr=on;ftag=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>..Record-Route: <sip:127.0.0.1;r2=
>>>           on;lr=on;ftag=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>..Via: SIP/2.0/UDP xx.xx.xx.2;branch=z9hG4bKf854.44da301080c743aeec10ba45573ba2e4.0..Via: SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;b
>>>           ranch=z9hG4bKkKgwgaE0;rport=5080..From: "41225017077" <sip:41225017077 at sip.adoovoice.com>;tag=16EE36B8-56B4E5C400006FEF-86FEF700..To: <sip:0000041227312221 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 50
>>>           4974996 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, PUBLISH, UPDATE, MESSAGE..Supported: replaces,100rel..P-Asserted-Identity: <
>>>           sip:41225017077 at sip.adoovoice.com>..Authorization: Digest username="pbxprisnet", realm="sip.adoovoice.com", nonce="2242964208", uri="sip:0000041227312221 at 77.72.169.129:5060;transport=udp", response="9
>>>           53a2ba986e16d9d2c3564149681dd58", algorithm=MD5..Content-Type: application/sdp..Content-Length: 265..Contact: <sip:ngcp-lb at xx.xx.xx.2:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=- 2
>>>           0054 20054 IN IP4 10.164.124.97..s=SDP data..c=IN IP4 213.55.176.206..t=0 0..m=audio 11888 RTP/AVP 0 8 9 101..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:101 telephone-e
>>>           vent/8000..a=sendrecv..a=ptime:20..a=direction:active..                                                                                                                                                
>>>         ################################################################################################
>>>         T 213.55.176.206:31002 -> xx.xx.xx.2:5060 [AP]
>>>           CANCEL sip:0227312221 at sip.adoovoice.com:5060 SIP/2.0..Via: SIP/2.0/TCP 10.20.12.202:5063;branch=z9hG4bK2530177975..From: "balmer" <sip:balmer at sip.adoovoice.com>;tag=801761386..To: <sip:0227312221 at sip.
>>>           adoovoice.com>..Call-ID: 504974996 at 10.20.12.202..CSeq: 2 CANCEL..Max-Forwards: 70..User-Agent: Yealink SIP-W52P 25.73.0.40..Content-Length: 0....                                                      
>>>         #
> 
> 
> 
> Le 05. 02. 16 17:12, Andreas Granig a ?crit :
> 
>> 
>> Hi, From the trace you provided, it seems your request just times out, as there is no reply at all from your peer. No idea if they do this because you're not sending the 00000 prefix you mentioned. Create a new rewrite rule set and put a rule like "^(.+)$" => "00000\1" into the outbound callee rule and assign this rule set in the peer preferences of your configured peering server. Please read carefully the handbook provided with the CE installation, specifically the configuration of peerings and peering rules. Andreas On 02/05/2016 03:59 PM, Jephth? Feugn? wrote:
>>> 
>>> Hello, I've been trying for weeks to have my trunk to voicetrading working with no success. I also tried a sip trunk to my GSM gateway with the same result. No ringing to the calle side, and no sound no ringing tone by the caller side.  Can some one please can help me solve this problem? Here is what I have during call with the command "ngrep sip" executed on the sipwise CE 4.2.1 server. Voicetrading is expecting for premium route on their side, the number to be perpended with "00000", xx.xx.xx.250 is the IP address of my sipwise CE 4.2.1 server: XX.XX.XX.250:5060 -> 77.72.169.129:5060 INVITE sip:00492271993120 at 77.72.169.129:5060;transport=udpSIP/2.0..Record-Route: <sip:XX.XX.XX.250;r2=on;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Record-Route: <sip:127.0.0.1;r2=on ;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Via: SIP/2.0/UDP XX.XX.XX.250;branch=z9hG4bKd906.5531f5d10bd0fe3667091afe519d5f94.0..Via: SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;bra nch=z9hG4bKZ7GCaaKk;rport=5080..From: "41225017077"<sip:41225017077 at sip.adoovoice.com>;tag=0F8733E5-56B4B7B700066935-870F0700..To:<sip:00492271993120 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 222572 206 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, PUBLISH, UPDATE, MESSAGE..Supported: replaces,100rel..P-Asserted-Identity: <sip: 41225017077 at sip.adoovoice.com>..Authorization: Digest username="pbxprisnet", realm="sip.adoovoice.com", nonce="2231175255", uri="sip:00492271993120 at 77.72.169.129:5060;transport=udp", response="dac6cac 8d25100ee03560bab867ba1be", algorithm=MD5..Content-Type: application/sdp..Content-Length: 265..Contact:<sip:ngcp-lb at XX.XX.XX.250:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=- 20036 2 0036 IN IP4 10.164.124.97..s=SDP data..c=IN IP4 213.55.176.206..t=0 0..m=audio 11852 RTP/AVP 0 8 9 101..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:101 telephone-event/8 000..a=sendrecv..a=ptime:20..a=direction:active.. ##################### U XX.XX.XX.250:5060 -> 77.72.169.129:5060 INVITE sip:00492271993120 at 77.72.169.129:5060;transport=udpSIP/2.0..Record-Route: <sip:XX.XX.XX.250;r2=on;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Record-Route: <sip:127.0.0.1;r2=on ;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Via: SIP/2.0/UDP XX.XX.XX.250;branch=z9hG4bKd906.5531f5d10bd0fe3667091afe519d5f94.0..Via: SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;bra nch=z9hG4bKZ7GCaaKk;rport=5080..From: "41225017077"<sip:41225017077 at sip.adoovoice.com>;tag=0F8733E5-56B4B7B700066935-870F0700..To:<sip:00492271993120 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 222572 206 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, PUBLISH, UPDATE, MESSAGE..Supported: replaces,100rel..P-Asserted-Identity: <sip: 41225017077 at sip.adoovoice.com>..Authorization: Digest username="pbxprisnet", realm="sip.adoovoice.com", nonce="2231175255", uri="sip:00492271993120 at 77.72.169.129:5060;transport=udp", response="dac6cac 8d25100ee03560bab867ba1be", algorithm=MD5..Content-Type: application/sdp..Content-Length: 265..Contact:<sip:ngcp-lb at XX.XX.XX.250:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=- 20036 2 0036 IN IP4 10.164.124.97..s=SDP data..c=IN IP4 213.55.176.206..t=0 0..m=audio 11852 RTP/AVP 0 8 9 101..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:101 telephone-event/8 000..a=sendrecv..a=ptime:20..a=direction:active.. ####################### U XX.XX.XX.250:5060 -> 77.72.169.129:5060 INVITE sip:00492271993120 at 77.72.169.129:5060;transport=udpSIP/2.0..Record-Route: <sip:XX.XX.XX.250;r2=on;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Record-Route: <sip:127.0.0.1;r2=on ;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Via: SIP/2.0/UDP XX.XX.XX.250;branch=z9hG4bKd906.5531f5d10bd0fe3667091afe519d5f94.0..Via: SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;bra nch=z9hG4bKZ7GCaaKk;rport=5080..From: "41225017077"<sip:41225017077 at sip.adoovoice.com>;tag=0F8733E5-56B4B7B700066935-870F0700..To:<sip:00492271993120 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 222572 206 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, PUBLISH, UPDATE, MESSAGE..Supported: replaces,100rel..P-Asserted-Identity: <sip: 41225017077 at sip.adoovoice.com>..Authorization: Digest username="pbxprisnet", realm="sip.adoovoice.com", nonce="2231175255", uri="sip:00492271993120 at 77.72.169.129:5060;transport=udp", response="dac6cac 8d25100ee03560bab867ba1be", algorithm=MD5..Content-Type: application/sdp..Content-Length: 265..Contact:<sip:ngcp-lb at XX.XX.XX.250:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=- 20036 2 0036 IN IP4 10.164.124.97..s=SDP data..c=IN IP4 213.55.176.206..t=0 0..m=audio 11852 RTP/AVP 0 8 9 101..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:101 telephone-event/8 000..a=sendrecv..a=ptime:20..a=direction:active.. ######################################### U XX.XX.XX.250:5060 -> 77.72.169.129:5060 INVITE sip:00492271993120 at 77.72.169.129:5060;transport=udpSIP/2.0..Record-Route: <sip:XX.XX.XX.250;r2=on;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Record-Route: <sip:127.0.0.1;r2=on ;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Via: SIP/2.0/UDP XX.XX.XX.250;branch=z9hG4bKd906.5531f5d10bd0fe3667091afe519d5f94.0..Via: SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;bra nch=z9hG4bKZ7GCaaKk;rport=5080..From: "41225017077"<sip:41225017077 at sip.adoovoice.com>;tag=0F8733E5-56B4B7B700066935-870F0700..To:<sip:00492271993120 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 222572 206 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, PUBLISH, UPDATE, MESSAGE..Supported: replaces,100rel..P-Asserted-Identity: <sip: 41225017077 at sip.adoovoice.com>..Authorization: Digest username="pbxprisnet", realm="sip.adoovoice.com", nonce="2231175255", uri="sip:00492271993120 at 77.72.169.129:5060;transport=udp", response="dac6cac 8d25100ee03560bab867ba1be", algorithm=MD5..Content-Type: application/sdp..Content-Length: 265..Contact:<sip:ngcp-lb at XX.XX.XX.250:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=- 20036 2 0036 IN IP4 10.164.124.97..s=SDP data..c=IN IP4 213.55.176.206..t=0 0..m=audio 11852 RTP/AVP 0 8 9 101..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:101 telephone-event/8 000..a=sendrecv..a=ptime:20..a=direction:active.. ################################################################################# U XX.XX.XX.250:5060 -> 77.72.169.129:5060 INVITE sip:00492271993120 at 77.72.169.129:5060;transport=udpSIP/2.0..Record-Route: <sip:XX.XX.XX.250;r2=on;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Record-Route: <sip:127.0.0.1;r2=on ;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Via: SIP/2.0/UDP XX.XX.XX.250;branch=z9hG4bKd906.5531f5d10bd0fe3667091afe519d5f94.0..Via: SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;bra nch=z9hG4bKZ7GCaaKk;rport=5080..From: "41225017077"<sip:41225017077 at sip.adoovoice.com>;tag=0F8733E5-56B4B7B700066935-870F0700..To:<sip:00492271993120 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 222572 206 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, PUBLISH, UPDATE, MESSAGE..Supported: replaces,100rel..P-Asserted-Identity: <sip: 41225017077 at sip.adoovoice.com>..Authorization: Digest username="pbxprisnet", realm="sip.adoovoice.com", nonce="2231175255", uri="sip:00492271993120 at 77.72.169.129:5060;transport=udp", response="dac6cac 8d25100ee03560bab867ba1be", algorithm=MD5..Content-Type: application/sdp..Content-Length: 265..Contact:<sip:ngcp-lb at XX.XX.XX.250:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=- 20036 2 0036 IN IP4 10.164.124.97..s=SDP data..c=IN IP4 213.55.176.206..t=0 0..m=audio 11852 RTP/AVP 0 8 9 101..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:101 telephone-event/8 000..a=sendrecv..a=ptime:20..a=direction:active.. ############################################################################ Thank you for your help Jephth? Feugn? _______________________________________________ Spce-user mailing listSpce-user at lists.sipwise.comhttps://lists.sipwise.com/listinfo/spce-user
>> 
>> _______________________________________________ Spce-user mailing listSpce-user at lists.sipwise.comhttps://lists.sipwise.com/listinfo/spce-user
> 
> 
> 
> 
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
> 


From j.feugne at prisnets.ch  Fri Feb  5 14:03:53 2016
From: j.feugne at prisnets.ch (=?UTF-8?Q?Jephth=C3=A9_Feugn=C3=A9?=)
Date: Fri, 5 Feb 2016 20:03:53 +0100
Subject: [Spce-user] Trunk to voicetrading configuration
In-Reply-To: <EA2E104E-D65F-4872-A38A-801C9103418C@nevian.org>
References: <56B4E6B0.5090307@prisnets.ch> <56B4B8C1.5060203@prisnets.ch>
 <56B4C9D1.1090008@sipwise.com>
 <EA2E104E-D65F-4872-A38A-801C9103418C@nevian.org>
Message-ID: <001a01d16047$f50c8d00$df25a700$@prisnets.ch>

HI!

213.55.176.206, is my 4G connection behind which is connected my IP Phone registered with my hosted Sipwise CE server (xx.xx.xx.250).
I can register directly to my Voicetrading account and place call behind my 4G connection, but not when I register to Sipwise.

Thank you helping me to solve this situation.

Jeph,


_____
Prisnets SA.
Office:   +41 22 501 70 70 / Fax : +41 22 501 70 67
Direct line : +41 22 508 72 70
Mobile:  +41 78 728 92 97
Email:     j.feugne at prisnets.ch
Skype:   jephtech - Twitter:  @prisnet_ch
http://www.prisnets.ch
Prisnet Telecommunications SA.  Route de Saint-Julien 184 A, 1228 Plan-Les-Ouates CH.

-----Message d'origine-----
De : Spce-user [mailto:spce-user-bounces at lists.sipwise.com] De la part de Serge Yuriev
Envoy? : vendredi, 5 f?vrier 2016 19:40
? : spce-user at lists.sipwise.com
Objet : Re: [Spce-user] Trunk to voicetrading configuration

Hi,

Who is 213.55.176.206? Is this someone you should proxy before passing upstream? Maybe your provider filters such requests?

-- 
Wbr, Serge via mobile

05.02.2016, 21:15, "Jephth? Feugn?" <j.feugne at prisnets.ch>:
> 
> Hi,
> Thank you for your reply. I unfortunately disable one of my rewrite rule by the time I made the call. I Cross check the rules once more and here is the result when I place call. still no ring both on the caller and callee  side:
> 
> 
>>>         U xx.xx.xx.2:5060 -> 77.72.169.129:5060
>>>           INVITE sip:0000041227312221 at 77.72.169.129:5060;transport=udp SIP/2.0..Record-Route: <sip:xx.xx.xx.2;r2=on;lr=on;ftag=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>..Record-Route: <sip:127.0.0.1;r2=
>>>           on;lr=on;ftag=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>..Via: SIP/2.0/UDP xx.xx.xx.2;branch=z9hG4bKe854.61a0e861a7f1d69a32327173a5932390.0..Via: SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;b
>>>           ranch=z9hG4bKtn6UJa1a;rport=5080..From: "41225017077" <sip:41225017077 at sip.adoovoice.com>;tag=16EE36B8-56B4E5C400006FEF-86FEF700..To: <sip:0000041227312221 at 77.72.169.129>..CSeq: 10 INVITE..Call-ID: 50
>>>           4974996 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, PUBLISH, UPDATE, MESSAGE..Supported: replaces,100rel..P-Asserted-Identity: <
>>>           sip:41225017077 at sip.adoovoice.com>..Content-Type: application/sdp..Content-Length: 265..Contact: <sip:ngcp-lb at xx.xx.xx.2:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=- 20054 20054 IN
>>>            IP4 10.164.124.97..s=SDP data..c=IN IP4 213.55.176.206..t=0 0..m=audio 11888 RTP/AVP 0 8 9 101..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:101 telephone-event/8000..a=
>>>           sendrecv..a=ptime:20..a=direction:active..                                                                                                                                                             
>>>         ##
>>>         U 77.72.169.129:5060 -> xx.xx.xx.2:5060
>>>           SIP/2.0 401 Unauthorized..Via: SIP/2.0/UDP xx.xx.xx.2:5060;branch=z9hG4bKe854.61a0e861a7f1d69a32327173a5932390.0..Via: SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;branch=z9hG4bKtn6UJa1a;rport=508
>>>           0..From: "41225017077" <sip:41225017077 at sip.adoovoice.com>;tag=16EE36B8-56B4E5C400006FEF-86FEF700..To: <sip:0000041227312221 at 77.72.169.129>..Contact: sip:0000041227312221 at 77.72.169.129:5060..Call-ID:
>>>           504974996 at 10.20.12.202_b2b-1..CSeq: 10 INVITE..Server: (Very nice Sip Registrar/Proxy Server)..Allow: ACK,BYE,CANCEL,INVITE,REGISTER,OPTIONS,INFO,MESSAGE..Record-route: <sip:xx.xx.xx.2;r2=on;lr;fta
>>>           g=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>,<sip:127.0.0.1;r2=on;lr;ftag=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>..WWW-Authenticate: Digest realm="sip.adoovoice.com",nonce="2242964208",algo
>>>           rithm=MD5..Content-Length: 0....                                                                                                                                                                       
>>>         #
>>>         U xx.xx.xx.2:5060 -> 77.72.169.129:5060
>>>           ACK sip:0000041227312221 at 77.72.169.129:5060;transport=udp SIP/2.0..Max-Forwards: 70..Record-Route: <sip:xx.xx.xx.2;r2=on;lr=on;ftag=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>..Record-Route: <si
>>>           p:127.0.0.1;r2=on;lr=on;ftag=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>..Via: SIP/2.0/UDP xx.xx.xx.2;branch=z9hG4bKe854.61a0e861a7f1d69a32327173a5932390.0..Via: SIP/2.0/UDP 127.0.0.1:5080;recei
>>>           ved=127.0.0.1;branch=z9hG4bKtn6UJa1a;rport=5080..From: "41225017077" <sip:41225017077 at sip.adoovoice.com>;tag=16EE36B8-56B4E5C400006FEF-86FEF700..To: <sip:0000041227312221 at 77.72.169.129>..Call-ID: 5049
>>>           74996 at 10.20.12.202_b2b-1..CSeq: 10 ACK..Content-Length: 0....                                                                                                                                          
>>>         #
>>>         U xx.xx.xx.2:5060 -> 77.72.169.129:5060
>>>           INVITE sip:0000041227312221 at 77.72.169.129:5060;transport=udp SIP/2.0..Record-Route: <sip:xx.xx.xx.2;r2=on;lr=on;ftag=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>..Record-Route: <sip:127.0.0.1;r2=
>>>           on;lr=on;ftag=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>..Via: SIP/2.0/UDP xx.xx.xx.2;branch=z9hG4bKf854.44da301080c743aeec10ba45573ba2e4.0..Via: SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;b
>>>           ranch=z9hG4bKkKgwgaE0;rport=5080..From: "41225017077" <sip:41225017077 at sip.adoovoice.com>;tag=16EE36B8-56B4E5C400006FEF-86FEF700..To: <sip:0000041227312221 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 50
>>>           4974996 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, PUBLISH, UPDATE, MESSAGE..Supported: replaces,100rel..P-Asserted-Identity: <
>>>           sip:41225017077 at sip.adoovoice.com>..Authorization: Digest username="pbxprisnet", realm="sip.adoovoice.com", nonce="2242964208", uri="sip:0000041227312221 at 77.72.169.129:5060;transport=udp", response="9
>>>           53a2ba986e16d9d2c3564149681dd58", algorithm=MD5..Content-Type: application/sdp..Content-Length: 265..Contact: <sip:ngcp-lb at xx.xx.xx.2:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=- 2
>>>           0054 20054 IN IP4 10.164.124.97..s=SDP data..c=IN IP4 213.55.176.206..t=0 0..m=audio 11888 RTP/AVP 0 8 9 101..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:101 telephone-e
>>>           vent/8000..a=sendrecv..a=ptime:20..a=direction:active..                                                                                                                                                
>>>         ########################
>>>         U xx.xx.xx.2:5060 -> 77.72.169.129:5060
>>>           INVITE sip:0000041227312221 at 77.72.169.129:5060;transport=udp SIP/2.0..Record-Route: <sip:xx.xx.xx.2;r2=on;lr=on;ftag=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>..Record-Route: <sip:127.0.0.1;r2=
>>>           on;lr=on;ftag=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>..Via: SIP/2.0/UDP xx.xx.xx.2;branch=z9hG4bKf854.44da301080c743aeec10ba45573ba2e4.0..Via: SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;b
>>>           ranch=z9hG4bKkKgwgaE0;rport=5080..From: "41225017077" <sip:41225017077 at sip.adoovoice.com>;tag=16EE36B8-56B4E5C400006FEF-86FEF700..To: <sip:0000041227312221 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 50
>>>           4974996 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, PUBLISH, UPDATE, MESSAGE..Supported: replaces,100rel..P-Asserted-Identity: <
>>>           sip:41225017077 at sip.adoovoice.com>..Authorization: Digest username="pbxprisnet", realm="sip.adoovoice.com", nonce="2242964208", uri="sip:0000041227312221 at 77.72.169.129:5060;transport=udp", response="9
>>>           53a2ba986e16d9d2c3564149681dd58", algorithm=MD5..Content-Type: application/sdp..Content-Length: 265..Contact: <sip:ngcp-lb at xx.xx.xx.2:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=- 2
>>>           0054 20054 IN IP4 10.164.124.97..s=SDP data..c=IN IP4 213.55.176.206..t=0 0..m=audio 11888 RTP/AVP 0 8 9 101..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:101 telephone-e
>>>           vent/8000..a=sendrecv..a=ptime:20..a=direction:active..                                                                                                                                                
>>>         #########################
>>>         U xx.xx.xx.2:5060 -> 77.72.169.129:5060
>>>           INVITE sip:0000041227312221 at 77.72.169.129:5060;transport=udp SIP/2.0..Record-Route: <sip:xx.xx.xx.2;r2=on;lr=on;ftag=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>..Record-Route: <sip:127.0.0.1;r2=
>>>           on;lr=on;ftag=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>..Via: SIP/2.0/UDP xx.xx.xx.2;branch=z9hG4bKf854.44da301080c743aeec10ba45573ba2e4.0..Via: SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;b
>>>           ranch=z9hG4bKkKgwgaE0;rport=5080..From: "41225017077" <sip:41225017077 at sip.adoovoice.com>;tag=16EE36B8-56B4E5C400006FEF-86FEF700..To: <sip:0000041227312221 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 50
>>>           4974996 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, PUBLISH, UPDATE, MESSAGE..Supported: replaces,100rel..P-Asserted-Identity: <
>>>           sip:41225017077 at sip.adoovoice.com>..Authorization: Digest username="pbxprisnet", realm="sip.adoovoice.com", nonce="2242964208", uri="sip:0000041227312221 at 77.72.169.129:5060;transport=udp", response="9
>>>           53a2ba986e16d9d2c3564149681dd58", algorithm=MD5..Content-Type: application/sdp..Content-Length: 265..Contact: <sip:ngcp-lb at xx.xx.xx.2:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=- 2
>>>           0054 20054 IN IP4 10.164.124.97..s=SDP data..c=IN IP4 213.55.176.206..t=0 0..m=audio 11888 RTP/AVP 0 8 9 101..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:101 telephone-e
>>>           vent/8000..a=sendrecv..a=ptime:20..a=direction:active..                                                                                                                                                
>>>         #############################################
>>>         U xx.xx.xx.2:5060 -> 77.72.169.129:5060
>>>           INVITE sip:0000041227312221 at 77.72.169.129:5060;transport=udp SIP/2.0..Record-Route: <sip:xx.xx.xx.2;r2=on;lr=on;ftag=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>..Record-Route: <sip:127.0.0.1;r2=
>>>           on;lr=on;ftag=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>..Via: SIP/2.0/UDP xx.xx.xx.2;branch=z9hG4bKf854.44da301080c743aeec10ba45573ba2e4.0..Via: SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;b
>>>           ranch=z9hG4bKkKgwgaE0;rport=5080..From: "41225017077" <sip:41225017077 at sip.adoovoice.com>;tag=16EE36B8-56B4E5C400006FEF-86FEF700..To: <sip:0000041227312221 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 50
>>>           4974996 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, PUBLISH, UPDATE, MESSAGE..Supported: replaces,100rel..P-Asserted-Identity: <
>>>           sip:41225017077 at sip.adoovoice.com>..Authorization: Digest username="pbxprisnet", realm="sip.adoovoice.com", nonce="2242964208", uri="sip:0000041227312221 at 77.72.169.129:5060;transport=udp", response="9
>>>           53a2ba986e16d9d2c3564149681dd58", algorithm=MD5..Content-Type: application/sdp..Content-Length: 265..Contact: <sip:ngcp-lb at xx.xx.xx.2:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=- 2
>>>           0054 20054 IN IP4 10.164.124.97..s=SDP data..c=IN IP4 213.55.176.206..t=0 0..m=audio 11888 RTP/AVP 0 8 9 101..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:101 telephone-e
>>>           vent/8000..a=sendrecv..a=ptime:20..a=direction:active..                                                                                                                                                
>>>         #################################################################################
>>>         U xx.xx.xx.2:5060 -> 77.72.169.129:5060
>>>           INVITE sip:0000041227312221 at 77.72.169.129:5060;transport=udp SIP/2.0..Record-Route: <sip:xx.xx.xx.2;r2=on;lr=on;ftag=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>..Record-Route: <sip:127.0.0.1;r2=
>>>           on;lr=on;ftag=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>..Via: SIP/2.0/UDP xx.xx.xx.2;branch=z9hG4bKf854.44da301080c743aeec10ba45573ba2e4.0..Via: SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;b
>>>           ranch=z9hG4bKkKgwgaE0;rport=5080..From: "41225017077" <sip:41225017077 at sip.adoovoice.com>;tag=16EE36B8-56B4E5C400006FEF-86FEF700..To: <sip:0000041227312221 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 50
>>>           4974996 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, PUBLISH, UPDATE, MESSAGE..Supported: replaces,100rel..P-Asserted-Identity: <
>>>           sip:41225017077 at sip.adoovoice.com>..Authorization: Digest username="pbxprisnet", realm="sip.adoovoice.com", nonce="2242964208", uri="sip:0000041227312221 at 77.72.169.129:5060;transport=udp", response="9
>>>           53a2ba986e16d9d2c3564149681dd58", algorithm=MD5..Content-Type: application/sdp..Content-Length: 265..Contact: <sip:ngcp-lb at xx.xx.xx.2:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=- 2
>>>           0054 20054 IN IP4 10.164.124.97..s=SDP data..c=IN IP4 213.55.176.206..t=0 0..m=audio 11888 RTP/AVP 0 8 9 101..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:101 telephone-e
>>>           vent/8000..a=sendrecv..a=ptime:20..a=direction:active..                                                                                                                                                
>>>         ################################################################################################
>>>         T 213.55.176.206:31002 -> xx.xx.xx.2:5060 [AP]
>>>           CANCEL sip:0227312221 at sip.adoovoice.com:5060 SIP/2.0..Via: SIP/2.0/TCP 10.20.12.202:5063;branch=z9hG4bK2530177975..From: "balmer" <sip:balmer at sip.adoovoice.com>;tag=801761386..To: <sip:0227312221 at sip.
>>>           adoovoice.com>..Call-ID: 504974996 at 10.20.12.202..CSeq: 2 CANCEL..Max-Forwards: 70..User-Agent: Yealink SIP-W52P 25.73.0.40..Content-Length: 0....                                                      
>>>         #
> 
> 
> 
> Le 05. 02. 16 17:12, Andreas Granig a ?crit :
> 
>> 
>> Hi, From the trace you provided, it seems your request just times out, as there is no reply at all from your peer. No idea if they do this because you're not sending the 00000 prefix you mentioned. Create a new rewrite rule set and put a rule like "^(.+)$" => "00000\1" into the outbound callee rule and assign this rule set in the peer preferences of your configured peering server. Please read carefully the handbook provided with the CE installation, specifically the configuration of peerings and peering rules. Andreas On 02/05/2016 03:59 PM, Jephth? Feugn? wrote:
>>> 
>>> Hello, I've been trying for weeks to have my trunk to voicetrading working with no success. I also tried a sip trunk to my GSM gateway with the same result. No ringing to the calle side, and no sound no ringing tone by the caller side.  Can some one please can help me solve this problem? Here is what I have during call with the command "ngrep sip" executed on the sipwise CE 4.2.1 server. Voicetrading is expecting for premium route on their side, the number to be perpended with "00000", xx.xx.xx.250 is the IP address of my sipwise CE 4.2.1 server: XX.XX.XX.250:5060 -> 77.72.169.129:5060 INVITE sip:00492271993120 at 77.72.169.129:5060;transport=udpSIP/2.0..Record-Route: <sip:XX.XX.XX.250;r2=on;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Record-Route: <sip:127.0.0.1;r2=on ;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Via: SIP/2.0/UDP XX.XX.XX.250;branch=z9hG4bKd906.5531f5d10bd0fe3667091afe519d5f94.0..Via: SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;bra nch=z9hG4bKZ7GCaaKk;rport=5080..From: "41225017077"<sip:41225017077 at sip.adoovoice.com>;tag=0F8733E5-56B4B7B700066935-870F0700..To:<sip:00492271993120 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 222572 206 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, PUBLISH, UPDATE, MESSAGE..Supported: replaces,100rel..P-Asserted-Identity: <sip: 41225017077 at sip.adoovoice.com>..Authorization: Digest username="pbxprisnet", realm="sip.adoovoice.com", nonce="2231175255", uri="sip:00492271993120 at 77.72.169.129:5060;transport=udp", response="dac6cac 8d25100ee03560bab867ba1be", algorithm=MD5..Content-Type: application/sdp..Content-Length: 265..Contact:<sip:ngcp-lb at XX.XX.XX.250:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=- 20036 2 0036 IN IP4 10.164.124.97..s=SDP data..c=IN IP4 213.55.176.206..t=0 0..m=audio 11852 RTP/AVP 0 8 9 101..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:101 telephone-event/8 000..a=sendrecv..a=ptime:20..a=direction:active.. ##################### U XX.XX.XX.250:5060 -> 77.72.169.129:5060 INVITE sip:00492271993120 at 77.72.169.129:5060;transport=udpSIP/2.0..Record-Route: <sip:XX.XX.XX.250;r2=on;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Record-Route: <sip:127.0.0.1;r2=on ;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Via: SIP/2.0/UDP XX.XX.XX.250;branch=z9hG4bKd906.5531f5d10bd0fe3667091afe519d5f94.0..Via: SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;bra nch=z9hG4bKZ7GCaaKk;rport=5080..From: "41225017077"<sip:41225017077 at sip.adoovoice.com>;tag=0F8733E5-56B4B7B700066935-870F0700..To:<sip:00492271993120 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 222572 206 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, PUBLISH, UPDATE, MESSAGE..Supported: replaces,100rel..P-Asserted-Identity: <sip: 41225017077 at sip.adoovoice.com>..Authorization: Digest username="pbxprisnet", realm="sip.adoovoice.com", nonce="2231175255", uri="sip:00492271993120 at 77.72.169.129:5060;transport=udp", response="dac6cac 8d25100ee03560bab867ba1be", algorithm=MD5..Content-Type: application/sdp..Content-Length: 265..Contact:<sip:ngcp-lb at XX.XX.XX.250:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=- 20036 2 0036 IN IP4 10.164.124.97..s=SDP data..c=IN IP4 213.55.176.206..t=0 0..m=audio 11852 RTP/AVP 0 8 9 101..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:101 telephone-event/8 000..a=sendrecv..a=ptime:20..a=direction:active.. ####################### U XX.XX.XX.250:5060 -> 77.72.169.129:5060 INVITE sip:00492271993120 at 77.72.169.129:5060;transport=udpSIP/2.0..Record-Route: <sip:XX.XX.XX.250;r2=on;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Record-Route: <sip:127.0.0.1;r2=on ;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Via: SIP/2.0/UDP XX.XX.XX.250;branch=z9hG4bKd906.5531f5d10bd0fe3667091afe519d5f94.0..Via: SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;bra nch=z9hG4bKZ7GCaaKk;rport=5080..From: "41225017077"<sip:41225017077 at sip.adoovoice.com>;tag=0F8733E5-56B4B7B700066935-870F0700..To:<sip:00492271993120 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 222572 206 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, PUBLISH, UPDATE, MESSAGE..Supported: replaces,100rel..P-Asserted-Identity: <sip: 41225017077 at sip.adoovoice.com>..Authorization: Digest username="pbxprisnet", realm="sip.adoovoice.com", nonce="2231175255", uri="sip:00492271993120 at 77.72.169.129:5060;transport=udp", response="dac6cac 8d25100ee03560bab867ba1be", algorithm=MD5..Content-Type: application/sdp..Content-Length: 265..Contact:<sip:ngcp-lb at XX.XX.XX.250:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=- 20036 2 0036 IN IP4 10.164.124.97..s=SDP data..c=IN IP4 213.55.176.206..t=0 0..m=audio 11852 RTP/AVP 0 8 9 101..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:101 telephone-event/8 000..a=sendrecv..a=ptime:20..a=direction:active.. ######################################### U XX.XX.XX.250:5060 -> 77.72.169.129:5060 INVITE sip:00492271993120 at 77.72.169.129:5060;transport=udpSIP/2.0..Record-Route: <sip:XX.XX.XX.250;r2=on;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Record-Route: <sip:127.0.0.1;r2=on ;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Via: SIP/2.0/UDP XX.XX.XX.250;branch=z9hG4bKd906.5531f5d10bd0fe3667091afe519d5f94.0..Via: SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;bra nch=z9hG4bKZ7GCaaKk;rport=5080..From: "41225017077"<sip:41225017077 at sip.adoovoice.com>;tag=0F8733E5-56B4B7B700066935-870F0700..To:<sip:00492271993120 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 222572 206 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, PUBLISH, UPDATE, MESSAGE..Supported: replaces,100rel..P-Asserted-Identity: <sip: 41225017077 at sip.adoovoice.com>..Authorization: Digest username="pbxprisnet", realm="sip.adoovoice.com", nonce="2231175255", uri="sip:00492271993120 at 77.72.169.129:5060;transport=udp", response="dac6cac 8d25100ee03560bab867ba1be", algorithm=MD5..Content-Type: application/sdp..Content-Length: 265..Contact:<sip:ngcp-lb at XX.XX.XX.250:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=- 20036 2 0036 IN IP4 10.164.124.97..s=SDP data..c=IN IP4 213.55.176.206..t=0 0..m=audio 11852 RTP/AVP 0 8 9 101..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:101 telephone-event/8 000..a=sendrecv..a=ptime:20..a=direction:active.. ################################################################################# U XX.XX.XX.250:5060 -> 77.72.169.129:5060 INVITE sip:00492271993120 at 77.72.169.129:5060;transport=udpSIP/2.0..Record-Route: <sip:XX.XX.XX.250;r2=on;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Record-Route: <sip:127.0.0.1;r2=on ;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Via: SIP/2.0/UDP XX.XX.XX.250;branch=z9hG4bKd906.5531f5d10bd0fe3667091afe519d5f94.0..Via: SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;bra nch=z9hG4bKZ7GCaaKk;rport=5080..From: "41225017077"<sip:41225017077 at sip.adoovoice.com>;tag=0F8733E5-56B4B7B700066935-870F0700..To:<sip:00492271993120 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 222572 206 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, PUBLISH, UPDATE, MESSAGE..Supported: replaces,100rel..P-Asserted-Identity: <sip: 41225017077 at sip.adoovoice.com>..Authorization: Digest username="pbxprisnet", realm="sip.adoovoice.com", nonce="2231175255", uri="sip:00492271993120 at 77.72.169.129:5060;transport=udp", response="dac6cac 8d25100ee03560bab867ba1be", algorithm=MD5..Content-Type: application/sdp..Content-Length: 265..Contact:<sip:ngcp-lb at XX.XX.XX.250:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=- 20036 2 0036 IN IP4 10.164.124.97..s=SDP data..c=IN IP4 213.55.176.206..t=0 0..m=audio 11852 RTP/AVP 0 8 9 101..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:101 telephone-event/8 000..a=sendrecv..a=ptime:20..a=direction:active.. ############################################################################ Thank you for your help Jephth? Feugn? _______________________________________________ Spce-user mailing listSpce-user at lists.sipwise.comhttps://lists.sipwise.com/listinfo/spce-user
>> 
>> _______________________________________________ Spce-user mailing listSpce-user at lists.sipwise.comhttps://lists.sipwise.com/listinfo/spce-user
> 
> 
> 
> 
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
> 
_______________________________________________
Spce-user mailing list
Spce-user at lists.sipwise.com
https://lists.sipwise.com/listinfo/spce-user



From me at nevian.org  Mon Feb  8 06:27:20 2016
From: me at nevian.org (Serge S. Yuriev)
Date: Mon, 8 Feb 2016 14:27:20 +0300
Subject: [Spce-user] Trunk to voicetrading configuration
In-Reply-To: <001a01d16047$f50c8d00$df25a700$@prisnets.ch>
References: <56B4E6B0.5090307@prisnets.ch> <56B4B8C1.5060203@prisnets.ch>
 <56B4C9D1.1090008@sipwise.com>
 <EA2E104E-D65F-4872-A38A-801C9103418C@nevian.org>
 <001a01d16047$f50c8d00$df25a700$@prisnets.ch>
Message-ID: <56B87B98.9090805@nevian.org>

Hi,

For a start I would try to include proxying - I bet your upstream 
dislike c= string if it don't match source/contact IP.
And ask provider to inspect theirs logs.

On 05/02/16 22:03, Jephth? Feugn? wrote:
> HI!
>
> 213.55.176.206, is my 4G connection behind which is connected my IP Phone registered with my hosted Sipwise CE server (xx.xx.xx.250).
> I can register directly to my Voicetrading account and place call behind my 4G connection, but not when I register to Sipwise.
>
> Thank you helping me to solve this situation.
>
> Jeph,
>
>
> _____
> Prisnets SA.
> Office:   +41 22 501 70 70 / Fax : +41 22 501 70 67
> Direct line : +41 22 508 72 70
> Mobile:  +41 78 728 92 97
> Email:     j.feugne at prisnets.ch
> Skype:   jephtech - Twitter:  @prisnet_ch
> http://www.prisnets.ch
> Prisnet Telecommunications SA.  Route de Saint-Julien 184 A, 1228 Plan-Les-Ouates CH.
>
> -----Message d'origine-----
> De : Spce-user [mailto:spce-user-bounces at lists.sipwise.com] De la part de Serge Yuriev
> Envoy? : vendredi, 5 f?vrier 2016 19:40
> ? : spce-user at lists.sipwise.com
> Objet : Re: [Spce-user] Trunk to voicetrading configuration
>
> Hi,
>
> Who is 213.55.176.206? Is this someone you should proxy before passing upstream? Maybe your provider filters such requests?
>

-- 
Serge S. Yuriev
Lead VoIP engineer



From j.feugne at prisnets.ch  Tue Feb  9 00:29:54 2016
From: j.feugne at prisnets.ch (=?UTF-8?Q?Jephth=c3=a9_Feugn=c3=a9?=)
Date: Tue, 9 Feb 2016 06:29:54 +0100
Subject: [Spce-user] Trunk to voicetrading configuration
In-Reply-To: <56B87B98.9090805@nevian.org>
References: <56B4E6B0.5090307@prisnets.ch> <56B4B8C1.5060203@prisnets.ch>
 <56B4C9D1.1090008@sipwise.com>
 <EA2E104E-D65F-4872-A38A-801C9103418C@nevian.org>
 <001a01d16047$f50c8d00$df25a700$@prisnets.ch> <56B87B98.9090805@nevian.org>
Message-ID: <56B97952.1000800@prisnets.ch>

Hello Serge,
where can I start looking in other to solve my issue. No way to get 
support form voicetrading, the have a strange support policy. the best 
they give to customer is their faq.

Regards,
Jeph

Le 08. 02. 16 12:27, Serge S. Yuriev a ?crit :
> Hi,
>
> For a start I would try to include proxying - I bet your upstream 
> dislike c= string if it don't match source/contact IP.
> And ask provider to inspect theirs logs.
>
> On 05/02/16 22:03, Jephth? Feugn? wrote:
>> HI!
>>
>> 213.55.176.206, is my 4G connection behind which is connected my IP 
>> Phone registered with my hosted Sipwise CE server (xx.xx.xx.250).
>> I can register directly to my Voicetrading account and place call 
>> behind my 4G connection, but not when I register to Sipwise.
>>
>> Thank you helping me to solve this situation.
>>
>> Jeph,
>>
>>
>> _____
>> Prisnets SA.
>> Office:   +41 22 501 70 70 / Fax : +41 22 501 70 67
>> Direct line : +41 22 508 72 70
>> Mobile:  +41 78 728 92 97
>> Email:     j.feugne at prisnets.ch
>> Skype:   jephtech - Twitter:  @prisnet_ch
>> http://www.prisnets.ch
>> Prisnet Telecommunications SA.  Route de Saint-Julien 184 A, 1228 
>> Plan-Les-Ouates CH.
>>
>> -----Message d'origine-----
>> De : Spce-user [mailto:spce-user-bounces at lists.sipwise.com] De la 
>> part de Serge Yuriev
>> Envoy? : vendredi, 5 f?vrier 2016 19:40
>> ? : spce-user at lists.sipwise.com
>> Objet : Re: [Spce-user] Trunk to voicetrading configuration
>>
>> Hi,
>>
>> Who is 213.55.176.206? Is this someone you should proxy before 
>> passing upstream? Maybe your provider filters such requests?
>>
>



From ricercaict at gmail.com  Wed Feb 10 03:22:57 2016
From: ricercaict at gmail.com (Giacomo)
Date: Wed, 10 Feb 2016 09:22:57 +0100
Subject: [Spce-user] APT Repo Error during ngcp-installer
Message-ID: <CAO_pOtW_=fyxAEv8syL2+U3cR_D6aPAFw-8LH635KwSnesdMyg@mail.gmail.com>

Dear All,
the problem is the following...

When i try to setup sipwise with ngcp-installer on a Debian 8 - 64bit
system after the dpkg -i of the latest stable (mr4.2.1) apt doesn't work
correctly and it shows the following:

Err https://deb.sipwise.com jessie/main amd64 Packages

Ign https://deb.sipwise.com jessie/main Translation-it_IT
Ign https://deb.sipwise.com jessie/main Translation-it
Ign https://deb.sipwise.com jessie/main Translation-en
W: Impossible to recovery
https://deb.sipwise.com/spce/mr4.2.1/dists/jessie/main/binary-amd64/Packages

E: Impossible to download some indexes: the old one will be used.

How can i solve the issue? If i try to navigate on the repo address
everything seems to be ok...

Thank you very much.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20160210/5ef860e9/attachment.html>

From agranig at sipwise.com  Wed Feb 10 07:34:14 2016
From: agranig at sipwise.com (Andreas Granig)
Date: Wed, 10 Feb 2016 13:34:14 +0100
Subject: [Spce-user] Rings once, then disconnects!
In-Reply-To: <DB5PR06MB1557E9176F0A2FCED9233799BED20@DB5PR06MB1557.eurprd06.prod.outlook.com>
References: <DB5PR06MB1557AB8F343FE2DD1C4AC44FBEDE0@DB5PR06MB1557.eurprd06.prod.outlook.com>
 <56AF3323.3090101@sipwise.com>
 <DB5PR06MB15571F52E939DC8818644634BEDE0@DB5PR06MB1557.eurprd06.prod.outlook.com>
 <56AF88BF.1020002@sipwise.com>
 <DB5PR06MB15573307ABE294694E402401BEDF0@DB5PR06MB1557.eurprd06.prod.outlook.com>
 <56B067B3.4030606@sipwise.com>
 <DB5PR06MB1557E9176F0A2FCED9233799BED20@DB5PR06MB1557.eurprd06.prod.outlook.com>
Message-ID: <56BB2E46.5070407@sipwise.com>

Hi,

I guess it wouldn't be too hard to add filtering video, there is
http://www.kamailio.org/docs/modules/4.3.x/modules/sdpops.html#sdpops.f.sdp_remove_media
for this purpose.

You can try it in BRANCH_ROUTE_SBC of
/etc/ngcp-config/templates/etc/kamailio/proxy/proxy.cfg.tt2 right before
the log line "Request leaving server".

Andreas

On 02/05/2016 07:40 AM, William Hilsum wrote:
> Hi Alex,
> 
> Apologies - I think I'm unintentionally being confusing!
> 
> This is not a problem as such with Sipwise - it is the sip client with the option "Allow video calls" that when turned on, it automatically causes my upstream carrier to reject the call (after a single ring, which is just weird...)
> 
> Anyway, I have another PBX here where on a per carrier basis, I have the option "Disable video calls". When this is ticked, it basically strips out all relevant headers such as what caused my calls on Sipwise to fail.
> 
> So my question really is, after finding out the issue here, is there anyway I can get Sipwise to strip out these headers to avoid similar issues? I have not tested, but, I am guessing if anyone has a VOIP videophone, they may have the same issue as the softphone wasn't actually trying to establish a video stream, it was just saying it was video compatible in the header.
> 
> Thanks,
> 
> William
> 
> -----Original Message-----
> From: Spce-user [mailto:spce-user-bounces at lists.sipwise.com] On Behalf Of Alex Lutay
> Sent: 02 February 2016 08:24
> To: spce-user at lists.sipwise.com
> Subject: Re: [Spce-user] Rings once, then disconnects!
> 
> Dear William,
> 
> Check incoming invite from softphone to Sipwise, I am strongly believe you will find the same part there.
> 
> Sipwise doesn't change SDP part a lot, mainly it is replacing IP (I believe you have replaced '<PBX-IP>' in SDP part manually, otherwise it is an error) and limit list of codecs if necessary (turned off by default).
> 
> You can also try to make a call from your softphone through your Carrier directly and compare invite sent by softphone and Sipwise.
> 
> On the first look I do not see anything which can cause 500 on carrier side here. Was the correct IPv4/IPv6 in <PBX-IP> ?
> 
> On 02/02/2016 01:03 AM, William Hilsum wrote:
>> These additional lines in the "invite (SDP) packet" from Sipwise to the carrier platform break the connection:
>>
>> m=video 32562 RTP/AVP 34
>> c=IN IP4 <PBX-IP>
>> a=rtpmap:34 H263/90000
>> a=fmtp:34 QCIF=1;CIF=1;SQCIF=1;CIF4=1
>> a=sendrecv
>> a=rtcp:32563
>> a=direction:both
> 
> --
> Alexander Lutay
> Head of Quality Assurance
> Sipwise GmbH, Campus 21/Europaring F15
> AT-2345 Brunn am Gebirge
> 
> Office: +43(0)13012036
> Email: alutay at sipwise.com
> Website: http://www.sipwise.com
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
> 


From j_e_vargas at live.com  Wed Feb 10 22:12:52 2016
From: j_e_vargas at live.com (Jose E. Vargas B.)
Date: Wed, 10 Feb 2016 19:12:52 -0800
Subject: [Spce-user] Trunk to voicetrading configuration
In-Reply-To: <56B97952.1000800@prisnets.ch>
References: <56B4E6B0.5090307@prisnets.ch> <56B4B8C1.5060203@prisnets.ch>
 <56B4C9D1.1090008@sipwise.com>
 <EA2E104E-D65F-4872-A38A-801C9103418C@nevian.org>
 <001a01d16047$f50c8d00$df25a700$@prisnets.ch> <56B87B98.9090805@nevian.org>
 <56B97952.1000800@prisnets.ch>
Message-ID: <BLU436-SMTP150E7282A4A3F4D45A9519BCA80@phx.gbl>

Hi, 
Maybe you are having NAT transversal issue when attempting to connect from behind the 4G hot spot.  I have had problems when working with 4G mifi and sipwise SPCE, some times not even being able to register.  Did you try putting your IP phone behind a different wifi router. Just my 2 cents, as I am also new with SPCE.
Jose  


> On Feb 8, 2016, at 9:29 PM, Jephth? Feugn? <j.feugne at prisnets.ch> wrote:
> 
> Hello Serge,
> where can I start looking in other to solve my issue. No way to get support form voicetrading, the have a strange support policy. the best they give to customer is their faq.
> 
> Regards,
> Jeph
> 
> Le 08. 02. 16 12:27, Serge S. Yuriev a ?crit :
>> Hi,
>> 
>> For a start I would try to include proxying - I bet your upstream dislike c= string if it don't match source/contact IP.
>> And ask provider to inspect theirs logs.
>> 
>> On 05/02/16 22:03, Jephth? Feugn? wrote:
>>> HI!
>>> 
>>> 213.55.176.206, is my 4G connection behind which is connected my IP Phone registered with my hosted Sipwise CE server (xx.xx.xx.250).
>>> I can register directly to my Voicetrading account and place call behind my 4G connection, but not when I register to Sipwise.
>>> 
>>> Thank you helping me to solve this situation.
>>> 
>>> Jeph,
>>> 
>>> 
>>> _____
>>> Prisnets SA.
>>> Office:   +41 22 501 70 70 / Fax : +41 22 501 70 67
>>> Direct line : +41 22 508 72 70
>>> Mobile:  +41 78 728 92 97
>>> Email:     j.feugne at prisnets.ch
>>> Skype:   jephtech - Twitter:  @prisnet_ch
>>> http://www.prisnets.ch
>>> Prisnet Telecommunications SA.  Route de Saint-Julien 184 A, 1228 Plan-Les-Ouates CH.
>>> 
>>> -----Message d'origine-----
>>> De : Spce-user [mailto:spce-user-bounces at lists.sipwise.com] De la part de Serge Yuriev
>>> Envoy? : vendredi, 5 f?vrier 2016 19:40
>>> ? : spce-user at lists.sipwise.com
>>> Objet : Re: [Spce-user] Trunk to voicetrading configuration
>>> 
>>> Hi,
>>> 
>>> Who is 213.55.176.206? Is this someone you should proxy before passing upstream? Maybe your provider filters such requests?
>>> 
>> 
> 
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 1776 bytes
Desc: not available
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20160210/331e0bb7/attachment.p7s>

From raul.alonso at tpartner.net  Thu Feb 11 07:18:32 2016
From: raul.alonso at tpartner.net (Raul)
Date: Thu, 11 Feb 2016 13:18:32 +0100
Subject: [Spce-user] Failed to create domain (A service could not be reached)
Message-ID: <089601d164c6$5335c4f0$f9a14ed0$@tpartner.net>

Hi guys, 

 

We have configured a virtual interface (with ip 10.255.255.100) to solve the
Audiocodes issue and then, since we did that, when we try to create a new
domain, NGCP-panel report us that error.

 

Feb 11 13:10:44 proxy02 ngcp-panel: ERROR: IP=88XXXXX
CALLED=Controller::Domain::create TX=1431E2001DAEC050 USER=administrator
DATA={ 'save' => 'Guardar', 'domain' => 'sip02.tpartner.net', 'submitid' =>
'', 'reseller.id' => '2', 'id' => ''} MSG="" LOG="Fallo al crear dominio
(DBIx::Class::Schema::txn_do(): problem connecting to "10.255.255.100", port
5582: Connection refused at /usr/share/perl5/NGCP/Panel/Utils/Prosody.pm
line 13 at /usr/share/perl5/NGCP/Panel/Controller/Domain.pm line 137#012)"

 

Thanks

Raul.

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20160211/0a24ee43/attachment.html>

From agranig at sipwise.com  Thu Feb 11 08:00:07 2016
From: agranig at sipwise.com (Andreas Granig)
Date: Thu, 11 Feb 2016 14:00:07 +0100
Subject: [Spce-user] Failed to create domain (A service could not be
 reached)
In-Reply-To: <089601d164c6$5335c4f0$f9a14ed0$@tpartner.net>
References: <089601d164c6$5335c4f0$f9a14ed0$@tpartner.net>
Message-ID: <56BC85D7.5010706@sipwise.com>

Hi,

Please check whether prosody is running and is listening on that ip.
Please also search the mailing list archive for prosody, since this
issue occured like 1-2 years ago when people were starting to use this
hack. Which SPCE version are you using? If I remember correctly, the
whole procedure has been simplified and optimized somewhere in the 3.x
series.

Andreas

On 02/11/2016 01:18 PM, Raul wrote:
> Hi guys,
> 
>  
> 
> We have configured a virtual interface (with ip 10.255.255.100) to solve
> the Audiocodes issue and then, since we did that, when we try to create
> a new domain, NGCP-panel report us that error.
> 
>  
> 
> Feb 11 13:10:44 proxy02 ngcp-panel: ERROR: IP=88XXXXX
> CALLED=Controller::Domain::create TX=1431E2001DAEC050 USER=administrator
> DATA={ 'save' => 'Guardar', 'domain' => 'sip02.tpartner.net', 'submitid'
> => '', 'reseller.id' => '2', 'id' => ''} MSG="" LOG="Fallo al crear
> dominio (DBIx::Class::Schema::txn_do(): problem connecting to
> "10.255.255.100", port 5582: Connection refused at
> /usr/share/perl5/NGCP/Panel/Utils/Prosody.pm line 13 at
> /usr/share/perl5/NGCP/Panel/Controller/Domain.pm line 137#012)"
> 
>  
> 
> Thanks
> 
> Raul.
> 
>  
> 
>  
> 
> 
> 
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
> 


From raul.alonso at tpartner.net  Thu Feb 11 09:11:27 2016
From: raul.alonso at tpartner.net (Raul)
Date: Thu, 11 Feb 2016 15:11:27 +0100
Subject: [Spce-user] Failed to create domain (A service could not be
	reached)
In-Reply-To: <56BC85D7.5010706@sipwise.com>
References: <089601d164c6$5335c4f0$f9a14ed0$@tpartner.net>
 <56BC85D7.5010706@sipwise.com>
Message-ID: <094101d164d6$192c2f00$4b848d00$@tpartner.net>

Hi Andreas,

Prosody si running but in 127.0.0.1 not in dummy IP.
I'm using the latest version LTS 3.8.4

Regrads,
Ra?l.

-----Mensaje original-----
De: Spce-user [mailto:spce-user-bounces at lists.sipwise.com] En nombre de
Andreas Granig
Enviado el: jueves, 11 de febrero de 2016 14:00
Para: spce-user at lists.sipwise.com
Asunto: Re: [Spce-user] Failed to create domain (A service could not be
reached)

Hi,

Please check whether prosody is running and is listening on that ip.
Please also search the mailing list archive for prosody, since this
issue occured like 1-2 years ago when people were starting to use this
hack. Which SPCE version are you using? If I remember correctly, the
whole procedure has been simplified and optimized somewhere in the 3.x
series.

Andreas

On 02/11/2016 01:18 PM, Raul wrote:
> Hi guys,
> 
>  
> 
> We have configured a virtual interface (with ip 10.255.255.100) to solve
> the Audiocodes issue and then, since we did that, when we try to create
> a new domain, NGCP-panel report us that error.
> 
>  
> 
> Feb 11 13:10:44 proxy02 ngcp-panel: ERROR: IP=88XXXXX
> CALLED=Controller::Domain::create TX=1431E2001DAEC050 USER=administrator
> DATA={ 'save' => 'Guardar', 'domain' => 'sip02.tpartner.net', 'submitid'
> => '', 'reseller.id' => '2', 'id' => ''} MSG="" LOG="Fallo al crear
> dominio (DBIx::Class::Schema::txn_do(): problem connecting to
> "10.255.255.100", port 5582: Connection refused at
> /usr/share/perl5/NGCP/Panel/Utils/Prosody.pm line 13 at
> /usr/share/perl5/NGCP/Panel/Controller/Domain.pm line 137#012)"
> 
>  
> 
> Thanks
> 
> Raul.
> 
>  
> 
>  
> 
> 
> 
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
> 
_______________________________________________
Spce-user mailing list
Spce-user at lists.sipwise.com
https://lists.sipwise.com/listinfo/spce-user



From matthias.hohl at telematica.at  Thu Feb 11 09:21:27 2016
From: matthias.hohl at telematica.at (Matthias Hohl)
Date: Thu, 11 Feb 2016 15:21:27 +0100 (CET)
Subject: [Spce-user] Lost connection to MySQL server during query (2013)
Message-ID: <1738202811.280332.1455200487946.JavaMail.zimbra@telematica.at>

Hello, 

we found a problem with SPCE and MySQL, so subscribers can't connect at some time: 
If we check log file, we see that the MySQL DB has a lost connection error. 

We have a intention that it maybe has something in common with our mySQL backup script, cause it just happens, and this not everytime, when the cronjob doing the script. 
I think it could be a problem with the mysqldump, that this freeze the tables and SPCE couldn't write into the tables. 

We try now with "--lock-tables=false" and waiting, if this happens again in the next few hours. 
What do you think, any other idea about that? 

Thanks. 



Backup-Job: 

#!/bin/sh 

DEST=backup-`date +"%Y%m%d-%H%M"` 

PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin" 

export PATH 



/usr/bin/mysqldump -uroot -pvN85tzTPp65QfW9 -A --events > /tmp/$DEST.mysql.sql 

tar czpf /tmp/$DEST.tgz -C / etc/ngcp-config etc/mysql home/jail/home/cdrexport -C /tmp $DEST.mysql.sql 

rm -f /tmp/$DEST.mysql.sql 



/usr/bin/ftp -pn >/dev/null 2>&1 <<end 

open ftp.xxx.xxx 

user xxx.xxx xxxx 

put /tmp/$DEST.tgz $DEST.tgz 

bye 

end 



rm -f /tmp/$DEST.tgz 



Cronjob: 

0,30 * * * * /root/backup.sh 



ERROR MESSAGE: 


Feb 10 00 :00:25 spce (local7.err) proxy[3749]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013) 

Feb 10 00 :00:25 spce (local7.err) proxy[3753]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013) 

Feb 10 00 :00:28 spce (local7.err) proxy[3741]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013) 

Feb 10 00 :00:29 spce (local7.err) proxy[3756]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013) 

Feb 10 00 :00:29 spce (local7.err) proxy[3752]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013) 

Feb 10 00 :00:31 spce (local7.err) proxy[3742]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013) 

Feb 10 00 :00:31 spce (local7.err) proxy[3747]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013) 

Feb 10 00 :30:18 spce (local7.err) proxy[3745]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013) 

Feb 10 00 :30:19 spce (local7.err) proxy[3742]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013) 

Feb 10 00 :30:19 spce (local7.err) proxy[3756]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013) 

Feb 10 00 :30:19 spce (local7.err) proxy[3741]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013) 

Feb 10 02 :00:17 spce (local7.err) proxy[3752]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013) 

Feb 10 02 :00:17 spce (local7.err) proxy[3749]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013) 

Feb 10 02 :00:17 spce (local7.err) proxy[3745]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013) 

Feb 10 02 :30:22 spce (local7.err) proxy[3752]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013) 

Feb 10 02 :30:22 spce (local7.err) proxy[3742]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013) 

Feb 10 02 :30:22 spce (local7.err) proxy[3747]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013) 

Feb 10 02 :30:22 spce (local7.err) proxy[3745]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013) 

Feb 10 02 :30:23 spce (local7.err) proxy[3753]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013) 

Feb 10 03 :00:19 spce (local7.err) proxy[3747]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013) 

Feb 10 03 :00:20 spce (local7.err) proxy[3749]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013) 

Feb 10 03 :00:22 spce (local7.err) proxy[3753]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013) 

Feb 10 03 :00:22 spce (local7.err) proxy[3745]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013) 

Feb 10 03 :00:23 spce (local7.err) proxy[3752]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013) 

Feb 10 03 :00:26 spce (local7.err) proxy[3749]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013) 

Feb 10 03 :30:22 spce (local7.err) proxy[3747]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013) 

Feb 10 03 :30:22 spce (local7.err) proxy[3753]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013) 

Feb 10 03 :30:23 spce (local7.err) proxy[3749]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013) 

Feb 10 06 :30:19 spce (local7.err) proxy[3747]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013) 

Feb 10 06 :30:19 spce (local7.err) proxy[3752]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013) 

Feb 10 06 :30:19 spce (local7.err) proxy[3742]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013) 

Feb 10 06 :30:19 spce (local7.err) proxy[3753]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013) 

Feb 10 06 :30:19 spce (local7.err) proxy[3741]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013) 

Feb 10 06 :30:19 spce (local7.err) proxy[3756]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013) 

Feb 10 08 :30:20 spce (local7.err) proxy[3747]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013) 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20160211/6a4cb818/attachment.html>

From me at nevian.org  Fri Feb 12 01:55:48 2016
From: me at nevian.org (Serge S. Yuriev)
Date: Fri, 12 Feb 2016 09:55:48 +0300
Subject: [Spce-user] Limit by minutes
Message-ID: <1779671455260148@web27h.yandex.ru>

An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20160212/10ed3dac/attachment.html>

From me at nevian.org  Fri Feb 12 01:59:09 2016
From: me at nevian.org (Serge Yuriev)
Date: Fri, 12 Feb 2016 09:59:09 +0300
Subject: [Spce-user] Trunk to voicetrading configuration
In-Reply-To: <56B97952.1000800@prisnets.ch>
References: <56B97952.1000800@prisnets.ch> <56B4E6B0.5090307@prisnets.ch>
 <56B4B8C1.5060203@prisnets.ch> <56B4C9D1.1090008@sipwise.com>
 <EA2E104E-D65F-4872-A38A-801C9103418C@nevian.org>
 <001a01d16047$f50c8d00$df25a700$@prisnets.ch> <56B87B98.9090805@nevian.org>
Message-ID: <7150A143-960A-4E4B-B2A6-B141080AF1BB@nevian.org>

Hi,

One more time: check why you announce customer IP in SDP? Perhaps you disabled proxying for domain/subscriber?

NB and go away from this provider as they should not leave you alone - you pay them.

-- 
Wbr, Serge via mobile

09.02.2016, 08:30, "Jephth? Feugn?" <j.feugne at prisnets.ch>:
> 
> Hello Serge,
> where can I start looking in other to solve my issue. No way to get 
> support form voicetrading, the have a strange support policy. the best 
> they give to customer is their faq.
> 
> Regards,
> Jeph
> 
> Le 08. 02. 16 12:27, Serge S. Yuriev a ?crit :
> 
>>  Hi,
>> 
>>  For a start I would try to include proxying - I bet your upstream 
>>  dislike c= string if it don't match source/contact IP.
>>  And ask provider to inspect theirs logs.
>> 
>>>  On 05/02/16 22:03, Jephth? Feugn? wrote:
>>>  HI!
>>> 
>>>  213.55.176.206, is my 4G connection behind which is connected my IP 
>>>  Phone registered with my hosted Sipwise CE server (xx.xx.xx.250).
>>>  I can register directly to my Voicetrading account and place call 
>>>  behind my 4G connection, but not when I register to Sipwise.
>>> 
>>>  Thank you helping me to solve this situation.
>>> 
>>>  Jeph,
>>> 
>>> 
>>>  _____
>>>  Prisnets SA.
>>>  Office: +41 22 501 70 70 / Fax : +41 22 501 70 67
>>>  Direct line : +41 22 508 72 70
>>>  Mobile: +41 78 728 92 97
>>>  Email: j.feugne at prisnets.ch
>>>  Skype: jephtech - Twitter: @prisnet_ch
>>>  http://www.prisnets.ch
>>>  Prisnet Telecommunications SA. Route de Saint-Julien 184 A, 1228 
>>>  Plan-Les-Ouates CH.
>>> 
>>>  -----Message d'origine-----
>>>  De : Spce-user [mailto:spce-user-bounces at lists.sipwise.com] De la 
>>>  part de Serge Yuriev
>>>  Envoy? : vendredi, 5 f?vrier 2016 19:40
>>>  ? : spce-user at lists.sipwise.com
>>>  Objet : Re: [Spce-user] Trunk to voicetrading configuration
>>> 
>>>  Hi,
>>> 
>>>  Who is 213.55.176.206? Is this someone you should proxy before 
>>>  passing upstream? Maybe your provider filters such requests?
> 
> 
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
> 


From alutay at sipwise.com  Fri Feb 12 10:05:20 2016
From: alutay at sipwise.com (Alex Lutay)
Date: Fri, 12 Feb 2016 16:05:20 +0100
Subject: [Spce-user] Upgrade to 4.2.1 causes in a cronjob failure
In-Reply-To: <027e01d15cdc$b940fea0$2bc2fbe0$@telematica.at>
References: <027e01d15cdc$b940fea0$2bc2fbe0$@telematica.at>
Message-ID: <56BDF4B0.40100@sipwise.com>

Hi all,

JFYI, the warning should be fixed with the latest
hotfix for mr4.2.1 ossbss:

> ngcp-ossbss (3.18.1.3+0~mr4.2.1.3) unstable; urgency=medium
> 
>   [ Kirill Solomko ]
>   * [fb693b2] MT#17669 adapted perl code for perl 5.20

Tnx for reporting!

On 02/01/2016 11:38 AM, Matthias Hohl wrote:
> I get this error per mail everytime when the fraud auto lock is running
> as cron.
> 
> What does this mean? An how can I solve it?
> 
> Cron <root at spce> if /usr/sbin/ngcp-check_active -q; then
> /usr/sbin/ngcp-fraud-auto-lock; fi
> 
> Smartmatch is experimental at /usr/share/perl5/Sipwise/Provisioning.pm
> line 1122.
> Use of my $_ is experimental at /usr/share/perl5/Sipwise/Provisioning.pm
> line 1146.
> defined(@array) is deprecated at /usr/share/perl5/PDF/Reuse.pm line 993.
> (Maybe you should just omit the defined()?)
> defined(@array) is deprecated at /usr/share/perl5/PDF/Reuse.pm line 993.
> (Maybe you should just omit the defined()?)
> Smartmatch is experimental at
> /usr/share/perl5/Sipwise/Provisioning/Voip/DB.pm line 748.
> given is experimental at /usr/share/perl5/Sipwise/Provisioning/Voip.pm
> line 6629.
> when is experimental at /usr/share/perl5/Sipwise/Provisioning/Voip.pm
> line 6630.
> when is experimental at /usr/share/perl5/Sipwise/Provisioning/Voip.pm
> line 6634.
> Smartmatch is experimental at
> /usr/share/perl5/Sipwise/Provisioning/Voip.pm line 6992.
> Smartmatch is experimental at
> /usr/share/perl5/Sipwise/Provisioning/Voip.pm line 7047.
> Smartmatch is experimental at
> /usr/share/perl5/Sipwise/Provisioning/Voip.pm line 7236.
> Smartmatch is experimental at
> /usr/share/perl5/Sipwise/Provisioning/Voip.pm line 7236.
> Smartmatch is experimental at
> /usr/share/perl5/Sipwise/Provisioning/Voip.pm line 7240.
> Smartmatch is experimental at
> /usr/share/perl5/Sipwise/Provisioning/Voip.pm line 7240.
> Smartmatch is experimental at
> /usr/share/perl5/Sipwise/Provisioning/Voip.pm line 7244.
> Smartmatch is experimental at
> /usr/share/perl5/Sipwise/Provisioning/Voip.pm line 7244.
> Smartmatch is experimental at
> /usr/share/perl5/Sipwise/Provisioning/Voip.pm line 7248.
> Smartmatch is experimental at
> /usr/share/perl5/Sipwise/Provisioning/Voip.pm line 7248.
> Smartmatch is experimental at
> /usr/share/perl5/Sipwise/Provisioning/Voip.pm line 7252.
> Smartmatch is experimental at
> /usr/share/perl5/Sipwise/Provisioning/Voip.pm line 7252.
> Use of my $_ is experimental at
> /usr/share/perl5/Sipwise/Provisioning/Voip.pm line 7259.

-- 
Alexander Lutay
Head of Quality Assurance
Sipwise GmbH, Campus 21/Europaring F15
AT-2345 Brunn am Gebirge

Office: +43(0)13012036
Email: alutay at sipwise.com
Website: http://www.sipwise.com


From matthias.hohl at telematica.at  Fri Feb 12 10:38:29 2016
From: matthias.hohl at telematica.at (Matthias Hohl)
Date: Fri, 12 Feb 2016 16:38:29 +0100 (CET)
Subject: [Spce-user] Urgent Problem after newest update 4.2.1
Message-ID: <495972341.303395.1455291509891.JavaMail.zimbra@telematica.at>

Hello, 

after latest update to 4.2.1 we analysied a problem with call forwardings. 
We set a CF for unconditional and unavailable and this works like a charme in the last releases, but after upgrade to 4.2.1 the CF doesn't work anymore. 

Any solution about this? 


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20160212/5998e063/attachment.html>

From matthias.hohl at telematica.at  Fri Feb 12 11:12:48 2016
From: matthias.hohl at telematica.at (Matthias Hohl)
Date: Fri, 12 Feb 2016 17:12:48 +0100 (CET)
Subject: [Spce-user] Concurrent max calls exceeded for callee
In-Reply-To: <21a6c01d1582c$eca02aa0$c5e07fe0$@telematica.at>
References: <08bc01d0ff47$05ffb770$11ff2650$@telematica.at>
 <094501d0ff5e$38125a80$a8370f80$@telematica.at>
 <2E0234B6-C07A-4D5A-AC8B-BB0EC1EB8694@telematica.at>
 <5639CECA.4000502@sipwise.com>
 <01fe01d13796$86cf2700$946d7500$@telematica.at> <56713A32.10403@sipwise.com>
 <21a6c01d1582c$eca02aa0$c5e07fe0$@telematica.at>
Message-ID: <1365632450.303696.1455293568776.JavaMail.zimbra@telematica.at>

Hello,

also with upgrade to 4.2.1 we still have the same problems with  Conncurent max calls exceeded for callee:

Example:
Feb 12 16:29:20 spce (local7.notice) proxy[3749]: NOTICE: <script>: Concurrent max calls exceeded for callee 'aef1bad0-ed48-4697-a55e-6ab25e723b5a' - R=sip:43137xxxxx at sip.xxx.at:5060 ID=3b0717627b45827e6a9a0f7a50f5f42a at xx.170.208.xxx:5060 UA='GlobalCall+T.38'
Feb 12 16:33:56 spce (local7.notice) proxy[3742]: NOTICE: <script>: Concurrent max calls exceeded for callee 'aef1bad0-ed48-4697-a55e-6ab25e723b5a' - R=sip:43137xxxxx at sip.xxx.at:5060 ID=2277847967b2b40325f5720a268a9056 at xx.170.208.xxx:5060 UA='GlobalCall+T.38'

But there are no concurrent calls on this subscriber!!!!

After doing "redis restart" it works again without problems.

Also there is NO voice message playing, that there are concurrent calls exceeded, so the callee just hear the ringing tone and nothing else.
But the Soundfile is set right. I load the default files and set the soundset on domain layer. so it should work.. outgoing the voice is speaking but incoming the callee doesn't hear anything just ringing!

please fix this as soon as possible.


Thanks!


----- Urspr?ngliche Mail -----
Von: "Matthias Hohl" <matthias.hohl at telematica.at>
An: "Daniel Grotti" <dgrotti at sipwise.com>, spce-user at lists.sipwise.com
Gesendet: Dienstag, 26. Januar 2016 12:30:17
Betreff: Re: [Spce-user] Concurrent max calls exceeded for callee

Hello,

when do you think, that you fix this issue, cause I have this problem
several times a week :/
I am currently on the latest 4.1.1 version including updates from last week.

Thanks.

-----Urspr?ngliche Nachricht-----
Von: Daniel Grotti [mailto:dgrotti at sipwise.com] 
Gesendet: Mittwoch, 16. Dezember 2015 11:17
An: Matthias Hohl <matthias.hohl at telematica.at>; spce-user at lists.sipwise.com
Betreff: Re: AW: [Spce-user] Concurrent max calls exceeded for callee

Hi Matthias,
We are aware of the problem on mr3.8.4 version and 4.x.
We are working on it since a while in order to fix definitely this issue.

Stay tuned.

--
Daniel Grotti
VoIP Engineer


Sipwise GmbH
Europaring F15 | 2345 Brunn am Gebirge, Austria | www.sipwise.com

On 12/16/2015 01:13 AM, Matthias Hohl wrote:
> Hello,
> 
> i have again this redis counter problem with "max calls exceeded for
callee"
> for some subscribers.
> It comes from time to time, that the SPCE told me, that max calls 
> exceeded but nobody is calling.
> 
> After restarting redis service (/etc/init.d/redis-server restart) 
> everything is working fine again, but I must restart the redis every few
days/week.
> 
> Is there another solution for this problem?
> 
> How could this happen, again and again on different subscribers?
> 
> Thanks for your answer!
> 
> 
> 
> -----Urspr?ngliche Nachricht-----
> Von: Spce-user [mailto:spce-user-bounces at lists.sipwise.com] Im Auftrag 
> von Daniel Grotti
> Gesendet: Mittwoch, 4. November 2015 10:24
> An: spce-user at lists.sipwise.com
> Betreff: Re: [Spce-user] Concurrent max calls exceeded for callee
> 
> Hi,
> you can reset redis counters for that user to 0.
> for example:
> 
> 
> # redis-cli -n 3 keys \*
> 
> 
> 
> # redis-cli -n 3 get userout:<SUBS_UUID> "2"
> # redis-cli -n 3 set userout:<SUBS_UUID> 0 OK # redis-cli -n 3 get 
> userout:<SUBS_UUID> "0"
> 
> 
> --
> Daniel Grotti
> VoIP Engineer
> 
> 
> Sipwise GmbH
> Europaring F15 | 2345 Brunn am Gebirge, Austria | www.sipwise.com
> 
> On 11/03/2015 10:29 AM, Matthias Hohl wrote:
>> Today the same problem happen again by an other subscriber. The 
>> subscriber has 4 lines but just one person is using the subscriber.
>> They place several calls this morning and called me now and told me, 
>> that she cant call place calls anymore cause phone told her: "all 
>> concurrent lines are in use, please try again later". I checked the 
>> server and the pbx and there are no active calls, so the limit cant 
>> be
> exceeded.
>>
>> After set the concurrent max limit to 5 or higher in subscriber 
>> preferences, calls works again, if i set it back to 4, the voice 
>> message comes again.
>>
>> This happen now several times with different subscribers in different 
>> time intervals. It looks like this is a redis bug or what do you think?
>>
>> Hope to read from you soon with some more informations.
>>
>> Btw: is restarting redis-server the right solution?
>>>
>>> /etc/init.d/redis-server stop
>>>
>>> rm -rf /var/lib/redis/*
>>>
>>> /etc/init.d/redis-server start
>>>
>>
>>
>> Von meinem iPhone gesendet
>>
>> Am 05.10.2015 um 13:09 schrieb Matthias Hohl 
>> <matthias.hohl at telematica.at <mailto:matthias.hohl at telematica.at>>:
>>
>>> I found a hint in an older posting?
>>>
>>> I have done now the following:
>>>
>>>  
>>>
>>> /etc/init.d/redis-server stop
>>>
>>> rm -rf /var/lib/redis/*
>>>
>>> /etc/init.d/redis-server start
>>>
>>>  
>>>
>>> It looks that it works now again, but can you tell me, what happened 
>>> and how this problem can be reproduced, and if this is the only 
>>> solution for it?
>>>
>>>  
>>>
>>> Thanks.
>>>
>>>  
>>>
>>> *Von:*Spce-user [mailto:spce-user-bounces at lists.sipwise.com] *Im 
>>> Auftrag von *Matthias Hohl
>>> *Gesendet:* Montag, 5. Oktober 2015 10:23
>>> *An:* spce-user at lists.sipwise.com
>>> <mailto:spce-user at lists.sipwise.com>
>>> *Betreff:* [Spce-user] Concurrent max calls exceeded for callee
>>>
>>>  
>>>
>>> Hello,
>>>
>>>  
>>>
>>> found out new problem today?
>>>
>>>  
>>>
>>> I subscriber can?t place or get calls and kamilio-proxy.log told me, 
>>> that ?Concurrent max calls exceeded for callee? and also sometimes 
>>> ?Concurrent_max calls exceeded for caller?
>>>
>>>  
>>>
>>> But the subscriber has 8 lines and no concurrent calls.
>>>
>>>  
>>>
>>>  
>>>
>>> What can I check to solve this problem?
>>>
>>>  
>>>
>>>  
>>>
>>> _______________________________________________
>>> Spce-user mailing list
>>> Spce-user at lists.sipwise.com <mailto:Spce-user at lists.sipwise.com>
>>> https://lists.sipwise.com/listinfo/spce-user
>>
>>
>> _______________________________________________
>> Spce-user mailing list
>> Spce-user at lists.sipwise.com
>> https://lists.sipwise.com/listinfo/spce-user
>>
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
> 
_______________________________________________
Spce-user mailing list
Spce-user at lists.sipwise.com
https://lists.sipwise.com/listinfo/spce-user


From matthias.hohl at telematica.at  Fri Feb 12 11:52:53 2016
From: matthias.hohl at telematica.at (Matthias Hohl)
Date: Fri, 12 Feb 2016 17:52:53 +0100 (CET)
Subject: [Spce-user] Urgent Problem after newest update 4.2.1
In-Reply-To: <495972341.303395.1455291509891.JavaMail.zimbra@telematica.at>
References: <495972341.303395.1455291509891.JavaMail.zimbra@telematica.at>
Message-ID: <E4F649CF-348C-45D4-8EC8-0E394134C717@telematica.at>

Hello again,

We found the failure. It happens in combination with the max concurrent call limit exceeded for callee problem i post several minutes later.



Von meinem iPhone gesendet

> Am 12.02.2016 um 16:39 schrieb Matthias Hohl <matthias.hohl at telematica.at>:
> 
> Hello,
> 
> after latest update to 4.2.1 we analysied a problem with call forwardings.
> We set a CF for unconditional and unavailable and this works like a charme in the last releases, but after upgrade to 4.2.1 the CF doesn't work anymore.
> 
> Any solution about this?
> 
> 
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20160212/e72b5536/attachment.html>

From me at nevian.org  Fri Feb 12 15:42:08 2016
From: me at nevian.org (Serge Yuriev)
Date: Fri, 12 Feb 2016 23:42:08 +0300
Subject: [Spce-user] Best way to replace SEMS
Message-ID: <A7FBF9D1-A0CE-4D16-B5A6-C5B9ABE93215@nevian.org>

Hello,

We need fully opaque SBC with media anchoring so I want to replace SEMS with something like FreeSWITCH or Asterisk.
That I need besides of headers processing?

btw There is fork of SEMS with needed features but it is a part of YETI-switch project and based on pretty old version. It would be nice to port these here.

-- 
Serge S. Yuriev





From manwe at sipdoc.net  Fri Feb 12 16:53:36 2016
From: manwe at sipdoc.net (Jon Bonilla (Manwe))
Date: Fri, 12 Feb 2016 22:53:36 +0100
Subject: [Spce-user] Best way to replace SEMS
In-Reply-To: <A7FBF9D1-A0CE-4D16-B5A6-C5B9ABE93215@nevian.org>
References: <A7FBF9D1-A0CE-4D16-B5A6-C5B9ABE93215@nevian.org>
Message-ID: <20160212225336.4eccdb5a@multivac>

El Fri, 12 Feb 2016 23:42:08 +0300
Serge Yuriev <me at nevian.org> escribi?:

> Hello,
> 
> We need fully opaque SBC with media anchoring so I want to replace SEMS with
> something like FreeSWITCH or Asterisk. That I need besides of headers
> processing?
> 
> btw There is fork of SEMS with needed features but it is a part of
> YETI-switch project and based on pretty old version. It would be nice to port
> these here.
> 

sems is a core part of the ngcp solution. It is heavily mantained and developed
by Frafos GmbH and Sipwise spends a lot of money and time supporting the
project. 

sems does much more than header filtering in the spce and even more in the pro
and carrier solutions. You cannot replace with other projects unless you want
to do heavy customization of your system. I can't even imagine how hard that
could be. 

Regarding those YETI functionalities you need, it would be nice if you could
sponsor Frafos so they add those ones to their public branch. Which are they
btw? 


cheers,

Jon

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: Firma digital OpenPGP
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20160212/89fca6d5/attachment.sig>

From matthias.hohl at telematica.at  Mon Feb 15 05:38:34 2016
From: matthias.hohl at telematica.at (Matthias Hohl)
Date: Mon, 15 Feb 2016 11:38:34 +0100 (CET)
Subject: [Spce-user] Lost connection to MySQL server during query (2013)
In-Reply-To: <1738202811.280332.1455200487946.JavaMail.zimbra@telematica.at>
References: <1738202811.280332.1455200487946.JavaMail.zimbra@telematica.at>
Message-ID: <0e8601d167dd$03b14e80$0b13eb80$@telematica.at>

Hello,

 

I want to give you a short update: The problem is still there.

 

If we do a mysql dump wie got following messages:

Also with mysql dump ?lock-tables? or ?single-transaction? there is no difference. By doing mysql dump the db lost connection, with everytime the same failure:

 

Feb 15 01:00:16 spce (local7.err) proxy[20447]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013)

Feb 15 01:00:16 spce (local7.err) proxy[20447]: ERROR: <core> [db_query.c:339]: db_do_update(): error while submitting query

Feb 15 01:00:16 spce (local7.err) proxy[20447]: ERROR: usrloc [ucontact.c:1142]: db_update_ucontact_ruid(): updating database failed

Feb 15 01:00:16 spce (local7.err) proxy[20447]: ERROR: usrloc [ucontact.c:1658]: update_contact_db(): failed to update database

Feb 15 01:00:16 spce (local7.err) proxy[20447]: ERROR: registrar [save.c:775]: update_contacts(): failed to update contact

 

We separate now the mysql dump from our other backup script, so the mysql dump will be done only 1 time a day at 01:00 o?clock to temporary fix the connection lost problem, until we get some input from you.

But in the meantime we found another ?connection lost? problem, which is not relevated to our mysqldump backup script.

 

It happens today 4 times at different times:

 

Feb 15 10:37:09 spce (local7.err) proxy[20453]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013)

Feb 15 10:37:09 spce (local7.err) proxy[20453]: ERROR: <core> [db_query.c:292]: db_do_delete(): error while submitting query

Feb 15 10:37:09 spce (local7.err) proxy[20453]: ERROR: dialog [dlg_db_handler.c:620]: remove_dialog_from_db(): failed to delete database information

 

I believe this could also be correlating with the ?redis counter? problem I posted (Concurrent max calls exceeded for callee) some days before. Maybe is this the reason, why the redis counter must be restarted to clear the active dialogs out ouf db.

 

Could this be true? And if yes, the main problem is the mysql lost connection problem, but how to fix that?

Has anybody maybe a solution for this problem?

 

It is very annoying if there are db lost connection problems :/

 

Thank you very much for any help.

 

 

 

Von: Spce-user [mailto:spce-user-bounces at lists.sipwise.com] Im Auftrag von Matthias Hohl
Gesendet: Donnerstag, 11. Februar 2016 15:21
An: spce-user at lists.sipwise.com
Betreff: [Spce-user] Lost connection to MySQL server during query (2013)

 

Hello,

 

we found a problem with SPCE and MySQL, so subscribers can't connect at some time:

If we check log file, we see that the MySQL DB has a lost connection error.

 

We have a intention that it maybe has something in common with our mySQL backup script, cause it just happens, and this not everytime, when the cronjob doing the script.

I think it could be a problem with the mysqldump, that this freeze the tables and SPCE couldn't write into the tables.

 

We try now with "--lock-tables=false" and waiting, if this happens again in the next few hours.

What do you think, any other idea about that?

 

Thanks.

 

Backup-Job:

#!/bin/sh

DEST=backup-`date +"%Y%m%d-%H%M"`

PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"

export PATH

 

/usr/bin/mysqldump -uroot -pvN85tzTPp65QfW9 -A --events > /tmp/$DEST.mysql.sql

tar czpf /tmp/$DEST.tgz -C / etc/ngcp-config etc/mysql home/jail/home/cdrexport -C /tmp $DEST.mysql.sql

rm -f /tmp/$DEST.mysql.sql

 

/usr/bin/ftp -pn >/dev/null 2>&1 <<end

open  <ftp://ftp.xxx.xxx> ftp.xxx.xxx

user xxx.xxx xxxx

put /tmp/$DEST.tgz $DEST.tgz

bye

end

 

rm -f /tmp/$DEST.tgz

 

Cronjob:

0,30 * * * *    /root/backup.sh

 

 

 

ERROR MESSAGE:

Feb 10 00:00:25 spce (local7.err) proxy[3749]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013)

Feb 10 00:00:25 spce (local7.err) proxy[3753]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013)

Feb 10 00:00:28 spce (local7.err) proxy[3741]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013)

Feb 10 00:00:29 spce (local7.err) proxy[3756]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013)

Feb 10 00:00:29 spce (local7.err) proxy[3752]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013)

Feb 10 00:00:31 spce (local7.err) proxy[3742]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013)

Feb 10 00:00:31 spce (local7.err) proxy[3747]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013)

Feb 10 00:30:18 spce (local7.err) proxy[3745]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013)

Feb 10 00:30:19 spce (local7.err) proxy[3742]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013)

Feb 10 00:30:19 spce (local7.err) proxy[3756]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013)

Feb 10 00:30:19 spce (local7.err) proxy[3741]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013)

Feb 10 02:00:17 spce (local7.err) proxy[3752]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013)

Feb 10 02:00:17 spce (local7.err) proxy[3749]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013)

Feb 10 02:00:17 spce (local7.err) proxy[3745]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013)

Feb 10 02:30:22 spce (local7.err) proxy[3752]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013)

Feb 10 02:30:22 spce (local7.err) proxy[3742]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013)

Feb 10 02:30:22 spce (local7.err) proxy[3747]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013)

Feb 10 02:30:22 spce (local7.err) proxy[3745]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013)

Feb 10 02:30:23 spce (local7.err) proxy[3753]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013)

Feb 10 03:00:19 spce (local7.err) proxy[3747]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013)

Feb 10 03:00:20 spce (local7.err) proxy[3749]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013)

Feb 10 03:00:22 spce (local7.err) proxy[3753]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013)

Feb 10 03:00:22 spce (local7.err) proxy[3745]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013)

Feb 10 03:00:23 spce (local7.err) proxy[3752]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013)

Feb 10 03:00:26 spce (local7.err) proxy[3749]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013)

Feb 10 03:30:22 spce (local7.err) proxy[3747]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013)

Feb 10 03:30:22 spce (local7.err) proxy[3753]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013)

Feb 10 03:30:23 spce (local7.err) proxy[3749]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013)

Feb 10 06:30:19 spce (local7.err) proxy[3747]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013)

Feb 10 06:30:19 spce (local7.err) proxy[3752]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013)

Feb 10 06:30:19 spce (local7.err) proxy[3742]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013)

Feb 10 06:30:19 spce (local7.err) proxy[3753]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013)

Feb 10 06:30:19 spce (local7.err) proxy[3741]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013)

Feb 10 06:30:19 spce (local7.err) proxy[3756]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013)

Feb 10 08:30:20 spce (local7.err) proxy[3747]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20160215/a8036837/attachment.html>

From apogrebennyk at sipwise.com  Mon Feb 15 05:59:49 2016
From: apogrebennyk at sipwise.com (Andrew Pogrebennyk)
Date: Mon, 15 Feb 2016 11:59:49 +0100
Subject: [Spce-user] Concurrent max calls exceeded for callee
In-Reply-To: <1365632450.303696.1455293568776.JavaMail.zimbra@telematica.at>
References: <08bc01d0ff47$05ffb770$11ff2650$@telematica.at>
 <094501d0ff5e$38125a80$a8370f80$@telematica.at>
 <2E0234B6-C07A-4D5A-AC8B-BB0EC1EB8694@telematica.at>
 <5639CECA.4000502@sipwise.com>
 <01fe01d13796$86cf2700$946d7500$@telematica.at> <56713A32.10403@sipwise.com>
 <21a6c01d1582c$eca02aa0$c5e07fe0$@telematica.at>
 <1365632450.303696.1455293568776.JavaMail.zimbra@telematica.at>
Message-ID: <56C1AFA5.9020505@sipwise.com>

Hi,
please share the kamailio-proxy.log for a start. Are you doing simple
call forward or multiple serial call forwards btw?

Regarding the voice message, we might need to look at the network trace
additionally. Did the audio message work before the upgrade on incoming
calls from the GW?

Regards,
Andrew

On 02/12/2016 05:12 PM, Matthias Hohl wrote:
> Hello,
> 
> also with upgrade to 4.2.1 we still have the same problems with  Conncurent max calls exceeded for callee:
> 
> Example:
> Feb 12 16:29:20 spce (local7.notice) proxy[3749]: NOTICE: <script>: Concurrent max calls exceeded for callee 'aef1bad0-ed48-4697-a55e-6ab25e723b5a' - R=sip:43137xxxxx at sip.xxx.at:5060 ID=3b0717627b45827e6a9a0f7a50f5f42a at xx.170.208.xxx:5060 UA='GlobalCall+T.38'
> Feb 12 16:33:56 spce (local7.notice) proxy[3742]: NOTICE: <script>: Concurrent max calls exceeded for callee 'aef1bad0-ed48-4697-a55e-6ab25e723b5a' - R=sip:43137xxxxx at sip.xxx.at:5060 ID=2277847967b2b40325f5720a268a9056 at xx.170.208.xxx:5060 UA='GlobalCall+T.38'
> 
> But there are no concurrent calls on this subscriber!!!!
> 
> After doing "redis restart" it works again without problems.
> 
> Also there is NO voice message playing, that there are concurrent calls exceeded, so the callee just hear the ringing tone and nothing else.
> But the Soundfile is set right. I load the default files and set the soundset on domain layer. so it should work.. outgoing the voice is speaking but incoming the callee doesn't hear anything just ringing!
> 
> please fix this as soon as possible.
> 
> 
> Thanks!



From matthias.hohl at telematica.at  Mon Feb 15 06:49:27 2016
From: matthias.hohl at telematica.at (Matthias Hohl)
Date: Mon, 15 Feb 2016 12:49:27 +0100 (CET)
Subject: [Spce-user] Concurrent max calls exceeded for callee
In-Reply-To: <56C1AFA5.9020505@sipwise.com>
References: <08bc01d0ff47$05ffb770$11ff2650$@telematica.at>
 <094501d0ff5e$38125a80$a8370f80$@telematica.at>
 <2E0234B6-C07A-4D5A-AC8B-BB0EC1EB8694@telematica.at>
 <5639CECA.4000502@sipwise.com>
 <01fe01d13796$86cf2700$946d7500$@telematica.at> <56713A32.10403@sipwise.com>
 <21a6c01d1582c$eca02aa0$c5e07fe0$@telematica.at>
 <1365632450.303696.1455293568776.JavaMail.zimbra@telematica.at>
 <56C1AFA5.9020505@sipwise.com>
Message-ID: <8F35314E-DF03-4A3B-BCCB-9B6D3486DA51@telematica.at>

Hello,

We do simple call forwards. Cf works again normally now after restarting redis...
But i believe it has something to do with the "db lost" problem i repost today in a orher topic.

No the audio messages also didn't work before the upgrade. :/ any idea?

Von meinem iPhone gesendet

> Am 15.02.2016 um 11:59 schrieb Andrew Pogrebennyk <apogrebennyk at sipwise.com>:
> 
> Hi,
> please share the kamailio-proxy.log for a start. Are you doing simple
> call forward or multiple serial call forwards btw?
> 
> Regarding the voice message, we might need to look at the network trace
> additionally. Did the audio message work before the upgrade on incoming
> calls from the GW?
> 
> Regards,
> Andrew
> 
>> On 02/12/2016 05:12 PM, Matthias Hohl wrote:
>> Hello,
>> 
>> also with upgrade to 4.2.1 we still have the same problems with  Conncurent max calls exceeded for callee:
>> 
>> Example:
>> Feb 12 16:29:20 spce (local7.notice) proxy[3749]: NOTICE: <script>: Concurrent max calls exceeded for callee 'aef1bad0-ed48-4697-a55e-6ab25e723b5a' - R=sip:43137xxxxx at sip.xxx.at:5060 ID=3b0717627b45827e6a9a0f7a50f5f42a at xx.170.208.xxx:5060 UA='GlobalCall+T.38'
>> Feb 12 16:33:56 spce (local7.notice) proxy[3742]: NOTICE: <script>: Concurrent max calls exceeded for callee 'aef1bad0-ed48-4697-a55e-6ab25e723b5a' - R=sip:43137xxxxx at sip.xxx.at:5060 ID=2277847967b2b40325f5720a268a9056 at xx.170.208.xxx:5060 UA='GlobalCall+T.38'
>> 
>> But there are no concurrent calls on this subscriber!!!!
>> 
>> After doing "redis restart" it works again without problems.
>> 
>> Also there is NO voice message playing, that there are concurrent calls exceeded, so the callee just hear the ringing tone and nothing else.
>> But the Soundfile is set right. I load the default files and set the soundset on domain layer. so it should work.. outgoing the voice is speaking but incoming the callee doesn't hear anything just ringing!
>> 
>> please fix this as soon as possible.
>> 
>> 
>> Thanks!
> 


From gerry.kernan at infinityit.ie  Mon Feb 15 08:06:17 2016
From: gerry.kernan at infinityit.ie (gerry kernan)
Date: Mon, 15 Feb 2016 13:06:17 +0000
Subject: [Spce-user] catch null useragent in register or invite.
Message-ID: <1e44bc87-3db2-46c3-a7b0-ef8ed228d351@infinityit.ie>

Hi 
 
I'm using the line in below kamailio-loadbalancer to catch any malicious registers or invites from known malicious UA types. I've noticed recently that we are getting invites and registers without any UA, I'm trying to catch these attempts with 
 
$ua == "<null>"  but I'm not catching them, is the syntax correct ?. all other regex are catching correctly so maybe <null> is incorrect.
 
 
if(is_method("REGISTER|INVITE") && ($ua =~ "^friendly.+" || $ua =~ "^sipvici.+" || $ua =~ "^sipcli.+" || $ua =~ "^VaxSIPUser.+" || $ua == "MizuPhone" || $ua == "voip" || $ua == "<null>"))
        {
                xlog("L_WARN", "Request rejected, malicious UA='$ua' IP='$si' - [% logreq_init -%]\n");
                exit;
 
 
 
 
Gerry Kernan
 
 
Infinity IT   |   17 The Mall   |   Beacon Court   |   Sandyford   |   Dublin D18 E3C8   |   Ireland
Tel:  +353 - (0)1 - 293 0090   |   E-Mail:  gerry.kernan at infinityit.ie
 
Managed IT Services       Infinity IT - www.infinityit.ie
IP Telephony                    Asterisk Consulting - www.asteriskconsulting.com
Contact Centre                Total Interact - www.totalinteract.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20160215/fa51a108/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 2681 bytes
Desc: not available
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20160215/fa51a108/attachment.jpg>

From barry at flanagan.ie  Mon Feb 15 08:10:56 2016
From: barry at flanagan.ie (Barry Flanagan)
Date: Mon, 15 Feb 2016 13:10:56 +0000
Subject: [Spce-user] catch null useragent in register or invite.
In-Reply-To: <1e44bc87-3db2-46c3-a7b0-ef8ed228d351@infinityit.ie>
References: <1e44bc87-3db2-46c3-a7b0-ef8ed228d351@infinityit.ie>
Message-ID: <CALJb54-5Y3VHeL+GSHPcOgVaiyq1umDZf620dGNhDETOtHtWRQ@mail.gmail.com>

On 15 Feb 2016 13:07, "gerry kernan" <gerry.kernan at infinityit.ie> wrote:
>
> Hi
>
>
>
> I?m using the line in below kamailio-loadbalancer to catch any malicious
registers or invites from known malicious UA types. I?ve noticed recently
that we are getting invites and registers without any UA, I?m trying to
catch these attempts with
>
>
>
> $ua == "<null>"  but I?m not catching them, is the syntax correct ?. all
other regex are catching correctly so maybe <null> is incorrect.
>

Hi Gerry,

I think it is $null you are looking for

-Barry Flanagan
>
>
>
>
> if(is_method("REGISTER|INVITE") && ($ua =~ "^friendly.+" || $ua =~
"^sipvici.+" || $ua =~ "^sipcli.+" || $ua =~ "^VaxSIPUser.+" || $ua ==
"MizuPhone" || $ua == "voip" || $ua == "<null>"))
>
>         {
>
>                 xlog("L_WARN", "Request rejected, malicious UA='$ua'
IP='$si' - [% logreq_init -%]\n");
>
>                 exit;
>
>
>
>
>
>
>
>
>
> Gerry Kernan
>
>
>
>
>
> Infinity IT   |   17 The Mall   |   Beacon Court   |   Sandyford   |
Dublin D18 E3C8   |   Ireland
>
> Tel:  +353 - (0)1 - 293 0090   |   E-Mail:  gerry.kernan at infinityit.ie
>
>
>
> Managed IT Services       Infinity IT - www.infinityit.ie
>
> IP Telephony                    Asterisk Consulting ?
www.asteriskconsulting.com
>
> Contact Centre                Total Interact ? www.totalinteract.com
>
>
>
>
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20160215/6d54e6dd/attachment.html>

From dgrotti at sipwise.com  Mon Feb 15 08:15:28 2016
From: dgrotti at sipwise.com (Daniel Grotti)
Date: Mon, 15 Feb 2016 14:15:28 +0100
Subject: [Spce-user] catch null useragent in register or invite.
In-Reply-To: <1e44bc87-3db2-46c3-a7b0-ef8ed228d351@infinityit.ie>
References: <1e44bc87-3db2-46c3-a7b0-ef8ed228d351@infinityit.ie>
Message-ID: <56C1CF70.9080809@sipwise.com>

Hi Gerry,
please try this in kamilio/proxy/kamailio.cfg it works for me.
For the null, try to check $ua == $null:


if( is_method("REGISTER|INVITE") && $sp != "5080" && !has_totag() )
         {
                 if($ua =~ "^friendly.+" || $ua =~ "^sipvici.+" || $ua 
=~ "^sipcli.+" || $ua =~ "^VaxSIPUser.+" || $ua == "MizuPhone" || $ua == 
"voip" || $ua == $null )
                 {
                         xlog("L_NOTICE", "UA='$ua' rejected - S=$rs 
SS='$rr' M=$rm R=$ru F=$fu T=$tu IP=$pr:$si:$sp UAIP=$si UA='$ua' ID=$ci 
\n");
                         exit;
                 }
         }
         ##end



I would be careful for the $null, cause you may reject good messages, 
just without User-Agent header.




*Daniel Grotti *
Head of Customer Support

Sipwise GmbH <http://www.sipwise.com> , Campus 21/Europaring F15
AT-2345 Brunn am Gebirge

Phone: +43(0)1 301 2032 <callto:+4313012032>
Email: dgrotti at sipwise.com <mailto:dgrotti at sipwise.com>
Website: www.sipwise.com <http://www.sipwise.com>

Particulars according Austrian Companies Code paragraph 14
"Sipwise GmbH" - Europaring F15 - 2345 Brunn am Gebirge
FN:305595f, Commercial Court Vienna, ATU64002206

On 02/15/2016 02:06 PM, gerry kernan wrote:
>
> Hi
>
> I?m using the line in below kamailio-loadbalancer to catch any 
> malicious registers or invites from known malicious UA types. I?ve 
> noticed recently that we are getting invites and registers without any 
> UA, I?m trying to catch these attempts with
>
> $ua == "<null>"  but I?m not catching them, is the syntax correct ?. 
> all other regex are catching correctly so maybe <null> is incorrect.
>
> if(is_method("REGISTER|INVITE") && ($ua =~ "^friendly.+" || $ua =~ 
> "^sipvici.+" || $ua =~ "^sipcli.+" || $ua =~ "^VaxSIPUser.+" || $ua == 
> "MizuPhone" || $ua == "voip" || $ua == "<null>"))
>
>         {
>
>                 xlog("L_WARN", "Request rejected, malicious UA='$ua' 
> IP='$si' - [% logreq_init -%]\n");
>
>                 exit;
>
> *Gerry Kernan*
>
> cid:image001.jpg at 01D105A5.2701B0E0
>
> *Infinity IT   |   17 The Mall   |   Beacon Court   |   Sandyford |   
> Dublin D18 E3C8   |   Ireland*
>
> *Tel: +353 - (0)1 - 293 0090   |   E-Mail: *gerry.kernan at infinityit.ie 
> <mailto:gerry.kernan at infinityit.ie>**
>
> **
>
> *Managed IT Services__Infinity IT*- www.infinityit.ie 
> <http://www.infinityit.ie/>
>
> *IP Telephony__Asterisk Consulting*? www.asteriskconsulting.com 
> <http://www.asteriskconsulting.com>
>
> *Contact Centre__Total Interact*? www.totalinteract.com 
> <http://www.totalinteract.com>
>
>
>
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20160215/6adfc12d/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 2681 bytes
Desc: not available
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20160215/6adfc12d/attachment.jpe>

From gerry.kernan at infinityit.ie  Mon Feb 15 08:17:50 2016
From: gerry.kernan at infinityit.ie (gerry kernan)
Date: Mon, 15 Feb 2016 13:17:50 +0000
Subject: [Spce-user] catch null useragent in register or invite.
In-Reply-To: <56C1CF70.9080809@sipwise.com>
References: <1e44bc87-3db2-46c3-a7b0-ef8ed228d351@infinityit.ie>
 <56C1CF70.9080809@sipwise.com>
Message-ID: <a3511e43-e6a8-4cd1-a245-f3789cbe6710@infinityit.ie>

Hi Barry and Daniel
 
Thanks for your quick responses .
 
 
Gerry Kernan
 
 
Infinity IT   |   17 The Mall   |   Beacon Court   |   Sandyford   |   Dublin D18 E3C8   |   Ireland
Tel:  +353 - (0)1 - 293 0090   |   E-Mail:  gerry.kernan at infinityit.ie
 
Managed IT Services       Infinity IT - www.infinityit.ie
IP Telephony                    Asterisk Consulting - www.asteriskconsulting.com
Contact Centre                Total Interact - www.totalinteract.com
 
From: Spce-user [mailto:spce-user-bounces at lists.sipwise.com] On Behalf Of Daniel Grotti
Sent: Monday 15 February 2016 13:15
To: spce-user at lists.sipwise.com
Subject: Re: [Spce-user] catch null useragent in register or invite.
 
Hi Gerry,
please try this in kamilio/proxy/kamailio.cfg it works for me.
For the null, try to check $ua == $null:


if( is_method("REGISTER|INVITE") && $sp != "5080" && !has_totag() )
        {
                if($ua =~ "^friendly.+" || $ua =~ "^sipvici.+" || $ua =~ "^sipcli.+" || $ua =~ "^VaxSIPUser.+" || $ua == "MizuPhone" || $ua == "voip" || $ua == $null )
                {
                        xlog("L_NOTICE", "UA='$ua' rejected - S=$rs SS='$rr' M=$rm R=$ru F=$fu T=$tu IP=$pr:$si:$sp UAIP=$si UA='$ua' ID=$ci \n");
                        exit;
                }
        }
        ##end



I would be careful for the $null, cause you may reject good messages, just without User-Agent header.



Daniel Grotti 
Head of Customer Support 
Sipwise GmbH , Campus 21/Europaring F15
AT-2345 Brunn am Gebirge 
Phone:  +43(0)1 301 2032 
Email:  dgrotti at sipwise.com 
Website:  www.sipwise.com 
Particulars according Austrian Companies Code paragraph 14
"Sipwise GmbH" - Europaring F15 - 2345 Brunn am Gebirge
FN:305595f, Commercial Court Vienna, ATU64002206 
On 02/15/2016 02:06 PM, gerry kernan wrote:
Hi 
 
I'm using the line in below kamailio-loadbalancer to catch any malicious registers or invites from known malicious UA types. I've noticed recently that we are getting invites and registers without any UA, I'm trying to catch these attempts with 
 
$ua == "<null>"  but I'm not catching them, is the syntax correct ?. all other regex are catching correctly so maybe <null> is incorrect.
 
 
if(is_method("REGISTER|INVITE") && ($ua =~ "^friendly.+" || $ua =~ "^sipvici.+" || $ua =~ "^sipcli.+" || $ua =~ "^VaxSIPUser.+" || $ua == "MizuPhone" || $ua == "voip" || $ua == "<null>"))
        {
                xlog("L_WARN", "Request rejected, malicious UA='$ua' IP='$si' - [% logreq_init -%]\n");
                exit;
 
 
 
 
Gerry Kernan
 
 
Infinity IT   |   17 The Mall   |   Beacon Court   |   Sandyford   |   Dublin D18 E3C8   |   Ireland
Tel:  +353 - (0)1 - 293 0090   |   E-Mail:  gerry.kernan at infinityit.ie
 
Managed IT Services       Infinity IT - www.infinityit.ie
IP Telephony                    Asterisk Consulting - www.asteriskconsulting.com
Contact Centre                Total Interact - www.totalinteract.com
 



_______________________________________________Spce-user mailing listSpce-user at lists.sipwise.comhttps://lists.sipwise.com/listinfo/spce-user
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20160215/8478ea29/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 2681 bytes
Desc: not available
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20160215/8478ea29/attachment.jpg>

From alutay at sipwise.com  Mon Feb 15 11:11:57 2016
From: alutay at sipwise.com (Alex Lutay)
Date: Mon, 15 Feb 2016 17:11:57 +0100
Subject: [Spce-user] APT Repo Error during ngcp-installer
In-Reply-To: <CAO_pOtW_=fyxAEv8syL2+U3cR_D6aPAFw-8LH635KwSnesdMyg@mail.gmail.com>
References: <CAO_pOtW_=fyxAEv8syL2+U3cR_D6aPAFw-8LH635KwSnesdMyg@mail.gmail.com>
Message-ID: <56C1F8CD.4030608@sipwise.com>

Hi,

Do you still noticing the issue?
I cannot reproduce it locally. :-(

On 02/10/2016 09:22 AM, Giacomo wrote:
> Dear All,
> the problem is the following...
> 
> When i try to setup sipwise with ngcp-installer on a Debian 8 - 64bit
> system after the dpkg -i of the latest stable (mr4.2.1) apt doesn't work
> correctly and it shows the following:
> 
> Err https://deb.sipwise.com jessie/main amd64 Packages
> 
> Ign https://deb.sipwise.com jessie/main Translation-it_IT
> Ign https://deb.sipwise.com jessie/main Translation-it
> Ign https://deb.sipwise.com jessie/main Translation-en
> W: Impossible to recovery
> https://deb.sipwise.com/spce/mr4.2.1/dists/jessie/main/binary-amd64/Packages
> 
> E: Impossible to download some indexes: the old one will be used.
> 
> How can i solve the issue? If i try to navigate on the repo address
> everything seems to be ok...
> 
> Thank you very much.

-- 
Alex Lutay


From William at ezpcltd.com  Tue Feb 16 14:36:49 2016
From: William at ezpcltd.com (William Hilsum)
Date: Tue, 16 Feb 2016 19:36:49 +0000
Subject: [Spce-user] Is there a full guide to parameters?
Message-ID: <DB5PR06MB1557925C19D90666E04D90D6BEAD0@DB5PR06MB1557.eurprd06.prod.outlook.com>

Hi

Whilst some parameters are self-explanatory and the documentation or help text explains, there are some which are pretty similar and the text isn't too clear.

Right now, I need to set per customer concurrent call limits and I'm struggling to understand the difference between:

Concurrent_max
Concurrent_max_per_account
Concurrent_max_total

There are also:

Concurrent_max_out
Concurrent_max_out_per_account
Concurrent_max_out_total

... I can't understand the need to set these differently from the above, but, after I know the first lot, I think I can guess what these are!

This aside, so I don't have to ask in the future, is there anywhere that lists a complete list of settings/profile options as I couldn't see these listed in the main manual?

Thanks,

William

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20160216/77b2059d/attachment.html>

From dgrotti at sipwise.com  Wed Feb 17 01:53:51 2016
From: dgrotti at sipwise.com (Daniel Grotti)
Date: Wed, 17 Feb 2016 07:53:51 +0100
Subject: [Spce-user] Is there a full guide to parameters?
In-Reply-To: <DB5PR06MB1557925C19D90666E04D90D6BEAD0@DB5PR06MB1557.eurprd06.prod.outlook.com>
Message-ID: <b3c1746a-fc2c-4409-ae3b-e4fe728042cc@email.android.com>

Hi William,
*_max define the amount of incoming+outbound calls.

*_max_out define the amount of outbound calls only.

Other thing you should know is that *_total includes also the call to local services such as voicemail, conference.

No there is no document for that, they are explained in the online help.
We will try to be more detailed then.

Daniel


On Feb 16, 2016 8:36 PM, William Hilsum <William at ezpcltd.com> wrote:
>
> Hi
>
> ?
>
> Whilst some parameters are self-explanatory and the documentation or help text explains, there are some which are pretty similar and the text isn?t too clear.
>
> ?
>
> Right now, I need to set per customer concurrent call limits and I?m struggling to understand the difference between:
>
> ?
>
> Concurrent_max
>
> Concurrent_max_per_account
>
> Concurrent_max_total
>
> ?
>
> There are also:
>
> ?
>
> Concurrent_max_out
>
> Concurrent_max_out_per_account
>
> Concurrent_max_out_total
>
> ?
>
> ? I can?t understand the need to set these differently from the above, but, after I know the first lot, I think I can guess what these are!
>
> ?
>
> This aside, so I don?t have to ask in the future, is there anywhere that lists a complete list of settings/profile options as I couldn?t see these listed in the main manual?
>
> ?
>
> Thanks,
>
> ?
>
> William
>
> ?

From admin at marcoteixeira.com  Wed Feb 17 03:36:28 2016
From: admin at marcoteixeira.com (Marco Teixeira)
Date: Wed, 17 Feb 2016 08:36:28 +0000
Subject: [Spce-user] Is there a full guide to parameters?
In-Reply-To: <DB5PR06MB1557925C19D90666E04D90D6BEAD0@DB5PR06MB1557.eurprd06.prod.outlook.com>
References: <DB5PR06MB1557925C19D90666E04D90D6BEAD0@DB5PR06MB1557.eurprd06.prod.outlook.com>
Message-ID: <CAD7smbj8ZxEEvfCTf6yoT54j8Rne98qeTVgQbYq+vnLZ_YUf3Q@mail.gmail.com>

Try hoovering (or clicking) your mouse over the question mark, next to each
parameter...

---
?Marco
---


On Tue, Feb 16, 2016 at 7:36 PM, William Hilsum <William at ezpcltd.com> wrote:

> Hi
>
>
>
> Whilst some parameters are self-explanatory and the documentation or help
> text explains, there are some which are pretty similar and the text isn?t
> too clear.
>
>
>
> Right now, I need to set per customer concurrent call limits and I?m
> struggling to understand the difference between:
>
>
>
> Concurrent_max
>
> Concurrent_max_per_account
>
> Concurrent_max_total
>
>
>
> There are also:
>
>
>
> Concurrent_max_out
>
> Concurrent_max_out_per_account
>
> Concurrent_max_out_total
>
>
>
> ? I can?t understand the need to set these differently from the above,
> but, after I know the first lot, I think I can guess what these are!
>
>
>
> This aside, so I don?t have to ask in the future, is there anywhere that
> lists a complete list of settings/profile options as I couldn?t see these
> listed in the main manual?
>
>
>
> Thanks,
>
>
>
> William
>
>
>
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20160217/ddf6b2e7/attachment.html>

From William at ezpcltd.com  Wed Feb 17 05:05:48 2016
From: William at ezpcltd.com (William Hilsum)
Date: Wed, 17 Feb 2016 10:05:48 +0000
Subject: [Spce-user] Is there a full guide to parameters?
In-Reply-To: <CAD7smbj8ZxEEvfCTf6yoT54j8Rne98qeTVgQbYq+vnLZ_YUf3Q@mail.gmail.com>
References: <DB5PR06MB1557925C19D90666E04D90D6BEAD0@DB5PR06MB1557.eurprd06.prod.outlook.com>
 <CAD7smbj8ZxEEvfCTf6yoT54j8Rne98qeTVgQbYq+vnLZ_YUf3Q@mail.gmail.com>
Message-ID: <DB5PR06MB155799F85D074AF802B23F32BEAE0@DB5PR06MB1557.eurprd06.prod.outlook.com>

Thanks, but, I already said I had!

It wasn?t too clear about the diffence between Max / max_total?



On Tue, Feb 16, 2016 at 7:36 PM, William Hilsum <William at ezpcltd.com<mailto:William at ezpcltd.com>> wrote:
Hi

Whilst some parameters are self-explanatory and the documentation or help text explains, there are some which are pretty similar and the text isn?t too clear.

Right now, I need to set per customer concurrent call limits and I?m struggling to understand the difference between:

Concurrent_max
Concurrent_max_per_account
Concurrent_max_total

There are also:

Concurrent_max_out
Concurrent_max_out_per_account
Concurrent_max_out_total

? I can?t understand the need to set these differently from the above, but, after I know the first lot, I think I can guess what these are!

This aside, so I don?t have to ask in the future, is there anywhere that lists a complete list of settings/profile options as I couldn?t see these listed in the main manual?

Thanks,

William


_______________________________________________
Spce-user mailing list
Spce-user at lists.sipwise.com<mailto:Spce-user at lists.sipwise.com>
https://lists.sipwise.com/listinfo/spce-user

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20160217/f0b811e1/attachment.html>

From William at ezpcltd.com  Wed Feb 17 05:06:39 2016
From: William at ezpcltd.com (William Hilsum)
Date: Wed, 17 Feb 2016 10:06:39 +0000
Subject: [Spce-user] Is there a full guide to parameters?
In-Reply-To: <b3c1746a-fc2c-4409-ae3b-e4fe728042cc@email.android.com>
References: <DB5PR06MB1557925C19D90666E04D90D6BEAD0@DB5PR06MB1557.eurprd06.prod.outlook.com>
 <b3c1746a-fc2c-4409-ae3b-e4fe728042cc@email.android.com>
Message-ID: <DB5PR06MB15576976D6198F58DB77E77EBEAE0@DB5PR06MB1557.eurprd06.prod.outlook.com>

Hi Daniel,

That is great, thank you.

I had no idea that it could treat calls in/out and the internal (voicemail) separately!

Thanks,

William

-----Original Message-----
From: Daniel Grotti [mailto:dgrotti at sipwise.com] 
Sent: 17 February 2016 06:54
To: William Hilsum <William at ezpcltd.com>
Cc: spce-user at lists.sipwise.com
Subject: Re: [Spce-user] Is there a full guide to parameters?

Hi William,
*_max define the amount of incoming+outbound calls.

*_max_out define the amount of outbound calls only.

Other thing you should know is that *_total includes also the call to local services such as voicemail, conference.

No there is no document for that, they are explained in the online help.
We will try to be more detailed then.

Daniel


On Feb 16, 2016 8:36 PM, William Hilsum <William at ezpcltd.com> wrote:
>
> Hi
>
> ?
>
> Whilst some parameters are self-explanatory and the documentation or help text explains, there are some which are pretty similar and the text isn?t too clear.
>
> ?
>
> Right now, I need to set per customer concurrent call limits and I?m struggling to understand the difference between:
>
> ?
>
> Concurrent_max
>
> Concurrent_max_per_account
>
> Concurrent_max_total
>
> ?
>
> There are also:
>
> ?
>
> Concurrent_max_out
>
> Concurrent_max_out_per_account
>
> Concurrent_max_out_total
>
> ?
>
> ? I can?t understand the need to set these differently from the above, but, after I know the first lot, I think I can guess what these are!
>
> ?
>
> This aside, so I don?t have to ask in the future, is there anywhere that lists a complete list of settings/profile options as I couldn?t see these listed in the main manual?
>
> ?
>
> Thanks,
>
> ?
>
> William
>
> ?

From admin at marcoteixeira.com  Wed Feb 17 09:35:21 2016
From: admin at marcoteixeira.com (Marco Teixeira)
Date: Wed, 17 Feb 2016 14:35:21 +0000
Subject: [Spce-user] Is there a full guide to parameters?
In-Reply-To: <DB5PR06MB155799F85D074AF802B23F32BEAE0@DB5PR06MB1557.eurprd06.prod.outlook.com>
References: <DB5PR06MB1557925C19D90666E04D90D6BEAD0@DB5PR06MB1557.eurprd06.prod.outlook.com>
 <CAD7smbj8ZxEEvfCTf6yoT54j8Rne98qeTVgQbYq+vnLZ_YUf3Q@mail.gmail.com>
 <DB5PR06MB155799F85D074AF802B23F32BEAE0@DB5PR06MB1557.eurprd06.prod.outlook.com>
Message-ID: <CAD7smbj+bZVTNW4-GmZ1PgfRGw7_YBe_PwLTi-_BOm6Z9AvrNg@mail.gmail.com>

:)
Yes you did. My bad for reading hastily.



On Wed, Feb 17, 2016 at 10:05 AM, William Hilsum <William at ezpcltd.com>
wrote:

> Thanks, but, I already said I had!
>
>
>
> It wasn?t too clear about the diffence between Max / max_total?
>
>
>
>
>
>
>
> On Tue, Feb 16, 2016 at 7:36 PM, William Hilsum <William at ezpcltd.com>
> wrote:
>
> Hi
>
>
>
> Whilst some parameters are self-explanatory and the documentation or help
> text explains, there are some which are pretty similar and the text isn?t
> too clear.
>
>
>
> Right now, I need to set per customer concurrent call limits and I?m
> struggling to understand the difference between:
>
>
>
> Concurrent_max
>
> Concurrent_max_per_account
>
> Concurrent_max_total
>
>
>
> There are also:
>
>
>
> Concurrent_max_out
>
> Concurrent_max_out_per_account
>
> Concurrent_max_out_total
>
>
>
> ? I can?t understand the need to set these differently from the above,
> but, after I know the first lot, I think I can guess what these are!
>
>
>
> This aside, so I don?t have to ask in the future, is there anywhere that
> lists a complete list of settings/profile options as I couldn?t see these
> listed in the main manual?
>
>
>
> Thanks,
>
>
>
> William
>
>
>
>
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
>
>
>
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20160217/e6483622/attachment.html>

From matthias.hohl at telematica.at  Thu Feb 18 06:06:43 2016
From: matthias.hohl at telematica.at (Matthias Hohl)
Date: Thu, 18 Feb 2016 12:06:43 +0100 (CET)
Subject: [Spce-user] Notification sounds (sound_set) by calls from
	PSTN/Peering not working
Message-ID: <01e801d16a3c$72a89d50$57f9d7f0$@telematica.at>

Hello,

 

i post several days ago a problem, that there is no voice message playing,
if there are concurrent calls exceeded, so the caller just hear the ringing
tone and nothing else.

Today I did some more tests and found out the problem, but no solution for
it.

 

The problem just happen, if the call comes from PSTN/Peering.

If the caller is another subscriber on the server, the notification sounds
works perfectly.

 

So if somebody from PSTN is calling a local subscriber, and this local
subscriber is not online or busy or call limit exceeded or whatever, the
call goes to the application server but the caller just hear the normal
ringing tone and no notification voice until the caller hang up by himself.

So the caller from PSTN/Peering doesn't recognize that the callee will never
answer and get no information about that the callee is not available, or
busy, or whatever.

BUT if the callee get called from another local subscriber, the notification
about unavailable or busy or whatever, will be played correctly.

So the problem just happen, if the call comes from a Peering (PSTN).

 

So normally the sound "callee_offline.wav" or "callee_busy.wav" etc should
be played as well if the call comes from PSTN/peering.

I set the soundset correctly and also activate the loop function, but like I
wrote, it just works with local calls but not with PSTN/peering calls.

 

Maybe I have somewhere a setting false or whatever, don't know.

I also checked the config.yml but can't find any hint for solving this
problem.

 

Would be nice, if you could help me out with this problem.

 

THANKS!

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20160218/e0414366/attachment.html>

From alutay at sipwise.com  Thu Feb 18 06:53:10 2016
From: alutay at sipwise.com (Alex Lutay)
Date: Thu, 18 Feb 2016 12:53:10 +0100
Subject: [Spce-user] Vulnerability Report CVE-2015-7547
Message-ID: <56C5B0A6.6000501@sipwise.com>

Hi all,

As reported by Google on their security blog recently,
a major security whole in glibc was discovered.

Affected systems: All NGCP versions

Please ensure you have appropriate Debian security repository enabled:
 - jessie based mr4.2.1+
> deb https://debian.sipwise.com/debian-security/ jessie-security main contrib non-free
 - wheezy based 3.0, 3.1, mr3.2.* - mr4.1.* (including mr3.8.* LTS)
> deb http://debian.sipwise.com/debian-security/ wheezy-security main contrib non-free
 - squeeze based 2.8 LTS
> deb http://debian.sipwise.com/debian/ squeeze-lts main

(you can use other non-Sipwise mirrors if you trust them,
while please verify you have latest/fixed packages versions there).

Ensure all the packages from glibc/eglibc sources are installed to the
fixed version. See the list of fixed versions here:
https://security-tracker.debian.org/tracker/CVE-2015-7547

All the Sipwise software are dynamically linked against glibc,
so all the services restart are necessary.

At the same time Sipwise doesn't have the information about the
statically linked software which can be installed on your servers,
so it is highly recommended to update all packages to the latest
available version:

>   apt-get update && apt-get upgrade && \
>   ngcp-update-db-schema && ngcp-update-cfg-schema && \
>   ngcpcfg apply "applying changes for CVE-2015-7547"

NOTE: please do not forget to update customtt if you have them before
applying new changes!

Additional Information:
> https://security-tracker.debian.org/tracker/CVE-2015-7547
> https://googleonlinesecurity.blogspot.co.at/2016/02/cve-2015-7547-glibc-getaddrinfo-stack.html
> https://sourceware.org/ml/libc-alpha/2016-02/msg00416.html

-- 
Alex Lutay
Head of Quality Assurance
Sipwise GmbH, Campus 21/Europaring F15
AT-2345 Brunn am Gebirge

Office: +43(0)13012036
Email: alutay at sipwise.com
Website: https://www.sipwise.com

Meet us @ ANGACOM: Hall 10.1 / booth N10
Exhibition and Congress for Broadband,
Cable & Satellite: 07 ? 09 June, 2016 in Cologne


From agranig at sipwise.com  Thu Feb 18 17:07:47 2016
From: agranig at sipwise.com (Andreas Granig)
Date: Thu, 18 Feb 2016 23:07:47 +0100
Subject: [Spce-user] Notification sounds (sound_set) by calls from
 PSTN/Peering not working
In-Reply-To: <01e801d16a3c$72a89d50$57f9d7f0$@telematica.at>
References: <01e801d16a3c$72a89d50$57f9d7f0$@telematica.at>
Message-ID: <56C640B3.8000402@sipwise.com>

Hi,

Maybe the peering server is ignoring the early media played by the system?

We've already thought about adding a config option to actually connect
the call and play the announcement within the connected call instead of
inside early media. Never followed through as it might have a regulatory
impact, since in that case costs are imposed on the calling party in
that case. It's on our radar, no specific release on when to do it though.

Andreas

On 02/18/2016 12:06 PM, Matthias Hohl wrote:
> Hello,
> 
>  
> 
> i post several days ago a problem, that there is no voice message
> playing, if there are concurrent calls exceeded, so the caller just hear
> the ringing tone and nothing else.
> 
> Today I did some more tests and found out the problem, but no solution
> for it.
> 
>  
> 
> The problem just happen, if the call comes from PSTN/Peering.
> 
> If the caller is another subscriber on the server, the notification
> sounds works perfectly.
> 
>  
> 
> So if somebody from PSTN is calling a local subscriber, and this local
> subscriber is not online or busy or call limit exceeded or whatever, the
> call goes to the application server but the caller just hear the normal
> ringing tone and no notification voice until the caller hang up by himself.
> 
> So the caller from PSTN/Peering doesn?t recognize that the callee will
> never answer and get no information about that the callee is not
> available, or busy, or whatever.
> 
> BUT if the callee get called from another local subscriber, the
> notification about unavailable or busy or whatever, will be played
> correctly.
> 
> So the problem just happen, if the call comes from a Peering (PSTN).
> 
>  
> 
> So normally the sound ?callee_offline.wav? or ?callee_busy.wav? etc
> should be played as well if the call comes from PSTN/peering.
> 
> I set the soundset correctly and also activate the loop function, but
> like I wrote, it just works with local calls but not with PSTN/peering
> calls.
> 
>  
> 
> Maybe I have somewhere a setting false or whatever, don?t know.
> 
> I also checked the config.yml but can?t find any hint for solving this
> problem.
> 
>  
> 
> Would be nice, if you could help me out with this problem.
> 
>  
> 
> THANKS!
> 
>  
> 
>  
> 
> 
> 
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
> 


From matthias.hohl at telematica.at  Thu Feb 18 17:52:44 2016
From: matthias.hohl at telematica.at (Matthias Hohl)
Date: Thu, 18 Feb 2016 23:52:44 +0100 (CET)
Subject: [Spce-user] Notification sounds (sound_set) by calls from
	PSTN/Peering not working
In-Reply-To: <56C640B3.8000402@sipwise.com>
References: <01e801d16a3c$72a89d50$57f9d7f0$@telematica.at>
 <56C640B3.8000402@sipwise.com>
Message-ID: <030c01d16a9f$0ec941f0$2c5bc5d0$@telematica.at>

Hello,

so you thinking, that the problem is at the Peering Server? That this one
doesn't allow the early media?
Is there any way to check, if the spce is playing the media right on peering
side?

Yah such a option maybe could be a good solution.
I will talk to my inbound peering provider, if they can check there config.

Thanks for the hint.


-----Urspr?ngliche Nachricht-----
Von: Spce-user [mailto:spce-user-bounces at lists.sipwise.com] Im Auftrag von
Andreas Granig
Gesendet: Donnerstag, 18. Februar 2016 23:08
An: spce-user at lists.sipwise.com
Betreff: Re: [Spce-user] Notification sounds (sound_set) by calls from
PSTN/Peering not working

Hi,

Maybe the peering server is ignoring the early media played by the system?

We've already thought about adding a config option to actually connect the
call and play the announcement within the connected call instead of inside
early media. Never followed through as it might have a regulatory impact,
since in that case costs are imposed on the calling party in that case. It's
on our radar, no specific release on when to do it though.

Andreas

On 02/18/2016 12:06 PM, Matthias Hohl wrote:
> Hello,
> 
>  
> 
> i post several days ago a problem, that there is no voice message 
> playing, if there are concurrent calls exceeded, so the caller just 
> hear the ringing tone and nothing else.
> 
> Today I did some more tests and found out the problem, but no solution 
> for it.
> 
>  
> 
> The problem just happen, if the call comes from PSTN/Peering.
> 
> If the caller is another subscriber on the server, the notification 
> sounds works perfectly.
> 
>  
> 
> So if somebody from PSTN is calling a local subscriber, and this local 
> subscriber is not online or busy or call limit exceeded or whatever, 
> the call goes to the application server but the caller just hear the 
> normal ringing tone and no notification voice until the caller hang up by
himself.
> 
> So the caller from PSTN/Peering doesn?t recognize that the callee will 
> never answer and get no information about that the callee is not 
> available, or busy, or whatever.
> 
> BUT if the callee get called from another local subscriber, the 
> notification about unavailable or busy or whatever, will be played 
> correctly.
> 
> So the problem just happen, if the call comes from a Peering (PSTN).
> 
>  
> 
> So normally the sound ?callee_offline.wav? or ?callee_busy.wav? etc 
> should be played as well if the call comes from PSTN/peering.
> 
> I set the soundset correctly and also activate the loop function, but 
> like I wrote, it just works with local calls but not with PSTN/peering 
> calls.
> 
>  
> 
> Maybe I have somewhere a setting false or whatever, don?t know.
> 
> I also checked the config.yml but can?t find any hint for solving this 
> problem.
> 
>  
> 
> Would be nice, if you could help me out with this problem.
> 
>  
> 
> THANKS!
> 
>  
> 
>  
> 
> 
> 
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
> 
_______________________________________________
Spce-user mailing list
Spce-user at lists.sipwise.com
https://lists.sipwise.com/listinfo/spce-user


From matthias.hohl at telematica.at  Fri Feb 19 08:06:48 2016
From: matthias.hohl at telematica.at (Matthias Hohl)
Date: Fri, 19 Feb 2016 14:06:48 +0100 (CET)
Subject: [Spce-user] Notification sounds (sound_set) by calls
	from	PSTN/Peering not working
In-Reply-To: <030c01d16a9f$0ec941f0$2c5bc5d0$@telematica.at>
References: <01e801d16a3c$72a89d50$57f9d7f0$@telematica.at>
 <56C640B3.8000402@sipwise.com>
 <030c01d16a9f$0ec941f0$2c5bc5d0$@telematica.at>
Message-ID: <7D181670-2B6B-48A9-83DD-799B3B35D576@telematica.at>

Fixed!
Was a problem by my carrier. They fixed that today.

Von meinem iPhone gesendet

> Am 18.02.2016 um 23:53 schrieb Matthias Hohl <matthias.hohl at telematica.at>:
> 
> Hello,
> 
> so you thinking, that the problem is at the Peering Server? That this one
> doesn't allow the early media?
> Is there any way to check, if the spce is playing the media right on peering
> side?
> 
> Yah such a option maybe could be a good solution.
> I will talk to my inbound peering provider, if they can check there config.
> 
> Thanks for the hint.
> 
> 
> -----Urspr?ngliche Nachricht-----
> Von: Spce-user [mailto:spce-user-bounces at lists.sipwise.com] Im Auftrag von
> Andreas Granig
> Gesendet: Donnerstag, 18. Februar 2016 23:08
> An: spce-user at lists.sipwise.com
> Betreff: Re: [Spce-user] Notification sounds (sound_set) by calls from
> PSTN/Peering not working
> 
> Hi,
> 
> Maybe the peering server is ignoring the early media played by the system?
> 
> We've already thought about adding a config option to actually connect the
> call and play the announcement within the connected call instead of inside
> early media. Never followed through as it might have a regulatory impact,
> since in that case costs are imposed on the calling party in that case. It's
> on our radar, no specific release on when to do it though.
> 
> Andreas
> 
>> On 02/18/2016 12:06 PM, Matthias Hohl wrote:
>> Hello,
>> 
>> 
>> 
>> i post several days ago a problem, that there is no voice message 
>> playing, if there are concurrent calls exceeded, so the caller just 
>> hear the ringing tone and nothing else.
>> 
>> Today I did some more tests and found out the problem, but no solution 
>> for it.
>> 
>> 
>> 
>> The problem just happen, if the call comes from PSTN/Peering.
>> 
>> If the caller is another subscriber on the server, the notification 
>> sounds works perfectly.
>> 
>> 
>> 
>> So if somebody from PSTN is calling a local subscriber, and this local 
>> subscriber is not online or busy or call limit exceeded or whatever, 
>> the call goes to the application server but the caller just hear the 
>> normal ringing tone and no notification voice until the caller hang up by
> himself.
>> 
>> So the caller from PSTN/Peering doesn?t recognize that the callee will 
>> never answer and get no information about that the callee is not 
>> available, or busy, or whatever.
>> 
>> BUT if the callee get called from another local subscriber, the 
>> notification about unavailable or busy or whatever, will be played 
>> correctly.
>> 
>> So the problem just happen, if the call comes from a Peering (PSTN).
>> 
>> 
>> 
>> So normally the sound ?callee_offline.wav? or ?callee_busy.wav? etc 
>> should be played as well if the call comes from PSTN/peering.
>> 
>> I set the soundset correctly and also activate the loop function, but 
>> like I wrote, it just works with local calls but not with PSTN/peering 
>> calls.
>> 
>> 
>> 
>> Maybe I have somewhere a setting false or whatever, don?t know.
>> 
>> I also checked the config.yml but can?t find any hint for solving this 
>> problem.
>> 
>> 
>> 
>> Would be nice, if you could help me out with this problem.
>> 
>> 
>> 
>> THANKS!
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> _______________________________________________
>> Spce-user mailing list
>> Spce-user at lists.sipwise.com
>> https://lists.sipwise.com/listinfo/spce-user
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user

From apogrebennyk at sipwise.com  Fri Feb 19 10:42:47 2016
From: apogrebennyk at sipwise.com (Andrew Pogrebennyk)
Date: Fri, 19 Feb 2016 16:42:47 +0100
Subject: [Spce-user] New sip:provider CE mr3.8.5 is available now
Message-ID: <56C737F7.6040508@sipwise.com>

Dear community!

This is to inform community about availability of the new SPCE mr3.8.5!
Please check release notes here:
https://www.sipwise.org/news/announcements/sipprovider-mr3-8-5-released/

mr3.8.5 is the next build in LTS release mr3.8 (62 bugfixes)
The InstallCD media, Vagrant box, Virtualbox, VMware and AMI images as
well as Docker hub container have been uploaded. As usual, please check
the handbook at https://www.sipwise.org/doc/mr3.8.5/spce/ for details.

Please report the new issueson this mailing list and thank you for the
bugreports and feedback you have already provided in the past!

Regards,
Andrew


From manwe at sipdoc.net  Fri Feb 19 16:52:16 2016
From: manwe at sipdoc.net (Jon Bonilla (Manwe))
Date: Fri, 19 Feb 2016 22:52:16 +0100
Subject: [Spce-user] ngcp-panel won't start after 3.8.5 upgrade
Message-ID: <20160219225216.58fc0426@multivac>

Hi all

Upgraded a 3.8.x system to 3.8.5 and now ngcp-panel won't start.

Please find attached the console message.



cheers,


Jon
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: panel_output.txt
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20160219/03059c7b/attachment.txt>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: Firma digital OpenPGP
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20160219/03059c7b/attachment.sig>

From alutay at sipwise.com  Fri Feb 19 17:40:14 2016
From: alutay at sipwise.com (Alex Lutay)
Date: Fri, 19 Feb 2016 23:40:14 +0100
Subject: [Spce-user] ngcp-panel won't start after 3.8.5 upgrade
In-Reply-To: <20160219225216.58fc0426@multivac>
References: <20160219225216.58fc0426@multivac>
Message-ID: <56C799CE.3000809@sipwise.com>

Hi Jon,

Please ensure you did not forget to run
ngcpc-update-cfg-schema and ngcpcfg apply
before starting ngcp-panel (in case if you upgrade it manually).

It looks like some configs were not generated properly,
please check /etc/ngcp-panel/ngcp_panel.conf
Maybe you have customtt there?
Or maybe some of packages were not updated? On hold? Modified?
Try 'ngcp-status' it can catch something.

I have downloaded fresh public vagrant mr3.8.5 and panel is running well
there, please compare the configs on vagrant and on your system.

P.S. please share the reason of the issue! Tnx!

On 02/19/2016 10:52 PM, Jon Bonilla (Manwe) wrote:
> Upgraded a 3.8.x system to 3.8.5 and now ngcp-panel won't start.
> Please find attached the console message.

-- 
Alexander Lutay
Head of Quality Assurance
Sipwise GmbH, Campus 21/Europaring F15
AT-2345 Brunn am Gebirge

Office: +43(0)13012036
Email: alutay at sipwise.com
Website: https://www.sipwise.com

Meet us @ ANGACOM: Hall 10.1 / booth N10
Exhibition and Congress for Broadband,
Cable & Satellite: 07 ? 09 June, 2016 in Cologne


From manwe at sipdoc.net  Fri Feb 19 17:50:20 2016
From: manwe at sipdoc.net (Jon Bonilla (Manwe))
Date: Fri, 19 Feb 2016 23:50:20 +0100
Subject: [Spce-user] ngcp-panel won't start after 3.8.5 upgrade
In-Reply-To: <56C799CE.3000809@sipwise.com>
References: <20160219225216.58fc0426@multivac> <56C799CE.3000809@sipwise.com>
Message-ID: <20160219235020.6ef4836d@multivac>

El Fri, 19 Feb 2016 23:40:14 +0100
Alex Lutay <alutay at sipwise.com> escribi?:

> Hi Jon,
> 
> Please ensure you did not forget to run
> ngcpc-update-cfg-schema and ngcpcfg apply
> before starting ngcp-panel (in case if you upgrade it manually).
> 
> It looks like some configs were not generated properly,
> please check /etc/ngcp-panel/ngcp_panel.conf
> Maybe you have customtt there?
> Or maybe some of packages were not updated? On hold? Modified?
> Try 'ngcp-status' it can catch something.
> 
> I have downloaded fresh public vagrant mr3.8.5 and panel is running well
> there, please compare the configs on vagrant and on your system.
> 
> P.S. please share the reason of the issue! Tnx!
> 
> On 02/19/2016 10:52 PM, Jon Bonilla (Manwe) wrote:
> > Upgraded a 3.8.x system to 3.8.5 and now ngcp-panel won't start.
> > Please find attached the console message.  
> 


Hi Alex

Thanks for the quick reply.

You're right. It's a customtt file. I have the new interception module section
missing in the config. I guess that's related to the new li integration. right?


cheers,

Jon



-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: Firma digital OpenPGP
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20160219/31a0ce95/attachment.sig>

From axessofficetheo at gmail.com  Tue Feb 23 04:30:24 2016
From: axessofficetheo at gmail.com (Theo)
Date: Tue, 23 Feb 2016 11:30:24 +0200
Subject: [Spce-user] Clir - Hiding caller ID
Message-ID: <CA+9+E=UjB5=O3UsXw-idtf3TwVJpCpc_n3Y2ZiutrMW2cHDYVQ@mail.gmail.com>

Hi

I am having some issues hiding our caller ID through some interconnects.
Sipwise does add the privacy flag to the header but does this in the "from
header". The response from our interconnect partners is that this is not
according to RFC:

"the caller here attempted to anonymize their call using only the
displayname of the FROM header." They did not include a P-Asserted Identity
/ Privacy header. The displayname of the FROM header is optional to begin
with, and while it's recommended that it be displayed at the far-end UI,
the far-end carriers are not required to use it at all."

So - are they correct in saying this and if so, how would we hide the
number the correct way?

Thanks for any input
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20160223/d1bcaeda/attachment.html>

From manwe at sipdoc.net  Tue Feb 23 05:14:36 2016
From: manwe at sipdoc.net (Jon Bonilla (Manwe))
Date: Tue, 23 Feb 2016 11:14:36 +0100
Subject: [Spce-user] Clir - Hiding caller ID
In-Reply-To: <CA+9+E=UjB5=O3UsXw-idtf3TwVJpCpc_n3Y2ZiutrMW2cHDYVQ@mail.gmail.com>
References: <CA+9+E=UjB5=O3UsXw-idtf3TwVJpCpc_n3Y2ZiutrMW2cHDYVQ@mail.gmail.com>
Message-ID: <20160223111436.52fddac1@multivac>

El Tue, 23 Feb 2016 11:30:24 +0200
Theo <axessofficetheo at gmail.com> escribi?:

> Hi
> 
> I am having some issues hiding our caller ID through some interconnects.
> Sipwise does add the privacy flag to the header but does this in the "from
> header". The response from our interconnect partners is that this is not
> according to RFC:
> 
> "the caller here attempted to anonymize their call using only the
> displayname of the FROM header." They did not include a P-Asserted Identity
> / Privacy header. The displayname of the FROM header is optional to begin
> with, and while it's recommended that it be displayed at the far-end UI,
> the far-end carriers are not required to use it at all."
> 
> So - are they correct in saying this and if so, how would we hide the
> number the correct way?
> 


When you hide the callerid and send a call to a peer, the ngcp system adds the
Privacy and the PAI headers by default.

When sending the call to a subscriber it does not. It only sends anonymous in
the from header.

could you paste one of those INVITE requests?


cheers,

Jon

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: Firma digital OpenPGP
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20160223/a900db9b/attachment.sig>

From axessofficetheo at gmail.com  Tue Feb 23 06:08:37 2016
From: axessofficetheo at gmail.com (Theo)
Date: Tue, 23 Feb 2016 13:08:37 +0200
Subject: [Spce-user] Clir - Hiding caller ID
In-Reply-To: <20160223111436.52fddac1@multivac>
References: <CA+9+E=UjB5=O3UsXw-idtf3TwVJpCpc_n3Y2ZiutrMW2cHDYVQ@mail.gmail.com>
 <20160223111436.52fddac1@multivac>
Message-ID: <CA+9+E=U0Z1o=NNEE37UgtVgPTAJXikjp_Uv=eJwgayqbyPOtQA@mail.gmail.com>

Hi

I had another look - you are correct it seems. Apologies. It's the next
step in the chain that strips the flag hence it doesn't arrive upstream.

Thanks!



On Tue, Feb 23, 2016 at 12:14 PM, Jon Bonilla (Manwe) <manwe at sipdoc.net>
wrote:

> El Tue, 23 Feb 2016 11:30:24 +0200
> Theo <axessofficetheo at gmail.com> escribi?:
>
> > Hi
> >
> > I am having some issues hiding our caller ID through some interconnects.
> > Sipwise does add the privacy flag to the header but does this in the
> "from
> > header". The response from our interconnect partners is that this is not
> > according to RFC:
> >
> > "the caller here attempted to anonymize their call using only the
> > displayname of the FROM header." They did not include a P-Asserted
> Identity
> > / Privacy header. The displayname of the FROM header is optional to begin
> > with, and while it's recommended that it be displayed at the far-end UI,
> > the far-end carriers are not required to use it at all."
> >
> > So - are they correct in saying this and if so, how would we hide the
> > number the correct way?
> >
>
>
> When you hide the callerid and send a call to a peer, the ngcp system adds
> the
> Privacy and the PAI headers by default.
>
> When sending the call to a subscriber it does not. It only sends anonymous
> in
> the from header.
>
> could you paste one of those INVITE requests?
>
>
> cheers,
>
> Jon
>
>
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20160223/5dbba3a9/attachment.html>

From admin at marcoteixeira.com  Wed Feb 24 18:06:55 2016
From: admin at marcoteixeira.com (Marco Teixeira)
Date: Wed, 24 Feb 2016 23:06:55 +0000
Subject: [Spce-user] Lua script errors
Message-ID: <CAD7smbiDmXjZhpUqn1nsZyhC6M5MnYXVin29MyUQur+7AanTuw@mail.gmail.com>

Hi,

Can anyone point me in the right direction on troubleshooting these errors
i'm seeing on proxy.log ?

Feb 24 23:00:16 sbc proxy[5325]: ERROR: app_lua [app_lua_api.c:672]:
app_lua_run(): error executing: del_dlg_profile_peer (err: 2)
Feb 24 23:00:16 sbc proxy[5325]: ERROR: app_lua [app_lua_api.c:674]:
app_lua_run(): error from Lua: /etc/kamailio/proxy/dlgcnt.lua:157: attempt
to concatenate global 'key' (a nil value)
Feb 24 23:00:16 sbc proxy[5325]: ERROR: <script>: Can't del peer[out]:3
profiles

# more /etc/ngcp_version
mr3.8.5

Tkx

---
?Marco
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20160224/8ba0641e/attachment.html>

From vseva at sipwise.com  Thu Feb 25 06:47:11 2016
From: vseva at sipwise.com (Victor Seva)
Date: Thu, 25 Feb 2016 12:47:11 +0100
Subject: [Spce-user] Lua script errors
In-Reply-To: <CAD7smbiDmXjZhpUqn1nsZyhC6M5MnYXVin29MyUQur+7AanTuw@mail.gmail.com>
References: <CAD7smbiDmXjZhpUqn1nsZyhC6M5MnYXVin29MyUQur+7AanTuw@mail.gmail.com>
Message-ID: <56CEE9BF.8070801@sipwise.com>

On 02/25/2016 12:06 AM, Marco Teixeira wrote:
> Hi,
> 
> Can anyone point me in the right direction on troubleshooting these
> errors i'm seeing on proxy.log ?
> 
> Feb 24 23:00:16 sbc proxy[5325]: ERROR: app_lua [app_lua_api.c:672]:
> app_lua_run(): error executing: del_dlg_profile_peer (err: 2)
> Feb 24 23:00:16 sbc proxy[5325]: ERROR: app_lua [app_lua_api.c:674]:
> app_lua_run(): error from Lua: /etc/kamailio/proxy/dlgcnt.lua:157:
> attempt to concatenate global 'key' (a nil value)
> Feb 24 23:00:16 sbc proxy[5325]: ERROR: <script>: Can't del peer[out]:3
> profiles
> 
> # more /etc/ngcp_version 
> mr3.8.5

Confirmed, I'm working on a fix. I'll keep you posted.

Thanks for reporting.

-- 
Victor Seva
Software Engineer

Phone: +43(0)1 301 2029
Email: vseva at sipwise.com
Website: www.sipwise.com

Particulars according Austrian Companies Code paragraph 14
"Sipwise GmbH? - Europaring F15 ? 2345 Brunn am Gebirge
FN:305595f, Commercial Court Vienna, ATU64002206

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20160225/032c0d1d/attachment.asc>

From vseva at sipwise.com  Thu Feb 25 09:13:27 2016
From: vseva at sipwise.com (Victor Seva)
Date: Thu, 25 Feb 2016 15:13:27 +0100
Subject: [Spce-user] Lua script errors
In-Reply-To: <56CEE9BF.8070801@sipwise.com>
References: <CAD7smbiDmXjZhpUqn1nsZyhC6M5MnYXVin29MyUQur+7AanTuw@mail.gmail.com>
 <56CEE9BF.8070801@sipwise.com>
Message-ID: <56CF0C07.408@sipwise.com>

On 02/25/2016 12:47 PM, Victor Seva wrote:
> Confirmed, I'm working on a fix. I'll keep you posted.

> ngcp-templates (3.8.5.6+0~mr3.8.5.6) unstable; urgency=medium
> 
>   [ Victor Seva ]
>   * [fe70fed] MT#17709 decrease redis counters if call forward fails, fix b09c6fd59430d
> 
>   [ Andrew Pogrebennyk ]
>   * [1f029b2] MT#17877 workaround wrong Referred-By domain from Yealink phones
> 
>   [ Sipwise Jenkins Builder ]
> 
>  -- Sipwise Jenkins Builder <jenkins at sipwise.com>  Thu, 25 Feb 2016 15:06:55 +0100

Released fix. Thanks for reporting


-- 
Victor Seva
Software Engineer

Phone: +43(0)1 301 2029
Email: vseva at sipwise.com
Website: www.sipwise.com

Particulars according Austrian Companies Code paragraph 14
"Sipwise GmbH? - Europaring F15 ? 2345 Brunn am Gebirge
FN:305595f, Commercial Court Vienna, ATU64002206

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20160225/79ef29bf/attachment.asc>

From admin at marcoteixeira.com  Thu Feb 25 09:58:46 2016
From: admin at marcoteixeira.com (Marco Teixeira)
Date: Thu, 25 Feb 2016 14:58:46 +0000
Subject: [Spce-user] Lua script errors
In-Reply-To: <56CF0C07.408@sipwise.com>
References: <CAD7smbiDmXjZhpUqn1nsZyhC6M5MnYXVin29MyUQur+7AanTuw@mail.gmail.com>
 <56CEE9BF.8070801@sipwise.com> <56CF0C07.408@sipwise.com>
Message-ID: <CAD7smbjqP8-gjoUqttC5wGJ59H3oN8sOXv+n0Eh4eBFqmFe_MA@mail.gmail.com>

Victor... Sorry for lagging on replying back to you.

Do you still need me to test ?
This is in production and i rather not...

How to update ? (manual style apt-get ngcp-cfg apply ??)


---
?Marco


On Thu, Feb 25, 2016 at 2:13 PM, Victor Seva <vseva at sipwise.com> wrote:

> On 02/25/2016 12:47 PM, Victor Seva wrote:
> > Confirmed, I'm working on a fix. I'll keep you posted.
>
> > ngcp-templates (3.8.5.6+0~mr3.8.5.6) unstable; urgency=medium
> >
> >   [ Victor Seva ]
> >   * [fe70fed] MT#17709 decrease redis counters if call forward fails,
> fix b09c6fd59430d
> >
> >   [ Andrew Pogrebennyk ]
> >   * [1f029b2] MT#17877 workaround wrong Referred-By domain from Yealink
> phones
> >
> >   [ Sipwise Jenkins Builder ]
> >
> >  -- Sipwise Jenkins Builder <jenkins at sipwise.com>  Thu, 25 Feb 2016
> 15:06:55 +0100
>
> Released fix. Thanks for reporting
>
>
> --
> Victor Seva
> Software Engineer
>
> Phone: +43(0)1 301 2029
> Email: vseva at sipwise.com
> Website: www.sipwise.com
>
> Particulars according Austrian Companies Code paragraph 14
> "Sipwise GmbH? - Europaring F15 ? 2345 Brunn am Gebirge
> FN:305595f, Commercial Court Vienna, ATU64002206
>
>
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20160225/4702fb04/attachment.html>

From admin at marcoteixeira.com  Thu Feb 25 10:05:56 2016
From: admin at marcoteixeira.com (Marco Teixeira)
Date: Thu, 25 Feb 2016 15:05:56 +0000
Subject: [Spce-user] Lua script errors
In-Reply-To: <CAD7smbjqP8-gjoUqttC5wGJ59H3oN8sOXv+n0Eh4eBFqmFe_MA@mail.gmail.com>
References: <CAD7smbiDmXjZhpUqn1nsZyhC6M5MnYXVin29MyUQur+7AanTuw@mail.gmail.com>
 <56CEE9BF.8070801@sipwise.com> <56CF0C07.408@sipwise.com>
 <CAD7smbjqP8-gjoUqttC5wGJ59H3oN8sOXv+n0Eh4eBFqmFe_MA@mail.gmail.com>
Message-ID: <CAD7smbi0dNp4fEMe-gCZN938CD5hTzKNBeEL4FDeyzRs=Ofh_w@mail.gmail.com>

Well, i wen't ahead and did:

apt-get update && apt-get upgrade && \
ngcp-update-db-schema && ngcp-update-cfg-schema && \
ngcpcfg apply

?Errors are gone. I do see sometimes warnings like these:
Feb 25 15:04:33 sbc proxy[20485]: WARNING: app_lua [app_lua_sr.c:100]:
lua_sr_log(): central:del[1:3] counter was -1
Feb 25 15:04:33 sbc proxy[20485]: WARNING: app_lua [app_lua_sr.c:100]:
lua_sr_log(): central:del[2:3] counter was -1

Is this normal ? Do i need to clear out redis counters or something ??


---
Cumprimentos / Best regards

Marco
---


On Thu, Feb 25, 2016 at 2:58 PM, Marco Teixeira <admin at marcoteixeira.com>
wrote:

> Victor... Sorry for lagging on replying back to you.
>
> Do you still need me to test ?
> This is in production and i rather not...
>
> How to update ? (manual style apt-get ngcp-cfg apply ??)
>
>
> ---
> ?Marco
>
>
> On Thu, Feb 25, 2016 at 2:13 PM, Victor Seva <vseva at sipwise.com> wrote:
>
>> On 02/25/2016 12:47 PM, Victor Seva wrote:
>> > Confirmed, I'm working on a fix. I'll keep you posted.
>>
>> > ngcp-templates (3.8.5.6+0~mr3.8.5.6) unstable; urgency=medium
>> >
>> >   [ Victor Seva ]
>> >   * [fe70fed] MT#17709 decrease redis counters if call forward fails,
>> fix b09c6fd59430d
>> >
>> >   [ Andrew Pogrebennyk ]
>> >   * [1f029b2] MT#17877 workaround wrong Referred-By domain from Yealink
>> phones
>> >
>> >   [ Sipwise Jenkins Builder ]
>> >
>> >  -- Sipwise Jenkins Builder <jenkins at sipwise.com>  Thu, 25 Feb 2016
>> 15:06:55 +0100
>>
>> Released fix. Thanks for reporting
>>
>>
>> --
>> Victor Seva
>> Software Engineer
>>
>> Phone: +43(0)1 301 2029
>> Email: vseva at sipwise.com
>> Website: www.sipwise.com
>>
>> Particulars according Austrian Companies Code paragraph 14
>> "Sipwise GmbH? - Europaring F15 ? 2345 Brunn am Gebirge
>> FN:305595f, Commercial Court Vienna, ATU64002206
>>
>>
>> _______________________________________________
>> Spce-user mailing list
>> Spce-user at lists.sipwise.com
>> https://lists.sipwise.com/listinfo/spce-user
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20160225/2e5b6f31/attachment.html>

From noreply at sipwise.com  Thu Feb 25 11:38:18 2016
From: noreply at sipwise.com (Sipwise Repository Tracker)
Date: Thu, 25 Feb 2016 17:38:18 +0100
Subject: [Spce-user] FYI: Package update(s) in release mr3.8.3
Message-ID: <1456418298.497668.17444.nullmailer@deb1.sipwise.com>

One or more updates have been released in NGCP release mr3.8.3:

* captagent was updated from version 5.2.10.0-1+0~mr3.8.3.13 to version 5.2.11.0-1+0~mr3.8.3.14
* captagent-dbg was updated from version 5.2.10.0-1+0~mr3.8.3.13 to version 5.2.11.0-1+0~mr3.8.3.14

To apply the latest update(s) execute:

  apt-get update && apt-get upgrade && \
  ngcp-update-db-schema && ngcp-update-cfg-schema && \
  ngcpcfg apply manual system update

If you encounter any problems please report a bug at
the spce-user at lists.sipwise.com mailing list.

Further documentation is available at:

  http://www.sipwise.com/products/spce/documentation/

This is an automated mail by the Continuous Delivery platform at Sipwise.com


From noreply at sipwise.com  Thu Feb 25 11:39:47 2016
From: noreply at sipwise.com (Sipwise Repository Tracker)
Date: Thu, 25 Feb 2016 17:39:47 +0100
Subject: [Spce-user] FYI: Package update(s) in release mr3.8.4
Message-ID: <1456418387.701981.18092.nullmailer@deb1.sipwise.com>

One or more updates have been released in NGCP release mr3.8.4:

* captagent was updated from version 5.2.10.0-1+0~mr3.8.4.11 to version 5.2.11.0-1+0~mr3.8.4.12
* captagent-dbg was updated from version 5.2.10.0-1+0~mr3.8.4.11 to version 5.2.11.0-1+0~mr3.8.4.12

To apply the latest update(s) execute:

  apt-get update && apt-get upgrade && \
  ngcp-update-db-schema && ngcp-update-cfg-schema && \
  ngcpcfg apply manual system update

If you encounter any problems please report a bug at
the spce-user at lists.sipwise.com mailing list.

Further documentation is available at:

  http://www.sipwise.com/products/spce/documentation/

This is an automated mail by the Continuous Delivery platform at Sipwise.com


From noreply at sipwise.com  Thu Feb 25 11:41:08 2016
From: noreply at sipwise.com (Sipwise Repository Tracker)
Date: Thu, 25 Feb 2016 17:41:08 +0100
Subject: [Spce-user] FYI: Package update(s) in release mr3.8.5
Message-ID: <1456418468.050997.18341.nullmailer@deb1.sipwise.com>

One or more updates have been released in NGCP release mr3.8.5:

* captagent was updated from version 5.2.10.0-1+0~mr3.8.5.7 to version 5.2.11.0-1+0~mr3.8.5.8
* captagent-dbg was updated from version 5.2.10.0-1+0~mr3.8.5.7 to version 5.2.11.0-1+0~mr3.8.5.8

To apply the latest update(s) execute:

  apt-get update && apt-get upgrade && \
  ngcp-update-db-schema && ngcp-update-cfg-schema && \
  ngcpcfg apply manual system update

If you encounter any problems please report a bug at
the spce-user at lists.sipwise.com mailing list.

Further documentation is available at:

  http://www.sipwise.com/products/spce/documentation/

This is an automated mail by the Continuous Delivery platform at Sipwise.com


From noreply at sipwise.com  Thu Feb 25 11:46:43 2016
From: noreply at sipwise.com (Sipwise Repository Tracker)
Date: Thu, 25 Feb 2016 17:46:43 +0100
Subject: [Spce-user] FYI: Package update(s) in release mr4.2.1
Message-ID: <1456418803.864036.19389.nullmailer@deb1.sipwise.com>

One or more updates have been released in NGCP release mr4.2.1:

* captagent was updated from version 5.2.10.1-1+0~mr4.2.1.10 to version 5.2.11.1-1+0~mr4.2.1.11
* captagent-dbg was updated from version 5.2.10.1-1+0~mr4.2.1.10 to version 5.2.11.1-1+0~mr4.2.1.11

To apply the latest update(s) execute:

  apt-get update && apt-get upgrade && \
  ngcp-update-db-schema && ngcp-update-cfg-schema && \
  ngcpcfg apply manual system update

If you encounter any problems please report a bug at
the spce-user at lists.sipwise.com mailing list.

Further documentation is available at:

  http://www.sipwise.com/products/spce/documentation/

This is an automated mail by the Continuous Delivery platform at Sipwise.com


From admin at marcoteixeira.com  Thu Feb 25 12:55:41 2016
From: admin at marcoteixeira.com (Marco Teixeira)
Date: Thu, 25 Feb 2016 17:55:41 +0000
Subject: [Spce-user] FYI: Package update(s) in release mr3.8.5
In-Reply-To: <1456418468.050997.18341.nullmailer@deb1.sipwise.com>
References: <1456418468.050997.18341.nullmailer@deb1.sipwise.com>
Message-ID: <CAD7smbiyJMCbsaFq4a4iKKCs8Bob0uGmHQNV8O95FPU4C1CpRw@mail.gmail.com>

?Hi,
Minor cosmetic... "page not found"?

On Thu, Feb 25, 2016 at 4:41 PM, Sipwise Repository Tracker <
noreply at sipwise.com> wrote:

> Further documentation is available at:
>
>   http://www.sipwise.com/products/spce/documentation/
>




---
Cumprimentos / Best regards

Marco Teixeira
email/gtalk: admin at marcoteixeira.com
skype: admin-marcoteixeira.com
---
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20160225/fb59c9d8/attachment.html>

From dgrotti at sipwise.com  Thu Feb 25 13:00:56 2016
From: dgrotti at sipwise.com (Daniel Grotti)
Date: Thu, 25 Feb 2016 19:00:56 +0100
Subject: [Spce-user] FYI: Package update(s) in release mr3.8.5
In-Reply-To: <CAD7smbiyJMCbsaFq4a4iKKCs8Bob0uGmHQNV8O95FPU4C1CpRw@mail.gmail.com>
Message-ID: <f7ef4e1f-1cc6-45ee-b127-28c02ed18767@email.android.com>

Oops... Typo.
Sipwise.org not .com

On Feb 25, 2016 6:55 PM, Marco Teixeira <admin at marcoteixeira.com> wrote:
>
> ?Hi,
> Minor cosmetic... "page not found"?
>
> On Thu, Feb 25, 2016 at 4:41 PM, Sipwise Repository Tracker <noreply at sipwise.com> wrote:
>>
>> Further documentation is available at:
>>
>> ? http://www.sipwise.com/products/spce/documentation/
>
>
>
>
>
> ---
> Cumprimentos / Best regards
>
> Marco Teixeira
> email/gtalk: admin at marcoteixeira.com
> skype: admin-marcoteixeira.com
> ---
>

From gavin.sweet at skyracktelecom.com  Fri Feb 26 05:27:10 2016
From: gavin.sweet at skyracktelecom.com (Gavin Sweet)
Date: Fri, 26 Feb 2016 10:27:10 -0000
Subject: [Spce-user] access to sipwise v 3.1 sw_vcs patch (not available in
	older branch on github)
Message-ID: <192901d17080$40a27b10$c1e77130$@skyracktelecom.com>

Hi - 

 

Can anyone please direct me/post here to the source for the sipwise v3.1
patch for sems - file name sw_vcs.patch? 

 

The oldest version in github here is 3.8

https://github.com/sipwise/sems/blob/mr3.8/debian/patches/sipwise/sw_vcs.pat
ch 

 

Fully appreciate that running on this old version is not ideal, but we are
not yet in a position to upgrade.

 

Thanks for your help,

 

Gavin

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20160226/c8a14393/attachment.html>

From alutay at sipwise.com  Fri Feb 26 06:00:55 2016
From: alutay at sipwise.com (Alex Lutay)
Date: Fri, 26 Feb 2016 12:00:55 +0100
Subject: [Spce-user] access to sipwise v 3.1 sw_vcs patch (not available
 in older branch on github)
In-Reply-To: <192901d17080$40a27b10$c1e77130$@skyracktelecom.com>
References: <192901d17080$40a27b10$c1e77130$@skyracktelecom.com>
Message-ID: <56D03067.8070106@sipwise.com>

Dear Gavin,

1) sems in mr3.8 has version 1.6.0 while sems in v3.1 was 1.4.3

2) Sipwise didn't use quilt to manage patches that time,
so no patches available for NGCP v3.1

3) you can check branch 1.4.3+spce3.0 to see the sources for NGCP v3.1
https://github.com/sipwise/sems/tree/1.4.3+spce3.0

Have a good day!

On 02/26/2016 11:27 AM, Gavin Sweet wrote:
> Can anyone please direct me/post here to the source for the sipwise v3.1
> patch for sems ? file name sw_vcs.patch?
> 
> The oldest version in github here is 3.8
> 
> https://github.com/sipwise/sems/blob/mr3.8/debian/patches/sipwise/sw_vcs.patch
> 
> Fully appreciate that running on this old version is not ideal, but we
> are not yet in a position to upgrade.

-- 
Alex Lutay


From admin at marcoteixeira.com  Fri Feb 26 16:14:03 2016
From: admin at marcoteixeira.com (Marco Teixeira)
Date: Fri, 26 Feb 2016 21:14:03 +0000
Subject: [Spce-user] ngcp-sems error stack-trace
Message-ID: <CAD7smbiYH92qCFG3X7A9U05poV3KzSXinCU0171hC4chJs_KXA@mail.gmail.com>

Hello,

I'm seeing these errors today... could it have to do with yesterday updates
?
For the ngcp team, i do have the call sip signalling in PCAP if want...
This was the only error a saw...

# cat /etc/ngcp_version
mr3.8.5

# cat /var/log/ngcp/sems.log
Feb 26 13:19:35 sbc ngcp-sems[20733]: [#7f21994d4700] [reply,
AmBasicSipDialog.cpp:575] ERROR:  could not find any transaction matching
request cseq
Feb 26 13:19:35 sbc ngcp-sems[20733]: [#7f21994d4700] [reply,
AmBasicSipDialog.cpp:579] ERROR:  request cseq=398486202; reply code=500;
callid=0gQAAC8WAAACBAAALxYAACDxoSeF4diiPZAuWPTh7LGPP44+3WQKcfpQxTjqxiiV at REDACTED_IP;
local_tag=3A37C073-56D050AB0003A812-A037E700;
remote_tag=REDACTED_IP+1+c739f1b5+28fcc5c8
Feb 26 13:19:35 sbc ngcp-sems[20733]: [#7f21994d4700] [log_stacktrace,
log.cpp:218] ERROR: stack-trace(0/[0x54cf15]):
/usr/sbin/ngcp-sems(log_stacktrace+0x35) [0x54cf15]
Feb 26 13:19:35 sbc ngcp-sems[20733]: [#7f21994d4700] [log_stacktrace,
log.cpp:218] ERROR: stack-trace(1/[0x498712]):
/usr/sbin/ngcp-sems(_ZN16AmBasicSipDialog5replyERK12AmSipRequestjRKSsPK10AmMimeBodyS4_i+0xa82)
[0x498712]
Feb 26 13:19:35 sbc ngcp-sems[20733]: [#7f21994d4700] [log_stacktrace,
log.cpp:218] ERROR: stack-trace(2/[0x48c2cb]):
/usr/sbin/ngcp-sems(_ZN12AmB2BSession12onSipRequestERK12AmSipRequest+0x3eb)
[0x48c2cb]
Feb 26 13:19:35 sbc ngcp-sems[20733]: [#7f21994d4700] [log_stacktrace,
log.cpp:218] ERROR: stack-trace(3/[0x7f21a48416c8]):
/usr/lib/ngcp-sems/plug-in//sbc.so(_ZN7CallLeg12onSipRequestERK12AmSipRequest+0x68)
[0x7f21a48416c8]
Feb 26 13:19:35 sbc ngcp-sems[20733]: [#7f21994d4700] [log_stacktrace,
log.cpp:218] ERROR: stack-trace(4/[0x7f21a488b3f5]):
/usr/lib/ngcp-sems/plug-in//sbc.so(_ZN10SBCCallLeg12onSipRequestERK12AmSipRequest+0x4c5)
[0x7f21a488b3f5]
Feb 26 13:19:35 sbc ngcp-sems[20733]: [#7f21994d4700] [log_stacktrace,
log.cpp:218] ERROR: stack-trace(5/[0x511f27]):
/usr/sbin/ngcp-sems(_ZN11AmSipDialog13onRxReqSanityERK12AmSipRequest+0x97)
[0x511f27]
Feb 26 13:19:35 sbc ngcp-sems[20733]: [#7f21994d4700] [log_stacktrace,
log.cpp:218] ERROR: stack-trace(6/[0x49a35b]):
/usr/sbin/ngcp-sems(_ZN16AmBasicSipDialog11onRxRequestERK12AmSipRequest+0x7b)
[0x49a35b]
Feb 26 13:19:35 sbc ngcp-sems[20733]: [#7f21994d4700] [log_stacktrace,
log.cpp:218] ERROR: stack-trace(7/[0x4f888b]): /usr/sbin/ngcp-sems()
[0x4f888b]
Feb 26 13:19:35 sbc ngcp-sems[20733]: [#7f21994d4700] [log_stacktrace,
log.cpp:218] ERROR: stack-trace(8/[0x7f21a4894717]):
/usr/lib/ngcp-sems/plug-in//sbc.so(_ZN10SBCCallLeg7processEP7AmEvent+0x177)
[0x7f21a4894717]
Feb 26 13:19:35 sbc ngcp-sems[20733]: [#7f21994d4700] [log_stacktrace,
log.cpp:218] ERROR: stack-trace(9/[0x4ba9fc]):
/usr/sbin/ngcp-sems(_ZN12AmEventQueue13processEventsEv+0x6c) [0x4ba9fc]
Feb 26 13:19:35 sbc ngcp-sems[20733]: [#7f21994d4700] [log_stacktrace,
log.cpp:218] ERROR: stack-trace(10/[0x4fa267]):
/usr/sbin/ngcp-sems(_ZN9AmSession28processEventsCatchExceptionsEv+0x37)
[0x4fa267]
Feb 26 13:19:35 sbc ngcp-sems[20733]: [#7f21994d4700] [log_stacktrace,
log.cpp:218] ERROR: stack-trace(11/[0x4fcccf]):
/usr/sbin/ngcp-sems(_ZN9AmSession15processingCycleEv+0x5f) [0x4fcccf]
Feb 26 13:19:35 sbc ngcp-sems[20733]: [#7f21994d4700] [log_stacktrace,
log.cpp:218] ERROR: stack-trace(12/[0x4f7dd1]):
/usr/sbin/ngcp-sems(_ZN9AmSession3runEv+0x81) [0x4f7dd1]
Feb 26 13:19:35 sbc ngcp-sems[20733]: [#7f21994d4700] [log_stacktrace,
log.cpp:218] ERROR: stack-trace(13/[0x52c6cc]):
/usr/sbin/ngcp-sems(_ZN8AmThread6_startEPv+0x5c) [0x52c6cc]
Feb 26 13:19:35 sbc ngcp-sems[20733]: [#7f21994d4700] [log_stacktrace,
log.cpp:218] ERROR: stack-trace(14/[0x7f21a8c57b50]):
/lib/x86_64-linux-gnu/libpthread.so.0(+0x6b50) [0x7f21a8c57b50]
Feb 26 13:19:35 sbc ngcp-sems[20733]: [#7f21994d4700] [log_stacktrace,
log.cpp:218] ERROR: stack-trace(15/[0x7f21a7b6530d]):
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d) [0x7f21a7b6530d]


---
Marco
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20160226/ac6823e0/attachment.html>

From admin at marcoteixeira.com  Fri Feb 26 18:12:25 2016
From: admin at marcoteixeira.com (Marco Teixeira)
Date: Fri, 26 Feb 2016 23:12:25 +0000
Subject: [Spce-user] System Statistics stopped working
In-Reply-To: <CAD7smbjKD9zohdQR7DbZB4W_Z4_nWM_MNiKY94h3rcQfv1d9UQ@mail.gmail.com>
References: <CAD7smbj1zw5O_-R16yyJB1+fNb=bqBSNWRXUvcx5zoTEmPnjiw@mail.gmail.com>
 <5624C307.8010404@sipwise.com>
 <CAD7smbgusq1rTY2bLZidfcvAuqbvAw1fqvFg_ZsSnTPyOY-X7A@mail.gmail.com>
 <CAD7smbjKD9zohdQR7DbZB4W_Z4_nWM_MNiKY94h3rcQfv1d9UQ@mail.gmail.com>
Message-ID: <CAD7smbh7CovFUp2-3Z+Ua6iM6Y_55v2zyO-8oup=OB9k-08iVg@mail.gmail.com>

Hello,

Getting back to this old issue... Back to basics.
- I installed a clean 3.8.3. Stats working ok.
- Changed default timezone from Europe/Vienna to GMT. Stats stopped
working...

Followed sugestion of deleting RRD files to allow regeneration...

===
root at spce:/var/lib/collectd/rrd# /etc/init.d/collectd stop
[ ok ] Stopping statistics collection and monitoring daemon: collectd.
root at spce:/var/lib/collectd/rrd# mv spce spce.bak
root at spce:/var/lib/collectd/rrd# ls -lap
total 12
drwxr-xr-x  3 root root 4096 Feb 26 23:10 ./
drwxr-xr-x  3 root root 4096 Feb 26 22:20 ../
drwxr-xr-x 48 root root 4096 Feb 26 22:30 spce.bak/
root at spce:/var/lib/collectd/rrd# /etc/init.d/collectd start
[ ok ] Starting statistics collection and monitoring daemon: collectd.
root at spce:/var/lib/collectd/rrd# ls -lapt
total 16
drwxr-xr-x 41 root root 4096 Feb 26 23:10 spce/
drwxr-xr-x  4 root root 4096 Feb 26 23:10 ./
drwxr-xr-x 48 root root 4096 Feb 26 22:30 spce.bak/
drwxr-xr-x  3 root root 4096 Feb 26 22:20 ../
root at spce:/var/lib/collectd/rrd#
===

?Did not work... Any more hints ?
Please ??


---
Marco
---


On Fri, Oct 23, 2015 at 1:59 AM, Marco Teixeira <admin at marcoteixeira.com>
wrote:

> Hi there,
>
> As it seems, i didn't catch these on the logs, on first time. Could this
> be it ?
> ntpd is running ... But i guess this only afects graphing ntp process ...
>
> === CUT
> Oct 23 00:27:09 localhost collectd[21512]: rrdtool plugin: Adjusting
> "RandomTimeout" to 0.000 seconds.
> Oct 23 00:27:09 localhost collectd[21512]: mysql plugin: Successfully
> connected to database <none> at server Localhost via UNIX socket (server
> version: 5.5.44-0+deb7u1-log, protocol version: 10)
> Oct 23 00:27:09 localhost collectd[21512]: recv(2) failed: Connection
> refused
> Oct 23 00:27:09 localhost collectd[21512]: ntpd plugin: ntpd_do_query
> (REQ_GET_KERNEL) failed with status -1
> Oct 23 00:27:09 localhost collectd[21512]: read-function of plugin `ntpd'
> failed. Will suspend it for 20 seconds.
>
>
>
>
> ---
> Cumprimentos / Best regards
>
> Marco
> ---
>
>
> On Thu, Oct 22, 2015 at 10:02 PM, Marco Teixeira <admin at marcoteixeira.com>
> wrote:
>
>> Well...
>>
>> One small corretion for future users getting to this, rrd files in
>> mr3.8.3 are on /var/lib/collectd/rrd/ $HOSTNAME
>>
>> Now, back to the problem in hand:
>> - collectd is fine
>> - rrd files have current timestamps
>> - "rrdtool fetch" works ok
>>
>> It seems something with graphics generation or saving... took a look at
>> the code in /usr/share/ngcp-panel/templates/statistics/lists.tt but i'm
>> having dificulties graspping it...
>> - there is a line "var tz_offset = [% tz_offset %];". Where does this
>> variable come from ? The system ?
>> - Are the graphics generated on the fly for display, or are they stored
>> somewhere else ?
>> - Does nginx have some timezone variable in the confs and not  copying
>> from the system ?
>>
>> ?thank you for your time...?
>>
>>
>> ---
>> Cumprimentos / Best regards
>>
>> Marco
>>
>>
>> On Mon, Oct 19, 2015 at 11:16 AM, Alex Lutay <alutay at sipwise.com> wrote:
>>
>>> Hi Marco,
>>>
>>> All system statistics are collected by collectd and are stored in RRD
>>> files located in /var/lib/collectd/rrd/spce/
>>>
>>> "Internally, RRDtool uses "seconds since the epoch" to keep track of
>>> time. This is the number of seconds since January first, 1970,
>>> midnight, UTC. When you are specifying a time in this format, it is UTC
>>> time automatically." (c) http://vandenbogaerdt.nl/rrdtool/timezone.php
>>>
>>> So, you need to check collecd log first to see new values are
>>> inserter properly, also you can manually extract RRD data using RRD
>>> tool fetch (to check content of RRD file).
>>>
>>> Finally you can move RRD files and restart collectd to init new
>>> statistics files. Then you can manually move old data in new RRD files
>>> if necessary.
>>>
>>> P.S. changing the timezone of server on the fly is not a good idea,
>>> AFAIK. As data in MySQL DB (like accounting, CDRs) stored in fields
>>> without timezone specified. Also MySQL works in server timezone by
>>> default.
>>>
>>> On 10/18/2015 10:22 PM, Marco Teixeira wrote:
>>> > Hello list,
>>> >
>>> > A couple weeks ago i lost system statistics... The page opens but
>>> > doesn't get pasted those loading progress circling dots... All of them,
>>> > on any variable i select on the dropdown box.
>>> >
>>> > I searched around on the logs, and found nothing.
>>> > Does anyone have a clue how to fix this ?
>>> >
>>> > # more /etc/ngcp_version
>>> > mr3.8.3
>>>
>>> --
>>> Alex Lutay
>>> _______________________________________________
>>> Spce-user mailing list
>>> Spce-user at lists.sipwise.com
>>> https://lists.sipwise.com/listinfo/spce-user
>>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20160226/5c041140/attachment.html>

From admin at marcoteixeira.com  Fri Feb 26 18:16:06 2016
From: admin at marcoteixeira.com (Marco Teixeira)
Date: Fri, 26 Feb 2016 23:16:06 +0000
Subject: [Spce-user] System Statistics stopped working
In-Reply-To: <CAD7smbh7CovFUp2-3Z+Ua6iM6Y_55v2zyO-8oup=OB9k-08iVg@mail.gmail.com>
References: <CAD7smbj1zw5O_-R16yyJB1+fNb=bqBSNWRXUvcx5zoTEmPnjiw@mail.gmail.com>
 <5624C307.8010404@sipwise.com>
 <CAD7smbgusq1rTY2bLZidfcvAuqbvAw1fqvFg_ZsSnTPyOY-X7A@mail.gmail.com>
 <CAD7smbjKD9zohdQR7DbZB4W_Z4_nWM_MNiKY94h3rcQfv1d9UQ@mail.gmail.com>
 <CAD7smbh7CovFUp2-3Z+Ua6iM6Y_55v2zyO-8oup=OB9k-08iVg@mail.gmail.com>
Message-ID: <CAD7smbhxJ1Xu8s22qL9YVuVgY80paC1hqB+G8kf2FdGBGyK5dw@mail.gmail.com>

If i change back to Europe/Vienna, Statistics start displaying again... Not
even a reboot needed...
I'm guessing a hardcoded tz_offset variable somewhere on the panel coding
maybe ...


===
Current default time zone: 'Europe/Vienna'
Local time is now:      Sat Feb 27 00:12:48 CET 2016.
Universal Time is now:  Fri Feb 26 23:12:48 UTC 2016.
===


On Fri, Feb 26, 2016 at 11:12 PM, Marco Teixeira <admin at marcoteixeira.com>
wrote:

> Hello,
>
> Getting back to this old issue... Back to basics.
> - I installed a clean 3.8.3. Stats working ok.
> - Changed default timezone from Europe/Vienna to GMT. Stats stopped
> working...
>
> Followed sugestion of deleting RRD files to allow regeneration...
>
> ===
> root at spce:/var/lib/collectd/rrd# /etc/init.d/collectd stop
> [ ok ] Stopping statistics collection and monitoring daemon: collectd.
> root at spce:/var/lib/collectd/rrd# mv spce spce.bak
> root at spce:/var/lib/collectd/rrd# ls -lap
> total 12
> drwxr-xr-x  3 root root 4096 Feb 26 23:10 ./
> drwxr-xr-x  3 root root 4096 Feb 26 22:20 ../
> drwxr-xr-x 48 root root 4096 Feb 26 22:30 spce.bak/
> root at spce:/var/lib/collectd/rrd# /etc/init.d/collectd start
> [ ok ] Starting statistics collection and monitoring daemon: collectd.
> root at spce:/var/lib/collectd/rrd# ls -lapt
> total 16
> drwxr-xr-x 41 root root 4096 Feb 26 23:10 spce/
> drwxr-xr-x  4 root root 4096 Feb 26 23:10 ./
> drwxr-xr-x 48 root root 4096 Feb 26 22:30 spce.bak/
> drwxr-xr-x  3 root root 4096 Feb 26 22:20 ../
> root at spce:/var/lib/collectd/rrd#
> ===
>
> ?Did not work... Any more hints ?
> Please ??
>
>
> ---
> Marco
> ---
>
>
> On Fri, Oct 23, 2015 at 1:59 AM, Marco Teixeira <admin at marcoteixeira.com>
> wrote:
>
>> Hi there,
>>
>> As it seems, i didn't catch these on the logs, on first time. Could this
>> be it ?
>> ntpd is running ... But i guess this only afects graphing ntp process ...
>>
>> === CUT
>> Oct 23 00:27:09 localhost collectd[21512]: rrdtool plugin: Adjusting
>> "RandomTimeout" to 0.000 seconds.
>> Oct 23 00:27:09 localhost collectd[21512]: mysql plugin: Successfully
>> connected to database <none> at server Localhost via UNIX socket (server
>> version: 5.5.44-0+deb7u1-log, protocol version: 10)
>> Oct 23 00:27:09 localhost collectd[21512]: recv(2) failed: Connection
>> refused
>> Oct 23 00:27:09 localhost collectd[21512]: ntpd plugin: ntpd_do_query
>> (REQ_GET_KERNEL) failed with status -1
>> Oct 23 00:27:09 localhost collectd[21512]: read-function of plugin `ntpd'
>> failed. Will suspend it for 20 seconds.
>>
>>
>>
>>
>> ---
>> Cumprimentos / Best regards
>>
>> Marco
>> ---
>>
>>
>> On Thu, Oct 22, 2015 at 10:02 PM, Marco Teixeira <admin at marcoteixeira.com
>> > wrote:
>>
>>> Well...
>>>
>>> One small corretion for future users getting to this, rrd files in
>>> mr3.8.3 are on /var/lib/collectd/rrd/ $HOSTNAME
>>>
>>> Now, back to the problem in hand:
>>> - collectd is fine
>>> - rrd files have current timestamps
>>> - "rrdtool fetch" works ok
>>>
>>> It seems something with graphics generation or saving... took a look at
>>> the code in /usr/share/ngcp-panel/templates/statistics/lists.tt but i'm
>>> having dificulties graspping it...
>>> - there is a line "var tz_offset = [% tz_offset %];". Where does this
>>> variable come from ? The system ?
>>> - Are the graphics generated on the fly for display, or are they stored
>>> somewhere else ?
>>> - Does nginx have some timezone variable in the confs and not  copying
>>> from the system ?
>>>
>>> ?thank you for your time...?
>>>
>>>
>>> ---
>>> Cumprimentos / Best regards
>>>
>>> Marco
>>>
>>>
>>> On Mon, Oct 19, 2015 at 11:16 AM, Alex Lutay <alutay at sipwise.com> wrote:
>>>
>>>> Hi Marco,
>>>>
>>>> All system statistics are collected by collectd and are stored in RRD
>>>> files located in /var/lib/collectd/rrd/spce/
>>>>
>>>> "Internally, RRDtool uses "seconds since the epoch" to keep track of
>>>> time. This is the number of seconds since January first, 1970,
>>>> midnight, UTC. When you are specifying a time in this format, it is UTC
>>>> time automatically." (c) http://vandenbogaerdt.nl/rrdtool/timezone.php
>>>>
>>>> So, you need to check collecd log first to see new values are
>>>> inserter properly, also you can manually extract RRD data using RRD
>>>> tool fetch (to check content of RRD file).
>>>>
>>>> Finally you can move RRD files and restart collectd to init new
>>>> statistics files. Then you can manually move old data in new RRD files
>>>> if necessary.
>>>>
>>>> P.S. changing the timezone of server on the fly is not a good idea,
>>>> AFAIK. As data in MySQL DB (like accounting, CDRs) stored in fields
>>>> without timezone specified. Also MySQL works in server timezone by
>>>> default.
>>>>
>>>> On 10/18/2015 10:22 PM, Marco Teixeira wrote:
>>>> > Hello list,
>>>> >
>>>> > A couple weeks ago i lost system statistics... The page opens but
>>>> > doesn't get pasted those loading progress circling dots... All of
>>>> them,
>>>> > on any variable i select on the dropdown box.
>>>> >
>>>> > I searched around on the logs, and found nothing.
>>>> > Does anyone have a clue how to fix this ?
>>>> >
>>>> > # more /etc/ngcp_version
>>>> > mr3.8.3
>>>>
>>>> --
>>>> Alex Lutay
>>>> _______________________________________________
>>>> Spce-user mailing list
>>>> Spce-user at lists.sipwise.com
>>>> https://lists.sipwise.com/listinfo/spce-user
>>>>
>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20160226/70b5db98/attachment.html>

From matthew at tenacit.net  Mon Feb 29 05:38:06 2016
From: matthew at tenacit.net (Matthew Ogden)
Date: Mon, 29 Feb 2016 12:38:06 +0200
Subject: [Spce-user] [22695407.548269] asterisk[27411]: segfault at 407 ip
 00007f26b6375133 sp 00007f26aff83760 error 6 in
 libmysqlclient_r.so.16.0.0[7f26b633f000+13e000]
Message-ID: <CAB4Z0mJw1oY6yYQPqeGjiByU_Uo_MTeP97O=KhpqZHGx5_MTGQ@mail.gmail.com>

Hi All

I'm trying to use VM in spce for the first time.

I'm getting the following problem:
Feb 29 12:31:27 spce kernel: [22695407.548269] asterisk[27411]: segfault at
407 ip 00007f26b6375133 sp 00007f26aff83760 error 6 in
libmysqlclient_r.so.16.0.0[7f26b633f000+13e000]

logged in syslog as soon as somoen calls 2000.

In asterisk I'm seeing (sanitized):

Connected to Asterisk 1.4.24.1-RSP (Community supported branch) currently
running on spce (pid = 27385)
Verbosity was 0 and is now 73
    -- Executing [abcSUBSCRIBER at sip_in:1]
Macro("SIP/sip.mydomain.net-011ead40", "voicemailowner_nopass|SUBSCRIBER")
in new stack
    -- Executing [s at macro-voicemailowner_nopass:1]
Answer("SIP/sip.mydomain.net-011ead40", "") in new stack
    -- Executing [s at macro-voicemailowner_nopass:2]
Set("SIP/sip.mydomain.net-011ead40", "TIMEOUT(digit)=5") in new stack
    -- Digit timeout set to 5
    -- Executing [s at macro-voicemailowner_nopass:3]
Set("SIP/sip.mydomain.net-011ead40", "TIMEOUT(response)=10") in new stack
    -- Response timeout set to 10
    -- Executing [s at macro-voicemailowner_nopass:4]
Wait("SIP/sip.mydomain.net-011ead40", "1") in new stack
    -- Executing [s at macro-voicemailowner_nopass:5]
VoiceMailMain("SIP/sip.mydomain.net-011ead40", "sSUBSCRIBER") in new stack
spce*CLI>


-- 





*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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20160229/540940b9/attachment.html>

From matthew at tenacit.net  Mon Feb 29 05:43:11 2016
From: matthew at tenacit.net (Matthew Ogden)
Date: Mon, 29 Feb 2016 12:43:11 +0200
Subject: [Spce-user] [22695407.548269] asterisk[27411]: segfault at 407
 ip 00007f26b6375133 sp 00007f26aff83760 error 6 in
 libmysqlclient_r.so.16.0.0[7f26b633f000+13e000]
In-Reply-To: <CAB4Z0mJw1oY6yYQPqeGjiByU_Uo_MTeP97O=KhpqZHGx5_MTGQ@mail.gmail.com>
References: <CAB4Z0mJw1oY6yYQPqeGjiByU_Uo_MTeP97O=KhpqZHGx5_MTGQ@mail.gmail.com>
Message-ID: <CAB4Z0mLZM7aZ8h9Bz1qvC735EQfY-M9aRE34Nakycm7JXo8zFA@mail.gmail.com>

I'm on version 3, but I'm running Debian 6.0.10 still.

based on the other threads, you guys are saying upgrade?

On 29 February 2016 at 12:38, Matthew Ogden <matthew at tenacit.net> wrote:

> Hi All
>
> I'm trying to use VM in spce for the first time.
>
> I'm getting the following problem:
> Feb 29 12:31:27 spce kernel: [22695407.548269] asterisk[27411]: segfault
> at 407 ip 00007f26b6375133 sp 00007f26aff83760 error 6 in
> libmysqlclient_r.so.16.0.0[7f26b633f000+13e000]
>
> logged in syslog as soon as somoen calls 2000.
>
> In asterisk I'm seeing (sanitized):
>
> Connected to Asterisk 1.4.24.1-RSP (Community supported branch) currently
> running on spce (pid = 27385)
> Verbosity was 0 and is now 73
>     -- Executing [abcSUBSCRIBER at sip_in:1]
> Macro("SIP/sip.mydomain.net-011ead40", "voicemailowner_nopass|SUBSCRIBER")
> in new stack
>     -- Executing [s at macro-voicemailowner_nopass:1]
> Answer("SIP/sip.mydomain.net-011ead40", "") in new stack
>     -- Executing [s at macro-voicemailowner_nopass:2]
> Set("SIP/sip.mydomain.net-011ead40", "TIMEOUT(digit)=5") in new stack
>     -- Digit timeout set to 5
>     -- Executing [s at macro-voicemailowner_nopass:3]
> Set("SIP/sip.mydomain.net-011ead40", "TIMEOUT(response)=10") in new stack
>     -- Response timeout set to 10
>     -- Executing [s at macro-voicemailowner_nopass:4]
> Wait("SIP/sip.mydomain.net-011ead40", "1") in new stack
>     -- Executing [s at macro-voicemailowner_nopass:5]
> VoiceMailMain("SIP/sip.mydomain.net-011ead40", "sSUBSCRIBER") in new stack
> spce*CLI>
>
>
> --
>
>
>
>
>
> *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
>
>
>



-- 





*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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20160229/042018a4/attachment.html>

From noreply at sipwise.com  Mon Feb 29 09:08:32 2016
From: noreply at sipwise.com (Sipwise Repository Tracker)
Date: Mon, 29 Feb 2016 15:08:32 +0100
Subject: [Spce-user] FYI: Package update(s) in release mr3.8.3
Message-ID: <1456754912.521359.14790.nullmailer@deb1.sipwise.com>

One or more updates have been released in NGCP release mr3.8.3:

* captagent was updated from version 5.2.11.0-1+0~mr3.8.3.14 to version 5.2.12.0-1+0~mr3.8.3.15
* captagent-dbg was updated from version 5.2.11.0-1+0~mr3.8.3.14 to version 5.2.12.0-1+0~mr3.8.3.15

To apply the latest update(s) execute:

  apt-get update && apt-get upgrade && \
  ngcp-update-db-schema && ngcp-update-cfg-schema && \
  ngcpcfg apply manual system update

If you encounter any problems please report a bug at
the spce-user at lists.sipwise.com mailing list.

Further documentation is available at:

  http://www.sipwise.org/products/spce/documentation/

This is an automated mail by the Continuous Delivery platform at Sipwise.com


From noreply at sipwise.com  Mon Feb 29 09:09:55 2016
From: noreply at sipwise.com (Sipwise Repository Tracker)
Date: Mon, 29 Feb 2016 15:09:55 +0100
Subject: [Spce-user] FYI: Package update(s) in release mr3.8.4
Message-ID: <1456754995.532091.15031.nullmailer@deb1.sipwise.com>

One or more updates have been released in NGCP release mr3.8.4:

* captagent was updated from version 5.2.11.0-1+0~mr3.8.4.12 to version 5.2.12.0-1+0~mr3.8.4.13
* captagent-dbg was updated from version 5.2.11.0-1+0~mr3.8.4.12 to version 5.2.12.0-1+0~mr3.8.4.13

To apply the latest update(s) execute:

  apt-get update && apt-get upgrade && \
  ngcp-update-db-schema && ngcp-update-cfg-schema && \
  ngcpcfg apply manual system update

If you encounter any problems please report a bug at
the spce-user at lists.sipwise.com mailing list.

Further documentation is available at:

  http://www.sipwise.org/products/spce/documentation/

This is an automated mail by the Continuous Delivery platform at Sipwise.com


From noreply at sipwise.com  Mon Feb 29 09:11:16 2016
From: noreply at sipwise.com (Sipwise Repository Tracker)
Date: Mon, 29 Feb 2016 15:11:16 +0100
Subject: [Spce-user] FYI: Package update(s) in release mr3.8.5
Message-ID: <1456755076.558468.15389.nullmailer@deb1.sipwise.com>

One or more updates have been released in NGCP release mr3.8.5:

* captagent was updated from version 5.2.11.0-1+0~mr3.8.5.8 to version 5.2.12.0-1+0~mr3.8.5.9
* captagent-dbg was updated from version 5.2.11.0-1+0~mr3.8.5.8 to version 5.2.12.0-1+0~mr3.8.5.9

To apply the latest update(s) execute:

  apt-get update && apt-get upgrade && \
  ngcp-update-db-schema && ngcp-update-cfg-schema && \
  ngcpcfg apply manual system update

If you encounter any problems please report a bug at
the spce-user at lists.sipwise.com mailing list.

Further documentation is available at:

  http://www.sipwise.org/products/spce/documentation/

This is an automated mail by the Continuous Delivery platform at Sipwise.com


From noreply at sipwise.com  Mon Feb 29 09:18:42 2016
From: noreply at sipwise.com (Sipwise Repository Tracker)
Date: Mon, 29 Feb 2016 15:18:42 +0100
Subject: [Spce-user] FYI: Package update(s) in release mr4.2.1
Message-ID: <1456755522.118207.16998.nullmailer@deb1.sipwise.com>

One or more updates have been released in NGCP release mr4.2.1:

* captagent was updated from version 5.2.11.1-1+0~mr4.2.1.11 to version 5.2.12.1-1+0~mr4.2.1.12
* captagent-dbg was updated from version 5.2.11.1-1+0~mr4.2.1.11 to version 5.2.12.1-1+0~mr4.2.1.12

To apply the latest update(s) execute:

  apt-get update && apt-get upgrade && \
  ngcp-update-db-schema && ngcp-update-cfg-schema && \
  ngcpcfg apply manual system update

If you encounter any problems please report a bug at
the spce-user at lists.sipwise.com mailing list.

Further documentation is available at:

  http://www.sipwise.org/products/spce/documentation/

This is an automated mail by the Continuous Delivery platform at Sipwise.com


From noreply at sipwise.com  Mon Feb 29 09:19:37 2016
From: noreply at sipwise.com (Sipwise Repository Tracker)
Date: Mon, 29 Feb 2016 15:19:37 +0100
Subject: [Spce-user] FYI: Package update(s) in release mr4.2.1
Message-ID: <1456755577.377592.17245.nullmailer@deb1.sipwise.com>

One or more updates have been released in NGCP release mr4.2.1:

* ngcp-db-schema was updated from version 4.2.1.1+0~mr4.2.1.1 to version 4.2.1.2+0~mr4.2.1.2

To apply the latest update(s) execute:

  apt-get update && apt-get upgrade && \
  ngcp-update-db-schema && ngcp-update-cfg-schema && \
  ngcpcfg apply manual system update

If you encounter any problems please report a bug at
the spce-user at lists.sipwise.com mailing list.

Further documentation is available at:

  http://www.sipwise.org/products/spce/documentation/

This is an automated mail by the Continuous Delivery platform at Sipwise.com


From noreply at sipwise.com  Mon Feb 29 09:22:04 2016
From: noreply at sipwise.com (Sipwise Repository Tracker)
Date: Mon, 29 Feb 2016 15:22:04 +0100
Subject: [Spce-user] FYI: Package update(s) in release mr3.8.5
Message-ID: <1456755724.240082.18051.nullmailer@deb1.sipwise.com>

One or more updates have been released in NGCP release mr3.8.5:

* ngcp-db-schema was updated from version 3.8.5.1+0~mr3.8.5.1 to version 3.8.5.2+0~mr3.8.5.2

To apply the latest update(s) execute:

  apt-get update && apt-get upgrade && \
  ngcp-update-db-schema && ngcp-update-cfg-schema && \
  ngcpcfg apply manual system update

If you encounter any problems please report a bug at
the spce-user at lists.sipwise.com mailing list.

Further documentation is available at:

  http://www.sipwise.org/products/spce/documentation/

This is an automated mail by the Continuous Delivery platform at Sipwise.com


From noreply at sipwise.com  Mon Feb 29 09:23:14 2016
From: noreply at sipwise.com (Sipwise Repository Tracker)
Date: Mon, 29 Feb 2016 15:23:14 +0100
Subject: [Spce-user] FYI: Package update(s) in release mr3.8.4
Message-ID: <1456755794.385043.18407.nullmailer@deb1.sipwise.com>

One or more updates have been released in NGCP release mr3.8.4:

* ngcp-db-schema was updated from version 3.8.4.1+0~mr3.8.4.1 to version 3.8.4.2+0~mr3.8.4.2

To apply the latest update(s) execute:

  apt-get update && apt-get upgrade && \
  ngcp-update-db-schema && ngcp-update-cfg-schema && \
  ngcpcfg apply manual system update

If you encounter any problems please report a bug at
the spce-user at lists.sipwise.com mailing list.

Further documentation is available at:

  http://www.sipwise.org/products/spce/documentation/

This is an automated mail by the Continuous Delivery platform at Sipwise.com


From admin at marcoteixeira.com  Mon Feb 29 10:20:30 2016
From: admin at marcoteixeira.com (Marco Teixeira)
Date: Mon, 29 Feb 2016 15:20:30 +0000
Subject: [Spce-user] System Statistics stopped working
In-Reply-To: <CAD7smbhxJ1Xu8s22qL9YVuVgY80paC1hqB+G8kf2FdGBGyK5dw@mail.gmail.com>
References: <CAD7smbj1zw5O_-R16yyJB1+fNb=bqBSNWRXUvcx5zoTEmPnjiw@mail.gmail.com>
 <5624C307.8010404@sipwise.com>
 <CAD7smbgusq1rTY2bLZidfcvAuqbvAw1fqvFg_ZsSnTPyOY-X7A@mail.gmail.com>
 <CAD7smbjKD9zohdQR7DbZB4W_Z4_nWM_MNiKY94h3rcQfv1d9UQ@mail.gmail.com>
 <CAD7smbh7CovFUp2-3Z+Ua6iM6Y_55v2zyO-8oup=OB9k-08iVg@mail.gmail.com>
 <CAD7smbhxJ1Xu8s22qL9YVuVgY80paC1hqB+G8kf2FdGBGyK5dw@mail.gmail.com>
Message-ID: <CAD7smbhXHey0dA=DhTcNHvBg9nm5EXrefPyrQ0h3g0BLrCsvPQ@mail.gmail.com>

Sorry to bump this up, but i really need to get this working... i imagine
it would be a simple thing to fix. I just don't know where...


On Fri, Feb 26, 2016 at 11:16 PM, Marco Teixeira <admin at marcoteixeira.com>
wrote:

> If i change back to Europe/Vienna, Statistics start displaying again...
> Not even a reboot needed...
> I'm guessing a hardcoded tz_offset variable somewhere on the panel coding
> maybe ...
>
>
> ===
> Current default time zone: 'Europe/Vienna'
> Local time is now:      Sat Feb 27 00:12:48 CET 2016.
> Universal Time is now:  Fri Feb 26 23:12:48 UTC 2016.
> ===
>
>
> On Fri, Feb 26, 2016 at 11:12 PM, Marco Teixeira <admin at marcoteixeira.com>
> wrote:
>
>> Hello,
>>
>> Getting back to this old issue... Back to basics.
>> - I installed a clean 3.8.3. Stats working ok.
>> - Changed default timezone from Europe/Vienna to GMT. Stats stopped
>> working...
>>
>> Followed sugestion of deleting RRD files to allow regeneration...
>>
>> ===
>> root at spce:/var/lib/collectd/rrd# /etc/init.d/collectd stop
>> [ ok ] Stopping statistics collection and monitoring daemon: collectd.
>> root at spce:/var/lib/collectd/rrd# mv spce spce.bak
>> root at spce:/var/lib/collectd/rrd# ls -lap
>> total 12
>> drwxr-xr-x  3 root root 4096 Feb 26 23:10 ./
>> drwxr-xr-x  3 root root 4096 Feb 26 22:20 ../
>> drwxr-xr-x 48 root root 4096 Feb 26 22:30 spce.bak/
>> root at spce:/var/lib/collectd/rrd# /etc/init.d/collectd start
>> [ ok ] Starting statistics collection and monitoring daemon: collectd.
>> root at spce:/var/lib/collectd/rrd# ls -lapt
>> total 16
>> drwxr-xr-x 41 root root 4096 Feb 26 23:10 spce/
>> drwxr-xr-x  4 root root 4096 Feb 26 23:10 ./
>> drwxr-xr-x 48 root root 4096 Feb 26 22:30 spce.bak/
>> drwxr-xr-x  3 root root 4096 Feb 26 22:20 ../
>> root at spce:/var/lib/collectd/rrd#
>> ===
>>
>> ?Did not work... Any more hints ?
>> Please ??
>>
>>
>> ---
>> Marco
>> ---
>>
>>
>> On Fri, Oct 23, 2015 at 1:59 AM, Marco Teixeira <admin at marcoteixeira.com>
>> wrote:
>>
>>> Hi there,
>>>
>>> As it seems, i didn't catch these on the logs, on first time. Could this
>>> be it ?
>>> ntpd is running ... But i guess this only afects graphing ntp process ...
>>>
>>> === CUT
>>> Oct 23 00:27:09 localhost collectd[21512]: rrdtool plugin: Adjusting
>>> "RandomTimeout" to 0.000 seconds.
>>> Oct 23 00:27:09 localhost collectd[21512]: mysql plugin: Successfully
>>> connected to database <none> at server Localhost via UNIX socket (server
>>> version: 5.5.44-0+deb7u1-log, protocol version: 10)
>>> Oct 23 00:27:09 localhost collectd[21512]: recv(2) failed: Connection
>>> refused
>>> Oct 23 00:27:09 localhost collectd[21512]: ntpd plugin: ntpd_do_query
>>> (REQ_GET_KERNEL) failed with status -1
>>> Oct 23 00:27:09 localhost collectd[21512]: read-function of plugin
>>> `ntpd' failed. Will suspend it for 20 seconds.
>>>
>>>
>>>
>>>
>>> ---
>>> Cumprimentos / Best regards
>>>
>>> Marco
>>> ---
>>>
>>>
>>> On Thu, Oct 22, 2015 at 10:02 PM, Marco Teixeira <
>>> admin at marcoteixeira.com> wrote:
>>>
>>>> Well...
>>>>
>>>> One small corretion for future users getting to this, rrd files in
>>>> mr3.8.3 are on /var/lib/collectd/rrd/ $HOSTNAME
>>>>
>>>> Now, back to the problem in hand:
>>>> - collectd is fine
>>>> - rrd files have current timestamps
>>>> - "rrdtool fetch" works ok
>>>>
>>>> It seems something with graphics generation or saving... took a look at
>>>> the code in /usr/share/ngcp-panel/templates/statistics/lists.tt but
>>>> i'm having dificulties graspping it...
>>>> - there is a line "var tz_offset = [% tz_offset %];". Where does this
>>>> variable come from ? The system ?
>>>> - Are the graphics generated on the fly for display, or are they stored
>>>> somewhere else ?
>>>> - Does nginx have some timezone variable in the confs and not  copying
>>>> from the system ?
>>>>
>>>> ?thank you for your time...?
>>>>
>>>>
>>>> ---
>>>> Cumprimentos / Best regards
>>>>
>>>> Marco
>>>>
>>>>
>>>> On Mon, Oct 19, 2015 at 11:16 AM, Alex Lutay <alutay at sipwise.com>
>>>> wrote:
>>>>
>>>>> Hi Marco,
>>>>>
>>>>> All system statistics are collected by collectd and are stored in RRD
>>>>> files located in /var/lib/collectd/rrd/spce/
>>>>>
>>>>> "Internally, RRDtool uses "seconds since the epoch" to keep track of
>>>>> time. This is the number of seconds since January first, 1970,
>>>>> midnight, UTC. When you are specifying a time in this format, it is UTC
>>>>> time automatically." (c) http://vandenbogaerdt.nl/rrdtool/timezone.php
>>>>>
>>>>> So, you need to check collecd log first to see new values are
>>>>> inserter properly, also you can manually extract RRD data using RRD
>>>>> tool fetch (to check content of RRD file).
>>>>>
>>>>> Finally you can move RRD files and restart collectd to init new
>>>>> statistics files. Then you can manually move old data in new RRD files
>>>>> if necessary.
>>>>>
>>>>> P.S. changing the timezone of server on the fly is not a good idea,
>>>>> AFAIK. As data in MySQL DB (like accounting, CDRs) stored in fields
>>>>> without timezone specified. Also MySQL works in server timezone by
>>>>> default.
>>>>>
>>>>> On 10/18/2015 10:22 PM, Marco Teixeira wrote:
>>>>> > Hello list,
>>>>> >
>>>>> > A couple weeks ago i lost system statistics... The page opens but
>>>>> > doesn't get pasted those loading progress circling dots... All of
>>>>> them,
>>>>> > on any variable i select on the dropdown box.
>>>>> >
>>>>> > I searched around on the logs, and found nothing.
>>>>> > Does anyone have a clue how to fix this ?
>>>>> >
>>>>> > # more /etc/ngcp_version
>>>>> > mr3.8.3
>>>>>
>>>>> --
>>>>> Alex Lutay
>>>>> _______________________________________________
>>>>> Spce-user mailing list
>>>>> Spce-user at lists.sipwise.com
>>>>> https://lists.sipwise.com/listinfo/spce-user
>>>>>
>>>>
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20160229/e89f2b86/attachment.html>

From noreply at sipwise.com  Mon Feb 29 11:54:22 2016
From: noreply at sipwise.com (Sipwise Repository Tracker)
Date: Mon, 29 Feb 2016 17:54:22 +0100
Subject: [Spce-user] FYI: Package update(s) in release mr3.8.3
Message-ID: <1456764862.568571.4976.nullmailer@deb1.sipwise.com>

One or more updates have been released in NGCP release mr3.8.3:

* captagent was updated from version 5.2.12.0-1+0~mr3.8.3.15 to version 5.2.13.0-1+0~mr3.8.3.16
* captagent-dbg was updated from version 5.2.12.0-1+0~mr3.8.3.15 to version 5.2.13.0-1+0~mr3.8.3.16

To apply the latest update(s) execute:

  apt-get update && apt-get upgrade && \
  ngcp-update-db-schema && ngcp-update-cfg-schema && \
  ngcpcfg apply manual system update

If you encounter any problems please report a bug at
the spce-user at lists.sipwise.com mailing list.

Further documentation is available at:

  http://www.sipwise.org/products/spce/documentation/

This is an automated mail by the Continuous Delivery platform at Sipwise.com


From noreply at sipwise.com  Mon Feb 29 11:55:42 2016
From: noreply at sipwise.com (Sipwise Repository Tracker)
Date: Mon, 29 Feb 2016 17:55:42 +0100
Subject: [Spce-user] FYI: Package update(s) in release mr3.8.4
Message-ID: <1456764942.396067.5213.nullmailer@deb1.sipwise.com>

One or more updates have been released in NGCP release mr3.8.4:

* captagent was updated from version 5.2.12.0-1+0~mr3.8.4.13 to version 5.2.13.0-1+0~mr3.8.4.14
* captagent-dbg was updated from version 5.2.12.0-1+0~mr3.8.4.13 to version 5.2.13.0-1+0~mr3.8.4.14

To apply the latest update(s) execute:

  apt-get update && apt-get upgrade && \
  ngcp-update-db-schema && ngcp-update-cfg-schema && \
  ngcpcfg apply manual system update

If you encounter any problems please report a bug at
the spce-user at lists.sipwise.com mailing list.

Further documentation is available at:

  http://www.sipwise.org/products/spce/documentation/

This is an automated mail by the Continuous Delivery platform at Sipwise.com


From noreply at sipwise.com  Mon Feb 29 11:57:08 2016
From: noreply at sipwise.com (Sipwise Repository Tracker)
Date: Mon, 29 Feb 2016 17:57:08 +0100
Subject: [Spce-user] FYI: Package update(s) in release mr3.8.5
Message-ID: <1456765028.495443.5531.nullmailer@deb1.sipwise.com>

One or more updates have been released in NGCP release mr3.8.5:

* captagent was updated from version 5.2.12.0-1+0~mr3.8.5.9 to version 5.2.13.0-1+0~mr3.8.5.10
* captagent-dbg was updated from version 5.2.12.0-1+0~mr3.8.5.9 to version 5.2.13.0-1+0~mr3.8.5.10

To apply the latest update(s) execute:

  apt-get update && apt-get upgrade && \
  ngcp-update-db-schema && ngcp-update-cfg-schema && \
  ngcpcfg apply manual system update

If you encounter any problems please report a bug at
the spce-user at lists.sipwise.com mailing list.

Further documentation is available at:

  http://www.sipwise.org/products/spce/documentation/

This is an automated mail by the Continuous Delivery platform at Sipwise.com


From noreply at sipwise.com  Mon Feb 29 12:02:57 2016
From: noreply at sipwise.com (Sipwise Repository Tracker)
Date: Mon, 29 Feb 2016 18:02:57 +0100
Subject: [Spce-user] FYI: Package update(s) in release mr4.2.1
Message-ID: <1456765377.488080.6622.nullmailer@deb1.sipwise.com>

One or more updates have been released in NGCP release mr4.2.1:

* captagent was updated from version 5.2.12.1-1+0~mr4.2.1.12 to version 5.2.13.1-1+0~mr4.2.1.13
* captagent-dbg was updated from version 5.2.12.1-1+0~mr4.2.1.12 to version 5.2.13.1-1+0~mr4.2.1.13

To apply the latest update(s) execute:

  apt-get update && apt-get upgrade && \
  ngcp-update-db-schema && ngcp-update-cfg-schema && \
  ngcpcfg apply manual system update

If you encounter any problems please report a bug at
the spce-user at lists.sipwise.com mailing list.

Further documentation is available at:

  http://www.sipwise.org/products/spce/documentation/

This is an automated mail by the Continuous Delivery platform at Sipwise.com


From alexander at schrego.com  Mon Feb  1 02:29:28 2016
From: alexander at schrego.com (Alexander Topolanek)
Date: Mon, 1 Feb 2016 08:29:28 +0100
Subject: [Spce-user] How to reset the invoice count
Message-ID: <56AF0958.1050904@schrego.com>

Hello,

Invoices generated by the web interface have an increasing serial 
number, If I need to change that serial number or reset it to start from 
1 how would I do that.
Can I truncate the table billing.invoices for that?

kind regards

-- 
Alexander Topolanek
System engineer



From vseva at sipwise.com  Mon Feb  1 04:27:31 2016
From: vseva at sipwise.com (Victor Seva)
Date: Mon, 1 Feb 2016 10:27:31 +0100
Subject: [Spce-user] New sip:provider CE mr4.2.1 is now available
In-Reply-To: <013701d15c76$b9618f50$2c24adf0$@telematica.at>
References: <56AB780C.8060705@sipwise.com>
 <013701d15c76$b9618f50$2c24adf0$@telematica.at>
Message-ID: <56AF2503.3040107@sipwise.com>

On 01/31/2016 11:28 PM, Matthias Hohl wrote:
> After starting the installation, the installation stops cause the directory ".ssh" is not available on the server.
> The ".ssh" directory must be created manually before I could run ngcp-upgrade again.


Thanks for your report!
-- 
Victor Seva
Software Engineer

Phone: +43(0)1 301 2029
Email: vseva at sipwise.com
Website: www.sipwise.com

Particulars according Austrian Companies Code paragraph 14
"Sipwise GmbH? - Europaring F15 ? 2345 Brunn am Gebirge
FN:305595f, Commercial Court Vienna, ATU64002206

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20160201/79fdc61a/attachment-0001.asc>

From alutay at sipwise.com  Mon Feb  1 05:27:47 2016
From: alutay at sipwise.com (Alex Lutay)
Date: Mon, 1 Feb 2016 11:27:47 +0100
Subject: [Spce-user] Rings once, then disconnects!
In-Reply-To: <DB5PR06MB1557AB8F343FE2DD1C4AC44FBEDE0@DB5PR06MB1557.eurprd06.prod.outlook.com>
References: <DB5PR06MB1557AB8F343FE2DD1C4AC44FBEDE0@DB5PR06MB1557.eurprd06.prod.outlook.com>
Message-ID: <56AF3323.3090101@sipwise.com>

Dear William,

As I can see on picture SPCE received "500 - Server Internal Error"
from your Carrier, so there is nothing we can tell you here.

Please ask your Carrier about the reason of internal server error here.

On 02/01/2016 03:08 AM, William Hilsum wrote:
[...skipped...]
> I?ve tried to do diagnostics ? I selected both legs of the call and made
> a quick picture: http://i.imgur.com/PzJF0Y5.jpg
[...skipped...]
> Feb  1 02:55:45 masterpbx1 (local7.notice) proxy[3350]: NOTICE:
> <script>: NAT-Reply - S=500 - Server Internal Error M=INVITE
> IP=**MY-HOME-IP**:56805 (127.0.0.1:5080)
> ID=ZTdlYmYwY2I2MmExZThkYmY1MTIxZGJmOGQyOWQ4ZmM. UA='<null>'
[...skipped...]

-- 
Alex Lutay



From matthias.hohl at telematica.at  Mon Feb  1 05:38:44 2016
From: matthias.hohl at telematica.at (Matthias Hohl)
Date: Mon, 1 Feb 2016 11:38:44 +0100 (CET)
Subject: [Spce-user] Upgrade to 4.2.1 causes in a cronjob failure
Message-ID: <027e01d15cdc$b940fea0$2bc2fbe0$@telematica.at>

Hello,

 

I get this error per mail everytime when the fraud auto lock is running as
cron.

 

What does this mean? An how can I solve it?

 

Thanks.

 

 

 

 

Cron <root at spce> if /usr/sbin/ngcp-check_active -q; then
/usr/sbin/ngcp-fraud-auto-lock; fi

 

Smartmatch is experimental at /usr/share/perl5/Sipwise/Provisioning.pm line
1122.
Use of my $_ is experimental at /usr/share/perl5/Sipwise/Provisioning.pm
line 1146.
defined(@array) is deprecated at /usr/share/perl5/PDF/Reuse.pm line 993.
(Maybe you should just omit the defined()?)
defined(@array) is deprecated at /usr/share/perl5/PDF/Reuse.pm line 993.
(Maybe you should just omit the defined()?)
Smartmatch is experimental at
/usr/share/perl5/Sipwise/Provisioning/Voip/DB.pm line 748.
given is experimental at /usr/share/perl5/Sipwise/Provisioning/Voip.pm line
6629.
when is experimental at /usr/share/perl5/Sipwise/Provisioning/Voip.pm line
6630.
when is experimental at /usr/share/perl5/Sipwise/Provisioning/Voip.pm line
6634.
Smartmatch is experimental at /usr/share/perl5/Sipwise/Provisioning/Voip.pm
line 6992.
Smartmatch is experimental at /usr/share/perl5/Sipwise/Provisioning/Voip.pm
line 7047.
Smartmatch is experimental at /usr/share/perl5/Sipwise/Provisioning/Voip.pm
line 7236.
Smartmatch is experimental at /usr/share/perl5/Sipwise/Provisioning/Voip.pm
line 7236.
Smartmatch is experimental at /usr/share/perl5/Sipwise/Provisioning/Voip.pm
line 7240.
Smartmatch is experimental at /usr/share/perl5/Sipwise/Provisioning/Voip.pm
line 7240.
Smartmatch is experimental at /usr/share/perl5/Sipwise/Provisioning/Voip.pm
line 7244.
Smartmatch is experimental at /usr/share/perl5/Sipwise/Provisioning/Voip.pm
line 7244.
Smartmatch is experimental at /usr/share/perl5/Sipwise/Provisioning/Voip.pm
line 7248.
Smartmatch is experimental at /usr/share/perl5/Sipwise/Provisioning/Voip.pm
line 7248.
Smartmatch is experimental at /usr/share/perl5/Sipwise/Provisioning/Voip.pm
line 7252.
Smartmatch is experimental at /usr/share/perl5/Sipwise/Provisioning/Voip.pm
line 7252.
Use of my $_ is experimental at
/usr/share/perl5/Sipwise/Provisioning/Voip.pm line 7259.

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20160201/3b7a244f/attachment-0001.html>

From vseva at sipwise.com  Mon Feb  1 06:03:54 2016
From: vseva at sipwise.com (Victor Seva)
Date: Mon, 1 Feb 2016 12:03:54 +0100
Subject: [Spce-user] New sip:provider CE mr4.2.1 is now available
In-Reply-To: <56AF2503.3040107@sipwise.com>
References: <56AB780C.8060705@sipwise.com>
 <013701d15c76$b9618f50$2c24adf0$@telematica.at>
 <56AF2503.3040107@sipwise.com>
Message-ID: <56AF3B9A.6000706@sipwise.com>

On 02/01/2016 10:27 AM, Victor Seva wrote:
> On 01/31/2016 11:28 PM, Matthias Hohl wrote:
>> After starting the installation, the installation stops cause the directory ".ssh" is not available on the server.
>> The ".ssh" directory must be created manually before I could run ngcp-upgrade again.
> 
> 
> Thanks for your report!

Fix released!

ngcp-support (0.3.1.2+0~mr4.2.1.2) unstable; urgency=medium

  [ Victor Seva ]
  * [acc3ed6] MT#17647 ngcp-support-access: assert ${HOME}/.ssh exists

  [ Sipwise Jenkins Builder ]

 -- Sipwise Jenkins Builder <jenkins at sipwise.com>  Mon, 01 Feb 2016
11:30:32 +0100

-- 
Victor Seva
Software Engineer

Phone: +43(0)1 301 2029
Email: vseva at sipwise.com
Website: www.sipwise.com

Particulars according Austrian Companies Code paragraph 14
"Sipwise GmbH? - Europaring F15 ? 2345 Brunn am Gebirge
FN:305595f, Commercial Court Vienna, ATU64002206

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20160201/3500160b/attachment-0001.asc>

From William at ezpcltd.com  Mon Feb  1 06:37:56 2016
From: William at ezpcltd.com (William Hilsum)
Date: Mon, 1 Feb 2016 11:37:56 +0000
Subject: [Spce-user] Rings once, then disconnects!
In-Reply-To: <56AF3323.3090101@sipwise.com>
References: <DB5PR06MB1557AB8F343FE2DD1C4AC44FBEDE0@DB5PR06MB1557.eurprd06.prod.outlook.com>
 <56AF3323.3090101@sipwise.com>
Message-ID: <DB5PR06MB15571F52E939DC8818644634BEDE0@DB5PR06MB1557.eurprd06.prod.outlook.com>

Hi,

I've been working on this overnight and made a bit more progress... and, it is a weird one!

I saw the Sipwise Ios App and I thought I would give it a go...

I made calls fine without issue!

It looks like the issue is then related to the softphone (I was using 3CX) doing something dodgy and/or Sipwise not removing/changing the headers.

I'm really unsure how to proceed here, but, I am guessing I just have a lot of trial and error ahead of me.

William

-----Original Message-----
From: Spce-user [mailto:spce-user-bounces at lists.sipwise.com] On Behalf Of Alex Lutay
Sent: 01 February 2016 10:28
To: spce-user at lists.sipwise.com
Subject: Re: [Spce-user] Rings once, then disconnects!

Dear William,

As I can see on picture SPCE received "500 - Server Internal Error"
from your Carrier, so there is nothing we can tell you here.

Please ask your Carrier about the reason of internal server error here.

On 02/01/2016 03:08 AM, William Hilsum wrote:
[...skipped...]
> I've tried to do diagnostics - I selected both legs of the call and 
> made a quick picture: http://i.imgur.com/PzJF0Y5.jpg
[...skipped...]
> Feb  1 02:55:45 masterpbx1 (local7.notice) proxy[3350]: NOTICE:
> <script>: NAT-Reply - S=500 - Server Internal Error M=INVITE
> IP=**MY-HOME-IP**:56805 (127.0.0.1:5080) 
> ID=ZTdlYmYwY2I2MmExZThkYmY1MTIxZGJmOGQyOWQ4ZmM. UA='<null>'
[...skipped...]

--
Alex Lutay

_______________________________________________
Spce-user mailing list
Spce-user at lists.sipwise.com
https://lists.sipwise.com/listinfo/spce-user


From j.feugne at prisnets.ch  Mon Feb  1 08:41:08 2016
From: j.feugne at prisnets.ch (=?UTF-8?Q?Jephth=C3=A9_Feugn=C3=A9?=)
Date: Mon, 1 Feb 2016 14:41:08 +0100
Subject: [Spce-user] No sound with outbound call
In-Reply-To: <CAD7smbgDKAQGN=Kr6uksNGrS960RyO3rta7uxThMkOZsbxo1Dg@mail.gmail.com>
References: <abf698f63423a025abf6efeee49764d4@prisnets.ch>
 <CAD7smbgDKAQGN=Kr6uksNGrS960RyO3rta7uxThMkOZsbxo1Dg@mail.gmail.com>
Message-ID: <013701d15cf6$3502c820$9f085860$@prisnets.ch>

Hello Marco,

Sorry to come back to you so late with the information you ask related to my problem in subject.

Here is what I have with the command you gave me:

77.72.169.131 is my Voip provider that is Voicetrading

84.xxx.xxx.xxx My sipwise NGCP VM instance that I?ve just upgrade to 4.2.1

Still no way to have the destination phone ringing.

 

13:32:51.232177 IP 213.55.176.206.3357 > 84.xxx.xxx.xxx.5060: Flags [.], ack 1125, win 16931, options [nop,nop,TS val 15666394 ecr 5685786], length 0

13:32:51.240915 IP 77.72.169.131.5060 > 84.xxx.xxx.xxx.5060: SIP, length: 813

13:32:51.241693 IP 84.xxx.xxx.xxx.5060 > 77.72.169.131.5060: SIP, length: 642

13:32:51.242006 IP 84.xxx.xxx.xxx.5060 > 77.72.169.131.5060: SIP, length: 1436

13:32:51.261239 IP 77.72.169.131.5060 > 84.xxx.xxx.xxx.5060: SIP, length: 813

13:32:51.261911 IP 84.xxx.xxx.xxx.5060 > 77.72.169.131.5060: SIP, length: 642

13:32:51.268555 IP 84.xxx.xxx.xxx.5060 > 213.55.176.206.3357: Flags [P.], seq 1125:1882, ack 2333, win 1452, options [nop,nop,TS val 5685805 ecr 15666394], length 757

13:32:51.325414 IP 213.55.176.206.3357 > 84.xxx.xxx.xxx.5060: Flags [.], ack 1882, win 16931, options [nop,nop,TS val 15666402 ecr 5685805], length 0

13:32:51.392226 IP 213.55.176.206.3357 > 84.xxx.xxx.xxx.5060: Flags [P.], seq 2333:2615, ack 1882, win 16931, options [nop,nop,TS val 15666408 ecr 5685805], length 282

13:32:51.428393 IP 84.xxx.xxx.xxx.5060 > 213.55.176.206.3357: Flags [.], ack 2615, win 1452, options [nop,nop,TS val 5685845 ecr 15666408], length 0

13:32:51.492618 IP 213.55.176.206.3357 > 84.xxx.xxx.xxx.5060: Flags [P.], seq 2615:3508, ack 1882, win 16931, options [nop,nop,TS val 15666417 ecr 5685845], length 893

13:32:51.492632 IP 84.xxx.xxx.xxx.5060 > 213.55.176.206.3357: Flags [.], ack 3508, win 1452, options [nop,nop,TS val 5685861 ecr 15666417], length 0

13:32:51.493556 IP 84.xxx.xxx.xxx.5060 > 213.55.176.206.3357: Flags [P.], seq 1882:2202, ack 3508, win 1452, options [nop,nop,TS val 5685861 ecr 15666417], length 320

13:32:51.498452 IP 84.xxx.xxx.xxx.5060 > 213.55.176.206.3357: Flags [P.], seq 2202:2683, ack 3508, win 1452, options [nop,nop,TS val 5685862 ecr 15666417], length 481

13:32:51.545170 IP 213.55.176.206.3357 > 84.xxx.xxx.xxx.5060: Flags [.], ack 2202, win 16931, options [nop,nop,TS val 15666424 ecr 5685861], length 0

13:32:51.545172 IP 213.55.176.206.3357 > 84.xxx.xxx.xxx.5060: Flags [.], ack 2683, win 16931, options [nop,nop,TS val 15666424 ecr 5685862], length 0

13:32:51.632516 IP 213.55.176.206.3357 > 84.xxx.xxx.xxx.5060: Flags [P.], seq 3508:3831, ack 2683, win 16931, options [nop,nop,TS val 15666432 ecr 5685862], length 323

13:32:51.672526 IP 84.xxx.xxx.xxx.5060 > 213.55.176.206.3357: Flags [.], ack 3831, win 1452, options [nop,nop,TS val 5685906 ecr 15666432], length 0

13:32:51.740698 IP 213.55.176.206.3357 > 84.xxx.xxx.xxx.5060: Flags [P.], seq 3831:4946, ack 2683, win 16931, options [nop,nop,TS val 15666441 ecr 5685906], length 1115

13:32:51.740711 IP 84.xxx.xxx.xxx.5060 > 213.55.176.206.3357: Flags [.], ack 4946, win 1452, options [nop,nop,TS val 5685923 ecr 15666441], length 0

13:32:51.741405 IP 84.xxx.xxx.xxx.5060 > 213.55.176.206.3357: Flags [P.], seq 2683:3004, ack 4946, win 1452, options [nop,nop,TS val 5685923 ecr 15666441], length 321

13:32:51.765479 IP 84.xxx.xxx.xxx.5060 > 77.72.169.129.5060: SIP, length: 1236

13:32:51.784621 IP 77.72.169.131.5060 > 84.xxx.xxx.xxx.5060: SIP, length: 813

13:32:51.785055 IP 213.55.176.206.3357 > 84.xxx.xxx.xxx.5060: Flags [.], ack 3004, win 16931, options [nop,nop,TS val 15666448 ecr 5685923], length 0

13:32:51.785187 IP 84.xxx.xxx.xxx.5060 > 77.72.169.129.5060: SIP, length: 642

13:32:51.785920 IP 84.xxx.xxx.xxx.5060 > 77.72.169.129.5060: SIP, length: 1436

13:32:51.805014 IP 77.72.169.131.5060 > 84.xxx.xxx.xxx.5060: SIP, length: 813

13:32:51.805610 IP 84.xxx.xxx.xxx.5060 > 77.72.169.129.5060: SIP, length: 642

13:32:51.812729 IP 84.xxx.xxx.xxx.5060 > 213.55.176.206.3357: Flags [P.], seq 3004:3761, ack 4946, win 1452, options [nop,nop,TS val 5685941 ecr 15666448], length 757

13:32:51.865097 IP 213.55.176.206.3357 > 84.xxx.xxx.xxx.5060: Flags [.], ack 3761, win 16931, options [nop,nop,TS val 15666456 ecr 5685941], length 0

13:32:51.952443 IP 213.55.176.206.3357 > 84.xxx.xxx.xxx.5060: Flags [P.], seq 4946:5228, ack 3761, win 16931, options [nop,nop,TS val 15666463 ecr 5685941], length 282

13:32:51.992428 IP 84.xxx.xxx.xxx.5060 > 213.55.176.206.3357: Flags [.], ack 5228, win 1452, options [nop,nop,TS val 5685986 ecr 15666463], length 0

13:32:55.460605 IP 84.xxx.xxx.xxx.5060 > 10.3.30.42.5080: SIP, length: 822

13:32:55.461871 IP 10.3.30.42.5080 > 84.xxx.xxx.xxx.5060: SIP, length: 1078

13:32:59.675499 IP 41.216.232.18.5060 > 84.xxx.xxx.xxx.5060: SIP, length: 3

13:33:11.603205 IP 84.xxx.xxx.xxx.5060 > 213.55.176.206.3357: Flags [P.], seq 3761:4458, ack 5228, win 1452, options [nop,nop,TS val 5690888 ecr 15666463], length 697

13:33:11.645161 IP 213.55.176.206.3357 > 84.xxx.xxx.xxx.5060: Flags [.], ack 4458, win 16931, options [nop,nop,TS val 15668435 ecr 5690888], length 0

13:33:11.792554 IP 213.55.176.206.3357 > 84.xxx.xxx.xxx.5060: Flags [P.], seq 5228:5649, ack 4458, win 16931, options [nop,nop,TS val 15668448 ecr 5690888], length 421

13:33:11.792566 IP 84.xxx.xxx.xxx.5060 > 213.55.176.206.3357: Flags [.], ack 5649, win 1452, options [nop,nop,TS val 5690936 ecr 15668448], length 0

13:33:11.845101 IP 213.55.176.206.3357 > 84.xxx.xxx.xxx.5060: Flags [P.], seq 5649:5653, ack 4458, win 16931, options [nop,nop,TS val 15668454 ecr 5690936], length 4

13:33:11.845121 IP 84.xxx.xxx.xxx.5060 > 213.55.176.206.3357: Flags [.], ack 5653, win 1452, options [nop,nop,TS val 5690949 ecr 15668454], length 0

13:33:11.845151 IP 84.xxx.xxx.xxx.5060 > 213.55.176.206.3357: Flags [P.], seq 4458:4460, ack 5653, win 1452, options [nop,nop,TS val 5690949 ecr 15668454], length 2

13:33:11.900125 IP 213.55.176.206.3357 > 84.xxx.xxx.xxx.5060: Flags [.], ack 4460, win 16931, options [nop,nop,TS val 15668459 ecr 5690949], length 0

Thank you for helping

Regards,

Jeph

 

 

 

_____

Prisnets SA.

Office:   +41 22 501 70 70 / Fax : +41 22 501 70 67

Direct line : +41 22 508 72 70

Mobile:  +41 78 728 92 97

Email:      <mailto:j.feugne at prisnets.ch> j.feugne at prisnets.ch

Skype:   jephtech - Twitter:  @prisnet_ch

 <http://www.prisnets.ch/> http://www.prisnets.ch
Prisnet Telecommunications SA.  Route de Saint-Julien 184 A, 1228 Plan-Les-Ouates CH.

 

De : Marco Teixeira [mailto:admin at marcoteixeira.com] 
Envoy? : samedi, 2 janvier 2016 16:55
? : j.feugne at prisnets.ch
Cc : spce-user at lists.sipwise.com
Objet : Re: [Spce-user] No sound with outbound call

 

Hi,

 

On a security side note, don't forget to replace your, and your peer's, real IP address before posting on public mailling lists.

 

About your issue, Can you tell that INVITE packet size ?

Try to grep it out of a tcpdump:

"tcpdump port 5060 -nnn | grep YOUR_PEER_IP_HERE"

 

?(apt-get install tcpdump, if you need)?




 

---

Marco

---

 

 

On Sat, Jan 2, 2016 at 7:56 AM, <j.feugne at prisnets.ch <mailto:j.feugne at prisnets.ch> > wrote:

hello,
I'm just starting with Sipwise and I've setup a VM running version mr4.1.1 CE.
I have followed the instructions of the manual and all subscribers can call each others.
I also setup a sip peer to voicetrading, and here is waht I have withthe command line ngrep sip on my vm while placing and outband call:
NB, voicetrading is expecting for premium rate all number to be leading with 00000 (5 zero)

U  <http://84.253.60.150:5060> 84.253.60.150:5060 ->  <http://77.72.169.129:5060> 77.72.169.129:5060
  INVITE  <sip:0000041227312221 at 77.72.169.129:5060;transport=udp> sip:0000041227312221 at 77.72.169.129:5060;transport=udp SIP/2.0..Record-Route: < <sip:84.253.60.150;r2=on;%0b %20lr=on;ftag=2AF8D981-568781960002DB55-51003700;ngcplb=yes> sip:84.253.60.150;r2=on;
  lr=on;ftag=2AF8D981-568781960002DB55-51003700;ngcplb=yes>..Record-Route: < <sip:127.0.0.1;r2=on;lr=on;ftag=2AF8%0b %20D981-568781960002DB55-51003700;ngcplb=yes> sip:127.0.0.1;r2=on;lr=on;ftag=2AF8
  D981-568781960002DB55-51003700;ngcplb=yes>..Via: SIP/2.0/UDP 84.253.60.150;branch=z9hG4bK603f.7793d5b01aaccef
  36467f073399c00c2.0..Via: SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;branch=z9hG4bKVg2PkaeG;rport=5080..Fr
  om: < <mailto:sip%3A41225017070 at prisnets.adoovoice.com> sip:41225017070 at prisnets.adoovoice.com>;tag=2AF8D981-568781960002DB55-51003700..To: <sip:000004122731222
   <mailto:1 at 77.72.169.129> 1 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: scRGTP71RF5cdeju0O0qmw.._b2b-1..Max-Forwards: 69..Allow: INVITE,
  ACK, CANCEL, BYE, NOTIFY, MESSAGE, OPTIONS, SUBSCRIBE..Supported: replaces, norefersub, extended-refer, outbo
  und, path, X-cisco-serviceuri..P-Asserted-Identity: < <mailto:sip%3A41225017070 at prisnets.adoovoice.com> sip:41225017070 at prisnets.adoovoice.com>..Authorization:
  Digest username="", realm=" <http://prisnets.adoovoice.com> prisnets.adoovoice.com", nonce="4087963395", uri=" <mailto:sip%3A0000041227312221 at 77.72.169.1> sip:0000041227312221 at 77.72.169.1
  29:5060;transport=udp", response="c2fb4cd3a1235efd35e99190aedc45c2", algorithm=MD5..Content-Type: application
  /sdp..Content-Length: 322..Contact: < <mailto:sip%3Angcp-lb at 84.253.60.150> sip:ngcp-lb at 84.253.60.150:5060;ngcpct=7369703a3132372e302e302e313a353038
  30>....v=0..o=Zoiper 0 0 IN IP4 84.253.60.150..s=Zoiper..c=IN IP4 84.253.60.150..t=0 0..m=audio 32468 RTP/AVP
   3 0 8 18 101..a=rtpmap:3 GSM/8000..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:18 G729/8000..a=fmtp
  :18 annexb=no..a=rtpmap:101 telephone-event/8000..a=fmtp:101 0-16..a=sendrecv..a=rtcp:32469..a=direction:both
  ..


After almost 1 minute with no ringing sound nor answer the call hang up.

Can someone please help me point out where the problem is comming and how I can solve it?

Thank you

Jephth? Feugn?
_______________________________________________
Spce-user mailing list
Spce-user at lists.sipwise.com <mailto:Spce-user at lists.sipwise.com> 
https://lists.sipwise.com/listinfo/spce-user

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20160201/fd176adc/attachment-0001.html>

From alexander at schrego.com  Mon Feb  1 08:46:47 2016
From: alexander at schrego.com (Alexander Topolanek)
Date: Mon, 1 Feb 2016 14:46:47 +0100
Subject: [Spce-user] upgrading to 4.2.1 fails on nonexistent old packages
Message-ID: <56AF61C7.7010307@schrego.com>

The uprade process fails when it tries to purge a nonexistant package:

2016-02-01 14:30:11: [23/36] Step '2.8/handle_apt_install_ngcp' has been 
executed already, continuing with the next step...
2016-02-01 14:30:11: [24/36] Running: 
/usr/share/ngcp-upgrade/steps/mr4.2/fix_purge_old_packages
Reading package lists... 0%
... Done^M
^MBuilding dependency tree...
... Done^M
E: Unable to locate package linux-headers-2.6-amd64
E: Couldn't find any package by regex 'linux-headers-2.6-amd64'
ERROR: the step 'mr4.2/fix_purge_old_packages' failed, upgrade aborted!
Please fix the root of the issue and restart 'ngcp-upgrade'

I*ve manually purged what can be purged and then commented out some 
lines in /usr/share/ngcp-upgrade/steps/mr4.2/fix_purge_old_packages.
After that the upgrade completed

kind regards

-- 
Alexander Topolanek
System engineer



From alutay at sipwise.com  Mon Feb  1 09:54:45 2016
From: alutay at sipwise.com (Alex Lutay)
Date: Mon, 1 Feb 2016 15:54:45 +0100
Subject: [Spce-user] upgrading to 4.2.1 fails on nonexistent old packages
In-Reply-To: <56AF61C7.7010307@schrego.com>
References: <56AF61C7.7010307@schrego.com>
Message-ID: <56AF71B5.7080702@sipwise.com>

Dear Alexander,

Thank you for the report here, internal ticket is MT#17665
should be fixed and hotfixed in mr4.2.1 shortly.

On 02/01/2016 02:46 PM, Alexander Topolanek wrote:
> The uprade process fails when it tries to purge a nonexistant package:
> 
> 2016-02-01 14:30:11: [23/36] Step '2.8/handle_apt_install_ngcp' has been
> executed already, continuing with the next step...
> 2016-02-01 14:30:11: [24/36] Running:
> /usr/share/ngcp-upgrade/steps/mr4.2/fix_purge_old_packages
> Reading package lists... 0%
> ... Done^M
> ^MBuilding dependency tree...
> ... Done^M
> E: Unable to locate package linux-headers-2.6-amd64
> E: Couldn't find any package by regex 'linux-headers-2.6-amd64'
> ERROR: the step 'mr4.2/fix_purge_old_packages' failed, upgrade aborted!
> Please fix the root of the issue and restart 'ngcp-upgrade'
> 
> I*ve manually purged what can be purged and then commented out some
> lines in /usr/share/ngcp-upgrade/steps/mr4.2/fix_purge_old_packages.
> After that the upgrade completed

-- 
Alex Lutay


From agranig at sipwise.com  Mon Feb  1 11:33:03 2016
From: agranig at sipwise.com (Andreas Granig)
Date: Mon, 1 Feb 2016 17:33:03 +0100
Subject: [Spce-user] Rings once, then disconnects!
In-Reply-To: <DB5PR06MB15571F52E939DC8818644634BEDE0@DB5PR06MB1557.eurprd06.prod.outlook.com>
References: <DB5PR06MB1557AB8F343FE2DD1C4AC44FBEDE0@DB5PR06MB1557.eurprd06.prod.outlook.com>
 <56AF3323.3090101@sipwise.com>
 <DB5PR06MB15571F52E939DC8818644634BEDE0@DB5PR06MB1557.eurprd06.prod.outlook.com>
Message-ID: <56AF88BF.1020002@sipwise.com>

Hi William,

Maybe your peering partner doesn't like the SDP body (specifically the
list of codecs) or something.

Try to limit the list of codecs on your 3CX to G711 as a start. Maybe
also the SIP message (the 500 from your carrier) contains a header
providing more details. From a SIP signaling perspective, there is a
B2BUA in the SPCE, so the outbound message should be *somewhat* equal
all the time no matter what client you're using, but then again the SDP
is passed through more or less as-is, which could be a starting point
for trouble-shooting.

Anyways, your carrier should be able to explain the reason why they're
sending a 500 reply.

Andreas

On 02/01/2016 12:37 PM, William Hilsum wrote:
> Hi,
> 
> I've been working on this overnight and made a bit more progress... and, it is a weird one!
> 
> I saw the Sipwise Ios App and I thought I would give it a go...
> 
> I made calls fine without issue!
> 
> It looks like the issue is then related to the softphone (I was using 3CX) doing something dodgy and/or Sipwise not removing/changing the headers.
> 
> I'm really unsure how to proceed here, but, I am guessing I just have a lot of trial and error ahead of me.
> 
> William
> 
> -----Original Message-----
> From: Spce-user [mailto:spce-user-bounces at lists.sipwise.com] On Behalf Of Alex Lutay
> Sent: 01 February 2016 10:28
> To: spce-user at lists.sipwise.com
> Subject: Re: [Spce-user] Rings once, then disconnects!
> 
> Dear William,
> 
> As I can see on picture SPCE received "500 - Server Internal Error"
> from your Carrier, so there is nothing we can tell you here.
> 
> Please ask your Carrier about the reason of internal server error here.
> 
> On 02/01/2016 03:08 AM, William Hilsum wrote:
> [...skipped...]
>> I've tried to do diagnostics - I selected both legs of the call and 
>> made a quick picture: http://i.imgur.com/PzJF0Y5.jpg
> [...skipped...]
>> Feb  1 02:55:45 masterpbx1 (local7.notice) proxy[3350]: NOTICE:
>> <script>: NAT-Reply - S=500 - Server Internal Error M=INVITE
>> IP=**MY-HOME-IP**:56805 (127.0.0.1:5080) 
>> ID=ZTdlYmYwY2I2MmExZThkYmY1MTIxZGJmOGQyOWQ4ZmM. UA='<null>'
> [...skipped...]
> 
> --
> Alex Lutay
> 
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
> 


From alutay at sipwise.com  Mon Feb  1 11:52:21 2016
From: alutay at sipwise.com (Alex Lutay)
Date: Mon, 1 Feb 2016 17:52:21 +0100
Subject: [Spce-user] upgrading to 4.2.1 fails on nonexistent old packages
In-Reply-To: <56AF71B5.7080702@sipwise.com>
References: <56AF61C7.7010307@schrego.com> <56AF71B5.7080702@sipwise.com>
Message-ID: <56AF8D45.6080307@sipwise.com>

Fixed.

The step "/usr/share/ngcp-upgrade/steps/mr4.2/fix_purge_old_packages"
should care about the list of installed packages before purging
unnecessary. Released hotfix for mr4.2.1 already.

On 02/01/2016 03:54 PM, Alex Lutay wrote:
> Thank you for the report here, internal ticket is MT#17665
> should be fixed and hotfixed in mr4.2.1 shortly.
> 
> On 02/01/2016 02:46 PM, Alexander Topolanek wrote:
>> The uprade process fails when it tries to purge a nonexistant package:
>>
>> 2016-02-01 14:30:11: [23/36] Step '2.8/handle_apt_install_ngcp' has been
>> executed already, continuing with the next step...
>> 2016-02-01 14:30:11: [24/36] Running:
>> /usr/share/ngcp-upgrade/steps/mr4.2/fix_purge_old_packages
>> Reading package lists... 0%
>> ... Done^M
>> ^MBuilding dependency tree...
>> ... Done^M
>> E: Unable to locate package linux-headers-2.6-amd64
>> E: Couldn't find any package by regex 'linux-headers-2.6-amd64'
>> ERROR: the step 'mr4.2/fix_purge_old_packages' failed, upgrade aborted!
>> Please fix the root of the issue and restart 'ngcp-upgrade'
>>
>> I*ve manually purged what can be purged and then commented out some
>> lines in /usr/share/ngcp-upgrade/steps/mr4.2/fix_purge_old_packages.
>> After that the upgrade completed

-- 
Alex Lutay


From William at ezpcltd.com  Mon Feb  1 19:03:15 2016
From: William at ezpcltd.com (William Hilsum)
Date: Tue, 2 Feb 2016 00:03:15 +0000
Subject: [Spce-user] Rings once, then disconnects!
In-Reply-To: <56AF88BF.1020002@sipwise.com>
References: <DB5PR06MB1557AB8F343FE2DD1C4AC44FBEDE0@DB5PR06MB1557.eurprd06.prod.outlook.com>
 <56AF3323.3090101@sipwise.com>
 <DB5PR06MB15571F52E939DC8818644634BEDE0@DB5PR06MB1557.eurprd06.prod.outlook.com>
 <56AF88BF.1020002@sipwise.com>
Message-ID: <DB5PR06MB15573307ABE294694E402401BEDF0@DB5PR06MB1557.eurprd06.prod.outlook.com>

Hi

This is now solved... The moment I unticked "allow video" on the softphone, it worked as expected. 

These additional lines in the "invite (SDP) packet" from Sipwise to the carrier platform break the connection:

m=video 32562 RTP/AVP 34
c=IN IP4 <PBX-IP>
a=rtpmap:34 H263/90000
a=fmtp:34 QCIF=1;CIF=1;SQCIF=1;CIF4=1
a=sendrecv
a=rtcp:32563
a=direction:both

so...

1. Is there anyway to disable voice/these headers being sent on a per carrier basis? 
2. Is this a case of the carrier not following spec? (should it be ignored if they don't support video?)
3. is it just a broken softphone? (if it is, this is the first problem I've had with it)
 Or something else?!

I still don't get how one single ring goes out! I can't say I am an expert at all on this, but, this is certainly a new one for me!

Thanks for your help Andreas and Alex.

William

-----Original Message-----
From: Spce-user [mailto:spce-user-bounces at lists.sipwise.com] On Behalf Of Andreas Granig
Sent: 01 February 2016 16:33
To: spce-user at lists.sipwise.com
Subject: Re: [Spce-user] Rings once, then disconnects!

Hi William,

Maybe your peering partner doesn't like the SDP body (specifically the list of codecs) or something.

Try to limit the list of codecs on your 3CX to G711 as a start. Maybe also the SIP message (the 500 from your carrier) contains a header providing more details. From a SIP signaling perspective, there is a B2BUA in the SPCE, so the outbound message should be *somewhat* equal all the time no matter what client you're using, but then again the SDP is passed through more or less as-is, which could be a starting point for trouble-shooting.

Anyways, your carrier should be able to explain the reason why they're sending a 500 reply.

Andreas

On 02/01/2016 12:37 PM, William Hilsum wrote:
> Hi,
> 
> I've been working on this overnight and made a bit more progress... and, it is a weird one!
> 
> I saw the Sipwise Ios App and I thought I would give it a go...
> 
> I made calls fine without issue!
> 
> It looks like the issue is then related to the softphone (I was using 3CX) doing something dodgy and/or Sipwise not removing/changing the headers.
> 
> I'm really unsure how to proceed here, but, I am guessing I just have a lot of trial and error ahead of me.
> 
> William
> 
> -----Original Message-----
> From: Spce-user [mailto:spce-user-bounces at lists.sipwise.com] On Behalf 
> Of Alex Lutay
> Sent: 01 February 2016 10:28
> To: spce-user at lists.sipwise.com
> Subject: Re: [Spce-user] Rings once, then disconnects!
> 
> Dear William,
> 
> As I can see on picture SPCE received "500 - Server Internal Error"
> from your Carrier, so there is nothing we can tell you here.
> 
> Please ask your Carrier about the reason of internal server error here.
> 
> On 02/01/2016 03:08 AM, William Hilsum wrote:
> [...skipped...]
>> I've tried to do diagnostics - I selected both legs of the call and 
>> made a quick picture: http://i.imgur.com/PzJF0Y5.jpg
> [...skipped...]
>> Feb  1 02:55:45 masterpbx1 (local7.notice) proxy[3350]: NOTICE:
>> <script>: NAT-Reply - S=500 - Server Internal Error M=INVITE
>> IP=**MY-HOME-IP**:56805 (127.0.0.1:5080) 
>> ID=ZTdlYmYwY2I2MmExZThkYmY1MTIxZGJmOGQyOWQ4ZmM. UA='<null>'
> [...skipped...]
> 
> --
> Alex Lutay
> 
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
> 
_______________________________________________
Spce-user mailing list
Spce-user at lists.sipwise.com
https://lists.sipwise.com/listinfo/spce-user


From alutay at sipwise.com  Tue Feb  2 03:24:19 2016
From: alutay at sipwise.com (Alex Lutay)
Date: Tue, 2 Feb 2016 09:24:19 +0100
Subject: [Spce-user] Rings once, then disconnects!
In-Reply-To: <DB5PR06MB15573307ABE294694E402401BEDF0@DB5PR06MB1557.eurprd06.prod.outlook.com>
References: <DB5PR06MB1557AB8F343FE2DD1C4AC44FBEDE0@DB5PR06MB1557.eurprd06.prod.outlook.com>
 <56AF3323.3090101@sipwise.com>
 <DB5PR06MB15571F52E939DC8818644634BEDE0@DB5PR06MB1557.eurprd06.prod.outlook.com>
 <56AF88BF.1020002@sipwise.com>
 <DB5PR06MB15573307ABE294694E402401BEDF0@DB5PR06MB1557.eurprd06.prod.outlook.com>
Message-ID: <56B067B3.4030606@sipwise.com>

Dear William,

Check incoming invite from softphone to Sipwise,
I am strongly believe you will find the same part there.

Sipwise doesn't change SDP part a lot, mainly it is replacing IP
(I believe you have replaced '<PBX-IP>' in SDP part manually, otherwise
it is an error) and limit list of codecs if necessary (turned off by
default).

You can also try to make a call from your softphone through your
Carrier directly and compare invite sent by softphone and Sipwise.

On the first look I do not see anything which can cause 500 on carrier
side here. Was the correct IPv4/IPv6 in <PBX-IP> ?

On 02/02/2016 01:03 AM, William Hilsum wrote:
> These additional lines in the "invite (SDP) packet" from Sipwise to the carrier platform break the connection:
> 
> m=video 32562 RTP/AVP 34
> c=IN IP4 <PBX-IP>
> a=rtpmap:34 H263/90000
> a=fmtp:34 QCIF=1;CIF=1;SQCIF=1;CIF4=1
> a=sendrecv
> a=rtcp:32563
> a=direction:both

-- 
Alexander Lutay
Head of Quality Assurance
Sipwise GmbH, Campus 21/Europaring F15
AT-2345 Brunn am Gebirge

Office: +43(0)13012036
Email: alutay at sipwise.com
Website: http://www.sipwise.com


From js at dacor.de  Tue Feb  2 07:52:17 2016
From: js at dacor.de (Julian Seifert)
Date: Tue, 2 Feb 2016 12:52:17 +0000
Subject: [Spce-user] trunk configuration
Message-ID: <07F41140D7F60847B76E3730B2ADCA6995F35C30@exchange.suecdacor.local>

Hi,

I'm currently working on building a sample configuration for a sip trunk
on which we can base our future trunk-setups.

I'm not 100% sure if I approach it correctly so please be gentle and what I actually want to know
is "how do you configure a sip trunk for a customer on sipwise the proper way?"

The pbx in our case is for example askozia which essentially is a asterisk
based solution afaik.
The askozia trunk configuration is quite straight forward and works with a variety of sip providers.

As we are now entering the business ourselves we'd like to configure our sipwise appropriately
to provide trunks.
We want to allow the trunkuser to dialout with DDIs (so "CLIP no screening")
In this example we want to provide the customer with a block of 100 numbers where 
there is a "centralnumber", commonly its the -0. 

I'm basing this example on the following number: 499561404956
We would like to be able to use 499561404956-0 to -99 as DDIs.

Currently I'm using a subscriber setup with the following specific settings.

- Primary number: 499561404956
- No Aliases
- extended dialing mode, send dialed number with extension (so calls using a DDI will reach the pbx)
- extension_in_npn (to set the ddi in outgoing calls as npn - if I understand the option properly)
- allowed_clis to "*" (or to 499561404956* to restrict the allowed CLIs to basenumber and DDIs?)
- e164_to_uri (unsure about this)
- would it be necessary to add all DDIs as aliases? (which is something we would like to avoid)

so - is this approach completely wrong? 
Is the regular approach to implement a trunk different?
Is there a "best practice" approach? 

Please share your knowledge/opinion/wisdom and if I used some terms in the wrong way please forgive my ignorance.

kind regards,

  Julian

From kim.philby at gmx.com  Tue Feb  2 15:44:09 2016
From: kim.philby at gmx.com (Kim Philby)
Date: Tue, 2 Feb 2016 21:44:09 +0100
Subject: [Spce-user] Manual delete of subscribers
Message-ID: <trinity-94d7bd6b-7ba1-4bb9-a692-aa20dc6dd8a2-1454445849737@3capp-mailcom-bs13>

An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20160202/572f5be3/attachment-0001.html>

From me at nevian.org  Thu Feb  4 10:50:50 2016
From: me at nevian.org (Serge S. Yuriev)
Date: Thu, 4 Feb 2016 18:50:50 +0300
Subject: [Spce-user] Number cleanup
In-Reply-To: <9428FDFA-A738-42C3-AC1F-83092E021A9C@nevian.org>
References: <9428FDFA-A738-42C3-AC1F-83092E021A9C@nevian.org>
Message-ID: <56B3735A.3030201@nevian.org>

Hi,

Anyone?

On 21/01/16 13:39, Serge Yuriev wrote:
> Hello,
>
> I try to construct rewrite rule to remove any non-digits numbers from destination.
> In sed this is simple as /[^0-9]//g
> But I have no idea how to do it here :(

-- 
Serge S. Yuriev
Lead VoIP engineer



From j_e_vargas at live.com  Thu Feb  4 13:38:25 2016
From: j_e_vargas at live.com (Jose E. Vargas B.)
Date: Thu, 4 Feb 2016 10:38:25 -0800
Subject: [Spce-user] bruteforcing sip credentials attack
In-Reply-To: <07F41140D7F60847B76E3730B2ADCA6995F35C30@exchange.suecdacor.local>
References: <07F41140D7F60847B76E3730B2ADCA6995F35C30@exchange.suecdacor.local>
Message-ID: <BLU436-SMTP260D4059BD5534FFF946A8EBCD10@phx.gbl>

Hello,

Just have a quick and probably easy question for the SP community. I am experimenting with the server and keep getting the entire day the following attack:

016/02/04 19:20:16.673827 188.138.33.14:5071 -> yy.yy.yy.yy:5060
INVITE sip:901141445209482 at xx.xx.xx.xx SIP/2.0
To: 901141445209482<sip:901141445209482 at xx.xx.xx.xx>
From: 0550<sip:0550 at xx.xx.xx.xx>;tag=67a87716
Via: SIP/2.0/UDP 188.138.33.14:5071;branch=z9hG4bK-6f67d7e24b4ac8a25f3d76106be4cb74;rport
Call-ID: 6f67d7e24b4ac8a25f3d76106be4cb74
CSeq: 1 INVITE
Contact: <sip:0550 at 188.138.33.14:5071>
Max-Forwards: 70
Allow: INVITE, ACK, CANCEL, BYE
User-Agent: sipcli/v1.8
Content-Type: application/sdp
Content-Length: 281

v=0
o=sipcli-Session 691746334 738426574 IN IP4 188.138.33.14
s=sipcli
c=IN IP4 188.138.33.14
t=0 0
m=audio 5073 RTP/AVP 18 0 8 101
a=fmtp:101 0-15
a=rtpmap:18 G729/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=ptime:20
a=sendrecv


I guess it is a funny group/folk trying to get unauthorized access to the server by sending multiple SIP invites with different accounts and possible free phone calls ;)  The problem is that SPCE won?t detect it as his attempts are spared in time.  Would like to get your guidance about blocking the entire IP or domain to SCPCE server. Could you please comment on how you deal with this type of attack?

Jose 

PS: 
    BTW - making changes to config.yml (failed _auth)?) didn?t help  
    Offending IP:  188.138.33.14


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20160204/7587fc9a/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 1776 bytes
Desc: not available
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20160204/7587fc9a/attachment-0001.p7s>

From rabs at dimension-virtual.com  Thu Feb  4 13:52:20 2016
From: rabs at dimension-virtual.com (=?utf-8?B?UmHDumw=?= Alexis Betancor Santana)
Date: Thu, 4 Feb 2016 19:52:20 +0100 (CET)
Subject: [Spce-user] bruteforcing sip credentials attack
In-Reply-To: <BLU436-SMTP260D4059BD5534FFF946A8EBCD10@phx.gbl>
References: <07F41140D7F60847B76E3730B2ADCA6995F35C30@exchange.suecdacor.local>
 <BLU436-SMTP260D4059BD5534FFF946A8EBCD10@phx.gbl>
Message-ID: <1047616280.316778.1454611940266.JavaMail.zimbra@dimension-virtual.com>

Easy ... 

291a292,298 
> ## filtering by UA : blacklist 
> if(is_method("REGISTER|INVITE|OPTIONS") && ($ua =~ "friendly-scanner" || $ua =~ "sipvicious" || $ua =~ "^sipcli.+")) 
> { 
> xlog("L_WARN", "Request rejected, malicious UA='$ua' from IP=$si - [% logreq_init -%]\n"); 
> exit; 
> } 
> 

Patch applied over the lb/kamailio.cfg.tt2 ... so create a .cusomtt.tt2 

> De: "Jose E. Vargas B." <j_e_vargas at live.com>
> Para: spce-user at lists.sipwise.com
> Enviados: Jueves, 4 de Febrero 2016 18:38:25
> Asunto: [Spce-user] bruteforcing sip credentials attack

> Hello,

> Just have a quick and probably easy question for the SP community. I am
> experimenting with the server and keep getting the entire day the following
> attack:

> 016/02/04 19:20:16.673827 188.138.33.14:5071 -> yy.yy.yy.yy:5060
> INVITE sip:901141445209482 at xx.xx.xx.xx SIP/2.0
> To: 901141445209482< sip:901141445209482 at xx.xx.xx.xx >
> From: 0550< sip:0550 at xx.xx.xx.xx >;tag=67a87716
> Via: SIP/2.0/UDP
> 188.138.33.14:5071;branch=z9hG4bK-6f67d7e24b4ac8a25f3d76106be4cb74;rport
> Call-ID: 6f67d7e24b4ac8a25f3d76106be4cb74
> CSeq: 1 INVITE
> Contact: < sip:0550 at 188.138.33.14:5071 >
> Max-Forwards: 70
> Allow: INVITE, ACK, CANCEL, BYE
> User-Agent: sipcli/v1.8
> Content-Type: application/sdp
> Content-Length: 281

> v=0
> o=sipcli-Session 691746334 738426574 IN IP4 188.138.33.14
> s=sipcli
> c=IN IP4 188.138.33.14
> t=0 0
> m=audio 5073 RTP/AVP 18 0 8 101
> a=fmtp:101 0-15
> a=rtpmap:18 G729/8000
> a=rtpmap:0 PCMU/8000
> a=rtpmap:8 PCMA/8000
> a=rtpmap:101 telephone-event/8000
> a=ptime:20
> a=sendrecv

> I guess it is a funny group/folk trying to get unauthorized access to the server
> by sending multiple SIP invites with different accounts and possible free phone
> calls ;) The problem is that SPCE won?t detect it as his attempts are spared in
> time. Would like to get your guidance about blocking the entire IP or domain to
> SCPCE server. Could you please comment on how you deal with this type of
> attack?

> Jose

> PS:
> BTW - making changes to config.yml (failed _auth)?) didn?t help
> Offending IP: 188.138.33.14

> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20160204/cdb504d7/attachment-0001.html>

From dgrotti at sipwise.com  Thu Feb  4 14:03:52 2016
From: dgrotti at sipwise.com (Daniel Grotti)
Date: Thu, 04 Feb 2016 20:03:52 +0100
Subject: [Spce-user] bruteforcing sip credentials attack
In-Reply-To: <BLU436-SMTP260D4059BD5534FFF946A8EBCD10@phx.gbl>
Message-ID: <46812e2e-1a1d-4c80-847e-d34d4f4d544e@email.android.com>

Hi,
Hope it will help and maybe give you some hints:

https://www.linkedin.com/pulse/securing-your-ngcp-against-sip-attacks-daniel-grotti?forceNoSplash=true


Daniel


On Feb 4, 2016 7:38 PM, "Jose E. Vargas B." <j_e_vargas at live.com> wrote:
>
> Hello,
>
> Just have a quick and probably easy question for the SP community. I am experimenting with the server and keep getting the entire day the following attack:
>
> 016/02/04 19:20:16.673827 188.138.33.14:5071 -> yy.yy.yy.yy:5060
> INVITE sip:901141445209482 at xx.xx.xx.xx SIP/2.0
> To: 901141445209482<sip:901141445209482 at xx.xx.xx.xx>
> From: 0550<sip:0550 at xx.xx.xx.xx>;tag=67a87716
> Via: SIP/2.0/UDP 188.138.33.14:5071;branch=z9hG4bK-6f67d7e24b4ac8a25f3d76106be4cb74;rport
> Call-ID: 6f67d7e24b4ac8a25f3d76106be4cb74
> CSeq: 1 INVITE
> Contact: <sip:0550 at 188.138.33.14:5071>
> Max-Forwards: 70
> Allow: INVITE, ACK, CANCEL, BYE
> User-Agent: sipcli/v1.8
> Content-Type: application/sdp
> Content-Length: 281
>
> v=0
> o=sipcli-Session 691746334 738426574 IN IP4 188.138.33.14
> s=sipcli
> c=IN IP4 188.138.33.14
> t=0 0
> m=audio 5073 RTP/AVP 18 0 8 101
> a=fmtp:101 0-15
> a=rtpmap:18 G729/8000
> a=rtpmap:0 PCMU/8000
> a=rtpmap:8 PCMA/8000
> a=rtpmap:101 telephone-event/8000
> a=ptime:20
> a=sendrecv
>
>
> I guess it is a funny group/folk trying to get unauthorized access to the server by sending multiple SIP invites with different accounts and possible free phone calls ;) ?The problem is that SPCE won?t detect it as his attempts are spared in time. ?Would like to get your guidance about blocking the entire IP or domain to SCPCE server. Could you please comment on how you deal with this type of attack?
>
> Jose?
>
> PS:?
> ? ? BTW - making changes to config.yml (failed _auth)?) didn?t help ?
> ? ? Offending IP: ?188.138.33.14
>
>

From mstorck at voipgate.com  Thu Feb  4 18:51:09 2016
From: mstorck at voipgate.com (Marc Storck)
Date: Thu, 4 Feb 2016 23:51:09 +0000
Subject: [Spce-user] MCID App issue
In-Reply-To: <9F7472F0-1DCE-41BD-BBFB-B3726276D01E@voipgate.com>
References: <464D53E5-C98C-4B05-9D53-63A3224442CF@voipgate.com>
 <1EA4E174-98A5-4DDF-A346-1191DDACD7E8@sipwise.com>,
 <9F7472F0-1DCE-41BD-BBFB-B3726276D01E@voipgate.com>
Message-ID: <42E0F0207938744EB3DA31C28FC221CF0136A41BA1@LCEXMBX02.cmsad.local>

I just upgraded to mr4.2.1.

I followed the steps described in the documentation. My system was almost good, I was only missing the audio file in the sound set.

However the problem persists:

Feb  5 00:42:38 cusax (local7.notice) proxy[3552]: NOTICE: <script>: New request on proxy - M=INVITE R=sip:*57 at sld.tld;user=phone F=sip:johndoe at sld.tld T=sip:*57 at sld.tld;user=phone IP=11.22.33.44:5732 (127.0.0.1:5060) ID=2639378387 at 11_22_33_44 UA='N510 IP PRO/42.210.00.000.000'
Feb  5 00:42:38 cusax (local7.notice) proxy[3552]: NOTICE: <script>: User-Provided CLI 'johndoe' taken from From-User - R=sip:*57 at sld.tld;user=phone ID=2639378387 at 11_22_33_44 UA='N510 IP PRO/42.210.00.000.000'
Feb  5 00:42:38 cusax (local7.notice) proxy[3552]: NOTICE: <script>: User-provided CLI 'johndoe' rejected, using network-provided CLI '898910001201001' - R=sip:*57 at sld.tld;user=phone ID=2639378387 at 11_22_33_44 UA='N510 IP PRO/42.210.00.000.000'
Feb  5 00:42:38 cusax (local7.notice) proxy[3552]: NOTICE: <script>: Setting '898910001201001 at sld.tld' as initiating user-provided CLI - R=sip:*57 at sld.tld;user=phone ID=2639378387 at 11_22_33_44 UA='N510 IP PRO/42.210.00.000.000'
Feb  5 00:42:38 cusax (local7.notice) proxy[3552]: NOTICE: <script>: Setting '898910001201001 at sld.tld' as initiating network-provided CLI - R=sip:*57 at sld.tld;user=phone ID=2639378387 at 11_22_33_44 UA='N510 IP PRO/42.210.00.000.000'
Feb  5 00:42:38 cusax (local7.notice) proxy[3552]: NOTICE: <script>: Rewriting called party '*57' to 'malicious_call' - R=sip:*57 at sld.tld;user=phone ID=2639378387 at 11_22_33_44 UA='N510 IP PRO/42.210.00.000.000'
Feb  5 00:42:38 cusax (local7.err) proxy[3552]: ERROR: app_lua [app_lua_api.c:680]: app_lua_run(): error executing: del_dlg_profile (err: 2)
Feb  5 00:42:38 cusax (local7.err) proxy[3552]: ERROR: app_lua [app_lua_api.c:682]: app_lua_run(): error from Lua: /etc/kamailio/proxy/dlgcnt.lua:101: can't restore callid from $dlg_var(lua_dlg_callid): is null
Feb  5 00:42:38 cusax (local7.err) proxy[3552]: ERROR: <script>: Failed to decrease redis counters - R=sip:you at kamailio.org ID=123 UA='<null>'
Feb  5 00:42:38 cusax (local7.notice) proxy[3552]: NOTICE: <script>: New request on proxy - M=ACK R=sip:*57 at sld.tld;user=phone F=sip:johndoe at sld.tld T=sip:*57 at sld.tld;user=phone IP=11.22.33.44:5732 (127.0.0.1:5060) ID=2639378387 at 11_22_33_44 UA='N510 IP PRO/42.210.00.000.000'

Does anybody have an idea what might be the missing part?

Regards,

Marc

________________________________________
From: Marc Storck
Sent: Friday, October 30, 2015 17:49
To: Kirill Solomko
Cc: spce-user at lists.sipwise.com
Subject: Re: [Spce-user] MCID App issue

So I set

store_recentcalls: ?yes'

followed by running

ngcpcfg apply

but the result is still quite the same:

Oct 30 17:45:08 cusax proxy[514]: NOTICE: <script>: Rewriting called party '*57' to 'malicious_call' - R=sip:*57 at sld.tld ID=OWU3ZmFiMDY5ZGE4ZGJkODE4ODdlMDhjMzg1MWFkYzc UA='Bria iOS release 3.4.4 stamp 31657'
Oct 30 17:45:08 cusax proxy[514]: ERROR: app_lua [app_lua_api.c:680]: app_lua_run(): error executing: del_dlg_profile (err: 2)
Oct 30 17:45:08 cusax proxy[514]: ERROR: app_lua [app_lua_api.c:682]: app_lua_run(): error from Lua: /etc/kamailio/proxy/dlgcnt.lua:101: can't restore callid from $dlg_var(lua_dlg_callid): is null
Oct 30 17:45:08 cusax proxy[514]: ERROR: <script>: Failed to decrease redis counters - R=sip:you at kamailio.org ID=123 UA='<null>'

Regards,

Marc

> On 30 Oct 2015, at 17:42, Kirill Solomko <ksolomko at sipwise.com> wrote:
>
> Hi Mark,
>
> You should also enable ?recent calls? support in config.yml
>
> kamailio:
>  proxy:
>    store_recentcalls: ?yes'
>
>> On 30 Oct 2015, at 17:24, Marc Storck <mstorck at voipgate.com> wrote:
>>
>> Good evening,
>>
>> I?m having this problem with the MCID app:
>>
>> Oct 30 17:21:34 cusax proxy[23526]: NOTICE: <script>: Rewriting called party '*57' to 'malicious_call' - R=sip:*57 at sld.tld ID=YmE5NDYzOWMyMWE2NWY0MjE3YTMwYWRkMDVkMjcwOWI UA='Bria iOS release 3.4.4 stamp 31657'
>> Oct 30 17:21:34 cusax proxy[23526]: ERROR: app_lua [app_lua_api.c:680]: app_lua_run(): error executing: del_dlg_profile (err: 2)
>> Oct 30 17:21:34 cusax proxy[23526]: ERROR: app_lua [app_lua_api.c:682]: app_lua_run(): error from Lua: /etc/kamailio/proxy/dlgcnt.lua:101: can't restore callid from $dlg_var(lua_dlg_callid): is null
>> Oct 30 17:21:34 cusax proxy[23526]: ERROR: <script>: Failed to decrease redis counters - R=sip:you at kamailio.org ID=123 UA='<null>?
>>
>> I activated the MCID app in config.yml, are there any further changes required?
>>
>> Regards,
>>
>> Marc
>> _______________________________________________
>> Spce-user mailing list
>> Spce-user at lists.sipwise.com
>> https://lists.sipwise.com/listinfo/spce-user
>
> Kind regards,
> Kirill



From William at ezpcltd.com  Fri Feb  5 01:40:48 2016
From: William at ezpcltd.com (William Hilsum)
Date: Fri, 5 Feb 2016 06:40:48 +0000
Subject: [Spce-user] Rings once, then disconnects!
In-Reply-To: <56B067B3.4030606@sipwise.com>
References: <DB5PR06MB1557AB8F343FE2DD1C4AC44FBEDE0@DB5PR06MB1557.eurprd06.prod.outlook.com>
 <56AF3323.3090101@sipwise.com>
 <DB5PR06MB15571F52E939DC8818644634BEDE0@DB5PR06MB1557.eurprd06.prod.outlook.com>
 <56AF88BF.1020002@sipwise.com>
 <DB5PR06MB15573307ABE294694E402401BEDF0@DB5PR06MB1557.eurprd06.prod.outlook.com>
 <56B067B3.4030606@sipwise.com>
Message-ID: <DB5PR06MB1557E9176F0A2FCED9233799BED20@DB5PR06MB1557.eurprd06.prod.outlook.com>

Hi Alex,

Apologies - I think I'm unintentionally being confusing!

This is not a problem as such with Sipwise - it is the sip client with the option "Allow video calls" that when turned on, it automatically causes my upstream carrier to reject the call (after a single ring, which is just weird...)

Anyway, I have another PBX here where on a per carrier basis, I have the option "Disable video calls". When this is ticked, it basically strips out all relevant headers such as what caused my calls on Sipwise to fail.

So my question really is, after finding out the issue here, is there anyway I can get Sipwise to strip out these headers to avoid similar issues? I have not tested, but, I am guessing if anyone has a VOIP videophone, they may have the same issue as the softphone wasn't actually trying to establish a video stream, it was just saying it was video compatible in the header.

Thanks,

William

-----Original Message-----
From: Spce-user [mailto:spce-user-bounces at lists.sipwise.com] On Behalf Of Alex Lutay
Sent: 02 February 2016 08:24
To: spce-user at lists.sipwise.com
Subject: Re: [Spce-user] Rings once, then disconnects!

Dear William,

Check incoming invite from softphone to Sipwise, I am strongly believe you will find the same part there.

Sipwise doesn't change SDP part a lot, mainly it is replacing IP (I believe you have replaced '<PBX-IP>' in SDP part manually, otherwise it is an error) and limit list of codecs if necessary (turned off by default).

You can also try to make a call from your softphone through your Carrier directly and compare invite sent by softphone and Sipwise.

On the first look I do not see anything which can cause 500 on carrier side here. Was the correct IPv4/IPv6 in <PBX-IP> ?

On 02/02/2016 01:03 AM, William Hilsum wrote:
> These additional lines in the "invite (SDP) packet" from Sipwise to the carrier platform break the connection:
> 
> m=video 32562 RTP/AVP 34
> c=IN IP4 <PBX-IP>
> a=rtpmap:34 H263/90000
> a=fmtp:34 QCIF=1;CIF=1;SQCIF=1;CIF4=1
> a=sendrecv
> a=rtcp:32563
> a=direction:both

--
Alexander Lutay
Head of Quality Assurance
Sipwise GmbH, Campus 21/Europaring F15
AT-2345 Brunn am Gebirge

Office: +43(0)13012036
Email: alutay at sipwise.com
Website: http://www.sipwise.com
_______________________________________________
Spce-user mailing list
Spce-user at lists.sipwise.com
https://lists.sipwise.com/listinfo/spce-user


From dgrotti at sipwise.com  Fri Feb  5 01:58:59 2016
From: dgrotti at sipwise.com (Daniel Grotti)
Date: Fri, 05 Feb 2016 07:58:59 +0100
Subject: [Spce-user] MCID App issue
In-Reply-To: <42E0F0207938744EB3DA31C28FC221CF0136A41BA1@LCEXMBX02.cmsad.local>
Message-ID: <634d081a-8463-4965-abbb-a282d8f21695@email.android.com>

Hi Marc,
Did you flag the subscriber preferences MCID ? It should be in the Internal section.
You should enable MCID there otherwise it won't work.

Daniel

On Feb 5, 2016 12:51 AM, Marc Storck <mstorck at voipgate.com> wrote:
>
> I just upgraded to mr4.2.1. 
>
> I followed the steps described in the documentation. My system was almost good, I was only missing the audio file in the sound set. 
>
> However the problem persists: 
>
> Feb? 5 00:42:38 cusax (local7.notice) proxy[3552]: NOTICE: <script>: New request on proxy - M=INVITE R=sip:*57 at sld.tld;user=phone F=sip:johndoe at sld.tld T=sip:*57 at sld.tld;user=phone IP=11.22.33.44:5732 (127.0.0.1:5060) ID=2639378387 at 11_22_33_44 UA='N510 IP PRO/42.210.00.000.000' 
> Feb? 5 00:42:38 cusax (local7.notice) proxy[3552]: NOTICE: <script>: User-Provided CLI 'johndoe' taken from From-User - R=sip:*57 at sld.tld;user=phone ID=2639378387 at 11_22_33_44 UA='N510 IP PRO/42.210.00.000.000' 
> Feb? 5 00:42:38 cusax (local7.notice) proxy[3552]: NOTICE: <script>: User-provided CLI 'johndoe' rejected, using network-provided CLI '898910001201001' - R=sip:*57 at sld.tld;user=phone ID=2639378387 at 11_22_33_44 UA='N510 IP PRO/42.210.00.000.000' 
> Feb? 5 00:42:38 cusax (local7.notice) proxy[3552]: NOTICE: <script>: Setting '898910001201001 at sld.tld' as initiating user-provided CLI - R=sip:*57 at sld.tld;user=phone ID=2639378387 at 11_22_33_44 UA='N510 IP PRO/42.210.00.000.000' 
> Feb? 5 00:42:38 cusax (local7.notice) proxy[3552]: NOTICE: <script>: Setting '898910001201001 at sld.tld' as initiating network-provided CLI - R=sip:*57 at sld.tld;user=phone ID=2639378387 at 11_22_33_44 UA='N510 IP PRO/42.210.00.000.000' 
> Feb? 5 00:42:38 cusax (local7.notice) proxy[3552]: NOTICE: <script>: Rewriting called party '*57' to 'malicious_call' - R=sip:*57 at sld.tld;user=phone ID=2639378387 at 11_22_33_44 UA='N510 IP PRO/42.210.00.000.000' 
> Feb? 5 00:42:38 cusax (local7.err) proxy[3552]: ERROR: app_lua [app_lua_api.c:680]: app_lua_run(): error executing: del_dlg_profile (err: 2) 
> Feb? 5 00:42:38 cusax (local7.err) proxy[3552]: ERROR: app_lua [app_lua_api.c:682]: app_lua_run(): error from Lua: /etc/kamailio/proxy/dlgcnt.lua:101: can't restore callid from $dlg_var(lua_dlg_callid): is null 
> Feb? 5 00:42:38 cusax (local7.err) proxy[3552]: ERROR: <script>: Failed to decrease redis counters - R=sip:you at kamailio.org ID=123 UA='<null>' 
> Feb? 5 00:42:38 cusax (local7.notice) proxy[3552]: NOTICE: <script>: New request on proxy - M=ACK R=sip:*57 at sld.tld;user=phone F=sip:johndoe at sld.tld T=sip:*57 at sld.tld;user=phone IP=11.22.33.44:5732 (127.0.0.1:5060) ID=2639378387 at 11_22_33_44 UA='N510 IP PRO/42.210.00.000.000' 
>
> Does anybody have an idea what might be the missing part? 
>
> Regards, 
>
> Marc 
>
> ________________________________________ 
> From: Marc Storck 
> Sent: Friday, October 30, 2015 17:49 
> To: Kirill Solomko 
> Cc: spce-user at lists.sipwise.com 
> Subject: Re: [Spce-user] MCID App issue 
>
> So I set 
>
> store_recentcalls: ?yes' 
>
> followed by running 
>
> ngcpcfg apply 
>
> but the result is still quite the same: 
>
> Oct 30 17:45:08 cusax proxy[514]: NOTICE: <script>: Rewriting called party '*57' to 'malicious_call' - R=sip:*57 at sld.tld ID=OWU3ZmFiMDY5ZGE4ZGJkODE4ODdlMDhjMzg1MWFkYzc UA='Bria iOS release 3.4.4 stamp 31657' 
> Oct 30 17:45:08 cusax proxy[514]: ERROR: app_lua [app_lua_api.c:680]: app_lua_run(): error executing: del_dlg_profile (err: 2) 
> Oct 30 17:45:08 cusax proxy[514]: ERROR: app_lua [app_lua_api.c:682]: app_lua_run(): error from Lua: /etc/kamailio/proxy/dlgcnt.lua:101: can't restore callid from $dlg_var(lua_dlg_callid): is null 
> Oct 30 17:45:08 cusax proxy[514]: ERROR: <script>: Failed to decrease redis counters - R=sip:you at kamailio.org ID=123 UA='<null>' 
>
> Regards, 
>
> Marc 
>
> > On 30 Oct 2015, at 17:42, Kirill Solomko <ksolomko at sipwise.com> wrote: 
> > 
> > Hi Mark, 
> > 
> > You should also enable ?recent calls? support in config.yml 
> > 
> > kamailio: 
> >? proxy: 
> >??? store_recentcalls: ?yes' 
> > 
> >> On 30 Oct 2015, at 17:24, Marc Storck <mstorck at voipgate.com> wrote: 
> >> 
> >> Good evening, 
> >> 
> >> I?m having this problem with the MCID app: 
> >> 
> >> Oct 30 17:21:34 cusax proxy[23526]: NOTICE: <script>: Rewriting called party '*57' to 'malicious_call' - R=sip:*57 at sld.tld ID=YmE5NDYzOWMyMWE2NWY0MjE3YTMwYWRkMDVkMjcwOWI UA='Bria iOS release 3.4.4 stamp 31657' 
> >> Oct 30 17:21:34 cusax proxy[23526]: ERROR: app_lua [app_lua_api.c:680]: app_lua_run(): error executing: del_dlg_profile (err: 2) 
> >> Oct 30 17:21:34 cusax proxy[23526]: ERROR: app_lua [app_lua_api.c:682]: app_lua_run(): error from Lua: /etc/kamailio/proxy/dlgcnt.lua:101: can't restore callid from $dlg_var(lua_dlg_callid): is null 
> >> Oct 30 17:21:34 cusax proxy[23526]: ERROR: <script>: Failed to decrease redis counters - R=sip:you at kamailio.org ID=123 UA='<null>? 
> >> 
> >> I activated the MCID app in config.yml, are there any further changes required? 
> >> 
> >> Regards, 
> >> 
> >> Marc 
> >> _______________________________________________ 
> >> Spce-user mailing list 
> >> Spce-user at lists.sipwise.com 
> >> https://lists.sipwise.com/listinfo/spce-user 
> > 
> > Kind regards, 
> > Kirill 
>
> _______________________________________________ 
> Spce-user mailing list 
> Spce-user at lists.sipwise.com 
> https://lists.sipwise.com/listinfo/spce-user 

From j_e_vargas at live.com  Fri Feb  5 03:21:08 2016
From: j_e_vargas at live.com (Jose E. Vargas B.)
Date: Fri, 5 Feb 2016 00:21:08 -0800
Subject: [Spce-user] bruteforcing sip credentials attack
In-Reply-To: <46812e2e-1a1d-4c80-847e-d34d4f4d544e@email.android.com>
References: <46812e2e-1a1d-4c80-847e-d34d4f4d544e@email.android.com>
Message-ID: <BLU436-SMTP14785083FBDB23E415E1FEDBCD20@phx.gbl>

Thanks for your help Daniel, Alexis and George. Problem is solved now!
Jose

> On Feb 4, 2016, at 11:03 AM, Daniel Grotti <dgrotti at sipwise.com> wrote:
> 
> Hi,
> Hope it will help and maybe give you some hints:
> 
> https://www.linkedin.com/pulse/securing-your-ngcp-against-sip-attacks-daniel-grotti?forceNoSplash=true
> 
> 
> Daniel
> 
> 
> On Feb 4, 2016 7:38 PM, "Jose E. Vargas B." <j_e_vargas at live.com> wrote:
>> 
>> Hello,
>> 
>> Just have a quick and probably easy question for the SP community. I am experimenting with the server and keep getting the entire day the following attack:
>> 
>> 016/02/04 19:20:16.673827 188.138.33.14:5071 -> yy.yy.yy.yy:5060
>> INVITE sip:901141445209482 at xx.xx.xx.xx SIP/2.0
>> To: 901141445209482<sip:901141445209482 at xx.xx.xx.xx>
>> From: 0550<sip:0550 at xx.xx.xx.xx>;tag=67a87716
>> Via: SIP/2.0/UDP 188.138.33.14:5071;branch=z9hG4bK-6f67d7e24b4ac8a25f3d76106be4cb74;rport
>> Call-ID: 6f67d7e24b4ac8a25f3d76106be4cb74
>> CSeq: 1 INVITE
>> Contact: <sip:0550 at 188.138.33.14:5071>
>> Max-Forwards: 70
>> Allow: INVITE, ACK, CANCEL, BYE
>> User-Agent: sipcli/v1.8
>> Content-Type: application/sdp
>> Content-Length: 281
>> 
>> v=0
>> o=sipcli-Session 691746334 738426574 IN IP4 188.138.33.14
>> s=sipcli
>> c=IN IP4 188.138.33.14
>> t=0 0
>> m=audio 5073 RTP/AVP 18 0 8 101
>> a=fmtp:101 0-15
>> a=rtpmap:18 G729/8000
>> a=rtpmap:0 PCMU/8000
>> a=rtpmap:8 PCMA/8000
>> a=rtpmap:101 telephone-event/8000
>> a=ptime:20
>> a=sendrecv
>> 
>> 
>> I guess it is a funny group/folk trying to get unauthorized access to the server by sending multiple SIP invites with different accounts and possible free phone calls ;)  The problem is that SPCE won?t detect it as his attempts are spared in time.  Would like to get your guidance about blocking the entire IP or domain to SCPCE server. Could you please comment on how you deal with this type of attack?
>> 
>> Jose 
>> 
>> PS: 
>>     BTW - making changes to config.yml (failed _auth)?) didn?t help  
>>     Offending IP:  188.138.33.14
>> 
>> 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 1776 bytes
Desc: not available
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20160205/1b48eec3/attachment-0001.p7s>

From mstorck at voipgate.com  Fri Feb  5 04:36:24 2016
From: mstorck at voipgate.com (Marc Storck)
Date: Fri, 5 Feb 2016 09:36:24 +0000
Subject: [Spce-user] MCID App issue
In-Reply-To: <634d081a-8463-4965-abbb-a282d8f21695@email.android.com>
References: <634d081a-8463-4965-abbb-a282d8f21695@email.android.com>
Message-ID: <2970CB78-9A94-41AB-8E04-63CC51B6C992@voipgate.com>

Hello Daniel,

That step is missing in the documentation.

I?ll test tonight.

Regards,

Marc Storck


> On 05 Feb 2016, at 07:58, Daniel Grotti <dgrotti at sipwise.com> wrote:
> 
> Hi Marc,
> Did you flag the subscriber preferences MCID ? It should be in the Internal section.
> You should enable MCID there otherwise it won't work.
> 
> Daniel
> 
> On Feb 5, 2016 12:51 AM, Marc Storck <mstorck at voipgate.com> wrote:
>> 
>> I just upgraded to mr4.2.1.
>> 
>> I followed the steps described in the documentation. My system was almost good, I was only missing the audio file in the sound set.
>> 
>> However the problem persists:
>> 
>> Feb  5 00:42:38 cusax (local7.notice) proxy[3552]: NOTICE: <script>: New request on proxy - M=INVITE R=sip:*57 at sld.tld;user=phone F=sip:johndoe at sld.tld T=sip:*57 at sld.tld;user=phone IP=11.22.33.44:5732 (127.0.0.1:5060) ID=2639378387 at 11_22_33_44 UA='N510 IP PRO/42.210.00.000.000'
>> Feb  5 00:42:38 cusax (local7.notice) proxy[3552]: NOTICE: <script>: User-Provided CLI 'johndoe' taken from From-User - R=sip:*57 at sld.tld;user=phone ID=2639378387 at 11_22_33_44 UA='N510 IP PRO/42.210.00.000.000'
>> Feb  5 00:42:38 cusax (local7.notice) proxy[3552]: NOTICE: <script>: User-provided CLI 'johndoe' rejected, using network-provided CLI '898910001201001' - R=sip:*57 at sld.tld;user=phone ID=2639378387 at 11_22_33_44 UA='N510 IP PRO/42.210.00.000.000'
>> Feb  5 00:42:38 cusax (local7.notice) proxy[3552]: NOTICE: <script>: Setting '898910001201001 at sld.tld' as initiating user-provided CLI - R=sip:*57 at sld.tld;user=phone ID=2639378387 at 11_22_33_44 UA='N510 IP PRO/42.210.00.000.000'
>> Feb  5 00:42:38 cusax (local7.notice) proxy[3552]: NOTICE: <script>: Setting '898910001201001 at sld.tld' as initiating network-provided CLI - R=sip:*57 at sld.tld;user=phone ID=2639378387 at 11_22_33_44 UA='N510 IP PRO/42.210.00.000.000'
>> Feb  5 00:42:38 cusax (local7.notice) proxy[3552]: NOTICE: <script>: Rewriting called party '*57' to 'malicious_call' - R=sip:*57 at sld.tld;user=phone ID=2639378387 at 11_22_33_44 UA='N510 IP PRO/42.210.00.000.000'
>> Feb  5 00:42:38 cusax (local7.err) proxy[3552]: ERROR: app_lua [app_lua_api.c:680]: app_lua_run(): error executing: del_dlg_profile (err: 2)
>> Feb  5 00:42:38 cusax (local7.err) proxy[3552]: ERROR: app_lua [app_lua_api.c:682]: app_lua_run(): error from Lua: /etc/kamailio/proxy/dlgcnt.lua:101: can't restore callid from $dlg_var(lua_dlg_callid): is null
>> Feb  5 00:42:38 cusax (local7.err) proxy[3552]: ERROR: <script>: Failed to decrease redis counters - R=sip:you at kamailio.org ID=123 UA='<null>'
>> Feb  5 00:42:38 cusax (local7.notice) proxy[3552]: NOTICE: <script>: New request on proxy - M=ACK R=sip:*57 at sld.tld;user=phone F=sip:johndoe at sld.tld T=sip:*57 at sld.tld;user=phone IP=11.22.33.44:5732 (127.0.0.1:5060) ID=2639378387 at 11_22_33_44 UA='N510 IP PRO/42.210.00.000.000'
>> 
>> Does anybody have an idea what might be the missing part?
>> 
>> Regards,
>> 
>> Marc
>> 
>> ________________________________________
>> From: Marc Storck
>> Sent: Friday, October 30, 2015 17:49
>> To: Kirill Solomko
>> Cc: spce-user at lists.sipwise.com
>> Subject: Re: [Spce-user] MCID App issue
>> 
>> So I set
>> 
>> store_recentcalls: ?yes'
>> 
>> followed by running
>> 
>> ngcpcfg apply
>> 
>> but the result is still quite the same:
>> 
>> Oct 30 17:45:08 cusax proxy[514]: NOTICE: <script>: Rewriting called party '*57' to 'malicious_call' - R=sip:*57 at sld.tld ID=OWU3ZmFiMDY5ZGE4ZGJkODE4ODdlMDhjMzg1MWFkYzc UA='Bria iOS release 3.4.4 stamp 31657'
>> Oct 30 17:45:08 cusax proxy[514]: ERROR: app_lua [app_lua_api.c:680]: app_lua_run(): error executing: del_dlg_profile (err: 2)
>> Oct 30 17:45:08 cusax proxy[514]: ERROR: app_lua [app_lua_api.c:682]: app_lua_run(): error from Lua: /etc/kamailio/proxy/dlgcnt.lua:101: can't restore callid from $dlg_var(lua_dlg_callid): is null
>> Oct 30 17:45:08 cusax proxy[514]: ERROR: <script>: Failed to decrease redis counters - R=sip:you at kamailio.org ID=123 UA='<null>'
>> 
>> Regards,
>> 
>> Marc
>> 
>>> On 30 Oct 2015, at 17:42, Kirill Solomko <ksolomko at sipwise.com> wrote:
>>> 
>>> Hi Mark,
>>> 
>>> You should also enable ?recent calls? support in config.yml
>>> 
>>> kamailio:
>>>   proxy:
>>>     store_recentcalls: ?yes'
>>> 
>>>> On 30 Oct 2015, at 17:24, Marc Storck <mstorck at voipgate.com> wrote:
>>>> 
>>>> Good evening,
>>>> 
>>>> I?m having this problem with the MCID app:
>>>> 
>>>> Oct 30 17:21:34 cusax proxy[23526]: NOTICE: <script>: Rewriting called party '*57' to 'malicious_call' - R=sip:*57 at sld.tld ID=YmE5NDYzOWMyMWE2NWY0MjE3YTMwYWRkMDVkMjcwOWI UA='Bria iOS release 3.4.4 stamp 31657'
>>>> Oct 30 17:21:34 cusax proxy[23526]: ERROR: app_lua [app_lua_api.c:680]: app_lua_run(): error executing: del_dlg_profile (err: 2)
>>>> Oct 30 17:21:34 cusax proxy[23526]: ERROR: app_lua [app_lua_api.c:682]: app_lua_run(): error from Lua: /etc/kamailio/proxy/dlgcnt.lua:101: can't restore callid from $dlg_var(lua_dlg_callid): is null
>>>> Oct 30 17:21:34 cusax proxy[23526]: ERROR: <script>: Failed to decrease redis counters - R=sip:you at kamailio.org ID=123 UA='<null>?
>>>> 
>>>> I activated the MCID app in config.yml, are there any further changes required?
>>>> 
>>>> Regards,
>>>> 
>>>> Marc
>>>> _______________________________________________
>>>> Spce-user mailing list
>>>> Spce-user at lists.sipwise.com
>>>> https://lists.sipwise.com/listinfo/spce-user
>>> 
>>> Kind regards,
>>> Kirill
>> 
>> _______________________________________________
>> Spce-user mailing list
>> Spce-user at lists.sipwise.com
>> https://lists.sipwise.com/listinfo/spce-user

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 841 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20160205/cc27e9e1/attachment-0001.asc>

From dgrotti at sipwise.com  Fri Feb  5 04:42:38 2016
From: dgrotti at sipwise.com (Daniel Grotti)
Date: Fri, 5 Feb 2016 10:42:38 +0100
Subject: [Spce-user] MCID App issue
In-Reply-To: <2970CB78-9A94-41AB-8E04-63CC51B6C992@voipgate.com>
References: <634d081a-8463-4965-abbb-a282d8f21695@email.android.com>
 <2970CB78-9A94-41AB-8E04-63CC51B6C992@voipgate.com>
Message-ID: <56B46E8E.8030906@sipwise.com>

Hi Marc,
it's part of mr4.2.1 documentation.
I introduced it when we noticed that was missing.

thanks.

*Daniel Grotti *
Head of Customer Support

Sipwise GmbH <http://www.sipwise.com> , Campus 21/Europaring F15
AT-2345 Brunn am Gebirge

Phone: +43(0)1 301 2032 <callto:+4313012032>
Email: dgrotti at sipwise.com <mailto:dgrotti at sipwise.com>
Website: www.sipwise.com <http://www.sipwise.com>

Particulars according Austrian Companies Code paragraph 14
"Sipwise GmbH" - Europaring F15 - 2345 Brunn am Gebirge
FN:305595f, Commercial Court Vienna, ATU64002206

On 02/05/2016 10:36 AM, Marc Storck wrote:
> Hello Daniel,
>
> That step is missing in the documentation.
>
> I?ll test tonight.
>
> Regards,
>
> Marc Storck
>
>
>> On 05 Feb 2016, at 07:58, Daniel Grotti <dgrotti at sipwise.com> wrote:
>>
>> Hi Marc,
>> Did you flag the subscriber preferences MCID ? It should be in the Internal section.
>> You should enable MCID there otherwise it won't work.
>>
>> Daniel
>>
>> On Feb 5, 2016 12:51 AM, Marc Storck <mstorck at voipgate.com> wrote:
>>> I just upgraded to mr4.2.1.
>>>
>>> I followed the steps described in the documentation. My system was almost good, I was only missing the audio file in the sound set.
>>>
>>> However the problem persists:
>>>
>>> Feb  5 00:42:38 cusax (local7.notice) proxy[3552]: NOTICE: <script>: New request on proxy - M=INVITE R=sip:*57 at sld.tld;user=phone F=sip:johndoe at sld.tld T=sip:*57 at sld.tld;user=phone IP=11.22.33.44:5732 (127.0.0.1:5060) ID=2639378387 at 11_22_33_44 UA='N510 IP PRO/42.210.00.000.000'
>>> Feb  5 00:42:38 cusax (local7.notice) proxy[3552]: NOTICE: <script>: User-Provided CLI 'johndoe' taken from From-User - R=sip:*57 at sld.tld;user=phone ID=2639378387 at 11_22_33_44 UA='N510 IP PRO/42.210.00.000.000'
>>> Feb  5 00:42:38 cusax (local7.notice) proxy[3552]: NOTICE: <script>: User-provided CLI 'johndoe' rejected, using network-provided CLI '898910001201001' - R=sip:*57 at sld.tld;user=phone ID=2639378387 at 11_22_33_44 UA='N510 IP PRO/42.210.00.000.000'
>>> Feb  5 00:42:38 cusax (local7.notice) proxy[3552]: NOTICE: <script>: Setting '898910001201001 at sld.tld' as initiating user-provided CLI - R=sip:*57 at sld.tld;user=phone ID=2639378387 at 11_22_33_44 UA='N510 IP PRO/42.210.00.000.000'
>>> Feb  5 00:42:38 cusax (local7.notice) proxy[3552]: NOTICE: <script>: Setting '898910001201001 at sld.tld' as initiating network-provided CLI - R=sip:*57 at sld.tld;user=phone ID=2639378387 at 11_22_33_44 UA='N510 IP PRO/42.210.00.000.000'
>>> Feb  5 00:42:38 cusax (local7.notice) proxy[3552]: NOTICE: <script>: Rewriting called party '*57' to 'malicious_call' - R=sip:*57 at sld.tld;user=phone ID=2639378387 at 11_22_33_44 UA='N510 IP PRO/42.210.00.000.000'
>>> Feb  5 00:42:38 cusax (local7.err) proxy[3552]: ERROR: app_lua [app_lua_api.c:680]: app_lua_run(): error executing: del_dlg_profile (err: 2)
>>> Feb  5 00:42:38 cusax (local7.err) proxy[3552]: ERROR: app_lua [app_lua_api.c:682]: app_lua_run(): error from Lua: /etc/kamailio/proxy/dlgcnt.lua:101: can't restore callid from $dlg_var(lua_dlg_callid): is null
>>> Feb  5 00:42:38 cusax (local7.err) proxy[3552]: ERROR: <script>: Failed to decrease redis counters - R=sip:you at kamailio.org ID=123 UA='<null>'
>>> Feb  5 00:42:38 cusax (local7.notice) proxy[3552]: NOTICE: <script>: New request on proxy - M=ACK R=sip:*57 at sld.tld;user=phone F=sip:johndoe at sld.tld T=sip:*57 at sld.tld;user=phone IP=11.22.33.44:5732 (127.0.0.1:5060) ID=2639378387 at 11_22_33_44 UA='N510 IP PRO/42.210.00.000.000'
>>>
>>> Does anybody have an idea what might be the missing part?
>>>
>>> Regards,
>>>
>>> Marc
>>>
>>> ________________________________________
>>> From: Marc Storck
>>> Sent: Friday, October 30, 2015 17:49
>>> To: Kirill Solomko
>>> Cc: spce-user at lists.sipwise.com
>>> Subject: Re: [Spce-user] MCID App issue
>>>
>>> So I set
>>>
>>> store_recentcalls: ?yes'
>>>
>>> followed by running
>>>
>>> ngcpcfg apply
>>>
>>> but the result is still quite the same:
>>>
>>> Oct 30 17:45:08 cusax proxy[514]: NOTICE: <script>: Rewriting called party '*57' to 'malicious_call' - R=sip:*57 at sld.tld ID=OWU3ZmFiMDY5ZGE4ZGJkODE4ODdlMDhjMzg1MWFkYzc UA='Bria iOS release 3.4.4 stamp 31657'
>>> Oct 30 17:45:08 cusax proxy[514]: ERROR: app_lua [app_lua_api.c:680]: app_lua_run(): error executing: del_dlg_profile (err: 2)
>>> Oct 30 17:45:08 cusax proxy[514]: ERROR: app_lua [app_lua_api.c:682]: app_lua_run(): error from Lua: /etc/kamailio/proxy/dlgcnt.lua:101: can't restore callid from $dlg_var(lua_dlg_callid): is null
>>> Oct 30 17:45:08 cusax proxy[514]: ERROR: <script>: Failed to decrease redis counters - R=sip:you at kamailio.org ID=123 UA='<null>'
>>>
>>> Regards,
>>>
>>> Marc
>>>
>>>> On 30 Oct 2015, at 17:42, Kirill Solomko <ksolomko at sipwise.com> wrote:
>>>>
>>>> Hi Mark,
>>>>
>>>> You should also enable ?recent calls? support in config.yml
>>>>
>>>> kamailio:
>>>>    proxy:
>>>>      store_recentcalls: ?yes'
>>>>
>>>>> On 30 Oct 2015, at 17:24, Marc Storck <mstorck at voipgate.com> wrote:
>>>>>
>>>>> Good evening,
>>>>>
>>>>> I?m having this problem with the MCID app:
>>>>>
>>>>> Oct 30 17:21:34 cusax proxy[23526]: NOTICE: <script>: Rewriting called party '*57' to 'malicious_call' - R=sip:*57 at sld.tld ID=YmE5NDYzOWMyMWE2NWY0MjE3YTMwYWRkMDVkMjcwOWI UA='Bria iOS release 3.4.4 stamp 31657'
>>>>> Oct 30 17:21:34 cusax proxy[23526]: ERROR: app_lua [app_lua_api.c:680]: app_lua_run(): error executing: del_dlg_profile (err: 2)
>>>>> Oct 30 17:21:34 cusax proxy[23526]: ERROR: app_lua [app_lua_api.c:682]: app_lua_run(): error from Lua: /etc/kamailio/proxy/dlgcnt.lua:101: can't restore callid from $dlg_var(lua_dlg_callid): is null
>>>>> Oct 30 17:21:34 cusax proxy[23526]: ERROR: <script>: Failed to decrease redis counters - R=sip:you at kamailio.org ID=123 UA='<null>?
>>>>>
>>>>> I activated the MCID app in config.yml, are there any further changes required?
>>>>>
>>>>> Regards,
>>>>>
>>>>> Marc
>>>>> _______________________________________________
>>>>> Spce-user mailing list
>>>>> Spce-user at lists.sipwise.com
>>>>> https://lists.sipwise.com/listinfo/spce-user
>>>> Kind regards,
>>>> Kirill
>>> _______________________________________________
>>> Spce-user mailing list
>>> Spce-user at lists.sipwise.com
>>> https://lists.sipwise.com/listinfo/spce-user

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20160205/e0f4cb80/attachment-0001.html>

From j.feugne at prisnets.ch  Fri Feb  5 06:57:27 2016
From: j.feugne at prisnets.ch (=?UTF-8?Q?Jephth=c3=a9_Feugn=c3=a9?=)
Date: Fri, 5 Feb 2016 12:57:27 +0100
Subject: [Spce-user]  trunk to voicetrading configuration
In-Reply-To: <56B46E8E.8030906@sipwise.com>
References: <634d081a-8463-4965-abbb-a282d8f21695@email.android.com>
 <2970CB78-9A94-41AB-8E04-63CC51B6C992@voipgate.com>
 <56B46E8E.8030906@sipwise.com>
Message-ID: <56B48E27.2080804@prisnets.ch>

Hello,
I've been trying for weeks to have my trunk to voicetrading working with 
no success. I also tried a sip trunk to my GSM gateway with the same 
result. No ringing to the calle side, and no sound no ringing tone by 
the caller side.

Can some one please can help me solve this problem?

Here is what I have during call with the command "ngrep sip" executed on 
the sipwise CE 4.2.1  server. Voicetrading is  expecting for premium 
route on their side, the number to be perpended with "00000", 
xx.xx.xx.250 is the IP address of my sipwise CE 4.2.1 server:



U xx.xx.xx.250:5060 -> 77.72.169.129:5060
   ACK sip:0000041227312221 at 77.72.169.129:5060;transport=udp 
SIP/2.0..Max-Forwards: 70..Record-Route: 
<sip:xx.xx.xx.250;r2=on;lr=on;ftag=3F73B03A-56B489EF00017901-870F0700;ngcplb=yes
   >..Record-Route: 
<sip:127.0.0.1;r2=on;lr=on;ftag=3F73B03A-56B489EF00017901-870F0700;ngcplb=yes>..Via: 
SIP/2.0/UDP 
xx.xx.xx.250;branch=z9hG4bK705f.3ceafc99ad73ca726fe67f2c96efb4ea.
   0..Via: SIP/2.0/UDP 
127.0.0.1:5080;received=127.0.0.1;branch=z9hG4bKqqDKvalZ;rport=5080..From: 
"41225017070" 
<sip:41225017070 at sip.adoovoice.com>;tag=3F73B03A-56B489EF00017901-870F0
   700..To: <sip:0000041227312221 at 77.72.169.129>..Call-ID: 
f3e84a2c-469f-1234-1eae-00163ee0653c_b2b-1..CSeq: 10 
ACK..Content-Length: 0....
#
U xx.xx.xx.250:5060 -> 77.72.169.129:5060
   INVITE sip:0000041227312221 at 77.72.169.129:5060;transport=udp 
SIP/2.0..Record-Route: 
<sip:xx.xx.xx.250;r2=on;lr=on;ftag=3F73B03A-56B489EF00017901-870F0700;ngcplb=yes>..Record-Route
   : 
<sip:127.0.0.1;r2=on;lr=on;ftag=3F73B03A-56B489EF00017901-870F0700;ngcplb=yes>..Via: 
SIP/2.0/UDP 
xx.xx.xx.250;branch=z9hG4bK805f.3b9fffb768d5164c476e3f831eb033fc.0..Via: 
SIP/2.0
   /UDP 
127.0.0.1:5080;received=127.0.0.1;branch=z9hG4bKx0gPrabm;rport=5080..From: 
"41225017070" 
<sip:41225017070 at sip.adoovoice.com>;tag=3F73B03A-56B489EF00017901-870F0700..To: 
<sip:0
   000041227312221 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 
f3e84a2c-469f-1234-1eae-00163ee0653c_b2b-1..Max-Forwards: 69..Allow: 
INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, UPDATE, R
   EGISTER, NOTIFY..Supported: path, replaces..P-Asserted-Identity: 
<sip:41225017070 at sip.adoovoice.com>..Authorization: Digest 
username="pbxprisnet", realm="sip.adoovoice.com", nonce=
   "99066203", 
uri="sip:0000041227312221 at 77.72.169.129:5060;transport=udp", 
response="e3fda1ac2871a94ed7b781e0f69741d0", 
algorithm=MD5..Content-Type: application/sdp..Content-Length:
   326..Contact: 
<sip:ngcp-lb at xx.xx.xx.250:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=FreeSWITCH 
1454642405 1454642406 IN IP4 xx.xx.xx.253..s=FreeSWITCH..c=IN IP4 8
   4.253.60.153..t=0 0..m=audio 29962 RTP/AVP 8 9 0 3 101 13..a=rtpmap:8 
PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:0 PCMU/8000..a=rtpmap:3 
GSM/8000..a=rtpmap:101 telephone-event/8000.
   .a=fmtp:101 0-16..a=sendrecv..a=ptime:20..a=direction:both..
################################
U xx.xx.xx.250:5060 -> 77.72.169.129:5060
   INVITE sip:0000041227312221 at 77.72.169.129:5060;transport=udp 
SIP/2.0..Record-Route: 
<sip:xx.xx.xx.250;r2=on;lr=on;ftag=3F73B03A-56B489EF00017901-870F0700;ngcplb=yes>..Record-Route
   : 
<sip:127.0.0.1;r2=on;lr=on;ftag=3F73B03A-56B489EF00017901-870F0700;ngcplb=yes>..Via: 
SIP/2.0/UDP 
xx.xx.xx.250;branch=z9hG4bK805f.3b9fffb768d5164c476e3f831eb033fc.0..Via: 
SIP/2.0
   /UDP 
127.0.0.1:5080;received=127.0.0.1;branch=z9hG4bKx0gPrabm;rport=5080..From: 
"41225017070" 
<sip:41225017070 at sip.adoovoice.com>;tag=3F73B03A-56B489EF00017901-870F0700..To: 
<sip:0
   000041227312221 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 
f3e84a2c-469f-1234-1eae-00163ee0653c_b2b-1..Max-Forwards: 69..Allow: 
INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, UPDATE, R
   EGISTER, NOTIFY..Supported: path, replaces..P-Asserted-Identity: 
<sip:41225017070 at sip.adoovoice.com>..Authorization: Digest 
username="pbxprisnet", realm="sip.adoovoice.com", nonce=
   "99066203", 
uri="sip:0000041227312221 at 77.72.169.129:5060;transport=udp", 
response="e3fda1ac2871a94ed7b781e0f69741d0", 
algorithm=MD5..Content-Type: application/sdp..Content-Length:
   326..Contact: 
<sip:ngcp-lb at xx.xx.xx.250:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=FreeSWITCH 
1454642405 1454642406 IN IP4 xx.xx.xx.253..s=FreeSWITCH..c=IN IP4 8
   4.253.60.153..t=0 0..m=audio 29962 RTP/AVP 8 9 0 3 101 13..a=rtpmap:8 
PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:0 PCMU/8000..a=rtpmap:3 
GSM/8000..a=rtpmap:101 telephone-event/8000.
   .a=fmtp:101 0-16..a=sendrecv..a=ptime:20..a=direction:both..
#############################
U xx.xx.xx.250:5060 -> 77.72.169.129:5060
   INVITE sip:0000041227312221 at 77.72.169.129:5060;transport=udp 
SIP/2.0..Record-Route: 
<sip:xx.xx.xx.250;r2=on;lr=on;ftag=3F73B03A-56B489EF00017901-870F0700;ngcplb=yes>..Record-Route
   : 
<sip:127.0.0.1;r2=on;lr=on;ftag=3F73B03A-56B489EF00017901-870F0700;ngcplb=yes>..Via: 
SIP/2.0/UDP 
xx.xx.xx.250;branch=z9hG4bK805f.3b9fffb768d5164c476e3f831eb033fc.0..Via: 
SIP/2.0
   /UDP 
127.0.0.1:5080;received=127.0.0.1;branch=z9hG4bKx0gPrabm;rport=5080..From: 
"41225017070" 
<sip:41225017070 at sip.adoovoice.com>;tag=3F73B03A-56B489EF00017901-870F0700..To: 
<sip:0
   000041227312221 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 
f3e84a2c-469f-1234-1eae-00163ee0653c_b2b-1..Max-Forwards: 69..Allow: 
INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, UPDATE, R
   EGISTER, NOTIFY..Supported: path, replaces..P-Asserted-Identity: 
<sip:41225017070 at sip.adoovoice.com>..Authorization: Digest 
username="pbxprisnet", realm="sip.adoovoice.com", nonce=
   "99066203", 
uri="sip:0000041227312221 at 77.72.169.129:5060;transport=udp", 
response="e3fda1ac2871a94ed7b781e0f69741d0", 
algorithm=MD5..Content-Type: application/sdp..Content-Length:
   326..Contact: 
<sip:ngcp-lb at xx.xx.xx.250:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=FreeSWITCH 
1454642405 1454642406 IN IP4 xx.xx.xx.253..s=FreeSWITCH..c=IN IP4 8
   4.253.60.153..t=0 0..m=audio 29962 RTP/AVP 8 9 0 3 101 13..a=rtpmap:8 
PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:0 PCMU/8000..a=rtpmap:3 
GSM/8000..a=rtpmap:101 telephone-event/8000.
   .a=fmtp:101 0-16..a=sendrecv..a=ptime:20..a=direction:both..
###################################################
U xx.xx.xx.250:5060 -> 77.72.169.129:5060
   INVITE sip:0000041227312221 at 77.72.169.129:5060;transport=udp 
SIP/2.0..Record-Route: 
<sip:xx.xx.xx.250;r2=on;lr=on;ftag=3F73B03A-56B489EF00017901-870F0700;ngcplb=yes>..Record-Route
   : 
<sip:127.0.0.1;r2=on;lr=on;ftag=3F73B03A-56B489EF00017901-870F0700;ngcplb=yes>..Via: 
SIP/2.0/UDP 
xx.xx.xx.250;branch=z9hG4bK805f.3b9fffb768d5164c476e3f831eb033fc.0..Via: 
SIP/2.0
   /UDP 
127.0.0.1:5080;received=127.0.0.1;branch=z9hG4bKx0gPrabm;rport=5080..From: 
"41225017070" 
<sip:41225017070 at sip.adoovoice.com>;tag=3F73B03A-56B489EF00017901-870F0700..To: 
<sip:0
   000041227312221 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 
f3e84a2c-469f-1234-1eae-00163ee0653c_b2b-1..Max-Forwards: 69..Allow: 
INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, UPDATE, R
   EGISTER, NOTIFY..Supported: path, replaces..P-Asserted-Identity: 
<sip:41225017070 at sip.adoovoice.com>..Authorization: Digest 
username="pbxprisnet", realm="sip.adoovoice.com", nonce=
   "99066203", 
uri="sip:0000041227312221 at 77.72.169.129:5060;transport=udp", 
response="e3fda1ac2871a94ed7b781e0f69741d0", 
algorithm=MD5..Content-Type: application/sdp..Content-Length:
   326..Contact: 
<sip:ngcp-lb at xx.xx.xx.250:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=FreeSWITCH 
1454642405 1454642406 IN IP4 xx.xx.xx.253..s=FreeSWITCH..c=IN IP4 8
   4.253.60.153..t=0 0..m=audio 29962 RTP/AVP 8 9 0 3 101 13..a=rtpmap:8 
PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:0 PCMU/8000..a=rtpmap:3 
GSM/8000..a=rtpmap:101 telephone-event/8000.
   .a=fmtp:101 0-16..a=sendrecv..a=ptime:20..a=direction:both..
######


Thank you for your contributions

Jephth? Feugn?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20160205/47dd82c2/attachment-0001.html>

From manwe at sipdoc.net  Fri Feb  5 07:07:38 2016
From: manwe at sipdoc.net (Jon Bonilla (Manwe))
Date: Fri, 5 Feb 2016 13:07:38 +0100
Subject: [Spce-user] trunk to voicetrading configuration
In-Reply-To: <56B48E27.2080804@prisnets.ch>
References: <634d081a-8463-4965-abbb-a282d8f21695@email.android.com>
 <2970CB78-9A94-41AB-8E04-63CC51B6C992@voipgate.com>
 <56B46E8E.8030906@sipwise.com> <56B48E27.2080804@prisnets.ch>
Message-ID: <20160205130738.49281a29@multivac>

El Fri, 5 Feb 2016 12:57:27 +0100
Jephth? Feugn? <j.feugne at prisnets.ch> escribi?:

> Hello,
> I've been trying for weeks to have my trunk to voicetrading working with 
> no success. I also tried a sip trunk to my GSM gateway with the same 
> result. No ringing to the calle side, and no sound no ringing tone by 
> the caller side.
> 
> Can some one please can help me solve this problem?
> 
> Here is what I have during call with the command "ngrep sip" executed on 
> the sipwise CE 4.2.1  server. Voicetrading is  expecting for premium 
> route on their side, the number to be perpended with "00000", 
> xx.xx.xx.250 is the IP address of my sipwise CE 4.2.1 server:
> 
> 
>

Please, do not answer mails to create a new thread. Press the "new mail" button.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: Firma digital OpenPGP
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20160205/fd55d046/attachment-0001.sig>

From j.feugne at prisnets.ch  Fri Feb  5 09:59:13 2016
From: j.feugne at prisnets.ch (=?UTF-8?Q?Jephth=c3=a9_Feugn=c3=a9?=)
Date: Fri, 5 Feb 2016 15:59:13 +0100
Subject: [Spce-user] Trunk to voicetrading configuration
Message-ID: <56B4B8C1.5060203@prisnets.ch>

Hello,
I've been trying for weeks to have my trunk to voicetrading working with no success. I also tried a sip trunk to my GSM gateway with the same
result. No ringing to the calle side, and no sound no ringing tone by the caller side.

Can some one please can help me solve this problem?

Here is what I have during call with the command "ngrep sip" executed on the sipwise CE 4.2.1  server. Voicetrading is  expecting for premium
route on their side, the number to be perpended with "00000", xx.xx.xx.250 is the IP address of my sipwise CE 4.2.1 server:


XX.XX.XX.250:5060 -> 77.72.169.129:5060
   INVITE sip:00492271993120 at 77.72.169.129:5060;transport=udp SIP/2.0..Record-Route: <sip:XX.XX.XX.250;r2=on;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Record-Route: <sip:127.0.0.1;r2=on
   ;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Via: SIP/2.0/UDP XX.XX.XX.250;branch=z9hG4bKd906.5531f5d10bd0fe3667091afe519d5f94.0..Via: SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;bra
   nch=z9hG4bKZ7GCaaKk;rport=5080..From: "41225017077" <sip:41225017077 at sip.adoovoice.com>;tag=0F8733E5-56B4B7B700066935-870F0700..To: <sip:00492271993120 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 222572
   206 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, PUBLISH, UPDATE, MESSAGE..Supported: replaces,100rel..P-Asserted-Identity: <sip:
   41225017077 at sip.adoovoice.com>..Authorization: Digest username="pbxprisnet", realm="sip.adoovoice.com", nonce="2231175255", uri="sip:00492271993120 at 77.72.169.129:5060;transport=udp", response="dac6cac
   8d25100ee03560bab867ba1be", algorithm=MD5..Content-Type: application/sdp..Content-Length: 265..Contact: <sip:ngcp-lb at XX.XX.XX.250:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=- 20036 2
   0036 IN IP4 10.164.124.97..s=SDP data..c=IN IP4 213.55.176.206..t=0 0..m=audio 11852 RTP/AVP 0 8 9 101..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:101 telephone-event/8
   000..a=sendrecv..a=ptime:20..a=direction:active..
#####################
U XX.XX.XX.250:5060 -> 77.72.169.129:5060
   INVITE sip:00492271993120 at 77.72.169.129:5060;transport=udp SIP/2.0..Record-Route: <sip:XX.XX.XX.250;r2=on;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Record-Route: <sip:127.0.0.1;r2=on
   ;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Via: SIP/2.0/UDP XX.XX.XX.250;branch=z9hG4bKd906.5531f5d10bd0fe3667091afe519d5f94.0..Via: SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;bra
   nch=z9hG4bKZ7GCaaKk;rport=5080..From: "41225017077" <sip:41225017077 at sip.adoovoice.com>;tag=0F8733E5-56B4B7B700066935-870F0700..To: <sip:00492271993120 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 222572
   206 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, PUBLISH, UPDATE, MESSAGE..Supported: replaces,100rel..P-Asserted-Identity: <sip:
   41225017077 at sip.adoovoice.com>..Authorization: Digest username="pbxprisnet", realm="sip.adoovoice.com", nonce="2231175255", uri="sip:00492271993120 at 77.72.169.129:5060;transport=udp", response="dac6cac
   8d25100ee03560bab867ba1be", algorithm=MD5..Content-Type: application/sdp..Content-Length: 265..Contact: <sip:ngcp-lb at XX.XX.XX.250:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=- 20036 2
   0036 IN IP4 10.164.124.97..s=SDP data..c=IN IP4 213.55.176.206..t=0 0..m=audio 11852 RTP/AVP 0 8 9 101..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:101 telephone-event/8
   000..a=sendrecv..a=ptime:20..a=direction:active..
#######################
U XX.XX.XX.250:5060 -> 77.72.169.129:5060
   INVITE sip:00492271993120 at 77.72.169.129:5060;transport=udp SIP/2.0..Record-Route: <sip:XX.XX.XX.250;r2=on;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Record-Route: <sip:127.0.0.1;r2=on
   ;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Via: SIP/2.0/UDP XX.XX.XX.250;branch=z9hG4bKd906.5531f5d10bd0fe3667091afe519d5f94.0..Via: SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;bra
   nch=z9hG4bKZ7GCaaKk;rport=5080..From: "41225017077" <sip:41225017077 at sip.adoovoice.com>;tag=0F8733E5-56B4B7B700066935-870F0700..To: <sip:00492271993120 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 222572
   206 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, PUBLISH, UPDATE, MESSAGE..Supported: replaces,100rel..P-Asserted-Identity: <sip:
   41225017077 at sip.adoovoice.com>..Authorization: Digest username="pbxprisnet", realm="sip.adoovoice.com", nonce="2231175255", uri="sip:00492271993120 at 77.72.169.129:5060;transport=udp", response="dac6cac
   8d25100ee03560bab867ba1be", algorithm=MD5..Content-Type: application/sdp..Content-Length: 265..Contact: <sip:ngcp-lb at XX.XX.XX.250:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=- 20036 2
   0036 IN IP4 10.164.124.97..s=SDP data..c=IN IP4 213.55.176.206..t=0 0..m=audio 11852 RTP/AVP 0 8 9 101..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:101 telephone-event/8
   000..a=sendrecv..a=ptime:20..a=direction:active..
#########################################
U XX.XX.XX.250:5060 -> 77.72.169.129:5060
   INVITE sip:00492271993120 at 77.72.169.129:5060;transport=udp SIP/2.0..Record-Route: <sip:XX.XX.XX.250;r2=on;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Record-Route: <sip:127.0.0.1;r2=on
   ;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Via: SIP/2.0/UDP XX.XX.XX.250;branch=z9hG4bKd906.5531f5d10bd0fe3667091afe519d5f94.0..Via: SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;bra
   nch=z9hG4bKZ7GCaaKk;rport=5080..From: "41225017077" <sip:41225017077 at sip.adoovoice.com>;tag=0F8733E5-56B4B7B700066935-870F0700..To: <sip:00492271993120 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 222572
   206 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, PUBLISH, UPDATE, MESSAGE..Supported: replaces,100rel..P-Asserted-Identity: <sip:
   41225017077 at sip.adoovoice.com>..Authorization: Digest username="pbxprisnet", realm="sip.adoovoice.com", nonce="2231175255", uri="sip:00492271993120 at 77.72.169.129:5060;transport=udp", response="dac6cac
   8d25100ee03560bab867ba1be", algorithm=MD5..Content-Type: application/sdp..Content-Length: 265..Contact: <sip:ngcp-lb at XX.XX.XX.250:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=- 20036 2
   0036 IN IP4 10.164.124.97..s=SDP data..c=IN IP4 213.55.176.206..t=0 0..m=audio 11852 RTP/AVP 0 8 9 101..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:101 telephone-event/8
   000..a=sendrecv..a=ptime:20..a=direction:active..
#################################################################################
U XX.XX.XX.250:5060 -> 77.72.169.129:5060
   INVITE sip:00492271993120 at 77.72.169.129:5060;transport=udp SIP/2.0..Record-Route: <sip:XX.XX.XX.250;r2=on;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Record-Route: <sip:127.0.0.1;r2=on
   ;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Via: SIP/2.0/UDP XX.XX.XX.250;branch=z9hG4bKd906.5531f5d10bd0fe3667091afe519d5f94.0..Via: SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;bra
   nch=z9hG4bKZ7GCaaKk;rport=5080..From: "41225017077" <sip:41225017077 at sip.adoovoice.com>;tag=0F8733E5-56B4B7B700066935-870F0700..To: <sip:00492271993120 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 222572
   206 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, PUBLISH, UPDATE, MESSAGE..Supported: replaces,100rel..P-Asserted-Identity: <sip:
   41225017077 at sip.adoovoice.com>..Authorization: Digest username="pbxprisnet", realm="sip.adoovoice.com", nonce="2231175255", uri="sip:00492271993120 at 77.72.169.129:5060;transport=udp", response="dac6cac
   8d25100ee03560bab867ba1be", algorithm=MD5..Content-Type: application/sdp..Content-Length: 265..Contact: <sip:ngcp-lb at XX.XX.XX.250:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=- 20036 2
   0036 IN IP4 10.164.124.97..s=SDP data..c=IN IP4 213.55.176.206..t=0 0..m=audio 11852 RTP/AVP 0 8 9 101..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:101 telephone-event/8
   000..a=sendrecv..a=ptime:20..a=direction:active..
############################################################################

Thank you for your help

Jephth? Feugn?



From mstorck at voipgate.com  Fri Feb  5 11:10:49 2016
From: mstorck at voipgate.com (Marc Storck)
Date: Fri, 5 Feb 2016 16:10:49 +0000
Subject: [Spce-user] MCID App issue
In-Reply-To: <56B46E8E.8030906@sipwise.com>
References: <634d081a-8463-4965-abbb-a282d8f21695@email.android.com>
 <2970CB78-9A94-41AB-8E04-63CC51B6C992@voipgate.com>
 <56B46E8E.8030906@sipwise.com>
Message-ID: <0DDF2E9C-9CDF-44A4-BF8C-FE17DE1EEF53@voipgate.com>

Great :-D

so please apply

:%s/is/was/g

to my last mail.

Regards,

Marc Storck


> On 05 Feb 2016, at 10:42, Daniel Grotti <dgrotti at sipwise.com> wrote:
> 
> Hi Marc,
> it's part of mr4.2.1 documentation.
> I introduced it when we noticed that was missing.
> 
> thanks.
> 
> DANIEL GROTTI
> Head of Customer Support
> Sipwise GmbH  <http://www.sipwise.com/>, Campus 21/Europaring F15
> AT-2345 Brunn am Gebirge
> 
> Phone:  +43(0)1 301 2032  <callto:+4313012032>
> Email:  dgrotti at sipwise.com  <mailto:dgrotti at sipwise.com>
> Website:  www.sipwise.com <http://www.sipwise.com/>
> Particulars according Austrian Companies Code paragraph 14
> "Sipwise GmbH" - Europaring F15 - 2345 Brunn am Gebirge
> FN:305595f, Commercial Court Vienna, ATU64002206
> 
> On 02/05/2016 10:36 AM, Marc Storck wrote:
>> Hello Daniel,
>> 
>> That step is missing in the documentation.
>> 
>> I?ll test tonight.
>> 
>> Regards,
>> 
>> Marc Storck
>> 
>> 
>>> On 05 Feb 2016, at 07:58, Daniel Grotti <dgrotti at sipwise.com> <mailto:dgrotti at sipwise.com> wrote:
>>> 
>>> Hi Marc,
>>> Did you flag the subscriber preferences MCID ? It should be in the Internal section.
>>> You should enable MCID there otherwise it won't work.
>>> 
>>> Daniel
>>> 
>>> On Feb 5, 2016 12:51 AM, Marc Storck <mstorck at voipgate.com> <mailto:mstorck at voipgate.com> wrote:
>>>> I just upgraded to mr4.2.1.
>>>> 
>>>> I followed the steps described in the documentation. My system was almost good, I was only missing the audio file in the sound set.
>>>> 
>>>> However the problem persists:
>>>> 
>>>> Feb  5 00:42:38 cusax (local7.notice) proxy[3552]: NOTICE: <script>: New request on proxy - M=INVITE R=sip:*57 at sld.tld;user=phone <mailto:R=sip:*57 at sld.tld;user=phone> F=sip:johndoe at sld.tld <mailto:F=sip:johndoe at sld.tld> T=sip:*57 at sld.tld;user=phone <mailto:T=sip:*57 at sld.tld;user=phone> IP=11.22.33.44:5732 (127.0.0.1:5060) ID=2639378387 at 11_22_33_44 UA='N510 IP PRO/42.210.00.000.000'
>>>> Feb  5 00:42:38 cusax (local7.notice) proxy[3552]: NOTICE: <script>: User-Provided CLI 'johndoe' taken from From-User - R=sip:*57 at sld.tld;user=phone <mailto:R=sip:*57 at sld.tld;user=phone> ID=2639378387 at 11_22_33_44 UA='N510 IP PRO/42.210.00.000.000'
>>>> Feb  5 00:42:38 cusax (local7.notice) proxy[3552]: NOTICE: <script>: User-provided CLI 'johndoe' rejected, using network-provided CLI '898910001201001' - R=sip:*57 at sld.tld;user=phone <mailto:R=sip:*57 at sld.tld;user=phone> ID=2639378387 at 11_22_33_44 UA='N510 IP PRO/42.210.00.000.000'
>>>> Feb  5 00:42:38 cusax (local7.notice) proxy[3552]: NOTICE: <script>: Setting '898910001201001 at sld.tld <mailto:898910001201001 at sld.tld>' as initiating user-provided CLI - R=sip:*57 at sld.tld;user=phone <mailto:R=sip:*57 at sld.tld;user=phone> ID=2639378387 at 11_22_33_44 UA='N510 IP PRO/42.210.00.000.000'
>>>> Feb  5 00:42:38 cusax (local7.notice) proxy[3552]: NOTICE: <script>: Setting '898910001201001 at sld.tld <mailto:898910001201001 at sld.tld>' as initiating network-provided CLI - R=sip:*57 at sld.tld;user=phone <mailto:R=sip:*57 at sld.tld;user=phone> ID=2639378387 at 11_22_33_44 UA='N510 IP PRO/42.210.00.000.000'
>>>> Feb  5 00:42:38 cusax (local7.notice) proxy[3552]: NOTICE: <script>: Rewriting called party '*57' to 'malicious_call' - R=sip:*57 at sld.tld;user=phone <mailto:R=sip:*57 at sld.tld;user=phone> ID=2639378387 at 11_22_33_44 UA='N510 IP PRO/42.210.00.000.000'
>>>> Feb  5 00:42:38 cusax (local7.err) proxy[3552]: ERROR: app_lua [app_lua_api.c:680]: app_lua_run(): error executing: del_dlg_profile (err: 2)
>>>> Feb  5 00:42:38 cusax (local7.err) proxy[3552]: ERROR: app_lua [app_lua_api.c:682]: app_lua_run(): error from Lua: /etc/kamailio/proxy/dlgcnt.lua:101: can't restore callid from $dlg_var(lua_dlg_callid): is null
>>>> Feb  5 00:42:38 cusax (local7.err) proxy[3552]: ERROR: <script>: Failed to decrease redis counters - R=sip:you at kamailio.org <mailto:R=sip:you at kamailio.org> ID=123 UA='<null>'
>>>> Feb  5 00:42:38 cusax (local7.notice) proxy[3552]: NOTICE: <script>: New request on proxy - M=ACK R=sip:*57 at sld.tld;user=phone <mailto:R=sip:*57 at sld.tld;user=phone> F=sip:johndoe at sld.tld <mailto:F=sip:johndoe at sld.tld> T=sip:*57 at sld.tld;user=phone <mailto:T=sip:*57 at sld.tld;user=phone> IP=11.22.33.44:5732 (127.0.0.1:5060) ID=2639378387 at 11_22_33_44 UA='N510 IP PRO/42.210.00.000.000'
>>>> 
>>>> Does anybody have an idea what might be the missing part?
>>>> 
>>>> Regards,
>>>> 
>>>> Marc
>>>> 
>>>> ________________________________________
>>>> From: Marc Storck
>>>> Sent: Friday, October 30, 2015 17:49
>>>> To: Kirill Solomko
>>>> Cc: spce-user at lists.sipwise.com <mailto:spce-user at lists.sipwise.com>
>>>> Subject: Re: [Spce-user] MCID App issue
>>>> 
>>>> So I set
>>>> 
>>>> store_recentcalls: ?yes'
>>>> 
>>>> followed by running
>>>> 
>>>> ngcpcfg apply
>>>> 
>>>> but the result is still quite the same:
>>>> 
>>>> Oct 30 17:45:08 cusax proxy[514]: NOTICE: <script>: Rewriting called party '*57' to 'malicious_call' - R=sip:*57 at sld.tld <mailto:R=sip:*57 at sld.tld> ID=OWU3ZmFiMDY5ZGE4ZGJkODE4ODdlMDhjMzg1MWFkYzc UA='Bria iOS release 3.4.4 stamp 31657'
>>>> Oct 30 17:45:08 cusax proxy[514]: ERROR: app_lua [app_lua_api.c:680]: app_lua_run(): error executing: del_dlg_profile (err: 2)
>>>> Oct 30 17:45:08 cusax proxy[514]: ERROR: app_lua [app_lua_api.c:682]: app_lua_run(): error from Lua: /etc/kamailio/proxy/dlgcnt.lua:101: can't restore callid from $dlg_var(lua_dlg_callid): is null
>>>> Oct 30 17:45:08 cusax proxy[514]: ERROR: <script>: Failed to decrease redis counters - R=sip:you at kamailio.org <mailto:R=sip:you at kamailio.org> ID=123 UA='<null>'
>>>> 
>>>> Regards,
>>>> 
>>>> Marc
>>>> 
>>>>> On 30 Oct 2015, at 17:42, Kirill Solomko <ksolomko at sipwise.com> <mailto:ksolomko at sipwise.com> wrote:
>>>>> 
>>>>> Hi Mark,
>>>>> 
>>>>> You should also enable ?recent calls? support in config.yml
>>>>> 
>>>>> kamailio:
>>>>>   proxy:
>>>>>     store_recentcalls: ?yes'
>>>>> 
>>>>>> On 30 Oct 2015, at 17:24, Marc Storck <mstorck at voipgate.com> <mailto:mstorck at voipgate.com> wrote:
>>>>>> 
>>>>>> Good evening,
>>>>>> 
>>>>>> I?m having this problem with the MCID app:
>>>>>> 
>>>>>> Oct 30 17:21:34 cusax proxy[23526]: NOTICE: <script>: Rewriting called party '*57' to 'malicious_call' - R=sip:*57 at sld.tld <mailto:R=sip:*57 at sld.tld> ID=YmE5NDYzOWMyMWE2NWY0MjE3YTMwYWRkMDVkMjcwOWI UA='Bria iOS release 3.4.4 stamp 31657'
>>>>>> Oct 30 17:21:34 cusax proxy[23526]: ERROR: app_lua [app_lua_api.c:680]: app_lua_run(): error executing: del_dlg_profile (err: 2)
>>>>>> Oct 30 17:21:34 cusax proxy[23526]: ERROR: app_lua [app_lua_api.c:682]: app_lua_run(): error from Lua: /etc/kamailio/proxy/dlgcnt.lua:101: can't restore callid from $dlg_var(lua_dlg_callid): is null
>>>>>> Oct 30 17:21:34 cusax proxy[23526]: ERROR: <script>: Failed to decrease redis counters - R=sip:you at kamailio.org <mailto:R=sip:you at kamailio.org> ID=123 UA='<null>?
>>>>>> 
>>>>>> I activated the MCID app in config.yml, are there any further changes required?
>>>>>> 
>>>>>> Regards,
>>>>>> 
>>>>>> Marc
>>>>>> _______________________________________________
>>>>>> Spce-user mailing list
>>>>>> Spce-user at lists.sipwise.com <mailto:Spce-user at lists.sipwise.com>
>>>>>> https://lists.sipwise.com/listinfo/spce-user <https://lists.sipwise.com/listinfo/spce-user>
>>>>> Kind regards,
>>>>> Kirill
>>>> _______________________________________________
>>>> Spce-user mailing list
>>>> Spce-user at lists.sipwise.com <mailto:Spce-user at lists.sipwise.com>
>>>> https://lists.sipwise.com/listinfo/spce-user <https://lists.sipwise.com/listinfo/spce-user>
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20160205/88976a35/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 841 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20160205/88976a35/attachment-0001.asc>

From agranig at sipwise.com  Fri Feb  5 11:12:01 2016
From: agranig at sipwise.com (Andreas Granig)
Date: Fri, 5 Feb 2016 17:12:01 +0100
Subject: [Spce-user] Trunk to voicetrading configuration
In-Reply-To: <56B4B8C1.5060203@prisnets.ch>
References: <56B4B8C1.5060203@prisnets.ch>
Message-ID: <56B4C9D1.1090008@sipwise.com>

Hi,

>From the trace you provided, it seems your request just times out, as
there is no reply at all from your peer. No idea if they do this because
you're not sending the 00000 prefix you mentioned.

Create a new rewrite rule set and put a rule like "^(.+)$" => "00000\1"
into the outbound callee rule and assign this rule set in the peer
preferences of your configured peering server.

Please read carefully the handbook provided with the CE installation,
specifically the configuration of peerings and peering rules.

Andreas

On 02/05/2016 03:59 PM, Jephth? Feugn? wrote:
> Hello,
> I've been trying for weeks to have my trunk to voicetrading working with
> no success. I also tried a sip trunk to my GSM gateway with the same
> result. No ringing to the calle side, and no sound no ringing tone by
> the caller side.
> 
> Can some one please can help me solve this problem?
> 
> Here is what I have during call with the command "ngrep sip" executed on
> the sipwise CE 4.2.1  server. Voicetrading is  expecting for premium
> route on their side, the number to be perpended with "00000",
> xx.xx.xx.250 is the IP address of my sipwise CE 4.2.1 server:
> 
> 
> XX.XX.XX.250:5060 -> 77.72.169.129:5060
>   INVITE sip:00492271993120 at 77.72.169.129:5060;transport=udp
> SIP/2.0..Record-Route:
> <sip:XX.XX.XX.250;r2=on;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Record-Route:
> <sip:127.0.0.1;r2=on
>   ;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Via:
> SIP/2.0/UDP
> XX.XX.XX.250;branch=z9hG4bKd906.5531f5d10bd0fe3667091afe519d5f94.0..Via:
> SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;bra
>   nch=z9hG4bKZ7GCaaKk;rport=5080..From: "41225017077"
> <sip:41225017077 at sip.adoovoice.com>;tag=0F8733E5-56B4B7B700066935-870F0700..To:
> <sip:00492271993120 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 222572
>   206 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE, PRACK, ACK,
> BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, PUBLISH, UPDATE,
> MESSAGE..Supported: replaces,100rel..P-Asserted-Identity: <sip:
>   41225017077 at sip.adoovoice.com>..Authorization: Digest
> username="pbxprisnet", realm="sip.adoovoice.com", nonce="2231175255",
> uri="sip:00492271993120 at 77.72.169.129:5060;transport=udp",
> response="dac6cac
>   8d25100ee03560bab867ba1be", algorithm=MD5..Content-Type:
> application/sdp..Content-Length: 265..Contact:
> <sip:ngcp-lb at XX.XX.XX.250:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=-
> 20036 2
>   0036 IN IP4 10.164.124.97..s=SDP data..c=IN IP4 213.55.176.206..t=0
> 0..m=audio 11852 RTP/AVP 0 8 9 101..a=rtpmap:0 PCMU/8000..a=rtpmap:8
> PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:101 telephone-event/8
>   000..a=sendrecv..a=ptime:20..a=direction:active..
> #####################
> U XX.XX.XX.250:5060 -> 77.72.169.129:5060
>   INVITE sip:00492271993120 at 77.72.169.129:5060;transport=udp
> SIP/2.0..Record-Route:
> <sip:XX.XX.XX.250;r2=on;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Record-Route:
> <sip:127.0.0.1;r2=on
>   ;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Via:
> SIP/2.0/UDP
> XX.XX.XX.250;branch=z9hG4bKd906.5531f5d10bd0fe3667091afe519d5f94.0..Via:
> SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;bra
>   nch=z9hG4bKZ7GCaaKk;rport=5080..From: "41225017077"
> <sip:41225017077 at sip.adoovoice.com>;tag=0F8733E5-56B4B7B700066935-870F0700..To:
> <sip:00492271993120 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 222572
>   206 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE, PRACK, ACK,
> BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, PUBLISH, UPDATE,
> MESSAGE..Supported: replaces,100rel..P-Asserted-Identity: <sip:
>   41225017077 at sip.adoovoice.com>..Authorization: Digest
> username="pbxprisnet", realm="sip.adoovoice.com", nonce="2231175255",
> uri="sip:00492271993120 at 77.72.169.129:5060;transport=udp",
> response="dac6cac
>   8d25100ee03560bab867ba1be", algorithm=MD5..Content-Type:
> application/sdp..Content-Length: 265..Contact:
> <sip:ngcp-lb at XX.XX.XX.250:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=-
> 20036 2
>   0036 IN IP4 10.164.124.97..s=SDP data..c=IN IP4 213.55.176.206..t=0
> 0..m=audio 11852 RTP/AVP 0 8 9 101..a=rtpmap:0 PCMU/8000..a=rtpmap:8
> PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:101 telephone-event/8
>   000..a=sendrecv..a=ptime:20..a=direction:active..
> #######################
> U XX.XX.XX.250:5060 -> 77.72.169.129:5060
>   INVITE sip:00492271993120 at 77.72.169.129:5060;transport=udp
> SIP/2.0..Record-Route:
> <sip:XX.XX.XX.250;r2=on;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Record-Route:
> <sip:127.0.0.1;r2=on
>   ;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Via:
> SIP/2.0/UDP
> XX.XX.XX.250;branch=z9hG4bKd906.5531f5d10bd0fe3667091afe519d5f94.0..Via:
> SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;bra
>   nch=z9hG4bKZ7GCaaKk;rport=5080..From: "41225017077"
> <sip:41225017077 at sip.adoovoice.com>;tag=0F8733E5-56B4B7B700066935-870F0700..To:
> <sip:00492271993120 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 222572
>   206 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE, PRACK, ACK,
> BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, PUBLISH, UPDATE,
> MESSAGE..Supported: replaces,100rel..P-Asserted-Identity: <sip:
>   41225017077 at sip.adoovoice.com>..Authorization: Digest
> username="pbxprisnet", realm="sip.adoovoice.com", nonce="2231175255",
> uri="sip:00492271993120 at 77.72.169.129:5060;transport=udp",
> response="dac6cac
>   8d25100ee03560bab867ba1be", algorithm=MD5..Content-Type:
> application/sdp..Content-Length: 265..Contact:
> <sip:ngcp-lb at XX.XX.XX.250:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=-
> 20036 2
>   0036 IN IP4 10.164.124.97..s=SDP data..c=IN IP4 213.55.176.206..t=0
> 0..m=audio 11852 RTP/AVP 0 8 9 101..a=rtpmap:0 PCMU/8000..a=rtpmap:8
> PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:101 telephone-event/8
>   000..a=sendrecv..a=ptime:20..a=direction:active..
> #########################################
> U XX.XX.XX.250:5060 -> 77.72.169.129:5060
>   INVITE sip:00492271993120 at 77.72.169.129:5060;transport=udp
> SIP/2.0..Record-Route:
> <sip:XX.XX.XX.250;r2=on;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Record-Route:
> <sip:127.0.0.1;r2=on
>   ;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Via:
> SIP/2.0/UDP
> XX.XX.XX.250;branch=z9hG4bKd906.5531f5d10bd0fe3667091afe519d5f94.0..Via:
> SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;bra
>   nch=z9hG4bKZ7GCaaKk;rport=5080..From: "41225017077"
> <sip:41225017077 at sip.adoovoice.com>;tag=0F8733E5-56B4B7B700066935-870F0700..To:
> <sip:00492271993120 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 222572
>   206 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE, PRACK, ACK,
> BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, PUBLISH, UPDATE,
> MESSAGE..Supported: replaces,100rel..P-Asserted-Identity: <sip:
>   41225017077 at sip.adoovoice.com>..Authorization: Digest
> username="pbxprisnet", realm="sip.adoovoice.com", nonce="2231175255",
> uri="sip:00492271993120 at 77.72.169.129:5060;transport=udp",
> response="dac6cac
>   8d25100ee03560bab867ba1be", algorithm=MD5..Content-Type:
> application/sdp..Content-Length: 265..Contact:
> <sip:ngcp-lb at XX.XX.XX.250:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=-
> 20036 2
>   0036 IN IP4 10.164.124.97..s=SDP data..c=IN IP4 213.55.176.206..t=0
> 0..m=audio 11852 RTP/AVP 0 8 9 101..a=rtpmap:0 PCMU/8000..a=rtpmap:8
> PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:101 telephone-event/8
>   000..a=sendrecv..a=ptime:20..a=direction:active..
> #################################################################################
> 
> U XX.XX.XX.250:5060 -> 77.72.169.129:5060
>   INVITE sip:00492271993120 at 77.72.169.129:5060;transport=udp
> SIP/2.0..Record-Route:
> <sip:XX.XX.XX.250;r2=on;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Record-Route:
> <sip:127.0.0.1;r2=on
>   ;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Via:
> SIP/2.0/UDP
> XX.XX.XX.250;branch=z9hG4bKd906.5531f5d10bd0fe3667091afe519d5f94.0..Via:
> SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;bra
>   nch=z9hG4bKZ7GCaaKk;rport=5080..From: "41225017077"
> <sip:41225017077 at sip.adoovoice.com>;tag=0F8733E5-56B4B7B700066935-870F0700..To:
> <sip:00492271993120 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 222572
>   206 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE, PRACK, ACK,
> BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, PUBLISH, UPDATE,
> MESSAGE..Supported: replaces,100rel..P-Asserted-Identity: <sip:
>   41225017077 at sip.adoovoice.com>..Authorization: Digest
> username="pbxprisnet", realm="sip.adoovoice.com", nonce="2231175255",
> uri="sip:00492271993120 at 77.72.169.129:5060;transport=udp",
> response="dac6cac
>   8d25100ee03560bab867ba1be", algorithm=MD5..Content-Type:
> application/sdp..Content-Length: 265..Contact:
> <sip:ngcp-lb at XX.XX.XX.250:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=-
> 20036 2
>   0036 IN IP4 10.164.124.97..s=SDP data..c=IN IP4 213.55.176.206..t=0
> 0..m=audio 11852 RTP/AVP 0 8 9 101..a=rtpmap:0 PCMU/8000..a=rtpmap:8
> PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:101 telephone-event/8
>   000..a=sendrecv..a=ptime:20..a=direction:active..
> ############################################################################
> 
> 
> Thank you for your help
> 
> Jephth? Feugn?
> 
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user


From dgrotti at sipwise.com  Fri Feb  5 11:15:41 2016
From: dgrotti at sipwise.com (Daniel Grotti)
Date: Fri, 05 Feb 2016 17:15:41 +0100
Subject: [Spce-user] MCID App issue
In-Reply-To: <0DDF2E9C-9CDF-44A4-BF8C-FE17DE1EEF53@voipgate.com>
Message-ID: <deb9b9dc-af14-4fa5-882c-9ca6097ed06d@email.android.com>

An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20160205/b64c93c8/attachment-0001.html>

From me at nevian.org  Fri Feb  5 13:09:54 2016
From: me at nevian.org (Serge Yuriev)
Date: Fri, 5 Feb 2016 21:09:54 +0300
Subject: [Spce-user] Trunk to voicetrading configuration
In-Reply-To: <56B4B8C1.5060203@prisnets.ch>
References: <56B4B8C1.5060203@prisnets.ch>
Message-ID: <C0EFEFFE-2D76-4177-A2AB-72ECE0151145@nevian.org>

Hello,

You said you can't use your GSM-gw also..
Looks like firewall issue to me.
Are you able to just ping your destinations and back?

-- 
Wbr, Serge via mobile

05.02.2016, 17:59, "Jephth? Feugn?" <j.feugne at prisnets.ch>:
> 
> Hello,
> I've been trying for weeks to have my trunk to voicetrading working with no success. I also tried a sip trunk to my GSM gateway with the same
> result. No ringing to the calle side, and no sound no ringing tone by the caller side.
> 
> Can some one please can help me solve this problem?
> 
> Here is what I have during call with the command "ngrep sip" executed on the sipwise CE 4.2.1 server. Voicetrading is expecting for premium
> route on their side, the number to be perpended with "00000", xx.xx.xx.250 is the IP address of my sipwise CE 4.2.1 server:
> 
> 
> XX.XX.XX.250:5060 -> 77.72.169.129:5060
>    INVITE sip:00492271993120 at 77.72.169.129:5060;transport=udp SIP/2.0..Record-Route: <sip:XX.XX.XX.250;r2=on;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Record-Route: <sip:127.0.0.1;r2=on
>    ;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Via: SIP/2.0/UDP XX.XX.XX.250;branch=z9hG4bKd906.5531f5d10bd0fe3667091afe519d5f94.0..Via: SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;bra
>    nch=z9hG4bKZ7GCaaKk;rport=5080..From: "41225017077" <sip:41225017077 at sip.adoovoice.com>;tag=0F8733E5-56B4B7B700066935-870F0700..To: <sip:00492271993120 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 222572
>    206 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, PUBLISH, UPDATE, MESSAGE..Supported: replaces,100rel..P-Asserted-Identity: <sip:
>    41225017077 at sip.adoovoice.com>..Authorization: Digest username="pbxprisnet", realm="sip.adoovoice.com", nonce="2231175255", uri="sip:00492271993120 at 77.72.169.129:5060;transport=udp", response="dac6cac
>    8d25100ee03560bab867ba1be", algorithm=MD5..Content-Type: application/sdp..Content-Length: 265..Contact: <sip:ngcp-lb at XX.XX.XX.250:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=- 20036 2
>    0036 IN IP4 10.164.124.97..s=SDP data..c=IN IP4 213.55.176.206..t=0 0..m=audio 11852 RTP/AVP 0 8 9 101..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:101 telephone-event/8
>    000..a=sendrecv..a=ptime:20..a=direction:active..
> #####################
> U XX.XX.XX.250:5060 -> 77.72.169.129:5060
>    INVITE sip:00492271993120 at 77.72.169.129:5060;transport=udp SIP/2.0..Record-Route: <sip:XX.XX.XX.250;r2=on;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Record-Route: <sip:127.0.0.1;r2=on
>    ;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Via: SIP/2.0/UDP XX.XX.XX.250;branch=z9hG4bKd906.5531f5d10bd0fe3667091afe519d5f94.0..Via: SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;bra
>    nch=z9hG4bKZ7GCaaKk;rport=5080..From: "41225017077" <sip:41225017077 at sip.adoovoice.com>;tag=0F8733E5-56B4B7B700066935-870F0700..To: <sip:00492271993120 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 222572
>    206 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, PUBLISH, UPDATE, MESSAGE..Supported: replaces,100rel..P-Asserted-Identity: <sip:
>    41225017077 at sip.adoovoice.com>..Authorization: Digest username="pbxprisnet", realm="sip.adoovoice.com", nonce="2231175255", uri="sip:00492271993120 at 77.72.169.129:5060;transport=udp", response="dac6cac
>    8d25100ee03560bab867ba1be", algorithm=MD5..Content-Type: application/sdp..Content-Length: 265..Contact: <sip:ngcp-lb at XX.XX.XX.250:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=- 20036 2
>    0036 IN IP4 10.164.124.97..s=SDP data..c=IN IP4 213.55.176.206..t=0 0..m=audio 11852 RTP/AVP 0 8 9 101..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:101 telephone-event/8
>    000..a=sendrecv..a=ptime:20..a=direction:active..
> #######################
> U XX.XX.XX.250:5060 -> 77.72.169.129:5060
>    INVITE sip:00492271993120 at 77.72.169.129:5060;transport=udp SIP/2.0..Record-Route: <sip:XX.XX.XX.250;r2=on;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Record-Route: <sip:127.0.0.1;r2=on
>    ;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Via: SIP/2.0/UDP XX.XX.XX.250;branch=z9hG4bKd906.5531f5d10bd0fe3667091afe519d5f94.0..Via: SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;bra
>    nch=z9hG4bKZ7GCaaKk;rport=5080..From: "41225017077" <sip:41225017077 at sip.adoovoice.com>;tag=0F8733E5-56B4B7B700066935-870F0700..To: <sip:00492271993120 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 222572
>    206 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, PUBLISH, UPDATE, MESSAGE..Supported: replaces,100rel..P-Asserted-Identity: <sip:
>    41225017077 at sip.adoovoice.com>..Authorization: Digest username="pbxprisnet", realm="sip.adoovoice.com", nonce="2231175255", uri="sip:00492271993120 at 77.72.169.129:5060;transport=udp", response="dac6cac
>    8d25100ee03560bab867ba1be", algorithm=MD5..Content-Type: application/sdp..Content-Length: 265..Contact: <sip:ngcp-lb at XX.XX.XX.250:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=- 20036 2
>    0036 IN IP4 10.164.124.97..s=SDP data..c=IN IP4 213.55.176.206..t=0 0..m=audio 11852 RTP/AVP 0 8 9 101..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:101 telephone-event/8
>    000..a=sendrecv..a=ptime:20..a=direction:active..
> #########################################
> U XX.XX.XX.250:5060 -> 77.72.169.129:5060
>    INVITE sip:00492271993120 at 77.72.169.129:5060;transport=udp SIP/2.0..Record-Route: <sip:XX.XX.XX.250;r2=on;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Record-Route: <sip:127.0.0.1;r2=on
>    ;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Via: SIP/2.0/UDP XX.XX.XX.250;branch=z9hG4bKd906.5531f5d10bd0fe3667091afe519d5f94.0..Via: SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;bra
>    nch=z9hG4bKZ7GCaaKk;rport=5080..From: "41225017077" <sip:41225017077 at sip.adoovoice.com>;tag=0F8733E5-56B4B7B700066935-870F0700..To: <sip:00492271993120 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 222572
>    206 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, PUBLISH, UPDATE, MESSAGE..Supported: replaces,100rel..P-Asserted-Identity: <sip:
>    41225017077 at sip.adoovoice.com>..Authorization: Digest username="pbxprisnet", realm="sip.adoovoice.com", nonce="2231175255", uri="sip:00492271993120 at 77.72.169.129:5060;transport=udp", response="dac6cac
>    8d25100ee03560bab867ba1be", algorithm=MD5..Content-Type: application/sdp..Content-Length: 265..Contact: <sip:ngcp-lb at XX.XX.XX.250:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=- 20036 2
>    0036 IN IP4 10.164.124.97..s=SDP data..c=IN IP4 213.55.176.206..t=0 0..m=audio 11852 RTP/AVP 0 8 9 101..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:101 telephone-event/8
>    000..a=sendrecv..a=ptime:20..a=direction:active..
> #################################################################################
> U XX.XX.XX.250:5060 -> 77.72.169.129:5060
>    INVITE sip:00492271993120 at 77.72.169.129:5060;transport=udp SIP/2.0..Record-Route: <sip:XX.XX.XX.250;r2=on;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Record-Route: <sip:127.0.0.1;r2=on
>    ;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Via: SIP/2.0/UDP XX.XX.XX.250;branch=z9hG4bKd906.5531f5d10bd0fe3667091afe519d5f94.0..Via: SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;bra
>    nch=z9hG4bKZ7GCaaKk;rport=5080..From: "41225017077" <sip:41225017077 at sip.adoovoice.com>;tag=0F8733E5-56B4B7B700066935-870F0700..To: <sip:00492271993120 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 222572
>    206 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, PUBLISH, UPDATE, MESSAGE..Supported: replaces,100rel..P-Asserted-Identity: <sip:
>    41225017077 at sip.adoovoice.com>..Authorization: Digest username="pbxprisnet", realm="sip.adoovoice.com", nonce="2231175255", uri="sip:00492271993120 at 77.72.169.129:5060;transport=udp", response="dac6cac
>    8d25100ee03560bab867ba1be", algorithm=MD5..Content-Type: application/sdp..Content-Length: 265..Contact: <sip:ngcp-lb at XX.XX.XX.250:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=- 20036 2
>    0036 IN IP4 10.164.124.97..s=SDP data..c=IN IP4 213.55.176.206..t=0 0..m=audio 11852 RTP/AVP 0 8 9 101..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:101 telephone-event/8
>    000..a=sendrecv..a=ptime:20..a=direction:active..
> ############################################################################
> 
> Thank you for your help
> 
> Jephth? Feugn?
> 
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
> 


From j.feugne at prisnets.ch  Fri Feb  5 13:15:12 2016
From: j.feugne at prisnets.ch (=?UTF-8?Q?Jephth=c3=a9_Feugn=c3=a9?=)
Date: Fri, 5 Feb 2016 19:15:12 +0100
Subject: [Spce-user] Trunk to voicetrading configuration
In-Reply-To: <56B4C9D1.1090008@sipwise.com>
References: <56B4B8C1.5060203@prisnets.ch> <56B4C9D1.1090008@sipwise.com>
Message-ID: <56B4E6B0.5090307@prisnets.ch>

Hi,
Thank you for your reply. I unfortunately disable one of my rewrite rule 
by the time I made the call. I Cross check the rules once more and here 
is the result when I place call. still no ring both on the caller and 
callee  side:


        U xx.xx.xx.2:5060 -> 77.72.169.129:5060
                   INVITE
        sip:0000041227312221 at 77.72.169.129:5060;transport=udp
        SIP/2.0..Record-Route:
        <sip:xx.xx.xx.2;r2=on;lr=on;ftag=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>..Record-Route:
        <sip:127.0.0.1;r2=
        on;lr=on;ftag=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>..Via:
        SIP/2.0/UDP
        xx.xx.xx.2;branch=z9hG4bKe854.61a0e861a7f1d69a32327173a5932390.0..Via:
        SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;b
        ranch=z9hG4bKtn6UJa1a;rport=5080..From: "41225017077"
        <sip:41225017077 at sip.adoovoice.com>;tag=16EE36B8-56B4E5C400006FEF-86FEF700..To:
        <sip:0000041227312221 at 77.72.169.129>..CSeq: 10 INVITE..Call-ID: 50
        4974996 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE,
        PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE,
        PUBLISH, UPDATE, MESSAGE..Supported:
        replaces,100rel..P-Asserted-Identity: <
        sip:41225017077 at sip.adoovoice.com>..Content-Type:
        application/sdp..Content-Length: 265..Contact:
        <sip:ngcp-lb at xx.xx.xx.2:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=-
        20054 20054 IN
                    IP4 10.164.124.97..s=SDP data..c=IN IP4
        213.55.176.206..t=0 0..m=audio 11888 RTP/AVP 0 8 9
        101..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:9
        G722/8000..a=rtpmap:101 telephone-event/8000..a=
        sendrecv..a=ptime:20..a=direction:active..
                 ##
                 U 77.72.169.129:5060 -> xx.xx.xx.2:5060
                   SIP/2.0 401 Unauthorized..Via: SIP/2.0/UDP
        xx.xx.xx.2:5060;branch=z9hG4bKe854.61a0e861a7f1d69a32327173a5932390.0..Via:
        SIP/2.0/UDP
        127.0.0.1:5080;received=127.0.0.1;branch=z9hG4bKtn6UJa1a;rport=508
                   0..From: "41225017077"
        <sip:41225017077 at sip.adoovoice.com>;tag=16EE36B8-56B4E5C400006FEF-86FEF700..To:
        <sip:0000041227312221 at 77.72.169.129>..Contact:
        sip:0000041227312221 at 77.72.169.129:5060..Call-ID:
        504974996 at 10.20.12.202_b2b-1..CSeq: 10 INVITE..Server: (Very
        nice Sip Registrar/Proxy Server)..Allow:
        ACK,BYE,CANCEL,INVITE,REGISTER,OPTIONS,INFO,MESSAGE..Record-route:
        <sip:xx.xx.xx.2;r2=on;lr;fta
        g=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>,<sip:127.0.0.1;r2=on;lr;ftag=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>..WWW-Authenticate:
        Digest realm="sip.adoovoice.com",nonce="2242964208",algo
                   rithm=MD5..Content-Length: 0....
                 #
                 U xx.xx.xx.2:5060 -> 77.72.169.129:5060
                   ACK
        sip:0000041227312221 at 77.72.169.129:5060;transport=udp
        SIP/2.0..Max-Forwards: 70..Record-Route:
        <sip:xx.xx.xx.2;r2=on;lr=on;ftag=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>..Record-Route:
        <si
        p:127.0.0.1;r2=on;lr=on;ftag=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>..Via:
        SIP/2.0/UDP
        xx.xx.xx.2;branch=z9hG4bKe854.61a0e861a7f1d69a32327173a5932390.0..Via:
        SIP/2.0/UDP 127.0.0.1:5080;recei
        ved=127.0.0.1;branch=z9hG4bKtn6UJa1a;rport=5080..From:
        "41225017077"
        <sip:41225017077 at sip.adoovoice.com>;tag=16EE36B8-56B4E5C400006FEF-86FEF700..To:
        <sip:0000041227312221 at 77.72.169.129>..Call-ID: 5049
        74996 at 10.20.12.202_b2b-1..CSeq: 10 ACK..Content-Length: 0....
                 #
                 U xx.xx.xx.2:5060 -> 77.72.169.129:5060
                   INVITE
        sip:0000041227312221 at 77.72.169.129:5060;transport=udp
        SIP/2.0..Record-Route:
        <sip:xx.xx.xx.2;r2=on;lr=on;ftag=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>..Record-Route:
        <sip:127.0.0.1;r2=
        on;lr=on;ftag=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>..Via:
        SIP/2.0/UDP
        xx.xx.xx.2;branch=z9hG4bKf854.44da301080c743aeec10ba45573ba2e4.0..Via:
        SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;b
        ranch=z9hG4bKkKgwgaE0;rport=5080..From: "41225017077"
        <sip:41225017077 at sip.adoovoice.com>;tag=16EE36B8-56B4E5C400006FEF-86FEF700..To:
        <sip:0000041227312221 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 50
        4974996 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE,
        PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE,
        PUBLISH, UPDATE, MESSAGE..Supported:
        replaces,100rel..P-Asserted-Identity: <
        sip:41225017077 at sip.adoovoice.com>..Authorization: Digest
        username="pbxprisnet", realm="sip.adoovoice.com",
        nonce="2242964208",
        uri="sip:0000041227312221 at 77.72.169.129:5060;transport=udp",
        response="9
        53a2ba986e16d9d2c3564149681dd58", algorithm=MD5..Content-Type:
        application/sdp..Content-Length: 265..Contact:
        <sip:ngcp-lb at xx.xx.xx.2:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=-
        2
                   0054 20054 IN IP4 10.164.124.97..s=SDP data..c=IN IP4
        213.55.176.206..t=0 0..m=audio 11888 RTP/AVP 0 8 9
        101..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:9
        G722/8000..a=rtpmap:101 telephone-e
        vent/8000..a=sendrecv..a=ptime:20..a=direction:active..
                 ########################
                 U xx.xx.xx.2:5060 -> 77.72.169.129:5060
                   INVITE
        sip:0000041227312221 at 77.72.169.129:5060;transport=udp
        SIP/2.0..Record-Route:
        <sip:xx.xx.xx.2;r2=on;lr=on;ftag=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>..Record-Route:
        <sip:127.0.0.1;r2=
        on;lr=on;ftag=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>..Via:
        SIP/2.0/UDP
        xx.xx.xx.2;branch=z9hG4bKf854.44da301080c743aeec10ba45573ba2e4.0..Via:
        SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;b
        ranch=z9hG4bKkKgwgaE0;rport=5080..From: "41225017077"
        <sip:41225017077 at sip.adoovoice.com>;tag=16EE36B8-56B4E5C400006FEF-86FEF700..To:
        <sip:0000041227312221 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 50
        4974996 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE,
        PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE,
        PUBLISH, UPDATE, MESSAGE..Supported:
        replaces,100rel..P-Asserted-Identity: <
        sip:41225017077 at sip.adoovoice.com>..Authorization: Digest
        username="pbxprisnet", realm="sip.adoovoice.com",
        nonce="2242964208",
        uri="sip:0000041227312221 at 77.72.169.129:5060;transport=udp",
        response="9
        53a2ba986e16d9d2c3564149681dd58", algorithm=MD5..Content-Type:
        application/sdp..Content-Length: 265..Contact:
        <sip:ngcp-lb at xx.xx.xx.2:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=-
        2
                   0054 20054 IN IP4 10.164.124.97..s=SDP data..c=IN IP4
        213.55.176.206..t=0 0..m=audio 11888 RTP/AVP 0 8 9
        101..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:9
        G722/8000..a=rtpmap:101 telephone-e
        vent/8000..a=sendrecv..a=ptime:20..a=direction:active..
                 #########################
                 U xx.xx.xx.2:5060 -> 77.72.169.129:5060
                   INVITE
        sip:0000041227312221 at 77.72.169.129:5060;transport=udp
        SIP/2.0..Record-Route:
        <sip:xx.xx.xx.2;r2=on;lr=on;ftag=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>..Record-Route:
        <sip:127.0.0.1;r2=
        on;lr=on;ftag=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>..Via:
        SIP/2.0/UDP
        xx.xx.xx.2;branch=z9hG4bKf854.44da301080c743aeec10ba45573ba2e4.0..Via:
        SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;b
        ranch=z9hG4bKkKgwgaE0;rport=5080..From: "41225017077"
        <sip:41225017077 at sip.adoovoice.com>;tag=16EE36B8-56B4E5C400006FEF-86FEF700..To:
        <sip:0000041227312221 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 50
        4974996 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE,
        PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE,
        PUBLISH, UPDATE, MESSAGE..Supported:
        replaces,100rel..P-Asserted-Identity: <
        sip:41225017077 at sip.adoovoice.com>..Authorization: Digest
        username="pbxprisnet", realm="sip.adoovoice.com",
        nonce="2242964208",
        uri="sip:0000041227312221 at 77.72.169.129:5060;transport=udp",
        response="9
        53a2ba986e16d9d2c3564149681dd58", algorithm=MD5..Content-Type:
        application/sdp..Content-Length: 265..Contact:
        <sip:ngcp-lb at xx.xx.xx.2:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=-
        2
                   0054 20054 IN IP4 10.164.124.97..s=SDP data..c=IN IP4
        213.55.176.206..t=0 0..m=audio 11888 RTP/AVP 0 8 9
        101..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:9
        G722/8000..a=rtpmap:101 telephone-e
        vent/8000..a=sendrecv..a=ptime:20..a=direction:active..
        #############################################
                 U xx.xx.xx.2:5060 -> 77.72.169.129:5060
                   INVITE
        sip:0000041227312221 at 77.72.169.129:5060;transport=udp
        SIP/2.0..Record-Route:
        <sip:xx.xx.xx.2;r2=on;lr=on;ftag=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>..Record-Route:
        <sip:127.0.0.1;r2=
        on;lr=on;ftag=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>..Via:
        SIP/2.0/UDP
        xx.xx.xx.2;branch=z9hG4bKf854.44da301080c743aeec10ba45573ba2e4.0..Via:
        SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;b
        ranch=z9hG4bKkKgwgaE0;rport=5080..From: "41225017077"
        <sip:41225017077 at sip.adoovoice.com>;tag=16EE36B8-56B4E5C400006FEF-86FEF700..To:
        <sip:0000041227312221 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 50
        4974996 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE,
        PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE,
        PUBLISH, UPDATE, MESSAGE..Supported:
        replaces,100rel..P-Asserted-Identity: <
        sip:41225017077 at sip.adoovoice.com>..Authorization: Digest
        username="pbxprisnet", realm="sip.adoovoice.com",
        nonce="2242964208",
        uri="sip:0000041227312221 at 77.72.169.129:5060;transport=udp",
        response="9
        53a2ba986e16d9d2c3564149681dd58", algorithm=MD5..Content-Type:
        application/sdp..Content-Length: 265..Contact:
        <sip:ngcp-lb at xx.xx.xx.2:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=-
        2
                   0054 20054 IN IP4 10.164.124.97..s=SDP data..c=IN IP4
        213.55.176.206..t=0 0..m=audio 11888 RTP/AVP 0 8 9
        101..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:9
        G722/8000..a=rtpmap:101 telephone-e
        vent/8000..a=sendrecv..a=ptime:20..a=direction:active..
        #################################################################################
                 U xx.xx.xx.2:5060 -> 77.72.169.129:5060
                   INVITE
        sip:0000041227312221 at 77.72.169.129:5060;transport=udp
        SIP/2.0..Record-Route:
        <sip:xx.xx.xx.2;r2=on;lr=on;ftag=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>..Record-Route:
        <sip:127.0.0.1;r2=
        on;lr=on;ftag=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>..Via:
        SIP/2.0/UDP
        xx.xx.xx.2;branch=z9hG4bKf854.44da301080c743aeec10ba45573ba2e4.0..Via:
        SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;b
        ranch=z9hG4bKkKgwgaE0;rport=5080..From: "41225017077"
        <sip:41225017077 at sip.adoovoice.com>;tag=16EE36B8-56B4E5C400006FEF-86FEF700..To:
        <sip:0000041227312221 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 50
        4974996 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE,
        PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE,
        PUBLISH, UPDATE, MESSAGE..Supported:
        replaces,100rel..P-Asserted-Identity: <
        sip:41225017077 at sip.adoovoice.com>..Authorization: Digest
        username="pbxprisnet", realm="sip.adoovoice.com",
        nonce="2242964208",
        uri="sip:0000041227312221 at 77.72.169.129:5060;transport=udp",
        response="9
        53a2ba986e16d9d2c3564149681dd58", algorithm=MD5..Content-Type:
        application/sdp..Content-Length: 265..Contact:
        <sip:ngcp-lb at xx.xx.xx.2:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=-
        2
                   0054 20054 IN IP4 10.164.124.97..s=SDP data..c=IN IP4
        213.55.176.206..t=0 0..m=audio 11888 RTP/AVP 0 8 9
        101..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:9
        G722/8000..a=rtpmap:101 telephone-e
        vent/8000..a=sendrecv..a=ptime:20..a=direction:active..
        ################################################################################################
                 T 213.55.176.206:31002 -> xx.xx.xx.2:5060 [AP]
                   CANCEL sip:0227312221 at sip.adoovoice.com:5060
        SIP/2.0..Via: SIP/2.0/TCP
        10.20.12.202:5063;branch=z9hG4bK2530177975..From: "balmer"
        <sip:balmer at sip.adoovoice.com>;tag=801761386..To:
        <sip:0227312221 at sip.
                   adoovoice.com>..Call-ID:
        504974996 at 10.20.12.202..CSeq: 2 CANCEL..Max-Forwards:
        70..User-Agent: Yealink SIP-W52P 25.73.0.40..Content-Length: 0....
                 #



Le 05. 02. 16 17:12, Andreas Granig a ?crit :
> Hi,
>
>  From the trace you provided, it seems your request just times out, as
> there is no reply at all from your peer. No idea if they do this because
> you're not sending the 00000 prefix you mentioned.
>
> Create a new rewrite rule set and put a rule like "^(.+)$" => "00000\1"
> into the outbound callee rule and assign this rule set in the peer
> preferences of your configured peering server.
>
> Please read carefully the handbook provided with the CE installation,
> specifically the configuration of peerings and peering rules.
>
> Andreas
>
> On 02/05/2016 03:59 PM, Jephth? Feugn? wrote:
>> Hello,
>> I've been trying for weeks to have my trunk to voicetrading working with
>> no success. I also tried a sip trunk to my GSM gateway with the same
>> result. No ringing to the calle side, and no sound no ringing tone by
>> the caller side.
>>
>> Can some one please can help me solve this problem?
>>
>> Here is what I have during call with the command "ngrep sip" executed on
>> the sipwise CE 4.2.1  server. Voicetrading is  expecting for premium
>> route on their side, the number to be perpended with "00000",
>> xx.xx.xx.250 is the IP address of my sipwise CE 4.2.1 server:
>>
>>
>> XX.XX.XX.250:5060 -> 77.72.169.129:5060
>>    INVITE sip:00492271993120 at 77.72.169.129:5060;transport=udp
>> SIP/2.0..Record-Route:
>> <sip:XX.XX.XX.250;r2=on;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Record-Route:
>> <sip:127.0.0.1;r2=on
>>    ;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Via:
>> SIP/2.0/UDP
>> XX.XX.XX.250;branch=z9hG4bKd906.5531f5d10bd0fe3667091afe519d5f94.0..Via:
>> SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;bra
>>    nch=z9hG4bKZ7GCaaKk;rport=5080..From: "41225017077"
>> <sip:41225017077 at sip.adoovoice.com>;tag=0F8733E5-56B4B7B700066935-870F0700..To:
>> <sip:00492271993120 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 222572
>>    206 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE, PRACK, ACK,
>> BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, PUBLISH, UPDATE,
>> MESSAGE..Supported: replaces,100rel..P-Asserted-Identity: <sip:
>>    41225017077 at sip.adoovoice.com>..Authorization: Digest
>> username="pbxprisnet", realm="sip.adoovoice.com", nonce="2231175255",
>> uri="sip:00492271993120 at 77.72.169.129:5060;transport=udp",
>> response="dac6cac
>>    8d25100ee03560bab867ba1be", algorithm=MD5..Content-Type:
>> application/sdp..Content-Length: 265..Contact:
>> <sip:ngcp-lb at XX.XX.XX.250:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=-
>> 20036 2
>>    0036 IN IP4 10.164.124.97..s=SDP data..c=IN IP4 213.55.176.206..t=0
>> 0..m=audio 11852 RTP/AVP 0 8 9 101..a=rtpmap:0 PCMU/8000..a=rtpmap:8
>> PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:101 telephone-event/8
>>    000..a=sendrecv..a=ptime:20..a=direction:active..
>> #####################
>> U XX.XX.XX.250:5060 -> 77.72.169.129:5060
>>    INVITE sip:00492271993120 at 77.72.169.129:5060;transport=udp
>> SIP/2.0..Record-Route:
>> <sip:XX.XX.XX.250;r2=on;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Record-Route:
>> <sip:127.0.0.1;r2=on
>>    ;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Via:
>> SIP/2.0/UDP
>> XX.XX.XX.250;branch=z9hG4bKd906.5531f5d10bd0fe3667091afe519d5f94.0..Via:
>> SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;bra
>>    nch=z9hG4bKZ7GCaaKk;rport=5080..From: "41225017077"
>> <sip:41225017077 at sip.adoovoice.com>;tag=0F8733E5-56B4B7B700066935-870F0700..To:
>> <sip:00492271993120 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 222572
>>    206 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE, PRACK, ACK,
>> BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, PUBLISH, UPDATE,
>> MESSAGE..Supported: replaces,100rel..P-Asserted-Identity: <sip:
>>    41225017077 at sip.adoovoice.com>..Authorization: Digest
>> username="pbxprisnet", realm="sip.adoovoice.com", nonce="2231175255",
>> uri="sip:00492271993120 at 77.72.169.129:5060;transport=udp",
>> response="dac6cac
>>    8d25100ee03560bab867ba1be", algorithm=MD5..Content-Type:
>> application/sdp..Content-Length: 265..Contact:
>> <sip:ngcp-lb at XX.XX.XX.250:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=-
>> 20036 2
>>    0036 IN IP4 10.164.124.97..s=SDP data..c=IN IP4 213.55.176.206..t=0
>> 0..m=audio 11852 RTP/AVP 0 8 9 101..a=rtpmap:0 PCMU/8000..a=rtpmap:8
>> PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:101 telephone-event/8
>>    000..a=sendrecv..a=ptime:20..a=direction:active..
>> #######################
>> U XX.XX.XX.250:5060 -> 77.72.169.129:5060
>>    INVITE sip:00492271993120 at 77.72.169.129:5060;transport=udp
>> SIP/2.0..Record-Route:
>> <sip:XX.XX.XX.250;r2=on;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Record-Route:
>> <sip:127.0.0.1;r2=on
>>    ;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Via:
>> SIP/2.0/UDP
>> XX.XX.XX.250;branch=z9hG4bKd906.5531f5d10bd0fe3667091afe519d5f94.0..Via:
>> SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;bra
>>    nch=z9hG4bKZ7GCaaKk;rport=5080..From: "41225017077"
>> <sip:41225017077 at sip.adoovoice.com>;tag=0F8733E5-56B4B7B700066935-870F0700..To:
>> <sip:00492271993120 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 222572
>>    206 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE, PRACK, ACK,
>> BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, PUBLISH, UPDATE,
>> MESSAGE..Supported: replaces,100rel..P-Asserted-Identity: <sip:
>>    41225017077 at sip.adoovoice.com>..Authorization: Digest
>> username="pbxprisnet", realm="sip.adoovoice.com", nonce="2231175255",
>> uri="sip:00492271993120 at 77.72.169.129:5060;transport=udp",
>> response="dac6cac
>>    8d25100ee03560bab867ba1be", algorithm=MD5..Content-Type:
>> application/sdp..Content-Length: 265..Contact:
>> <sip:ngcp-lb at XX.XX.XX.250:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=-
>> 20036 2
>>    0036 IN IP4 10.164.124.97..s=SDP data..c=IN IP4 213.55.176.206..t=0
>> 0..m=audio 11852 RTP/AVP 0 8 9 101..a=rtpmap:0 PCMU/8000..a=rtpmap:8
>> PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:101 telephone-event/8
>>    000..a=sendrecv..a=ptime:20..a=direction:active..
>> #########################################
>> U XX.XX.XX.250:5060 -> 77.72.169.129:5060
>>    INVITE sip:00492271993120 at 77.72.169.129:5060;transport=udp
>> SIP/2.0..Record-Route:
>> <sip:XX.XX.XX.250;r2=on;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Record-Route:
>> <sip:127.0.0.1;r2=on
>>    ;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Via:
>> SIP/2.0/UDP
>> XX.XX.XX.250;branch=z9hG4bKd906.5531f5d10bd0fe3667091afe519d5f94.0..Via:
>> SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;bra
>>    nch=z9hG4bKZ7GCaaKk;rport=5080..From: "41225017077"
>> <sip:41225017077 at sip.adoovoice.com>;tag=0F8733E5-56B4B7B700066935-870F0700..To:
>> <sip:00492271993120 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 222572
>>    206 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE, PRACK, ACK,
>> BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, PUBLISH, UPDATE,
>> MESSAGE..Supported: replaces,100rel..P-Asserted-Identity: <sip:
>>    41225017077 at sip.adoovoice.com>..Authorization: Digest
>> username="pbxprisnet", realm="sip.adoovoice.com", nonce="2231175255",
>> uri="sip:00492271993120 at 77.72.169.129:5060;transport=udp",
>> response="dac6cac
>>    8d25100ee03560bab867ba1be", algorithm=MD5..Content-Type:
>> application/sdp..Content-Length: 265..Contact:
>> <sip:ngcp-lb at XX.XX.XX.250:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=-
>> 20036 2
>>    0036 IN IP4 10.164.124.97..s=SDP data..c=IN IP4 213.55.176.206..t=0
>> 0..m=audio 11852 RTP/AVP 0 8 9 101..a=rtpmap:0 PCMU/8000..a=rtpmap:8
>> PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:101 telephone-event/8
>>    000..a=sendrecv..a=ptime:20..a=direction:active..
>> #################################################################################
>>
>> U XX.XX.XX.250:5060 -> 77.72.169.129:5060
>>    INVITE sip:00492271993120 at 77.72.169.129:5060;transport=udp
>> SIP/2.0..Record-Route:
>> <sip:XX.XX.XX.250;r2=on;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Record-Route:
>> <sip:127.0.0.1;r2=on
>>    ;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Via:
>> SIP/2.0/UDP
>> XX.XX.XX.250;branch=z9hG4bKd906.5531f5d10bd0fe3667091afe519d5f94.0..Via:
>> SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;bra
>>    nch=z9hG4bKZ7GCaaKk;rport=5080..From: "41225017077"
>> <sip:41225017077 at sip.adoovoice.com>;tag=0F8733E5-56B4B7B700066935-870F0700..To:
>> <sip:00492271993120 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 222572
>>    206 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE, PRACK, ACK,
>> BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, PUBLISH, UPDATE,
>> MESSAGE..Supported: replaces,100rel..P-Asserted-Identity: <sip:
>>    41225017077 at sip.adoovoice.com>..Authorization: Digest
>> username="pbxprisnet", realm="sip.adoovoice.com", nonce="2231175255",
>> uri="sip:00492271993120 at 77.72.169.129:5060;transport=udp",
>> response="dac6cac
>>    8d25100ee03560bab867ba1be", algorithm=MD5..Content-Type:
>> application/sdp..Content-Length: 265..Contact:
>> <sip:ngcp-lb at XX.XX.XX.250:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=-
>> 20036 2
>>    0036 IN IP4 10.164.124.97..s=SDP data..c=IN IP4 213.55.176.206..t=0
>> 0..m=audio 11852 RTP/AVP 0 8 9 101..a=rtpmap:0 PCMU/8000..a=rtpmap:8
>> PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:101 telephone-event/8
>>    000..a=sendrecv..a=ptime:20..a=direction:active..
>> ############################################################################
>>
>>
>> Thank you for your help
>>
>> Jephth? Feugn?
>>
>> _______________________________________________
>> Spce-user mailing list
>> Spce-user at lists.sipwise.com
>> https://lists.sipwise.com/listinfo/spce-user
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20160205/346e9f8c/attachment-0001.html>

From me at nevian.org  Fri Feb  5 13:39:32 2016
From: me at nevian.org (Serge Yuriev)
Date: Fri, 5 Feb 2016 21:39:32 +0300
Subject: [Spce-user] Trunk to voicetrading configuration
In-Reply-To: <56B4E6B0.5090307@prisnets.ch>
References: <56B4E6B0.5090307@prisnets.ch> <56B4B8C1.5060203@prisnets.ch>
 <56B4C9D1.1090008@sipwise.com>
Message-ID: <EA2E104E-D65F-4872-A38A-801C9103418C@nevian.org>

Hi,

Who is 213.55.176.206? Is this someone you should proxy before passing upstream? Maybe your provider filters such requests?

-- 
Wbr, Serge via mobile

05.02.2016, 21:15, "Jephth? Feugn?" <j.feugne at prisnets.ch>:
> 
> Hi,
> Thank you for your reply. I unfortunately disable one of my rewrite rule by the time I made the call. I Cross check the rules once more and here is the result when I place call. still no ring both on the caller and callee  side:
> 
> 
>>>         U xx.xx.xx.2:5060 -> 77.72.169.129:5060
>>>           INVITE sip:0000041227312221 at 77.72.169.129:5060;transport=udp SIP/2.0..Record-Route: <sip:xx.xx.xx.2;r2=on;lr=on;ftag=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>..Record-Route: <sip:127.0.0.1;r2=
>>>           on;lr=on;ftag=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>..Via: SIP/2.0/UDP xx.xx.xx.2;branch=z9hG4bKe854.61a0e861a7f1d69a32327173a5932390.0..Via: SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;b
>>>           ranch=z9hG4bKtn6UJa1a;rport=5080..From: "41225017077" <sip:41225017077 at sip.adoovoice.com>;tag=16EE36B8-56B4E5C400006FEF-86FEF700..To: <sip:0000041227312221 at 77.72.169.129>..CSeq: 10 INVITE..Call-ID: 50
>>>           4974996 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, PUBLISH, UPDATE, MESSAGE..Supported: replaces,100rel..P-Asserted-Identity: <
>>>           sip:41225017077 at sip.adoovoice.com>..Content-Type: application/sdp..Content-Length: 265..Contact: <sip:ngcp-lb at xx.xx.xx.2:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=- 20054 20054 IN
>>>            IP4 10.164.124.97..s=SDP data..c=IN IP4 213.55.176.206..t=0 0..m=audio 11888 RTP/AVP 0 8 9 101..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:101 telephone-event/8000..a=
>>>           sendrecv..a=ptime:20..a=direction:active..                                                                                                                                                             
>>>         ##
>>>         U 77.72.169.129:5060 -> xx.xx.xx.2:5060
>>>           SIP/2.0 401 Unauthorized..Via: SIP/2.0/UDP xx.xx.xx.2:5060;branch=z9hG4bKe854.61a0e861a7f1d69a32327173a5932390.0..Via: SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;branch=z9hG4bKtn6UJa1a;rport=508
>>>           0..From: "41225017077" <sip:41225017077 at sip.adoovoice.com>;tag=16EE36B8-56B4E5C400006FEF-86FEF700..To: <sip:0000041227312221 at 77.72.169.129>..Contact: sip:0000041227312221 at 77.72.169.129:5060..Call-ID:
>>>           504974996 at 10.20.12.202_b2b-1..CSeq: 10 INVITE..Server: (Very nice Sip Registrar/Proxy Server)..Allow: ACK,BYE,CANCEL,INVITE,REGISTER,OPTIONS,INFO,MESSAGE..Record-route: <sip:xx.xx.xx.2;r2=on;lr;fta
>>>           g=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>,<sip:127.0.0.1;r2=on;lr;ftag=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>..WWW-Authenticate: Digest realm="sip.adoovoice.com",nonce="2242964208",algo
>>>           rithm=MD5..Content-Length: 0....                                                                                                                                                                       
>>>         #
>>>         U xx.xx.xx.2:5060 -> 77.72.169.129:5060
>>>           ACK sip:0000041227312221 at 77.72.169.129:5060;transport=udp SIP/2.0..Max-Forwards: 70..Record-Route: <sip:xx.xx.xx.2;r2=on;lr=on;ftag=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>..Record-Route: <si
>>>           p:127.0.0.1;r2=on;lr=on;ftag=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>..Via: SIP/2.0/UDP xx.xx.xx.2;branch=z9hG4bKe854.61a0e861a7f1d69a32327173a5932390.0..Via: SIP/2.0/UDP 127.0.0.1:5080;recei
>>>           ved=127.0.0.1;branch=z9hG4bKtn6UJa1a;rport=5080..From: "41225017077" <sip:41225017077 at sip.adoovoice.com>;tag=16EE36B8-56B4E5C400006FEF-86FEF700..To: <sip:0000041227312221 at 77.72.169.129>..Call-ID: 5049
>>>           74996 at 10.20.12.202_b2b-1..CSeq: 10 ACK..Content-Length: 0....                                                                                                                                          
>>>         #
>>>         U xx.xx.xx.2:5060 -> 77.72.169.129:5060
>>>           INVITE sip:0000041227312221 at 77.72.169.129:5060;transport=udp SIP/2.0..Record-Route: <sip:xx.xx.xx.2;r2=on;lr=on;ftag=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>..Record-Route: <sip:127.0.0.1;r2=
>>>           on;lr=on;ftag=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>..Via: SIP/2.0/UDP xx.xx.xx.2;branch=z9hG4bKf854.44da301080c743aeec10ba45573ba2e4.0..Via: SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;b
>>>           ranch=z9hG4bKkKgwgaE0;rport=5080..From: "41225017077" <sip:41225017077 at sip.adoovoice.com>;tag=16EE36B8-56B4E5C400006FEF-86FEF700..To: <sip:0000041227312221 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 50
>>>           4974996 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, PUBLISH, UPDATE, MESSAGE..Supported: replaces,100rel..P-Asserted-Identity: <
>>>           sip:41225017077 at sip.adoovoice.com>..Authorization: Digest username="pbxprisnet", realm="sip.adoovoice.com", nonce="2242964208", uri="sip:0000041227312221 at 77.72.169.129:5060;transport=udp", response="9
>>>           53a2ba986e16d9d2c3564149681dd58", algorithm=MD5..Content-Type: application/sdp..Content-Length: 265..Contact: <sip:ngcp-lb at xx.xx.xx.2:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=- 2
>>>           0054 20054 IN IP4 10.164.124.97..s=SDP data..c=IN IP4 213.55.176.206..t=0 0..m=audio 11888 RTP/AVP 0 8 9 101..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:101 telephone-e
>>>           vent/8000..a=sendrecv..a=ptime:20..a=direction:active..                                                                                                                                                
>>>         ########################
>>>         U xx.xx.xx.2:5060 -> 77.72.169.129:5060
>>>           INVITE sip:0000041227312221 at 77.72.169.129:5060;transport=udp SIP/2.0..Record-Route: <sip:xx.xx.xx.2;r2=on;lr=on;ftag=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>..Record-Route: <sip:127.0.0.1;r2=
>>>           on;lr=on;ftag=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>..Via: SIP/2.0/UDP xx.xx.xx.2;branch=z9hG4bKf854.44da301080c743aeec10ba45573ba2e4.0..Via: SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;b
>>>           ranch=z9hG4bKkKgwgaE0;rport=5080..From: "41225017077" <sip:41225017077 at sip.adoovoice.com>;tag=16EE36B8-56B4E5C400006FEF-86FEF700..To: <sip:0000041227312221 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 50
>>>           4974996 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, PUBLISH, UPDATE, MESSAGE..Supported: replaces,100rel..P-Asserted-Identity: <
>>>           sip:41225017077 at sip.adoovoice.com>..Authorization: Digest username="pbxprisnet", realm="sip.adoovoice.com", nonce="2242964208", uri="sip:0000041227312221 at 77.72.169.129:5060;transport=udp", response="9
>>>           53a2ba986e16d9d2c3564149681dd58", algorithm=MD5..Content-Type: application/sdp..Content-Length: 265..Contact: <sip:ngcp-lb at xx.xx.xx.2:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=- 2
>>>           0054 20054 IN IP4 10.164.124.97..s=SDP data..c=IN IP4 213.55.176.206..t=0 0..m=audio 11888 RTP/AVP 0 8 9 101..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:101 telephone-e
>>>           vent/8000..a=sendrecv..a=ptime:20..a=direction:active..                                                                                                                                                
>>>         #########################
>>>         U xx.xx.xx.2:5060 -> 77.72.169.129:5060
>>>           INVITE sip:0000041227312221 at 77.72.169.129:5060;transport=udp SIP/2.0..Record-Route: <sip:xx.xx.xx.2;r2=on;lr=on;ftag=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>..Record-Route: <sip:127.0.0.1;r2=
>>>           on;lr=on;ftag=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>..Via: SIP/2.0/UDP xx.xx.xx.2;branch=z9hG4bKf854.44da301080c743aeec10ba45573ba2e4.0..Via: SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;b
>>>           ranch=z9hG4bKkKgwgaE0;rport=5080..From: "41225017077" <sip:41225017077 at sip.adoovoice.com>;tag=16EE36B8-56B4E5C400006FEF-86FEF700..To: <sip:0000041227312221 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 50
>>>           4974996 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, PUBLISH, UPDATE, MESSAGE..Supported: replaces,100rel..P-Asserted-Identity: <
>>>           sip:41225017077 at sip.adoovoice.com>..Authorization: Digest username="pbxprisnet", realm="sip.adoovoice.com", nonce="2242964208", uri="sip:0000041227312221 at 77.72.169.129:5060;transport=udp", response="9
>>>           53a2ba986e16d9d2c3564149681dd58", algorithm=MD5..Content-Type: application/sdp..Content-Length: 265..Contact: <sip:ngcp-lb at xx.xx.xx.2:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=- 2
>>>           0054 20054 IN IP4 10.164.124.97..s=SDP data..c=IN IP4 213.55.176.206..t=0 0..m=audio 11888 RTP/AVP 0 8 9 101..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:101 telephone-e
>>>           vent/8000..a=sendrecv..a=ptime:20..a=direction:active..                                                                                                                                                
>>>         #############################################
>>>         U xx.xx.xx.2:5060 -> 77.72.169.129:5060
>>>           INVITE sip:0000041227312221 at 77.72.169.129:5060;transport=udp SIP/2.0..Record-Route: <sip:xx.xx.xx.2;r2=on;lr=on;ftag=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>..Record-Route: <sip:127.0.0.1;r2=
>>>           on;lr=on;ftag=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>..Via: SIP/2.0/UDP xx.xx.xx.2;branch=z9hG4bKf854.44da301080c743aeec10ba45573ba2e4.0..Via: SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;b
>>>           ranch=z9hG4bKkKgwgaE0;rport=5080..From: "41225017077" <sip:41225017077 at sip.adoovoice.com>;tag=16EE36B8-56B4E5C400006FEF-86FEF700..To: <sip:0000041227312221 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 50
>>>           4974996 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, PUBLISH, UPDATE, MESSAGE..Supported: replaces,100rel..P-Asserted-Identity: <
>>>           sip:41225017077 at sip.adoovoice.com>..Authorization: Digest username="pbxprisnet", realm="sip.adoovoice.com", nonce="2242964208", uri="sip:0000041227312221 at 77.72.169.129:5060;transport=udp", response="9
>>>           53a2ba986e16d9d2c3564149681dd58", algorithm=MD5..Content-Type: application/sdp..Content-Length: 265..Contact: <sip:ngcp-lb at xx.xx.xx.2:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=- 2
>>>           0054 20054 IN IP4 10.164.124.97..s=SDP data..c=IN IP4 213.55.176.206..t=0 0..m=audio 11888 RTP/AVP 0 8 9 101..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:101 telephone-e
>>>           vent/8000..a=sendrecv..a=ptime:20..a=direction:active..                                                                                                                                                
>>>         #################################################################################
>>>         U xx.xx.xx.2:5060 -> 77.72.169.129:5060
>>>           INVITE sip:0000041227312221 at 77.72.169.129:5060;transport=udp SIP/2.0..Record-Route: <sip:xx.xx.xx.2;r2=on;lr=on;ftag=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>..Record-Route: <sip:127.0.0.1;r2=
>>>           on;lr=on;ftag=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>..Via: SIP/2.0/UDP xx.xx.xx.2;branch=z9hG4bKf854.44da301080c743aeec10ba45573ba2e4.0..Via: SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;b
>>>           ranch=z9hG4bKkKgwgaE0;rport=5080..From: "41225017077" <sip:41225017077 at sip.adoovoice.com>;tag=16EE36B8-56B4E5C400006FEF-86FEF700..To: <sip:0000041227312221 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 50
>>>           4974996 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, PUBLISH, UPDATE, MESSAGE..Supported: replaces,100rel..P-Asserted-Identity: <
>>>           sip:41225017077 at sip.adoovoice.com>..Authorization: Digest username="pbxprisnet", realm="sip.adoovoice.com", nonce="2242964208", uri="sip:0000041227312221 at 77.72.169.129:5060;transport=udp", response="9
>>>           53a2ba986e16d9d2c3564149681dd58", algorithm=MD5..Content-Type: application/sdp..Content-Length: 265..Contact: <sip:ngcp-lb at xx.xx.xx.2:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=- 2
>>>           0054 20054 IN IP4 10.164.124.97..s=SDP data..c=IN IP4 213.55.176.206..t=0 0..m=audio 11888 RTP/AVP 0 8 9 101..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:101 telephone-e
>>>           vent/8000..a=sendrecv..a=ptime:20..a=direction:active..                                                                                                                                                
>>>         ################################################################################################
>>>         T 213.55.176.206:31002 -> xx.xx.xx.2:5060 [AP]
>>>           CANCEL sip:0227312221 at sip.adoovoice.com:5060 SIP/2.0..Via: SIP/2.0/TCP 10.20.12.202:5063;branch=z9hG4bK2530177975..From: "balmer" <sip:balmer at sip.adoovoice.com>;tag=801761386..To: <sip:0227312221 at sip.
>>>           adoovoice.com>..Call-ID: 504974996 at 10.20.12.202..CSeq: 2 CANCEL..Max-Forwards: 70..User-Agent: Yealink SIP-W52P 25.73.0.40..Content-Length: 0....                                                      
>>>         #
> 
> 
> 
> Le 05. 02. 16 17:12, Andreas Granig a ?crit :
> 
>> 
>> Hi, From the trace you provided, it seems your request just times out, as there is no reply at all from your peer. No idea if they do this because you're not sending the 00000 prefix you mentioned. Create a new rewrite rule set and put a rule like "^(.+)$" => "00000\1" into the outbound callee rule and assign this rule set in the peer preferences of your configured peering server. Please read carefully the handbook provided with the CE installation, specifically the configuration of peerings and peering rules. Andreas On 02/05/2016 03:59 PM, Jephth? Feugn? wrote:
>>> 
>>> Hello, I've been trying for weeks to have my trunk to voicetrading working with no success. I also tried a sip trunk to my GSM gateway with the same result. No ringing to the calle side, and no sound no ringing tone by the caller side.  Can some one please can help me solve this problem? Here is what I have during call with the command "ngrep sip" executed on the sipwise CE 4.2.1 server. Voicetrading is expecting for premium route on their side, the number to be perpended with "00000", xx.xx.xx.250 is the IP address of my sipwise CE 4.2.1 server: XX.XX.XX.250:5060 -> 77.72.169.129:5060 INVITE sip:00492271993120 at 77.72.169.129:5060;transport=udpSIP/2.0..Record-Route: <sip:XX.XX.XX.250;r2=on;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Record-Route: <sip:127.0.0.1;r2=on ;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Via: SIP/2.0/UDP XX.XX.XX.250;branch=z9hG4bKd906.5531f5d10bd0fe3667091afe519d5f94.0..Via: SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;bra nch=z9hG4bKZ7GCaaKk;rport=5080..From: "41225017077"<sip:41225017077 at sip.adoovoice.com>;tag=0F8733E5-56B4B7B700066935-870F0700..To:<sip:00492271993120 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 222572 206 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, PUBLISH, UPDATE, MESSAGE..Supported: replaces,100rel..P-Asserted-Identity: <sip: 41225017077 at sip.adoovoice.com>..Authorization: Digest username="pbxprisnet", realm="sip.adoovoice.com", nonce="2231175255", uri="sip:00492271993120 at 77.72.169.129:5060;transport=udp", response="dac6cac 8d25100ee03560bab867ba1be", algorithm=MD5..Content-Type: application/sdp..Content-Length: 265..Contact:<sip:ngcp-lb at XX.XX.XX.250:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=- 20036 2 0036 IN IP4 10.164.124.97..s=SDP data..c=IN IP4 213.55.176.206..t=0 0..m=audio 11852 RTP/AVP 0 8 9 101..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:101 telephone-event/8 000..a=sendrecv..a=ptime:20..a=direction:active.. ##################### U XX.XX.XX.250:5060 -> 77.72.169.129:5060 INVITE sip:00492271993120 at 77.72.169.129:5060;transport=udpSIP/2.0..Record-Route: <sip:XX.XX.XX.250;r2=on;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Record-Route: <sip:127.0.0.1;r2=on ;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Via: SIP/2.0/UDP XX.XX.XX.250;branch=z9hG4bKd906.5531f5d10bd0fe3667091afe519d5f94.0..Via: SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;bra nch=z9hG4bKZ7GCaaKk;rport=5080..From: "41225017077"<sip:41225017077 at sip.adoovoice.com>;tag=0F8733E5-56B4B7B700066935-870F0700..To:<sip:00492271993120 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 222572 206 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, PUBLISH, UPDATE, MESSAGE..Supported: replaces,100rel..P-Asserted-Identity: <sip: 41225017077 at sip.adoovoice.com>..Authorization: Digest username="pbxprisnet", realm="sip.adoovoice.com", nonce="2231175255", uri="sip:00492271993120 at 77.72.169.129:5060;transport=udp", response="dac6cac 8d25100ee03560bab867ba1be", algorithm=MD5..Content-Type: application/sdp..Content-Length: 265..Contact:<sip:ngcp-lb at XX.XX.XX.250:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=- 20036 2 0036 IN IP4 10.164.124.97..s=SDP data..c=IN IP4 213.55.176.206..t=0 0..m=audio 11852 RTP/AVP 0 8 9 101..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:101 telephone-event/8 000..a=sendrecv..a=ptime:20..a=direction:active.. ####################### U XX.XX.XX.250:5060 -> 77.72.169.129:5060 INVITE sip:00492271993120 at 77.72.169.129:5060;transport=udpSIP/2.0..Record-Route: <sip:XX.XX.XX.250;r2=on;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Record-Route: <sip:127.0.0.1;r2=on ;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Via: SIP/2.0/UDP XX.XX.XX.250;branch=z9hG4bKd906.5531f5d10bd0fe3667091afe519d5f94.0..Via: SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;bra nch=z9hG4bKZ7GCaaKk;rport=5080..From: "41225017077"<sip:41225017077 at sip.adoovoice.com>;tag=0F8733E5-56B4B7B700066935-870F0700..To:<sip:00492271993120 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 222572 206 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, PUBLISH, UPDATE, MESSAGE..Supported: replaces,100rel..P-Asserted-Identity: <sip: 41225017077 at sip.adoovoice.com>..Authorization: Digest username="pbxprisnet", realm="sip.adoovoice.com", nonce="2231175255", uri="sip:00492271993120 at 77.72.169.129:5060;transport=udp", response="dac6cac 8d25100ee03560bab867ba1be", algorithm=MD5..Content-Type: application/sdp..Content-Length: 265..Contact:<sip:ngcp-lb at XX.XX.XX.250:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=- 20036 2 0036 IN IP4 10.164.124.97..s=SDP data..c=IN IP4 213.55.176.206..t=0 0..m=audio 11852 RTP/AVP 0 8 9 101..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:101 telephone-event/8 000..a=sendrecv..a=ptime:20..a=direction:active.. ######################################### U XX.XX.XX.250:5060 -> 77.72.169.129:5060 INVITE sip:00492271993120 at 77.72.169.129:5060;transport=udpSIP/2.0..Record-Route: <sip:XX.XX.XX.250;r2=on;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Record-Route: <sip:127.0.0.1;r2=on ;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Via: SIP/2.0/UDP XX.XX.XX.250;branch=z9hG4bKd906.5531f5d10bd0fe3667091afe519d5f94.0..Via: SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;bra nch=z9hG4bKZ7GCaaKk;rport=5080..From: "41225017077"<sip:41225017077 at sip.adoovoice.com>;tag=0F8733E5-56B4B7B700066935-870F0700..To:<sip:00492271993120 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 222572 206 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, PUBLISH, UPDATE, MESSAGE..Supported: replaces,100rel..P-Asserted-Identity: <sip: 41225017077 at sip.adoovoice.com>..Authorization: Digest username="pbxprisnet", realm="sip.adoovoice.com", nonce="2231175255", uri="sip:00492271993120 at 77.72.169.129:5060;transport=udp", response="dac6cac 8d25100ee03560bab867ba1be", algorithm=MD5..Content-Type: application/sdp..Content-Length: 265..Contact:<sip:ngcp-lb at XX.XX.XX.250:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=- 20036 2 0036 IN IP4 10.164.124.97..s=SDP data..c=IN IP4 213.55.176.206..t=0 0..m=audio 11852 RTP/AVP 0 8 9 101..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:101 telephone-event/8 000..a=sendrecv..a=ptime:20..a=direction:active.. ################################################################################# U XX.XX.XX.250:5060 -> 77.72.169.129:5060 INVITE sip:00492271993120 at 77.72.169.129:5060;transport=udpSIP/2.0..Record-Route: <sip:XX.XX.XX.250;r2=on;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Record-Route: <sip:127.0.0.1;r2=on ;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Via: SIP/2.0/UDP XX.XX.XX.250;branch=z9hG4bKd906.5531f5d10bd0fe3667091afe519d5f94.0..Via: SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;bra nch=z9hG4bKZ7GCaaKk;rport=5080..From: "41225017077"<sip:41225017077 at sip.adoovoice.com>;tag=0F8733E5-56B4B7B700066935-870F0700..To:<sip:00492271993120 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 222572 206 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, PUBLISH, UPDATE, MESSAGE..Supported: replaces,100rel..P-Asserted-Identity: <sip: 41225017077 at sip.adoovoice.com>..Authorization: Digest username="pbxprisnet", realm="sip.adoovoice.com", nonce="2231175255", uri="sip:00492271993120 at 77.72.169.129:5060;transport=udp", response="dac6cac 8d25100ee03560bab867ba1be", algorithm=MD5..Content-Type: application/sdp..Content-Length: 265..Contact:<sip:ngcp-lb at XX.XX.XX.250:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=- 20036 2 0036 IN IP4 10.164.124.97..s=SDP data..c=IN IP4 213.55.176.206..t=0 0..m=audio 11852 RTP/AVP 0 8 9 101..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:101 telephone-event/8 000..a=sendrecv..a=ptime:20..a=direction:active.. ############################################################################ Thank you for your help Jephth? Feugn? _______________________________________________ Spce-user mailing listSpce-user at lists.sipwise.comhttps://lists.sipwise.com/listinfo/spce-user
>> 
>> _______________________________________________ Spce-user mailing listSpce-user at lists.sipwise.comhttps://lists.sipwise.com/listinfo/spce-user
> 
> 
> 
> 
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
> 


From j.feugne at prisnets.ch  Fri Feb  5 14:03:53 2016
From: j.feugne at prisnets.ch (=?UTF-8?Q?Jephth=C3=A9_Feugn=C3=A9?=)
Date: Fri, 5 Feb 2016 20:03:53 +0100
Subject: [Spce-user] Trunk to voicetrading configuration
In-Reply-To: <EA2E104E-D65F-4872-A38A-801C9103418C@nevian.org>
References: <56B4E6B0.5090307@prisnets.ch> <56B4B8C1.5060203@prisnets.ch>
 <56B4C9D1.1090008@sipwise.com>
 <EA2E104E-D65F-4872-A38A-801C9103418C@nevian.org>
Message-ID: <001a01d16047$f50c8d00$df25a700$@prisnets.ch>

HI!

213.55.176.206, is my 4G connection behind which is connected my IP Phone registered with my hosted Sipwise CE server (xx.xx.xx.250).
I can register directly to my Voicetrading account and place call behind my 4G connection, but not when I register to Sipwise.

Thank you helping me to solve this situation.

Jeph,


_____
Prisnets SA.
Office:   +41 22 501 70 70 / Fax : +41 22 501 70 67
Direct line : +41 22 508 72 70
Mobile:  +41 78 728 92 97
Email:     j.feugne at prisnets.ch
Skype:   jephtech - Twitter:  @prisnet_ch
http://www.prisnets.ch
Prisnet Telecommunications SA.  Route de Saint-Julien 184 A, 1228 Plan-Les-Ouates CH.

-----Message d'origine-----
De : Spce-user [mailto:spce-user-bounces at lists.sipwise.com] De la part de Serge Yuriev
Envoy? : vendredi, 5 f?vrier 2016 19:40
? : spce-user at lists.sipwise.com
Objet : Re: [Spce-user] Trunk to voicetrading configuration

Hi,

Who is 213.55.176.206? Is this someone you should proxy before passing upstream? Maybe your provider filters such requests?

-- 
Wbr, Serge via mobile

05.02.2016, 21:15, "Jephth? Feugn?" <j.feugne at prisnets.ch>:
> 
> Hi,
> Thank you for your reply. I unfortunately disable one of my rewrite rule by the time I made the call. I Cross check the rules once more and here is the result when I place call. still no ring both on the caller and callee  side:
> 
> 
>>>         U xx.xx.xx.2:5060 -> 77.72.169.129:5060
>>>           INVITE sip:0000041227312221 at 77.72.169.129:5060;transport=udp SIP/2.0..Record-Route: <sip:xx.xx.xx.2;r2=on;lr=on;ftag=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>..Record-Route: <sip:127.0.0.1;r2=
>>>           on;lr=on;ftag=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>..Via: SIP/2.0/UDP xx.xx.xx.2;branch=z9hG4bKe854.61a0e861a7f1d69a32327173a5932390.0..Via: SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;b
>>>           ranch=z9hG4bKtn6UJa1a;rport=5080..From: "41225017077" <sip:41225017077 at sip.adoovoice.com>;tag=16EE36B8-56B4E5C400006FEF-86FEF700..To: <sip:0000041227312221 at 77.72.169.129>..CSeq: 10 INVITE..Call-ID: 50
>>>           4974996 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, PUBLISH, UPDATE, MESSAGE..Supported: replaces,100rel..P-Asserted-Identity: <
>>>           sip:41225017077 at sip.adoovoice.com>..Content-Type: application/sdp..Content-Length: 265..Contact: <sip:ngcp-lb at xx.xx.xx.2:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=- 20054 20054 IN
>>>            IP4 10.164.124.97..s=SDP data..c=IN IP4 213.55.176.206..t=0 0..m=audio 11888 RTP/AVP 0 8 9 101..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:101 telephone-event/8000..a=
>>>           sendrecv..a=ptime:20..a=direction:active..                                                                                                                                                             
>>>         ##
>>>         U 77.72.169.129:5060 -> xx.xx.xx.2:5060
>>>           SIP/2.0 401 Unauthorized..Via: SIP/2.0/UDP xx.xx.xx.2:5060;branch=z9hG4bKe854.61a0e861a7f1d69a32327173a5932390.0..Via: SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;branch=z9hG4bKtn6UJa1a;rport=508
>>>           0..From: "41225017077" <sip:41225017077 at sip.adoovoice.com>;tag=16EE36B8-56B4E5C400006FEF-86FEF700..To: <sip:0000041227312221 at 77.72.169.129>..Contact: sip:0000041227312221 at 77.72.169.129:5060..Call-ID:
>>>           504974996 at 10.20.12.202_b2b-1..CSeq: 10 INVITE..Server: (Very nice Sip Registrar/Proxy Server)..Allow: ACK,BYE,CANCEL,INVITE,REGISTER,OPTIONS,INFO,MESSAGE..Record-route: <sip:xx.xx.xx.2;r2=on;lr;fta
>>>           g=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>,<sip:127.0.0.1;r2=on;lr;ftag=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>..WWW-Authenticate: Digest realm="sip.adoovoice.com",nonce="2242964208",algo
>>>           rithm=MD5..Content-Length: 0....                                                                                                                                                                       
>>>         #
>>>         U xx.xx.xx.2:5060 -> 77.72.169.129:5060
>>>           ACK sip:0000041227312221 at 77.72.169.129:5060;transport=udp SIP/2.0..Max-Forwards: 70..Record-Route: <sip:xx.xx.xx.2;r2=on;lr=on;ftag=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>..Record-Route: <si
>>>           p:127.0.0.1;r2=on;lr=on;ftag=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>..Via: SIP/2.0/UDP xx.xx.xx.2;branch=z9hG4bKe854.61a0e861a7f1d69a32327173a5932390.0..Via: SIP/2.0/UDP 127.0.0.1:5080;recei
>>>           ved=127.0.0.1;branch=z9hG4bKtn6UJa1a;rport=5080..From: "41225017077" <sip:41225017077 at sip.adoovoice.com>;tag=16EE36B8-56B4E5C400006FEF-86FEF700..To: <sip:0000041227312221 at 77.72.169.129>..Call-ID: 5049
>>>           74996 at 10.20.12.202_b2b-1..CSeq: 10 ACK..Content-Length: 0....                                                                                                                                          
>>>         #
>>>         U xx.xx.xx.2:5060 -> 77.72.169.129:5060
>>>           INVITE sip:0000041227312221 at 77.72.169.129:5060;transport=udp SIP/2.0..Record-Route: <sip:xx.xx.xx.2;r2=on;lr=on;ftag=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>..Record-Route: <sip:127.0.0.1;r2=
>>>           on;lr=on;ftag=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>..Via: SIP/2.0/UDP xx.xx.xx.2;branch=z9hG4bKf854.44da301080c743aeec10ba45573ba2e4.0..Via: SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;b
>>>           ranch=z9hG4bKkKgwgaE0;rport=5080..From: "41225017077" <sip:41225017077 at sip.adoovoice.com>;tag=16EE36B8-56B4E5C400006FEF-86FEF700..To: <sip:0000041227312221 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 50
>>>           4974996 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, PUBLISH, UPDATE, MESSAGE..Supported: replaces,100rel..P-Asserted-Identity: <
>>>           sip:41225017077 at sip.adoovoice.com>..Authorization: Digest username="pbxprisnet", realm="sip.adoovoice.com", nonce="2242964208", uri="sip:0000041227312221 at 77.72.169.129:5060;transport=udp", response="9
>>>           53a2ba986e16d9d2c3564149681dd58", algorithm=MD5..Content-Type: application/sdp..Content-Length: 265..Contact: <sip:ngcp-lb at xx.xx.xx.2:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=- 2
>>>           0054 20054 IN IP4 10.164.124.97..s=SDP data..c=IN IP4 213.55.176.206..t=0 0..m=audio 11888 RTP/AVP 0 8 9 101..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:101 telephone-e
>>>           vent/8000..a=sendrecv..a=ptime:20..a=direction:active..                                                                                                                                                
>>>         ########################
>>>         U xx.xx.xx.2:5060 -> 77.72.169.129:5060
>>>           INVITE sip:0000041227312221 at 77.72.169.129:5060;transport=udp SIP/2.0..Record-Route: <sip:xx.xx.xx.2;r2=on;lr=on;ftag=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>..Record-Route: <sip:127.0.0.1;r2=
>>>           on;lr=on;ftag=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>..Via: SIP/2.0/UDP xx.xx.xx.2;branch=z9hG4bKf854.44da301080c743aeec10ba45573ba2e4.0..Via: SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;b
>>>           ranch=z9hG4bKkKgwgaE0;rport=5080..From: "41225017077" <sip:41225017077 at sip.adoovoice.com>;tag=16EE36B8-56B4E5C400006FEF-86FEF700..To: <sip:0000041227312221 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 50
>>>           4974996 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, PUBLISH, UPDATE, MESSAGE..Supported: replaces,100rel..P-Asserted-Identity: <
>>>           sip:41225017077 at sip.adoovoice.com>..Authorization: Digest username="pbxprisnet", realm="sip.adoovoice.com", nonce="2242964208", uri="sip:0000041227312221 at 77.72.169.129:5060;transport=udp", response="9
>>>           53a2ba986e16d9d2c3564149681dd58", algorithm=MD5..Content-Type: application/sdp..Content-Length: 265..Contact: <sip:ngcp-lb at xx.xx.xx.2:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=- 2
>>>           0054 20054 IN IP4 10.164.124.97..s=SDP data..c=IN IP4 213.55.176.206..t=0 0..m=audio 11888 RTP/AVP 0 8 9 101..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:101 telephone-e
>>>           vent/8000..a=sendrecv..a=ptime:20..a=direction:active..                                                                                                                                                
>>>         #########################
>>>         U xx.xx.xx.2:5060 -> 77.72.169.129:5060
>>>           INVITE sip:0000041227312221 at 77.72.169.129:5060;transport=udp SIP/2.0..Record-Route: <sip:xx.xx.xx.2;r2=on;lr=on;ftag=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>..Record-Route: <sip:127.0.0.1;r2=
>>>           on;lr=on;ftag=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>..Via: SIP/2.0/UDP xx.xx.xx.2;branch=z9hG4bKf854.44da301080c743aeec10ba45573ba2e4.0..Via: SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;b
>>>           ranch=z9hG4bKkKgwgaE0;rport=5080..From: "41225017077" <sip:41225017077 at sip.adoovoice.com>;tag=16EE36B8-56B4E5C400006FEF-86FEF700..To: <sip:0000041227312221 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 50
>>>           4974996 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, PUBLISH, UPDATE, MESSAGE..Supported: replaces,100rel..P-Asserted-Identity: <
>>>           sip:41225017077 at sip.adoovoice.com>..Authorization: Digest username="pbxprisnet", realm="sip.adoovoice.com", nonce="2242964208", uri="sip:0000041227312221 at 77.72.169.129:5060;transport=udp", response="9
>>>           53a2ba986e16d9d2c3564149681dd58", algorithm=MD5..Content-Type: application/sdp..Content-Length: 265..Contact: <sip:ngcp-lb at xx.xx.xx.2:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=- 2
>>>           0054 20054 IN IP4 10.164.124.97..s=SDP data..c=IN IP4 213.55.176.206..t=0 0..m=audio 11888 RTP/AVP 0 8 9 101..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:101 telephone-e
>>>           vent/8000..a=sendrecv..a=ptime:20..a=direction:active..                                                                                                                                                
>>>         #############################################
>>>         U xx.xx.xx.2:5060 -> 77.72.169.129:5060
>>>           INVITE sip:0000041227312221 at 77.72.169.129:5060;transport=udp SIP/2.0..Record-Route: <sip:xx.xx.xx.2;r2=on;lr=on;ftag=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>..Record-Route: <sip:127.0.0.1;r2=
>>>           on;lr=on;ftag=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>..Via: SIP/2.0/UDP xx.xx.xx.2;branch=z9hG4bKf854.44da301080c743aeec10ba45573ba2e4.0..Via: SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;b
>>>           ranch=z9hG4bKkKgwgaE0;rport=5080..From: "41225017077" <sip:41225017077 at sip.adoovoice.com>;tag=16EE36B8-56B4E5C400006FEF-86FEF700..To: <sip:0000041227312221 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 50
>>>           4974996 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, PUBLISH, UPDATE, MESSAGE..Supported: replaces,100rel..P-Asserted-Identity: <
>>>           sip:41225017077 at sip.adoovoice.com>..Authorization: Digest username="pbxprisnet", realm="sip.adoovoice.com", nonce="2242964208", uri="sip:0000041227312221 at 77.72.169.129:5060;transport=udp", response="9
>>>           53a2ba986e16d9d2c3564149681dd58", algorithm=MD5..Content-Type: application/sdp..Content-Length: 265..Contact: <sip:ngcp-lb at xx.xx.xx.2:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=- 2
>>>           0054 20054 IN IP4 10.164.124.97..s=SDP data..c=IN IP4 213.55.176.206..t=0 0..m=audio 11888 RTP/AVP 0 8 9 101..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:101 telephone-e
>>>           vent/8000..a=sendrecv..a=ptime:20..a=direction:active..                                                                                                                                                
>>>         #################################################################################
>>>         U xx.xx.xx.2:5060 -> 77.72.169.129:5060
>>>           INVITE sip:0000041227312221 at 77.72.169.129:5060;transport=udp SIP/2.0..Record-Route: <sip:xx.xx.xx.2;r2=on;lr=on;ftag=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>..Record-Route: <sip:127.0.0.1;r2=
>>>           on;lr=on;ftag=16EE36B8-56B4E5C400006FEF-86FEF700;ngcplb=yes>..Via: SIP/2.0/UDP xx.xx.xx.2;branch=z9hG4bKf854.44da301080c743aeec10ba45573ba2e4.0..Via: SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;b
>>>           ranch=z9hG4bKkKgwgaE0;rport=5080..From: "41225017077" <sip:41225017077 at sip.adoovoice.com>;tag=16EE36B8-56B4E5C400006FEF-86FEF700..To: <sip:0000041227312221 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 50
>>>           4974996 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, PUBLISH, UPDATE, MESSAGE..Supported: replaces,100rel..P-Asserted-Identity: <
>>>           sip:41225017077 at sip.adoovoice.com>..Authorization: Digest username="pbxprisnet", realm="sip.adoovoice.com", nonce="2242964208", uri="sip:0000041227312221 at 77.72.169.129:5060;transport=udp", response="9
>>>           53a2ba986e16d9d2c3564149681dd58", algorithm=MD5..Content-Type: application/sdp..Content-Length: 265..Contact: <sip:ngcp-lb at xx.xx.xx.2:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=- 2
>>>           0054 20054 IN IP4 10.164.124.97..s=SDP data..c=IN IP4 213.55.176.206..t=0 0..m=audio 11888 RTP/AVP 0 8 9 101..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:101 telephone-e
>>>           vent/8000..a=sendrecv..a=ptime:20..a=direction:active..                                                                                                                                                
>>>         ################################################################################################
>>>         T 213.55.176.206:31002 -> xx.xx.xx.2:5060 [AP]
>>>           CANCEL sip:0227312221 at sip.adoovoice.com:5060 SIP/2.0..Via: SIP/2.0/TCP 10.20.12.202:5063;branch=z9hG4bK2530177975..From: "balmer" <sip:balmer at sip.adoovoice.com>;tag=801761386..To: <sip:0227312221 at sip.
>>>           adoovoice.com>..Call-ID: 504974996 at 10.20.12.202..CSeq: 2 CANCEL..Max-Forwards: 70..User-Agent: Yealink SIP-W52P 25.73.0.40..Content-Length: 0....                                                      
>>>         #
> 
> 
> 
> Le 05. 02. 16 17:12, Andreas Granig a ?crit :
> 
>> 
>> Hi, From the trace you provided, it seems your request just times out, as there is no reply at all from your peer. No idea if they do this because you're not sending the 00000 prefix you mentioned. Create a new rewrite rule set and put a rule like "^(.+)$" => "00000\1" into the outbound callee rule and assign this rule set in the peer preferences of your configured peering server. Please read carefully the handbook provided with the CE installation, specifically the configuration of peerings and peering rules. Andreas On 02/05/2016 03:59 PM, Jephth? Feugn? wrote:
>>> 
>>> Hello, I've been trying for weeks to have my trunk to voicetrading working with no success. I also tried a sip trunk to my GSM gateway with the same result. No ringing to the calle side, and no sound no ringing tone by the caller side.  Can some one please can help me solve this problem? Here is what I have during call with the command "ngrep sip" executed on the sipwise CE 4.2.1 server. Voicetrading is expecting for premium route on their side, the number to be perpended with "00000", xx.xx.xx.250 is the IP address of my sipwise CE 4.2.1 server: XX.XX.XX.250:5060 -> 77.72.169.129:5060 INVITE sip:00492271993120 at 77.72.169.129:5060;transport=udpSIP/2.0..Record-Route: <sip:XX.XX.XX.250;r2=on;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Record-Route: <sip:127.0.0.1;r2=on ;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Via: SIP/2.0/UDP XX.XX.XX.250;branch=z9hG4bKd906.5531f5d10bd0fe3667091afe519d5f94.0..Via: SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;bra nch=z9hG4bKZ7GCaaKk;rport=5080..From: "41225017077"<sip:41225017077 at sip.adoovoice.com>;tag=0F8733E5-56B4B7B700066935-870F0700..To:<sip:00492271993120 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 222572 206 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, PUBLISH, UPDATE, MESSAGE..Supported: replaces,100rel..P-Asserted-Identity: <sip: 41225017077 at sip.adoovoice.com>..Authorization: Digest username="pbxprisnet", realm="sip.adoovoice.com", nonce="2231175255", uri="sip:00492271993120 at 77.72.169.129:5060;transport=udp", response="dac6cac 8d25100ee03560bab867ba1be", algorithm=MD5..Content-Type: application/sdp..Content-Length: 265..Contact:<sip:ngcp-lb at XX.XX.XX.250:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=- 20036 2 0036 IN IP4 10.164.124.97..s=SDP data..c=IN IP4 213.55.176.206..t=0 0..m=audio 11852 RTP/AVP 0 8 9 101..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:101 telephone-event/8 000..a=sendrecv..a=ptime:20..a=direction:active.. ##################### U XX.XX.XX.250:5060 -> 77.72.169.129:5060 INVITE sip:00492271993120 at 77.72.169.129:5060;transport=udpSIP/2.0..Record-Route: <sip:XX.XX.XX.250;r2=on;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Record-Route: <sip:127.0.0.1;r2=on ;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Via: SIP/2.0/UDP XX.XX.XX.250;branch=z9hG4bKd906.5531f5d10bd0fe3667091afe519d5f94.0..Via: SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;bra nch=z9hG4bKZ7GCaaKk;rport=5080..From: "41225017077"<sip:41225017077 at sip.adoovoice.com>;tag=0F8733E5-56B4B7B700066935-870F0700..To:<sip:00492271993120 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 222572 206 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, PUBLISH, UPDATE, MESSAGE..Supported: replaces,100rel..P-Asserted-Identity: <sip: 41225017077 at sip.adoovoice.com>..Authorization: Digest username="pbxprisnet", realm="sip.adoovoice.com", nonce="2231175255", uri="sip:00492271993120 at 77.72.169.129:5060;transport=udp", response="dac6cac 8d25100ee03560bab867ba1be", algorithm=MD5..Content-Type: application/sdp..Content-Length: 265..Contact:<sip:ngcp-lb at XX.XX.XX.250:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=- 20036 2 0036 IN IP4 10.164.124.97..s=SDP data..c=IN IP4 213.55.176.206..t=0 0..m=audio 11852 RTP/AVP 0 8 9 101..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:101 telephone-event/8 000..a=sendrecv..a=ptime:20..a=direction:active.. ####################### U XX.XX.XX.250:5060 -> 77.72.169.129:5060 INVITE sip:00492271993120 at 77.72.169.129:5060;transport=udpSIP/2.0..Record-Route: <sip:XX.XX.XX.250;r2=on;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Record-Route: <sip:127.0.0.1;r2=on ;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Via: SIP/2.0/UDP XX.XX.XX.250;branch=z9hG4bKd906.5531f5d10bd0fe3667091afe519d5f94.0..Via: SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;bra nch=z9hG4bKZ7GCaaKk;rport=5080..From: "41225017077"<sip:41225017077 at sip.adoovoice.com>;tag=0F8733E5-56B4B7B700066935-870F0700..To:<sip:00492271993120 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 222572 206 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, PUBLISH, UPDATE, MESSAGE..Supported: replaces,100rel..P-Asserted-Identity: <sip: 41225017077 at sip.adoovoice.com>..Authorization: Digest username="pbxprisnet", realm="sip.adoovoice.com", nonce="2231175255", uri="sip:00492271993120 at 77.72.169.129:5060;transport=udp", response="dac6cac 8d25100ee03560bab867ba1be", algorithm=MD5..Content-Type: application/sdp..Content-Length: 265..Contact:<sip:ngcp-lb at XX.XX.XX.250:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=- 20036 2 0036 IN IP4 10.164.124.97..s=SDP data..c=IN IP4 213.55.176.206..t=0 0..m=audio 11852 RTP/AVP 0 8 9 101..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:101 telephone-event/8 000..a=sendrecv..a=ptime:20..a=direction:active.. ######################################### U XX.XX.XX.250:5060 -> 77.72.169.129:5060 INVITE sip:00492271993120 at 77.72.169.129:5060;transport=udpSIP/2.0..Record-Route: <sip:XX.XX.XX.250;r2=on;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Record-Route: <sip:127.0.0.1;r2=on ;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Via: SIP/2.0/UDP XX.XX.XX.250;branch=z9hG4bKd906.5531f5d10bd0fe3667091afe519d5f94.0..Via: SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;bra nch=z9hG4bKZ7GCaaKk;rport=5080..From: "41225017077"<sip:41225017077 at sip.adoovoice.com>;tag=0F8733E5-56B4B7B700066935-870F0700..To:<sip:00492271993120 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 222572 206 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, PUBLISH, UPDATE, MESSAGE..Supported: replaces,100rel..P-Asserted-Identity: <sip: 41225017077 at sip.adoovoice.com>..Authorization: Digest username="pbxprisnet", realm="sip.adoovoice.com", nonce="2231175255", uri="sip:00492271993120 at 77.72.169.129:5060;transport=udp", response="dac6cac 8d25100ee03560bab867ba1be", algorithm=MD5..Content-Type: application/sdp..Content-Length: 265..Contact:<sip:ngcp-lb at XX.XX.XX.250:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=- 20036 2 0036 IN IP4 10.164.124.97..s=SDP data..c=IN IP4 213.55.176.206..t=0 0..m=audio 11852 RTP/AVP 0 8 9 101..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:101 telephone-event/8 000..a=sendrecv..a=ptime:20..a=direction:active.. ################################################################################# U XX.XX.XX.250:5060 -> 77.72.169.129:5060 INVITE sip:00492271993120 at 77.72.169.129:5060;transport=udpSIP/2.0..Record-Route: <sip:XX.XX.XX.250;r2=on;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Record-Route: <sip:127.0.0.1;r2=on ;lr=on;ftag=0F8733E5-56B4B7B700066935-870F0700;ngcplb=yes>..Via: SIP/2.0/UDP XX.XX.XX.250;branch=z9hG4bKd906.5531f5d10bd0fe3667091afe519d5f94.0..Via: SIP/2.0/UDP 127.0.0.1:5080;received=127.0.0.1;bra nch=z9hG4bKZ7GCaaKk;rport=5080..From: "41225017077"<sip:41225017077 at sip.adoovoice.com>;tag=0F8733E5-56B4B7B700066935-870F0700..To:<sip:00492271993120 at 77.72.169.129>..CSeq: 11 INVITE..Call-ID: 222572 206 at 10.20.12.202_b2b-1..Max-Forwards: 69..Allow: INVITE, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, PUBLISH, UPDATE, MESSAGE..Supported: replaces,100rel..P-Asserted-Identity: <sip: 41225017077 at sip.adoovoice.com>..Authorization: Digest username="pbxprisnet", realm="sip.adoovoice.com", nonce="2231175255", uri="sip:00492271993120 at 77.72.169.129:5060;transport=udp", response="dac6cac 8d25100ee03560bab867ba1be", algorithm=MD5..Content-Type: application/sdp..Content-Length: 265..Contact:<sip:ngcp-lb at XX.XX.XX.250:5060;ngcpct=7369703a3132372e302e302e313a35303830>....v=0..o=- 20036 2 0036 IN IP4 10.164.124.97..s=SDP data..c=IN IP4 213.55.176.206..t=0 0..m=audio 11852 RTP/AVP 0 8 9 101..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:9 G722/8000..a=rtpmap:101 telephone-event/8 000..a=sendrecv..a=ptime:20..a=direction:active.. ############################################################################ Thank you for your help Jephth? Feugn? _______________________________________________ Spce-user mailing listSpce-user at lists.sipwise.comhttps://lists.sipwise.com/listinfo/spce-user
>> 
>> _______________________________________________ Spce-user mailing listSpce-user at lists.sipwise.comhttps://lists.sipwise.com/listinfo/spce-user
> 
> 
> 
> 
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
> 
_______________________________________________
Spce-user mailing list
Spce-user at lists.sipwise.com
https://lists.sipwise.com/listinfo/spce-user



From me at nevian.org  Mon Feb  8 06:27:20 2016
From: me at nevian.org (Serge S. Yuriev)
Date: Mon, 8 Feb 2016 14:27:20 +0300
Subject: [Spce-user] Trunk to voicetrading configuration
In-Reply-To: <001a01d16047$f50c8d00$df25a700$@prisnets.ch>
References: <56B4E6B0.5090307@prisnets.ch> <56B4B8C1.5060203@prisnets.ch>
 <56B4C9D1.1090008@sipwise.com>
 <EA2E104E-D65F-4872-A38A-801C9103418C@nevian.org>
 <001a01d16047$f50c8d00$df25a700$@prisnets.ch>
Message-ID: <56B87B98.9090805@nevian.org>

Hi,

For a start I would try to include proxying - I bet your upstream 
dislike c= string if it don't match source/contact IP.
And ask provider to inspect theirs logs.

On 05/02/16 22:03, Jephth? Feugn? wrote:
> HI!
>
> 213.55.176.206, is my 4G connection behind which is connected my IP Phone registered with my hosted Sipwise CE server (xx.xx.xx.250).
> I can register directly to my Voicetrading account and place call behind my 4G connection, but not when I register to Sipwise.
>
> Thank you helping me to solve this situation.
>
> Jeph,
>
>
> _____
> Prisnets SA.
> Office:   +41 22 501 70 70 / Fax : +41 22 501 70 67
> Direct line : +41 22 508 72 70
> Mobile:  +41 78 728 92 97
> Email:     j.feugne at prisnets.ch
> Skype:   jephtech - Twitter:  @prisnet_ch
> http://www.prisnets.ch
> Prisnet Telecommunications SA.  Route de Saint-Julien 184 A, 1228 Plan-Les-Ouates CH.
>
> -----Message d'origine-----
> De : Spce-user [mailto:spce-user-bounces at lists.sipwise.com] De la part de Serge Yuriev
> Envoy? : vendredi, 5 f?vrier 2016 19:40
> ? : spce-user at lists.sipwise.com
> Objet : Re: [Spce-user] Trunk to voicetrading configuration
>
> Hi,
>
> Who is 213.55.176.206? Is this someone you should proxy before passing upstream? Maybe your provider filters such requests?
>

-- 
Serge S. Yuriev
Lead VoIP engineer



From j.feugne at prisnets.ch  Tue Feb  9 00:29:54 2016
From: j.feugne at prisnets.ch (=?UTF-8?Q?Jephth=c3=a9_Feugn=c3=a9?=)
Date: Tue, 9 Feb 2016 06:29:54 +0100
Subject: [Spce-user] Trunk to voicetrading configuration
In-Reply-To: <56B87B98.9090805@nevian.org>
References: <56B4E6B0.5090307@prisnets.ch> <56B4B8C1.5060203@prisnets.ch>
 <56B4C9D1.1090008@sipwise.com>
 <EA2E104E-D65F-4872-A38A-801C9103418C@nevian.org>
 <001a01d16047$f50c8d00$df25a700$@prisnets.ch> <56B87B98.9090805@nevian.org>
Message-ID: <56B97952.1000800@prisnets.ch>

Hello Serge,
where can I start looking in other to solve my issue. No way to get 
support form voicetrading, the have a strange support policy. the best 
they give to customer is their faq.

Regards,
Jeph

Le 08. 02. 16 12:27, Serge S. Yuriev a ?crit :
> Hi,
>
> For a start I would try to include proxying - I bet your upstream 
> dislike c= string if it don't match source/contact IP.
> And ask provider to inspect theirs logs.
>
> On 05/02/16 22:03, Jephth? Feugn? wrote:
>> HI!
>>
>> 213.55.176.206, is my 4G connection behind which is connected my IP 
>> Phone registered with my hosted Sipwise CE server (xx.xx.xx.250).
>> I can register directly to my Voicetrading account and place call 
>> behind my 4G connection, but not when I register to Sipwise.
>>
>> Thank you helping me to solve this situation.
>>
>> Jeph,
>>
>>
>> _____
>> Prisnets SA.
>> Office:   +41 22 501 70 70 / Fax : +41 22 501 70 67
>> Direct line : +41 22 508 72 70
>> Mobile:  +41 78 728 92 97
>> Email:     j.feugne at prisnets.ch
>> Skype:   jephtech - Twitter:  @prisnet_ch
>> http://www.prisnets.ch
>> Prisnet Telecommunications SA.  Route de Saint-Julien 184 A, 1228 
>> Plan-Les-Ouates CH.
>>
>> -----Message d'origine-----
>> De : Spce-user [mailto:spce-user-bounces at lists.sipwise.com] De la 
>> part de Serge Yuriev
>> Envoy? : vendredi, 5 f?vrier 2016 19:40
>> ? : spce-user at lists.sipwise.com
>> Objet : Re: [Spce-user] Trunk to voicetrading configuration
>>
>> Hi,
>>
>> Who is 213.55.176.206? Is this someone you should proxy before 
>> passing upstream? Maybe your provider filters such requests?
>>
>



From ricercaict at gmail.com  Wed Feb 10 03:22:57 2016
From: ricercaict at gmail.com (Giacomo)
Date: Wed, 10 Feb 2016 09:22:57 +0100
Subject: [Spce-user] APT Repo Error during ngcp-installer
Message-ID: <CAO_pOtW_=fyxAEv8syL2+U3cR_D6aPAFw-8LH635KwSnesdMyg@mail.gmail.com>

Dear All,
the problem is the following...

When i try to setup sipwise with ngcp-installer on a Debian 8 - 64bit
system after the dpkg -i of the latest stable (mr4.2.1) apt doesn't work
correctly and it shows the following:

Err https://deb.sipwise.com jessie/main amd64 Packages

Ign https://deb.sipwise.com jessie/main Translation-it_IT
Ign https://deb.sipwise.com jessie/main Translation-it
Ign https://deb.sipwise.com jessie/main Translation-en
W: Impossible to recovery
https://deb.sipwise.com/spce/mr4.2.1/dists/jessie/main/binary-amd64/Packages

E: Impossible to download some indexes: the old one will be used.

How can i solve the issue? If i try to navigate on the repo address
everything seems to be ok...

Thank you very much.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20160210/5ef860e9/attachment-0001.html>

From agranig at sipwise.com  Wed Feb 10 07:34:14 2016
From: agranig at sipwise.com (Andreas Granig)
Date: Wed, 10 Feb 2016 13:34:14 +0100
Subject: [Spce-user] Rings once, then disconnects!
In-Reply-To: <DB5PR06MB1557E9176F0A2FCED9233799BED20@DB5PR06MB1557.eurprd06.prod.outlook.com>
References: <DB5PR06MB1557AB8F343FE2DD1C4AC44FBEDE0@DB5PR06MB1557.eurprd06.prod.outlook.com>
 <56AF3323.3090101@sipwise.com>
 <DB5PR06MB15571F52E939DC8818644634BEDE0@DB5PR06MB1557.eurprd06.prod.outlook.com>
 <56AF88BF.1020002@sipwise.com>
 <DB5PR06MB15573307ABE294694E402401BEDF0@DB5PR06MB1557.eurprd06.prod.outlook.com>
 <56B067B3.4030606@sipwise.com>
 <DB5PR06MB1557E9176F0A2FCED9233799BED20@DB5PR06MB1557.eurprd06.prod.outlook.com>
Message-ID: <56BB2E46.5070407@sipwise.com>

Hi,

I guess it wouldn't be too hard to add filtering video, there is
http://www.kamailio.org/docs/modules/4.3.x/modules/sdpops.html#sdpops.f.sdp_remove_media
for this purpose.

You can try it in BRANCH_ROUTE_SBC of
/etc/ngcp-config/templates/etc/kamailio/proxy/proxy.cfg.tt2 right before
the log line "Request leaving server".

Andreas

On 02/05/2016 07:40 AM, William Hilsum wrote:
> Hi Alex,
> 
> Apologies - I think I'm unintentionally being confusing!
> 
> This is not a problem as such with Sipwise - it is the sip client with the option "Allow video calls" that when turned on, it automatically causes my upstream carrier to reject the call (after a single ring, which is just weird...)
> 
> Anyway, I have another PBX here where on a per carrier basis, I have the option "Disable video calls". When this is ticked, it basically strips out all relevant headers such as what caused my calls on Sipwise to fail.
> 
> So my question really is, after finding out the issue here, is there anyway I can get Sipwise to strip out these headers to avoid similar issues? I have not tested, but, I am guessing if anyone has a VOIP videophone, they may have the same issue as the softphone wasn't actually trying to establish a video stream, it was just saying it was video compatible in the header.
> 
> Thanks,
> 
> William
> 
> -----Original Message-----
> From: Spce-user [mailto:spce-user-bounces at lists.sipwise.com] On Behalf Of Alex Lutay
> Sent: 02 February 2016 08:24
> To: spce-user at lists.sipwise.com
> Subject: Re: [Spce-user] Rings once, then disconnects!
> 
> Dear William,
> 
> Check incoming invite from softphone to Sipwise, I am strongly believe you will find the same part there.
> 
> Sipwise doesn't change SDP part a lot, mainly it is replacing IP (I believe you have replaced '<PBX-IP>' in SDP part manually, otherwise it is an error) and limit list of codecs if necessary (turned off by default).
> 
> You can also try to make a call from your softphone through your Carrier directly and compare invite sent by softphone and Sipwise.
> 
> On the first look I do not see anything which can cause 500 on carrier side here. Was the correct IPv4/IPv6 in <PBX-IP> ?
> 
> On 02/02/2016 01:03 AM, William Hilsum wrote:
>> These additional lines in the "invite (SDP) packet" from Sipwise to the carrier platform break the connection:
>>
>> m=video 32562 RTP/AVP 34
>> c=IN IP4 <PBX-IP>
>> a=rtpmap:34 H263/90000
>> a=fmtp:34 QCIF=1;CIF=1;SQCIF=1;CIF4=1
>> a=sendrecv
>> a=rtcp:32563
>> a=direction:both
> 
> --
> Alexander Lutay
> Head of Quality Assurance
> Sipwise GmbH, Campus 21/Europaring F15
> AT-2345 Brunn am Gebirge
> 
> Office: +43(0)13012036
> Email: alutay at sipwise.com
> Website: http://www.sipwise.com
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
> 


From j_e_vargas at live.com  Wed Feb 10 22:12:52 2016
From: j_e_vargas at live.com (Jose E. Vargas B.)
Date: Wed, 10 Feb 2016 19:12:52 -0800
Subject: [Spce-user] Trunk to voicetrading configuration
In-Reply-To: <56B97952.1000800@prisnets.ch>
References: <56B4E6B0.5090307@prisnets.ch> <56B4B8C1.5060203@prisnets.ch>
 <56B4C9D1.1090008@sipwise.com>
 <EA2E104E-D65F-4872-A38A-801C9103418C@nevian.org>
 <001a01d16047$f50c8d00$df25a700$@prisnets.ch> <56B87B98.9090805@nevian.org>
 <56B97952.1000800@prisnets.ch>
Message-ID: <BLU436-SMTP150E7282A4A3F4D45A9519BCA80@phx.gbl>

Hi, 
Maybe you are having NAT transversal issue when attempting to connect from behind the 4G hot spot.  I have had problems when working with 4G mifi and sipwise SPCE, some times not even being able to register.  Did you try putting your IP phone behind a different wifi router. Just my 2 cents, as I am also new with SPCE.
Jose  


> On Feb 8, 2016, at 9:29 PM, Jephth? Feugn? <j.feugne at prisnets.ch> wrote:
> 
> Hello Serge,
> where can I start looking in other to solve my issue. No way to get support form voicetrading, the have a strange support policy. the best they give to customer is their faq.
> 
> Regards,
> Jeph
> 
> Le 08. 02. 16 12:27, Serge S. Yuriev a ?crit :
>> Hi,
>> 
>> For a start I would try to include proxying - I bet your upstream dislike c= string if it don't match source/contact IP.
>> And ask provider to inspect theirs logs.
>> 
>> On 05/02/16 22:03, Jephth? Feugn? wrote:
>>> HI!
>>> 
>>> 213.55.176.206, is my 4G connection behind which is connected my IP Phone registered with my hosted Sipwise CE server (xx.xx.xx.250).
>>> I can register directly to my Voicetrading account and place call behind my 4G connection, but not when I register to Sipwise.
>>> 
>>> Thank you helping me to solve this situation.
>>> 
>>> Jeph,
>>> 
>>> 
>>> _____
>>> Prisnets SA.
>>> Office:   +41 22 501 70 70 / Fax : +41 22 501 70 67
>>> Direct line : +41 22 508 72 70
>>> Mobile:  +41 78 728 92 97
>>> Email:     j.feugne at prisnets.ch
>>> Skype:   jephtech - Twitter:  @prisnet_ch
>>> http://www.prisnets.ch
>>> Prisnet Telecommunications SA.  Route de Saint-Julien 184 A, 1228 Plan-Les-Ouates CH.
>>> 
>>> -----Message d'origine-----
>>> De : Spce-user [mailto:spce-user-bounces at lists.sipwise.com] De la part de Serge Yuriev
>>> Envoy? : vendredi, 5 f?vrier 2016 19:40
>>> ? : spce-user at lists.sipwise.com
>>> Objet : Re: [Spce-user] Trunk to voicetrading configuration
>>> 
>>> Hi,
>>> 
>>> Who is 213.55.176.206? Is this someone you should proxy before passing upstream? Maybe your provider filters such requests?
>>> 
>> 
> 
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 1776 bytes
Desc: not available
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20160210/331e0bb7/attachment-0001.p7s>

From raul.alonso at tpartner.net  Thu Feb 11 07:18:32 2016
From: raul.alonso at tpartner.net (Raul)
Date: Thu, 11 Feb 2016 13:18:32 +0100
Subject: [Spce-user] Failed to create domain (A service could not be reached)
Message-ID: <089601d164c6$5335c4f0$f9a14ed0$@tpartner.net>

Hi guys, 

 

We have configured a virtual interface (with ip 10.255.255.100) to solve the
Audiocodes issue and then, since we did that, when we try to create a new
domain, NGCP-panel report us that error.

 

Feb 11 13:10:44 proxy02 ngcp-panel: ERROR: IP=88XXXXX
CALLED=Controller::Domain::create TX=1431E2001DAEC050 USER=administrator
DATA={ 'save' => 'Guardar', 'domain' => 'sip02.tpartner.net', 'submitid' =>
'', 'reseller.id' => '2', 'id' => ''} MSG="" LOG="Fallo al crear dominio
(DBIx::Class::Schema::txn_do(): problem connecting to "10.255.255.100", port
5582: Connection refused at /usr/share/perl5/NGCP/Panel/Utils/Prosody.pm
line 13 at /usr/share/perl5/NGCP/Panel/Controller/Domain.pm line 137#012)"

 

Thanks

Raul.

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20160211/0a24ee43/attachment-0001.html>

From agranig at sipwise.com  Thu Feb 11 08:00:07 2016
From: agranig at sipwise.com (Andreas Granig)
Date: Thu, 11 Feb 2016 14:00:07 +0100
Subject: [Spce-user] Failed to create domain (A service could not be
 reached)
In-Reply-To: <089601d164c6$5335c4f0$f9a14ed0$@tpartner.net>
References: <089601d164c6$5335c4f0$f9a14ed0$@tpartner.net>
Message-ID: <56BC85D7.5010706@sipwise.com>

Hi,

Please check whether prosody is running and is listening on that ip.
Please also search the mailing list archive for prosody, since this
issue occured like 1-2 years ago when people were starting to use this
hack. Which SPCE version are you using? If I remember correctly, the
whole procedure has been simplified and optimized somewhere in the 3.x
series.

Andreas

On 02/11/2016 01:18 PM, Raul wrote:
> Hi guys,
> 
>  
> 
> We have configured a virtual interface (with ip 10.255.255.100) to solve
> the Audiocodes issue and then, since we did that, when we try to create
> a new domain, NGCP-panel report us that error.
> 
>  
> 
> Feb 11 13:10:44 proxy02 ngcp-panel: ERROR: IP=88XXXXX
> CALLED=Controller::Domain::create TX=1431E2001DAEC050 USER=administrator
> DATA={ 'save' => 'Guardar', 'domain' => 'sip02.tpartner.net', 'submitid'
> => '', 'reseller.id' => '2', 'id' => ''} MSG="" LOG="Fallo al crear
> dominio (DBIx::Class::Schema::txn_do(): problem connecting to
> "10.255.255.100", port 5582: Connection refused at
> /usr/share/perl5/NGCP/Panel/Utils/Prosody.pm line 13 at
> /usr/share/perl5/NGCP/Panel/Controller/Domain.pm line 137#012)"
> 
>  
> 
> Thanks
> 
> Raul.
> 
>  
> 
>  
> 
> 
> 
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
> 


From raul.alonso at tpartner.net  Thu Feb 11 09:11:27 2016
From: raul.alonso at tpartner.net (Raul)
Date: Thu, 11 Feb 2016 15:11:27 +0100
Subject: [Spce-user] Failed to create domain (A service could not be
	reached)
In-Reply-To: <56BC85D7.5010706@sipwise.com>
References: <089601d164c6$5335c4f0$f9a14ed0$@tpartner.net>
 <56BC85D7.5010706@sipwise.com>
Message-ID: <094101d164d6$192c2f00$4b848d00$@tpartner.net>

Hi Andreas,

Prosody si running but in 127.0.0.1 not in dummy IP.
I'm using the latest version LTS 3.8.4

Regrads,
Ra?l.

-----Mensaje original-----
De: Spce-user [mailto:spce-user-bounces at lists.sipwise.com] En nombre de
Andreas Granig
Enviado el: jueves, 11 de febrero de 2016 14:00
Para: spce-user at lists.sipwise.com
Asunto: Re: [Spce-user] Failed to create domain (A service could not be
reached)

Hi,

Please check whether prosody is running and is listening on that ip.
Please also search the mailing list archive for prosody, since this
issue occured like 1-2 years ago when people were starting to use this
hack. Which SPCE version are you using? If I remember correctly, the
whole procedure has been simplified and optimized somewhere in the 3.x
series.

Andreas

On 02/11/2016 01:18 PM, Raul wrote:
> Hi guys,
> 
>  
> 
> We have configured a virtual interface (with ip 10.255.255.100) to solve
> the Audiocodes issue and then, since we did that, when we try to create
> a new domain, NGCP-panel report us that error.
> 
>  
> 
> Feb 11 13:10:44 proxy02 ngcp-panel: ERROR: IP=88XXXXX
> CALLED=Controller::Domain::create TX=1431E2001DAEC050 USER=administrator
> DATA={ 'save' => 'Guardar', 'domain' => 'sip02.tpartner.net', 'submitid'
> => '', 'reseller.id' => '2', 'id' => ''} MSG="" LOG="Fallo al crear
> dominio (DBIx::Class::Schema::txn_do(): problem connecting to
> "10.255.255.100", port 5582: Connection refused at
> /usr/share/perl5/NGCP/Panel/Utils/Prosody.pm line 13 at
> /usr/share/perl5/NGCP/Panel/Controller/Domain.pm line 137#012)"
> 
>  
> 
> Thanks
> 
> Raul.
> 
>  
> 
>  
> 
> 
> 
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
> 
_______________________________________________
Spce-user mailing list
Spce-user at lists.sipwise.com
https://lists.sipwise.com/listinfo/spce-user



From matthias.hohl at telematica.at  Thu Feb 11 09:21:27 2016
From: matthias.hohl at telematica.at (Matthias Hohl)
Date: Thu, 11 Feb 2016 15:21:27 +0100 (CET)
Subject: [Spce-user] Lost connection to MySQL server during query (2013)
Message-ID: <1738202811.280332.1455200487946.JavaMail.zimbra@telematica.at>

Hello, 

we found a problem with SPCE and MySQL, so subscribers can't connect at some time: 
If we check log file, we see that the MySQL DB has a lost connection error. 

We have a intention that it maybe has something in common with our mySQL backup script, cause it just happens, and this not everytime, when the cronjob doing the script. 
I think it could be a problem with the mysqldump, that this freeze the tables and SPCE couldn't write into the tables. 

We try now with "--lock-tables=false" and waiting, if this happens again in the next few hours. 
What do you think, any other idea about that? 

Thanks. 



Backup-Job: 

#!/bin/sh 

DEST=backup-`date +"%Y%m%d-%H%M"` 

PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin" 

export PATH 



/usr/bin/mysqldump -uroot -pvN85tzTPp65QfW9 -A --events > /tmp/$DEST.mysql.sql 

tar czpf /tmp/$DEST.tgz -C / etc/ngcp-config etc/mysql home/jail/home/cdrexport -C /tmp $DEST.mysql.sql 

rm -f /tmp/$DEST.mysql.sql 



/usr/bin/ftp -pn >/dev/null 2>&1 <<end 

open ftp.xxx.xxx 

user xxx.xxx xxxx 

put /tmp/$DEST.tgz $DEST.tgz 

bye 

end 



rm -f /tmp/$DEST.tgz 



Cronjob: 

0,30 * * * * /root/backup.sh 



ERROR MESSAGE: 


Feb 10 00 :00:25 spce (local7.err) proxy[3749]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013) 

Feb 10 00 :00:25 spce (local7.err) proxy[3753]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013) 

Feb 10 00 :00:28 spce (local7.err) proxy[3741]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013) 

Feb 10 00 :00:29 spce (local7.err) proxy[3756]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013) 

Feb 10 00 :00:29 spce (local7.err) proxy[3752]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013) 

Feb 10 00 :00:31 spce (local7.err) proxy[3742]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013) 

Feb 10 00 :00:31 spce (local7.err) proxy[3747]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013) 

Feb 10 00 :30:18 spce (local7.err) proxy[3745]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013) 

Feb 10 00 :30:19 spce (local7.err) proxy[3742]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013) 

Feb 10 00 :30:19 spce (local7.err) proxy[3756]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013) 

Feb 10 00 :30:19 spce (local7.err) proxy[3741]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013) 

Feb 10 02 :00:17 spce (local7.err) proxy[3752]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013) 

Feb 10 02 :00:17 spce (local7.err) proxy[3749]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013) 

Feb 10 02 :00:17 spce (local7.err) proxy[3745]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013) 

Feb 10 02 :30:22 spce (local7.err) proxy[3752]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013) 

Feb 10 02 :30:22 spce (local7.err) proxy[3742]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013) 

Feb 10 02 :30:22 spce (local7.err) proxy[3747]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013) 

Feb 10 02 :30:22 spce (local7.err) proxy[3745]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013) 

Feb 10 02 :30:23 spce (local7.err) proxy[3753]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013) 

Feb 10 03 :00:19 spce (local7.err) proxy[3747]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013) 

Feb 10 03 :00:20 spce (local7.err) proxy[3749]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013) 

Feb 10 03 :00:22 spce (local7.err) proxy[3753]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013) 

Feb 10 03 :00:22 spce (local7.err) proxy[3745]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013) 

Feb 10 03 :00:23 spce (local7.err) proxy[3752]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013) 

Feb 10 03 :00:26 spce (local7.err) proxy[3749]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013) 

Feb 10 03 :30:22 spce (local7.err) proxy[3747]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013) 

Feb 10 03 :30:22 spce (local7.err) proxy[3753]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013) 

Feb 10 03 :30:23 spce (local7.err) proxy[3749]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013) 

Feb 10 06 :30:19 spce (local7.err) proxy[3747]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013) 

Feb 10 06 :30:19 spce (local7.err) proxy[3752]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013) 

Feb 10 06 :30:19 spce (local7.err) proxy[3742]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013) 

Feb 10 06 :30:19 spce (local7.err) proxy[3753]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013) 

Feb 10 06 :30:19 spce (local7.err) proxy[3741]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013) 

Feb 10 06 :30:19 spce (local7.err) proxy[3756]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013) 

Feb 10 08 :30:20 spce (local7.err) proxy[3747]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013) 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20160211/6a4cb818/attachment-0001.html>

From me at nevian.org  Fri Feb 12 01:55:48 2016
From: me at nevian.org (Serge S. Yuriev)
Date: Fri, 12 Feb 2016 09:55:48 +0300
Subject: [Spce-user] Limit by minutes
Message-ID: <1779671455260148@web27h.yandex.ru>

An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20160212/10ed3dac/attachment-0001.html>

From me at nevian.org  Fri Feb 12 01:59:09 2016
From: me at nevian.org (Serge Yuriev)
Date: Fri, 12 Feb 2016 09:59:09 +0300
Subject: [Spce-user] Trunk to voicetrading configuration
In-Reply-To: <56B97952.1000800@prisnets.ch>
References: <56B97952.1000800@prisnets.ch> <56B4E6B0.5090307@prisnets.ch>
 <56B4B8C1.5060203@prisnets.ch> <56B4C9D1.1090008@sipwise.com>
 <EA2E104E-D65F-4872-A38A-801C9103418C@nevian.org>
 <001a01d16047$f50c8d00$df25a700$@prisnets.ch> <56B87B98.9090805@nevian.org>
Message-ID: <7150A143-960A-4E4B-B2A6-B141080AF1BB@nevian.org>

Hi,

One more time: check why you announce customer IP in SDP? Perhaps you disabled proxying for domain/subscriber?

NB and go away from this provider as they should not leave you alone - you pay them.

-- 
Wbr, Serge via mobile

09.02.2016, 08:30, "Jephth? Feugn?" <j.feugne at prisnets.ch>:
> 
> Hello Serge,
> where can I start looking in other to solve my issue. No way to get 
> support form voicetrading, the have a strange support policy. the best 
> they give to customer is their faq.
> 
> Regards,
> Jeph
> 
> Le 08. 02. 16 12:27, Serge S. Yuriev a ?crit :
> 
>>  Hi,
>> 
>>  For a start I would try to include proxying - I bet your upstream 
>>  dislike c= string if it don't match source/contact IP.
>>  And ask provider to inspect theirs logs.
>> 
>>>  On 05/02/16 22:03, Jephth? Feugn? wrote:
>>>  HI!
>>> 
>>>  213.55.176.206, is my 4G connection behind which is connected my IP 
>>>  Phone registered with my hosted Sipwise CE server (xx.xx.xx.250).
>>>  I can register directly to my Voicetrading account and place call 
>>>  behind my 4G connection, but not when I register to Sipwise.
>>> 
>>>  Thank you helping me to solve this situation.
>>> 
>>>  Jeph,
>>> 
>>> 
>>>  _____
>>>  Prisnets SA.
>>>  Office: +41 22 501 70 70 / Fax : +41 22 501 70 67
>>>  Direct line : +41 22 508 72 70
>>>  Mobile: +41 78 728 92 97
>>>  Email: j.feugne at prisnets.ch
>>>  Skype: jephtech - Twitter: @prisnet_ch
>>>  http://www.prisnets.ch
>>>  Prisnet Telecommunications SA. Route de Saint-Julien 184 A, 1228 
>>>  Plan-Les-Ouates CH.
>>> 
>>>  -----Message d'origine-----
>>>  De : Spce-user [mailto:spce-user-bounces at lists.sipwise.com] De la 
>>>  part de Serge Yuriev
>>>  Envoy? : vendredi, 5 f?vrier 2016 19:40
>>>  ? : spce-user at lists.sipwise.com
>>>  Objet : Re: [Spce-user] Trunk to voicetrading configuration
>>> 
>>>  Hi,
>>> 
>>>  Who is 213.55.176.206? Is this someone you should proxy before 
>>>  passing upstream? Maybe your provider filters such requests?
> 
> 
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
> 


From alutay at sipwise.com  Fri Feb 12 10:05:20 2016
From: alutay at sipwise.com (Alex Lutay)
Date: Fri, 12 Feb 2016 16:05:20 +0100
Subject: [Spce-user] Upgrade to 4.2.1 causes in a cronjob failure
In-Reply-To: <027e01d15cdc$b940fea0$2bc2fbe0$@telematica.at>
References: <027e01d15cdc$b940fea0$2bc2fbe0$@telematica.at>
Message-ID: <56BDF4B0.40100@sipwise.com>

Hi all,

JFYI, the warning should be fixed with the latest
hotfix for mr4.2.1 ossbss:

> ngcp-ossbss (3.18.1.3+0~mr4.2.1.3) unstable; urgency=medium
> 
>   [ Kirill Solomko ]
>   * [fb693b2] MT#17669 adapted perl code for perl 5.20

Tnx for reporting!

On 02/01/2016 11:38 AM, Matthias Hohl wrote:
> I get this error per mail everytime when the fraud auto lock is running
> as cron.
> 
> What does this mean? An how can I solve it?
> 
> Cron <root at spce> if /usr/sbin/ngcp-check_active -q; then
> /usr/sbin/ngcp-fraud-auto-lock; fi
> 
> Smartmatch is experimental at /usr/share/perl5/Sipwise/Provisioning.pm
> line 1122.
> Use of my $_ is experimental at /usr/share/perl5/Sipwise/Provisioning.pm
> line 1146.
> defined(@array) is deprecated at /usr/share/perl5/PDF/Reuse.pm line 993.
> (Maybe you should just omit the defined()?)
> defined(@array) is deprecated at /usr/share/perl5/PDF/Reuse.pm line 993.
> (Maybe you should just omit the defined()?)
> Smartmatch is experimental at
> /usr/share/perl5/Sipwise/Provisioning/Voip/DB.pm line 748.
> given is experimental at /usr/share/perl5/Sipwise/Provisioning/Voip.pm
> line 6629.
> when is experimental at /usr/share/perl5/Sipwise/Provisioning/Voip.pm
> line 6630.
> when is experimental at /usr/share/perl5/Sipwise/Provisioning/Voip.pm
> line 6634.
> Smartmatch is experimental at
> /usr/share/perl5/Sipwise/Provisioning/Voip.pm line 6992.
> Smartmatch is experimental at
> /usr/share/perl5/Sipwise/Provisioning/Voip.pm line 7047.
> Smartmatch is experimental at
> /usr/share/perl5/Sipwise/Provisioning/Voip.pm line 7236.
> Smartmatch is experimental at
> /usr/share/perl5/Sipwise/Provisioning/Voip.pm line 7236.
> Smartmatch is experimental at
> /usr/share/perl5/Sipwise/Provisioning/Voip.pm line 7240.
> Smartmatch is experimental at
> /usr/share/perl5/Sipwise/Provisioning/Voip.pm line 7240.
> Smartmatch is experimental at
> /usr/share/perl5/Sipwise/Provisioning/Voip.pm line 7244.
> Smartmatch is experimental at
> /usr/share/perl5/Sipwise/Provisioning/Voip.pm line 7244.
> Smartmatch is experimental at
> /usr/share/perl5/Sipwise/Provisioning/Voip.pm line 7248.
> Smartmatch is experimental at
> /usr/share/perl5/Sipwise/Provisioning/Voip.pm line 7248.
> Smartmatch is experimental at
> /usr/share/perl5/Sipwise/Provisioning/Voip.pm line 7252.
> Smartmatch is experimental at
> /usr/share/perl5/Sipwise/Provisioning/Voip.pm line 7252.
> Use of my $_ is experimental at
> /usr/share/perl5/Sipwise/Provisioning/Voip.pm line 7259.

-- 
Alexander Lutay
Head of Quality Assurance
Sipwise GmbH, Campus 21/Europaring F15
AT-2345 Brunn am Gebirge

Office: +43(0)13012036
Email: alutay at sipwise.com
Website: http://www.sipwise.com


From matthias.hohl at telematica.at  Fri Feb 12 10:38:29 2016
From: matthias.hohl at telematica.at (Matthias Hohl)
Date: Fri, 12 Feb 2016 16:38:29 +0100 (CET)
Subject: [Spce-user] Urgent Problem after newest update 4.2.1
Message-ID: <495972341.303395.1455291509891.JavaMail.zimbra@telematica.at>

Hello, 

after latest update to 4.2.1 we analysied a problem with call forwardings. 
We set a CF for unconditional and unavailable and this works like a charme in the last releases, but after upgrade to 4.2.1 the CF doesn't work anymore. 

Any solution about this? 


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20160212/5998e063/attachment-0001.html>

From matthias.hohl at telematica.at  Fri Feb 12 11:12:48 2016
From: matthias.hohl at telematica.at (Matthias Hohl)
Date: Fri, 12 Feb 2016 17:12:48 +0100 (CET)
Subject: [Spce-user] Concurrent max calls exceeded for callee
In-Reply-To: <21a6c01d1582c$eca02aa0$c5e07fe0$@telematica.at>
References: <08bc01d0ff47$05ffb770$11ff2650$@telematica.at>
 <094501d0ff5e$38125a80$a8370f80$@telematica.at>
 <2E0234B6-C07A-4D5A-AC8B-BB0EC1EB8694@telematica.at>
 <5639CECA.4000502@sipwise.com>
 <01fe01d13796$86cf2700$946d7500$@telematica.at> <56713A32.10403@sipwise.com>
 <21a6c01d1582c$eca02aa0$c5e07fe0$@telematica.at>
Message-ID: <1365632450.303696.1455293568776.JavaMail.zimbra@telematica.at>

Hello,

also with upgrade to 4.2.1 we still have the same problems with  Conncurent max calls exceeded for callee:

Example:
Feb 12 16:29:20 spce (local7.notice) proxy[3749]: NOTICE: <script>: Concurrent max calls exceeded for callee 'aef1bad0-ed48-4697-a55e-6ab25e723b5a' - R=sip:43137xxxxx at sip.xxx.at:5060 ID=3b0717627b45827e6a9a0f7a50f5f42a at xx.170.208.xxx:5060 UA='GlobalCall+T.38'
Feb 12 16:33:56 spce (local7.notice) proxy[3742]: NOTICE: <script>: Concurrent max calls exceeded for callee 'aef1bad0-ed48-4697-a55e-6ab25e723b5a' - R=sip:43137xxxxx at sip.xxx.at:5060 ID=2277847967b2b40325f5720a268a9056 at xx.170.208.xxx:5060 UA='GlobalCall+T.38'

But there are no concurrent calls on this subscriber!!!!

After doing "redis restart" it works again without problems.

Also there is NO voice message playing, that there are concurrent calls exceeded, so the callee just hear the ringing tone and nothing else.
But the Soundfile is set right. I load the default files and set the soundset on domain layer. so it should work.. outgoing the voice is speaking but incoming the callee doesn't hear anything just ringing!

please fix this as soon as possible.


Thanks!


----- Urspr?ngliche Mail -----
Von: "Matthias Hohl" <matthias.hohl at telematica.at>
An: "Daniel Grotti" <dgrotti at sipwise.com>, spce-user at lists.sipwise.com
Gesendet: Dienstag, 26. Januar 2016 12:30:17
Betreff: Re: [Spce-user] Concurrent max calls exceeded for callee

Hello,

when do you think, that you fix this issue, cause I have this problem
several times a week :/
I am currently on the latest 4.1.1 version including updates from last week.

Thanks.

-----Urspr?ngliche Nachricht-----
Von: Daniel Grotti [mailto:dgrotti at sipwise.com] 
Gesendet: Mittwoch, 16. Dezember 2015 11:17
An: Matthias Hohl <matthias.hohl at telematica.at>; spce-user at lists.sipwise.com
Betreff: Re: AW: [Spce-user] Concurrent max calls exceeded for callee

Hi Matthias,
We are aware of the problem on mr3.8.4 version and 4.x.
We are working on it since a while in order to fix definitely this issue.

Stay tuned.

--
Daniel Grotti
VoIP Engineer


Sipwise GmbH
Europaring F15 | 2345 Brunn am Gebirge, Austria | www.sipwise.com

On 12/16/2015 01:13 AM, Matthias Hohl wrote:
> Hello,
> 
> i have again this redis counter problem with "max calls exceeded for
callee"
> for some subscribers.
> It comes from time to time, that the SPCE told me, that max calls 
> exceeded but nobody is calling.
> 
> After restarting redis service (/etc/init.d/redis-server restart) 
> everything is working fine again, but I must restart the redis every few
days/week.
> 
> Is there another solution for this problem?
> 
> How could this happen, again and again on different subscribers?
> 
> Thanks for your answer!
> 
> 
> 
> -----Urspr?ngliche Nachricht-----
> Von: Spce-user [mailto:spce-user-bounces at lists.sipwise.com] Im Auftrag 
> von Daniel Grotti
> Gesendet: Mittwoch, 4. November 2015 10:24
> An: spce-user at lists.sipwise.com
> Betreff: Re: [Spce-user] Concurrent max calls exceeded for callee
> 
> Hi,
> you can reset redis counters for that user to 0.
> for example:
> 
> 
> # redis-cli -n 3 keys \*
> 
> 
> 
> # redis-cli -n 3 get userout:<SUBS_UUID> "2"
> # redis-cli -n 3 set userout:<SUBS_UUID> 0 OK # redis-cli -n 3 get 
> userout:<SUBS_UUID> "0"
> 
> 
> --
> Daniel Grotti
> VoIP Engineer
> 
> 
> Sipwise GmbH
> Europaring F15 | 2345 Brunn am Gebirge, Austria | www.sipwise.com
> 
> On 11/03/2015 10:29 AM, Matthias Hohl wrote:
>> Today the same problem happen again by an other subscriber. The 
>> subscriber has 4 lines but just one person is using the subscriber.
>> They place several calls this morning and called me now and told me, 
>> that she cant call place calls anymore cause phone told her: "all 
>> concurrent lines are in use, please try again later". I checked the 
>> server and the pbx and there are no active calls, so the limit cant 
>> be
> exceeded.
>>
>> After set the concurrent max limit to 5 or higher in subscriber 
>> preferences, calls works again, if i set it back to 4, the voice 
>> message comes again.
>>
>> This happen now several times with different subscribers in different 
>> time intervals. It looks like this is a redis bug or what do you think?
>>
>> Hope to read from you soon with some more informations.
>>
>> Btw: is restarting redis-server the right solution?
>>>
>>> /etc/init.d/redis-server stop
>>>
>>> rm -rf /var/lib/redis/*
>>>
>>> /etc/init.d/redis-server start
>>>
>>
>>
>> Von meinem iPhone gesendet
>>
>> Am 05.10.2015 um 13:09 schrieb Matthias Hohl 
>> <matthias.hohl at telematica.at <mailto:matthias.hohl at telematica.at>>:
>>
>>> I found a hint in an older posting?
>>>
>>> I have done now the following:
>>>
>>>  
>>>
>>> /etc/init.d/redis-server stop
>>>
>>> rm -rf /var/lib/redis/*
>>>
>>> /etc/init.d/redis-server start
>>>
>>>  
>>>
>>> It looks that it works now again, but can you tell me, what happened 
>>> and how this problem can be reproduced, and if this is the only 
>>> solution for it?
>>>
>>>  
>>>
>>> Thanks.
>>>
>>>  
>>>
>>> *Von:*Spce-user [mailto:spce-user-bounces at lists.sipwise.com] *Im 
>>> Auftrag von *Matthias Hohl
>>> *Gesendet:* Montag, 5. Oktober 2015 10:23
>>> *An:* spce-user at lists.sipwise.com
>>> <mailto:spce-user at lists.sipwise.com>
>>> *Betreff:* [Spce-user] Concurrent max calls exceeded for callee
>>>
>>>  
>>>
>>> Hello,
>>>
>>>  
>>>
>>> found out new problem today?
>>>
>>>  
>>>
>>> I subscriber can?t place or get calls and kamilio-proxy.log told me, 
>>> that ?Concurrent max calls exceeded for callee? and also sometimes 
>>> ?Concurrent_max calls exceeded for caller?
>>>
>>>  
>>>
>>> But the subscriber has 8 lines and no concurrent calls.
>>>
>>>  
>>>
>>>  
>>>
>>> What can I check to solve this problem?
>>>
>>>  
>>>
>>>  
>>>
>>> _______________________________________________
>>> Spce-user mailing list
>>> Spce-user at lists.sipwise.com <mailto:Spce-user at lists.sipwise.com>
>>> https://lists.sipwise.com/listinfo/spce-user
>>
>>
>> _______________________________________________
>> Spce-user mailing list
>> Spce-user at lists.sipwise.com
>> https://lists.sipwise.com/listinfo/spce-user
>>
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
> 
_______________________________________________
Spce-user mailing list
Spce-user at lists.sipwise.com
https://lists.sipwise.com/listinfo/spce-user


From matthias.hohl at telematica.at  Fri Feb 12 11:52:53 2016
From: matthias.hohl at telematica.at (Matthias Hohl)
Date: Fri, 12 Feb 2016 17:52:53 +0100 (CET)
Subject: [Spce-user] Urgent Problem after newest update 4.2.1
In-Reply-To: <495972341.303395.1455291509891.JavaMail.zimbra@telematica.at>
References: <495972341.303395.1455291509891.JavaMail.zimbra@telematica.at>
Message-ID: <E4F649CF-348C-45D4-8EC8-0E394134C717@telematica.at>

Hello again,

We found the failure. It happens in combination with the max concurrent call limit exceeded for callee problem i post several minutes later.



Von meinem iPhone gesendet

> Am 12.02.2016 um 16:39 schrieb Matthias Hohl <matthias.hohl at telematica.at>:
> 
> Hello,
> 
> after latest update to 4.2.1 we analysied a problem with call forwardings.
> We set a CF for unconditional and unavailable and this works like a charme in the last releases, but after upgrade to 4.2.1 the CF doesn't work anymore.
> 
> Any solution about this?
> 
> 
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20160212/e72b5536/attachment-0001.html>

From me at nevian.org  Fri Feb 12 15:42:08 2016
From: me at nevian.org (Serge Yuriev)
Date: Fri, 12 Feb 2016 23:42:08 +0300
Subject: [Spce-user] Best way to replace SEMS
Message-ID: <A7FBF9D1-A0CE-4D16-B5A6-C5B9ABE93215@nevian.org>

Hello,

We need fully opaque SBC with media anchoring so I want to replace SEMS with something like FreeSWITCH or Asterisk.
That I need besides of headers processing?

btw There is fork of SEMS with needed features but it is a part of YETI-switch project and based on pretty old version. It would be nice to port these here.

-- 
Serge S. Yuriev





From manwe at sipdoc.net  Fri Feb 12 16:53:36 2016
From: manwe at sipdoc.net (Jon Bonilla (Manwe))
Date: Fri, 12 Feb 2016 22:53:36 +0100
Subject: [Spce-user] Best way to replace SEMS
In-Reply-To: <A7FBF9D1-A0CE-4D16-B5A6-C5B9ABE93215@nevian.org>
References: <A7FBF9D1-A0CE-4D16-B5A6-C5B9ABE93215@nevian.org>
Message-ID: <20160212225336.4eccdb5a@multivac>

El Fri, 12 Feb 2016 23:42:08 +0300
Serge Yuriev <me at nevian.org> escribi?:

> Hello,
> 
> We need fully opaque SBC with media anchoring so I want to replace SEMS with
> something like FreeSWITCH or Asterisk. That I need besides of headers
> processing?
> 
> btw There is fork of SEMS with needed features but it is a part of
> YETI-switch project and based on pretty old version. It would be nice to port
> these here.
> 

sems is a core part of the ngcp solution. It is heavily mantained and developed
by Frafos GmbH and Sipwise spends a lot of money and time supporting the
project. 

sems does much more than header filtering in the spce and even more in the pro
and carrier solutions. You cannot replace with other projects unless you want
to do heavy customization of your system. I can't even imagine how hard that
could be. 

Regarding those YETI functionalities you need, it would be nice if you could
sponsor Frafos so they add those ones to their public branch. Which are they
btw? 


cheers,

Jon

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: Firma digital OpenPGP
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20160212/89fca6d5/attachment-0001.sig>

From matthias.hohl at telematica.at  Mon Feb 15 05:38:34 2016
From: matthias.hohl at telematica.at (Matthias Hohl)
Date: Mon, 15 Feb 2016 11:38:34 +0100 (CET)
Subject: [Spce-user] Lost connection to MySQL server during query (2013)
In-Reply-To: <1738202811.280332.1455200487946.JavaMail.zimbra@telematica.at>
References: <1738202811.280332.1455200487946.JavaMail.zimbra@telematica.at>
Message-ID: <0e8601d167dd$03b14e80$0b13eb80$@telematica.at>

Hello,

 

I want to give you a short update: The problem is still there.

 

If we do a mysql dump wie got following messages:

Also with mysql dump ?lock-tables? or ?single-transaction? there is no difference. By doing mysql dump the db lost connection, with everytime the same failure:

 

Feb 15 01:00:16 spce (local7.err) proxy[20447]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013)

Feb 15 01:00:16 spce (local7.err) proxy[20447]: ERROR: <core> [db_query.c:339]: db_do_update(): error while submitting query

Feb 15 01:00:16 spce (local7.err) proxy[20447]: ERROR: usrloc [ucontact.c:1142]: db_update_ucontact_ruid(): updating database failed

Feb 15 01:00:16 spce (local7.err) proxy[20447]: ERROR: usrloc [ucontact.c:1658]: update_contact_db(): failed to update database

Feb 15 01:00:16 spce (local7.err) proxy[20447]: ERROR: registrar [save.c:775]: update_contacts(): failed to update contact

 

We separate now the mysql dump from our other backup script, so the mysql dump will be done only 1 time a day at 01:00 o?clock to temporary fix the connection lost problem, until we get some input from you.

But in the meantime we found another ?connection lost? problem, which is not relevated to our mysqldump backup script.

 

It happens today 4 times at different times:

 

Feb 15 10:37:09 spce (local7.err) proxy[20453]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013)

Feb 15 10:37:09 spce (local7.err) proxy[20453]: ERROR: <core> [db_query.c:292]: db_do_delete(): error while submitting query

Feb 15 10:37:09 spce (local7.err) proxy[20453]: ERROR: dialog [dlg_db_handler.c:620]: remove_dialog_from_db(): failed to delete database information

 

I believe this could also be correlating with the ?redis counter? problem I posted (Concurrent max calls exceeded for callee) some days before. Maybe is this the reason, why the redis counter must be restarted to clear the active dialogs out ouf db.

 

Could this be true? And if yes, the main problem is the mysql lost connection problem, but how to fix that?

Has anybody maybe a solution for this problem?

 

It is very annoying if there are db lost connection problems :/

 

Thank you very much for any help.

 

 

 

Von: Spce-user [mailto:spce-user-bounces at lists.sipwise.com] Im Auftrag von Matthias Hohl
Gesendet: Donnerstag, 11. Februar 2016 15:21
An: spce-user at lists.sipwise.com
Betreff: [Spce-user] Lost connection to MySQL server during query (2013)

 

Hello,

 

we found a problem with SPCE and MySQL, so subscribers can't connect at some time:

If we check log file, we see that the MySQL DB has a lost connection error.

 

We have a intention that it maybe has something in common with our mySQL backup script, cause it just happens, and this not everytime, when the cronjob doing the script.

I think it could be a problem with the mysqldump, that this freeze the tables and SPCE couldn't write into the tables.

 

We try now with "--lock-tables=false" and waiting, if this happens again in the next few hours.

What do you think, any other idea about that?

 

Thanks.

 

Backup-Job:

#!/bin/sh

DEST=backup-`date +"%Y%m%d-%H%M"`

PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"

export PATH

 

/usr/bin/mysqldump -uroot -pvN85tzTPp65QfW9 -A --events > /tmp/$DEST.mysql.sql

tar czpf /tmp/$DEST.tgz -C / etc/ngcp-config etc/mysql home/jail/home/cdrexport -C /tmp $DEST.mysql.sql

rm -f /tmp/$DEST.mysql.sql

 

/usr/bin/ftp -pn >/dev/null 2>&1 <<end

open  <ftp://ftp.xxx.xxx> ftp.xxx.xxx

user xxx.xxx xxxx

put /tmp/$DEST.tgz $DEST.tgz

bye

end

 

rm -f /tmp/$DEST.tgz

 

Cronjob:

0,30 * * * *    /root/backup.sh

 

 

 

ERROR MESSAGE:

Feb 10 00:00:25 spce (local7.err) proxy[3749]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013)

Feb 10 00:00:25 spce (local7.err) proxy[3753]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013)

Feb 10 00:00:28 spce (local7.err) proxy[3741]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013)

Feb 10 00:00:29 spce (local7.err) proxy[3756]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013)

Feb 10 00:00:29 spce (local7.err) proxy[3752]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013)

Feb 10 00:00:31 spce (local7.err) proxy[3742]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013)

Feb 10 00:00:31 spce (local7.err) proxy[3747]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013)

Feb 10 00:30:18 spce (local7.err) proxy[3745]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013)

Feb 10 00:30:19 spce (local7.err) proxy[3742]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013)

Feb 10 00:30:19 spce (local7.err) proxy[3756]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013)

Feb 10 00:30:19 spce (local7.err) proxy[3741]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013)

Feb 10 02:00:17 spce (local7.err) proxy[3752]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013)

Feb 10 02:00:17 spce (local7.err) proxy[3749]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013)

Feb 10 02:00:17 spce (local7.err) proxy[3745]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013)

Feb 10 02:30:22 spce (local7.err) proxy[3752]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013)

Feb 10 02:30:22 spce (local7.err) proxy[3742]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013)

Feb 10 02:30:22 spce (local7.err) proxy[3747]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013)

Feb 10 02:30:22 spce (local7.err) proxy[3745]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013)

Feb 10 02:30:23 spce (local7.err) proxy[3753]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013)

Feb 10 03:00:19 spce (local7.err) proxy[3747]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013)

Feb 10 03:00:20 spce (local7.err) proxy[3749]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013)

Feb 10 03:00:22 spce (local7.err) proxy[3753]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013)

Feb 10 03:00:22 spce (local7.err) proxy[3745]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013)

Feb 10 03:00:23 spce (local7.err) proxy[3752]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013)

Feb 10 03:00:26 spce (local7.err) proxy[3749]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013)

Feb 10 03:30:22 spce (local7.err) proxy[3747]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013)

Feb 10 03:30:22 spce (local7.err) proxy[3753]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013)

Feb 10 03:30:23 spce (local7.err) proxy[3749]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013)

Feb 10 06:30:19 spce (local7.err) proxy[3747]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013)

Feb 10 06:30:19 spce (local7.err) proxy[3752]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013)

Feb 10 06:30:19 spce (local7.err) proxy[3742]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013)

Feb 10 06:30:19 spce (local7.err) proxy[3753]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013)

Feb 10 06:30:19 spce (local7.err) proxy[3741]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013)

Feb 10 06:30:19 spce (local7.err) proxy[3756]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013)

Feb 10 08:30:20 spce (local7.err) proxy[3747]: ERROR: db_mysql [km_dbase.c:124]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20160215/a8036837/attachment-0001.html>

From apogrebennyk at sipwise.com  Mon Feb 15 05:59:49 2016
From: apogrebennyk at sipwise.com (Andrew Pogrebennyk)
Date: Mon, 15 Feb 2016 11:59:49 +0100
Subject: [Spce-user] Concurrent max calls exceeded for callee
In-Reply-To: <1365632450.303696.1455293568776.JavaMail.zimbra@telematica.at>
References: <08bc01d0ff47$05ffb770$11ff2650$@telematica.at>
 <094501d0ff5e$38125a80$a8370f80$@telematica.at>
 <2E0234B6-C07A-4D5A-AC8B-BB0EC1EB8694@telematica.at>
 <5639CECA.4000502@sipwise.com>
 <01fe01d13796$86cf2700$946d7500$@telematica.at> <56713A32.10403@sipwise.com>
 <21a6c01d1582c$eca02aa0$c5e07fe0$@telematica.at>
 <1365632450.303696.1455293568776.JavaMail.zimbra@telematica.at>
Message-ID: <56C1AFA5.9020505@sipwise.com>

Hi,
please share the kamailio-proxy.log for a start. Are you doing simple
call forward or multiple serial call forwards btw?

Regarding the voice message, we might need to look at the network trace
additionally. Did the audio message work before the upgrade on incoming
calls from the GW?

Regards,
Andrew

On 02/12/2016 05:12 PM, Matthias Hohl wrote:
> Hello,
> 
> also with upgrade to 4.2.1 we still have the same problems with  Conncurent max calls exceeded for callee:
> 
> Example:
> Feb 12 16:29:20 spce (local7.notice) proxy[3749]: NOTICE: <script>: Concurrent max calls exceeded for callee 'aef1bad0-ed48-4697-a55e-6ab25e723b5a' - R=sip:43137xxxxx at sip.xxx.at:5060 ID=3b0717627b45827e6a9a0f7a50f5f42a at xx.170.208.xxx:5060 UA='GlobalCall+T.38'
> Feb 12 16:33:56 spce (local7.notice) proxy[3742]: NOTICE: <script>: Concurrent max calls exceeded for callee 'aef1bad0-ed48-4697-a55e-6ab25e723b5a' - R=sip:43137xxxxx at sip.xxx.at:5060 ID=2277847967b2b40325f5720a268a9056 at xx.170.208.xxx:5060 UA='GlobalCall+T.38'
> 
> But there are no concurrent calls on this subscriber!!!!
> 
> After doing "redis restart" it works again without problems.
> 
> Also there is NO voice message playing, that there are concurrent calls exceeded, so the callee just hear the ringing tone and nothing else.
> But the Soundfile is set right. I load the default files and set the soundset on domain layer. so it should work.. outgoing the voice is speaking but incoming the callee doesn't hear anything just ringing!
> 
> please fix this as soon as possible.
> 
> 
> Thanks!



From matthias.hohl at telematica.at  Mon Feb 15 06:49:27 2016
From: matthias.hohl at telematica.at (Matthias Hohl)
Date: Mon, 15 Feb 2016 12:49:27 +0100 (CET)
Subject: [Spce-user] Concurrent max calls exceeded for callee
In-Reply-To: <56C1AFA5.9020505@sipwise.com>
References: <08bc01d0ff47$05ffb770$11ff2650$@telematica.at>
 <094501d0ff5e$38125a80$a8370f80$@telematica.at>
 <2E0234B6-C07A-4D5A-AC8B-BB0EC1EB8694@telematica.at>
 <5639CECA.4000502@sipwise.com>
 <01fe01d13796$86cf2700$946d7500$@telematica.at> <56713A32.10403@sipwise.com>
 <21a6c01d1582c$eca02aa0$c5e07fe0$@telematica.at>
 <1365632450.303696.1455293568776.JavaMail.zimbra@telematica.at>
 <56C1AFA5.9020505@sipwise.com>
Message-ID: <8F35314E-DF03-4A3B-BCCB-9B6D3486DA51@telematica.at>

Hello,

We do simple call forwards. Cf works again normally now after restarting redis...
But i believe it has something to do with the "db lost" problem i repost today in a orher topic.

No the audio messages also didn't work before the upgrade. :/ any idea?

Von meinem iPhone gesendet

> Am 15.02.2016 um 11:59 schrieb Andrew Pogrebennyk <apogrebennyk at sipwise.com>:
> 
> Hi,
> please share the kamailio-proxy.log for a start. Are you doing simple
> call forward or multiple serial call forwards btw?
> 
> Regarding the voice message, we might need to look at the network trace
> additionally. Did the audio message work before the upgrade on incoming
> calls from the GW?
> 
> Regards,
> Andrew
> 
>> On 02/12/2016 05:12 PM, Matthias Hohl wrote:
>> Hello,
>> 
>> also with upgrade to 4.2.1 we still have the same problems with  Conncurent max calls exceeded for callee:
>> 
>> Example:
>> Feb 12 16:29:20 spce (local7.notice) proxy[3749]: NOTICE: <script>: Concurrent max calls exceeded for callee 'aef1bad0-ed48-4697-a55e-6ab25e723b5a' - R=sip:43137xxxxx at sip.xxx.at:5060 ID=3b0717627b45827e6a9a0f7a50f5f42a at xx.170.208.xxx:5060 UA='GlobalCall+T.38'
>> Feb 12 16:33:56 spce (local7.notice) proxy[3742]: NOTICE: <script>: Concurrent max calls exceeded for callee 'aef1bad0-ed48-4697-a55e-6ab25e723b5a' - R=sip:43137xxxxx at sip.xxx.at:5060 ID=2277847967b2b40325f5720a268a9056 at xx.170.208.xxx:5060 UA='GlobalCall+T.38'
>> 
>> But there are no concurrent calls on this subscriber!!!!
>> 
>> After doing "redis restart" it works again without problems.
>> 
>> Also there is NO voice message playing, that there are concurrent calls exceeded, so the callee just hear the ringing tone and nothing else.
>> But the Soundfile is set right. I load the default files and set the soundset on domain layer. so it should work.. outgoing the voice is speaking but incoming the callee doesn't hear anything just ringing!
>> 
>> please fix this as soon as possible.
>> 
>> 
>> Thanks!
> 


From gerry.kernan at infinityit.ie  Mon Feb 15 08:06:17 2016
From: gerry.kernan at infinityit.ie (gerry kernan)
Date: Mon, 15 Feb 2016 13:06:17 +0000
Subject: [Spce-user] catch null useragent in register or invite.
Message-ID: <1e44bc87-3db2-46c3-a7b0-ef8ed228d351@infinityit.ie>

Hi 
 
I'm using the line in below kamailio-loadbalancer to catch any malicious registers or invites from known malicious UA types. I've noticed recently that we are getting invites and registers without any UA, I'm trying to catch these attempts with 
 
$ua == "<null>"  but I'm not catching them, is the syntax correct ?. all other regex are catching correctly so maybe <null> is incorrect.
 
 
if(is_method("REGISTER|INVITE") && ($ua =~ "^friendly.+" || $ua =~ "^sipvici.+" || $ua =~ "^sipcli.+" || $ua =~ "^VaxSIPUser.+" || $ua == "MizuPhone" || $ua == "voip" || $ua == "<null>"))
        {
                xlog("L_WARN", "Request rejected, malicious UA='$ua' IP='$si' - [% logreq_init -%]\n");
                exit;
 
 
 
 
Gerry Kernan
 
 
Infinity IT   |   17 The Mall   |   Beacon Court   |   Sandyford   |   Dublin D18 E3C8   |   Ireland
Tel:  +353 - (0)1 - 293 0090   |   E-Mail:  gerry.kernan at infinityit.ie
 
Managed IT Services       Infinity IT - www.infinityit.ie
IP Telephony                    Asterisk Consulting - www.asteriskconsulting.com
Contact Centre                Total Interact - www.totalinteract.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20160215/fa51a108/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 2681 bytes
Desc: not available
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20160215/fa51a108/attachment-0001.jpg>

From barry at flanagan.ie  Mon Feb 15 08:10:56 2016
From: barry at flanagan.ie (Barry Flanagan)
Date: Mon, 15 Feb 2016 13:10:56 +0000
Subject: [Spce-user] catch null useragent in register or invite.
In-Reply-To: <1e44bc87-3db2-46c3-a7b0-ef8ed228d351@infinityit.ie>
References: <1e44bc87-3db2-46c3-a7b0-ef8ed228d351@infinityit.ie>
Message-ID: <CALJb54-5Y3VHeL+GSHPcOgVaiyq1umDZf620dGNhDETOtHtWRQ@mail.gmail.com>

On 15 Feb 2016 13:07, "gerry kernan" <gerry.kernan at infinityit.ie> wrote:
>
> Hi
>
>
>
> I?m using the line in below kamailio-loadbalancer to catch any malicious
registers or invites from known malicious UA types. I?ve noticed recently
that we are getting invites and registers without any UA, I?m trying to
catch these attempts with
>
>
>
> $ua == "<null>"  but I?m not catching them, is the syntax correct ?. all
other regex are catching correctly so maybe <null> is incorrect.
>

Hi Gerry,

I think it is $null you are looking for

-Barry Flanagan
>
>
>
>
> if(is_method("REGISTER|INVITE") && ($ua =~ "^friendly.+" || $ua =~
"^sipvici.+" || $ua =~ "^sipcli.+" || $ua =~ "^VaxSIPUser.+" || $ua ==
"MizuPhone" || $ua == "voip" || $ua == "<null>"))
>
>         {
>
>                 xlog("L_WARN", "Request rejected, malicious UA='$ua'
IP='$si' - [% logreq_init -%]\n");
>
>                 exit;
>
>
>
>
>
>
>
>
>
> Gerry Kernan
>
>
>
>
>
> Infinity IT   |   17 The Mall   |   Beacon Court   |   Sandyford   |
Dublin D18 E3C8   |   Ireland
>
> Tel:  +353 - (0)1 - 293 0090   |   E-Mail:  gerry.kernan at infinityit.ie
>
>
>
> Managed IT Services       Infinity IT - www.infinityit.ie
>
> IP Telephony                    Asterisk Consulting ?
www.asteriskconsulting.com
>
> Contact Centre                Total Interact ? www.totalinteract.com
>
>
>
>
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20160215/6d54e6dd/attachment-0001.html>

From dgrotti at sipwise.com  Mon Feb 15 08:15:28 2016
From: dgrotti at sipwise.com (Daniel Grotti)
Date: Mon, 15 Feb 2016 14:15:28 +0100
Subject: [Spce-user] catch null useragent in register or invite.
In-Reply-To: <1e44bc87-3db2-46c3-a7b0-ef8ed228d351@infinityit.ie>
References: <1e44bc87-3db2-46c3-a7b0-ef8ed228d351@infinityit.ie>
Message-ID: <56C1CF70.9080809@sipwise.com>

Hi Gerry,
please try this in kamilio/proxy/kamailio.cfg it works for me.
For the null, try to check $ua == $null:


if( is_method("REGISTER|INVITE") && $sp != "5080" && !has_totag() )
         {
                 if($ua =~ "^friendly.+" || $ua =~ "^sipvici.+" || $ua 
=~ "^sipcli.+" || $ua =~ "^VaxSIPUser.+" || $ua == "MizuPhone" || $ua == 
"voip" || $ua == $null )
                 {
                         xlog("L_NOTICE", "UA='$ua' rejected - S=$rs 
SS='$rr' M=$rm R=$ru F=$fu T=$tu IP=$pr:$si:$sp UAIP=$si UA='$ua' ID=$ci 
\n");
                         exit;
                 }
         }
         ##end



I would be careful for the $null, cause you may reject good messages, 
just without User-Agent header.




*Daniel Grotti *
Head of Customer Support

Sipwise GmbH <http://www.sipwise.com> , Campus 21/Europaring F15
AT-2345 Brunn am Gebirge

Phone: +43(0)1 301 2032 <callto:+4313012032>
Email: dgrotti at sipwise.com <mailto:dgrotti at sipwise.com>
Website: www.sipwise.com <http://www.sipwise.com>

Particulars according Austrian Companies Code paragraph 14
"Sipwise GmbH" - Europaring F15 - 2345 Brunn am Gebirge
FN:305595f, Commercial Court Vienna, ATU64002206

On 02/15/2016 02:06 PM, gerry kernan wrote:
>
> Hi
>
> I?m using the line in below kamailio-loadbalancer to catch any 
> malicious registers or invites from known malicious UA types. I?ve 
> noticed recently that we are getting invites and registers without any 
> UA, I?m trying to catch these attempts with
>
> $ua == "<null>"  but I?m not catching them, is the syntax correct ?. 
> all other regex are catching correctly so maybe <null> is incorrect.
>
> if(is_method("REGISTER|INVITE") && ($ua =~ "^friendly.+" || $ua =~ 
> "^sipvici.+" || $ua =~ "^sipcli.+" || $ua =~ "^VaxSIPUser.+" || $ua == 
> "MizuPhone" || $ua == "voip" || $ua == "<null>"))
>
>         {
>
>                 xlog("L_WARN", "Request rejected, malicious UA='$ua' 
> IP='$si' - [% logreq_init -%]\n");
>
>                 exit;
>
> *Gerry Kernan*
>
> cid:image001.jpg at 01D105A5.2701B0E0
>
> *Infinity IT   |   17 The Mall   |   Beacon Court   |   Sandyford |   
> Dublin D18 E3C8   |   Ireland*
>
> *Tel: +353 - (0)1 - 293 0090   |   E-Mail: *gerry.kernan at infinityit.ie 
> <mailto:gerry.kernan at infinityit.ie>**
>
> **
>
> *Managed IT Services__Infinity IT*- www.infinityit.ie 
> <http://www.infinityit.ie/>
>
> *IP Telephony__Asterisk Consulting*? www.asteriskconsulting.com 
> <http://www.asteriskconsulting.com>
>
> *Contact Centre__Total Interact*? www.totalinteract.com 
> <http://www.totalinteract.com>
>
>
>
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20160215/6adfc12d/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 2681 bytes
Desc: not available
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20160215/6adfc12d/attachment-0001.jpe>

From gerry.kernan at infinityit.ie  Mon Feb 15 08:17:50 2016
From: gerry.kernan at infinityit.ie (gerry kernan)
Date: Mon, 15 Feb 2016 13:17:50 +0000
Subject: [Spce-user] catch null useragent in register or invite.
In-Reply-To: <56C1CF70.9080809@sipwise.com>
References: <1e44bc87-3db2-46c3-a7b0-ef8ed228d351@infinityit.ie>
 <56C1CF70.9080809@sipwise.com>
Message-ID: <a3511e43-e6a8-4cd1-a245-f3789cbe6710@infinityit.ie>

Hi Barry and Daniel
 
Thanks for your quick responses .
 
 
Gerry Kernan
 
 
Infinity IT   |   17 The Mall   |   Beacon Court   |   Sandyford   |   Dublin D18 E3C8   |   Ireland
Tel:  +353 - (0)1 - 293 0090   |   E-Mail:  gerry.kernan at infinityit.ie
 
Managed IT Services       Infinity IT - www.infinityit.ie
IP Telephony                    Asterisk Consulting - www.asteriskconsulting.com
Contact Centre                Total Interact - www.totalinteract.com
 
From: Spce-user [mailto:spce-user-bounces at lists.sipwise.com] On Behalf Of Daniel Grotti
Sent: Monday 15 February 2016 13:15
To: spce-user at lists.sipwise.com
Subject: Re: [Spce-user] catch null useragent in register or invite.
 
Hi Gerry,
please try this in kamilio/proxy/kamailio.cfg it works for me.
For the null, try to check $ua == $null:


if( is_method("REGISTER|INVITE") && $sp != "5080" && !has_totag() )
        {
                if($ua =~ "^friendly.+" || $ua =~ "^sipvici.+" || $ua =~ "^sipcli.+" || $ua =~ "^VaxSIPUser.+" || $ua == "MizuPhone" || $ua == "voip" || $ua == $null )
                {
                        xlog("L_NOTICE", "UA='$ua' rejected - S=$rs SS='$rr' M=$rm R=$ru F=$fu T=$tu IP=$pr:$si:$sp UAIP=$si UA='$ua' ID=$ci \n");
                        exit;
                }
        }
        ##end



I would be careful for the $null, cause you may reject good messages, just without User-Agent header.



Daniel Grotti 
Head of Customer Support 
Sipwise GmbH , Campus 21/Europaring F15
AT-2345 Brunn am Gebirge 
Phone:  +43(0)1 301 2032 
Email:  dgrotti at sipwise.com 
Website:  www.sipwise.com 
Particulars according Austrian Companies Code paragraph 14
"Sipwise GmbH" - Europaring F15 - 2345 Brunn am Gebirge
FN:305595f, Commercial Court Vienna, ATU64002206 
On 02/15/2016 02:06 PM, gerry kernan wrote:
Hi 
 
I'm using the line in below kamailio-loadbalancer to catch any malicious registers or invites from known malicious UA types. I've noticed recently that we are getting invites and registers without any UA, I'm trying to catch these attempts with 
 
$ua == "<null>"  but I'm not catching them, is the syntax correct ?. all other regex are catching correctly so maybe <null> is incorrect.
 
 
if(is_method("REGISTER|INVITE") && ($ua =~ "^friendly.+" || $ua =~ "^sipvici.+" || $ua =~ "^sipcli.+" || $ua =~ "^VaxSIPUser.+" || $ua == "MizuPhone" || $ua == "voip" || $ua == "<null>"))
        {
                xlog("L_WARN", "Request rejected, malicious UA='$ua' IP='$si' - [% logreq_init -%]\n");
                exit;
 
 
 
 
Gerry Kernan
 
 
Infinity IT   |   17 The Mall   |   Beacon Court   |   Sandyford   |   Dublin D18 E3C8   |   Ireland
Tel:  +353 - (0)1 - 293 0090   |   E-Mail:  gerry.kernan at infinityit.ie
 
Managed IT Services       Infinity IT - www.infinityit.ie
IP Telephony                    Asterisk Consulting - www.asteriskconsulting.com
Contact Centre                Total Interact - www.totalinteract.com
 



_______________________________________________Spce-user mailing listSpce-user at lists.sipwise.comhttps://lists.sipwise.com/listinfo/spce-user
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20160215/8478ea29/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 2681 bytes
Desc: not available
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20160215/8478ea29/attachment-0001.jpg>

From alutay at sipwise.com  Mon Feb 15 11:11:57 2016
From: alutay at sipwise.com (Alex Lutay)
Date: Mon, 15 Feb 2016 17:11:57 +0100
Subject: [Spce-user] APT Repo Error during ngcp-installer
In-Reply-To: <CAO_pOtW_=fyxAEv8syL2+U3cR_D6aPAFw-8LH635KwSnesdMyg@mail.gmail.com>
References: <CAO_pOtW_=fyxAEv8syL2+U3cR_D6aPAFw-8LH635KwSnesdMyg@mail.gmail.com>
Message-ID: <56C1F8CD.4030608@sipwise.com>

Hi,

Do you still noticing the issue?
I cannot reproduce it locally. :-(

On 02/10/2016 09:22 AM, Giacomo wrote:
> Dear All,
> the problem is the following...
> 
> When i try to setup sipwise with ngcp-installer on a Debian 8 - 64bit
> system after the dpkg -i of the latest stable (mr4.2.1) apt doesn't work
> correctly and it shows the following:
> 
> Err https://deb.sipwise.com jessie/main amd64 Packages
> 
> Ign https://deb.sipwise.com jessie/main Translation-it_IT
> Ign https://deb.sipwise.com jessie/main Translation-it
> Ign https://deb.sipwise.com jessie/main Translation-en
> W: Impossible to recovery
> https://deb.sipwise.com/spce/mr4.2.1/dists/jessie/main/binary-amd64/Packages
> 
> E: Impossible to download some indexes: the old one will be used.
> 
> How can i solve the issue? If i try to navigate on the repo address
> everything seems to be ok...
> 
> Thank you very much.

-- 
Alex Lutay


From William at ezpcltd.com  Tue Feb 16 14:36:49 2016
From: William at ezpcltd.com (William Hilsum)
Date: Tue, 16 Feb 2016 19:36:49 +0000
Subject: [Spce-user] Is there a full guide to parameters?
Message-ID: <DB5PR06MB1557925C19D90666E04D90D6BEAD0@DB5PR06MB1557.eurprd06.prod.outlook.com>

Hi

Whilst some parameters are self-explanatory and the documentation or help text explains, there are some which are pretty similar and the text isn't too clear.

Right now, I need to set per customer concurrent call limits and I'm struggling to understand the difference between:

Concurrent_max
Concurrent_max_per_account
Concurrent_max_total

There are also:

Concurrent_max_out
Concurrent_max_out_per_account
Concurrent_max_out_total

... I can't understand the need to set these differently from the above, but, after I know the first lot, I think I can guess what these are!

This aside, so I don't have to ask in the future, is there anywhere that lists a complete list of settings/profile options as I couldn't see these listed in the main manual?

Thanks,

William

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20160216/77b2059d/attachment-0001.html>

From dgrotti at sipwise.com  Wed Feb 17 01:53:51 2016
From: dgrotti at sipwise.com (Daniel Grotti)
Date: Wed, 17 Feb 2016 07:53:51 +0100
Subject: [Spce-user] Is there a full guide to parameters?
In-Reply-To: <DB5PR06MB1557925C19D90666E04D90D6BEAD0@DB5PR06MB1557.eurprd06.prod.outlook.com>
Message-ID: <b3c1746a-fc2c-4409-ae3b-e4fe728042cc@email.android.com>

Hi William,
*_max define the amount of incoming+outbound calls.

*_max_out define the amount of outbound calls only.

Other thing you should know is that *_total includes also the call to local services such as voicemail, conference.

No there is no document for that, they are explained in the online help.
We will try to be more detailed then.

Daniel


On Feb 16, 2016 8:36 PM, William Hilsum <William at ezpcltd.com> wrote:
>
> Hi
>
> ?
>
> Whilst some parameters are self-explanatory and the documentation or help text explains, there are some which are pretty similar and the text isn?t too clear.
>
> ?
>
> Right now, I need to set per customer concurrent call limits and I?m struggling to understand the difference between:
>
> ?
>
> Concurrent_max
>
> Concurrent_max_per_account
>
> Concurrent_max_total
>
> ?
>
> There are also:
>
> ?
>
> Concurrent_max_out
>
> Concurrent_max_out_per_account
>
> Concurrent_max_out_total
>
> ?
>
> ? I can?t understand the need to set these differently from the above, but, after I know the first lot, I think I can guess what these are!
>
> ?
>
> This aside, so I don?t have to ask in the future, is there anywhere that lists a complete list of settings/profile options as I couldn?t see these listed in the main manual?
>
> ?
>
> Thanks,
>
> ?
>
> William
>
> ?

From admin at marcoteixeira.com  Wed Feb 17 03:36:28 2016
From: admin at marcoteixeira.com (Marco Teixeira)
Date: Wed, 17 Feb 2016 08:36:28 +0000
Subject: [Spce-user] Is there a full guide to parameters?
In-Reply-To: <DB5PR06MB1557925C19D90666E04D90D6BEAD0@DB5PR06MB1557.eurprd06.prod.outlook.com>
References: <DB5PR06MB1557925C19D90666E04D90D6BEAD0@DB5PR06MB1557.eurprd06.prod.outlook.com>
Message-ID: <CAD7smbj8ZxEEvfCTf6yoT54j8Rne98qeTVgQbYq+vnLZ_YUf3Q@mail.gmail.com>

Try hoovering (or clicking) your mouse over the question mark, next to each
parameter...

---
?Marco
---


On Tue, Feb 16, 2016 at 7:36 PM, William Hilsum <William at ezpcltd.com> wrote:

> Hi
>
>
>
> Whilst some parameters are self-explanatory and the documentation or help
> text explains, there are some which are pretty similar and the text isn?t
> too clear.
>
>
>
> Right now, I need to set per customer concurrent call limits and I?m
> struggling to understand the difference between:
>
>
>
> Concurrent_max
>
> Concurrent_max_per_account
>
> Concurrent_max_total
>
>
>
> There are also:
>
>
>
> Concurrent_max_out
>
> Concurrent_max_out_per_account
>
> Concurrent_max_out_total
>
>
>
> ? I can?t understand the need to set these differently from the above,
> but, after I know the first lot, I think I can guess what these are!
>
>
>
> This aside, so I don?t have to ask in the future, is there anywhere that
> lists a complete list of settings/profile options as I couldn?t see these
> listed in the main manual?
>
>
>
> Thanks,
>
>
>
> William
>
>
>
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20160217/ddf6b2e7/attachment-0001.html>

From William at ezpcltd.com  Wed Feb 17 05:05:48 2016
From: William at ezpcltd.com (William Hilsum)
Date: Wed, 17 Feb 2016 10:05:48 +0000
Subject: [Spce-user] Is there a full guide to parameters?
In-Reply-To: <CAD7smbj8ZxEEvfCTf6yoT54j8Rne98qeTVgQbYq+vnLZ_YUf3Q@mail.gmail.com>
References: <DB5PR06MB1557925C19D90666E04D90D6BEAD0@DB5PR06MB1557.eurprd06.prod.outlook.com>
 <CAD7smbj8ZxEEvfCTf6yoT54j8Rne98qeTVgQbYq+vnLZ_YUf3Q@mail.gmail.com>
Message-ID: <DB5PR06MB155799F85D074AF802B23F32BEAE0@DB5PR06MB1557.eurprd06.prod.outlook.com>

Thanks, but, I already said I had!

It wasn?t too clear about the diffence between Max / max_total?



On Tue, Feb 16, 2016 at 7:36 PM, William Hilsum <William at ezpcltd.com<mailto:William at ezpcltd.com>> wrote:
Hi

Whilst some parameters are self-explanatory and the documentation or help text explains, there are some which are pretty similar and the text isn?t too clear.

Right now, I need to set per customer concurrent call limits and I?m struggling to understand the difference between:

Concurrent_max
Concurrent_max_per_account
Concurrent_max_total

There are also:

Concurrent_max_out
Concurrent_max_out_per_account
Concurrent_max_out_total

? I can?t understand the need to set these differently from the above, but, after I know the first lot, I think I can guess what these are!

This aside, so I don?t have to ask in the future, is there anywhere that lists a complete list of settings/profile options as I couldn?t see these listed in the main manual?

Thanks,

William


_______________________________________________
Spce-user mailing list
Spce-user at lists.sipwise.com<mailto:Spce-user at lists.sipwise.com>
https://lists.sipwise.com/listinfo/spce-user

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20160217/f0b811e1/attachment-0001.html>

From William at ezpcltd.com  Wed Feb 17 05:06:39 2016
From: William at ezpcltd.com (William Hilsum)
Date: Wed, 17 Feb 2016 10:06:39 +0000
Subject: [Spce-user] Is there a full guide to parameters?
In-Reply-To: <b3c1746a-fc2c-4409-ae3b-e4fe728042cc@email.android.com>
References: <DB5PR06MB1557925C19D90666E04D90D6BEAD0@DB5PR06MB1557.eurprd06.prod.outlook.com>
 <b3c1746a-fc2c-4409-ae3b-e4fe728042cc@email.android.com>
Message-ID: <DB5PR06MB15576976D6198F58DB77E77EBEAE0@DB5PR06MB1557.eurprd06.prod.outlook.com>

Hi Daniel,

That is great, thank you.

I had no idea that it could treat calls in/out and the internal (voicemail) separately!

Thanks,

William

-----Original Message-----
From: Daniel Grotti [mailto:dgrotti at sipwise.com] 
Sent: 17 February 2016 06:54
To: William Hilsum <William at ezpcltd.com>
Cc: spce-user at lists.sipwise.com
Subject: Re: [Spce-user] Is there a full guide to parameters?

Hi William,
*_max define the amount of incoming+outbound calls.

*_max_out define the amount of outbound calls only.

Other thing you should know is that *_total includes also the call to local services such as voicemail, conference.

No there is no document for that, they are explained in the online help.
We will try to be more detailed then.

Daniel


On Feb 16, 2016 8:36 PM, William Hilsum <William at ezpcltd.com> wrote:
>
> Hi
>
> ?
>
> Whilst some parameters are self-explanatory and the documentation or help text explains, there are some which are pretty similar and the text isn?t too clear.
>
> ?
>
> Right now, I need to set per customer concurrent call limits and I?m struggling to understand the difference between:
>
> ?
>
> Concurrent_max
>
> Concurrent_max_per_account
>
> Concurrent_max_total
>
> ?
>
> There are also:
>
> ?
>
> Concurrent_max_out
>
> Concurrent_max_out_per_account
>
> Concurrent_max_out_total
>
> ?
>
> ? I can?t understand the need to set these differently from the above, but, after I know the first lot, I think I can guess what these are!
>
> ?
>
> This aside, so I don?t have to ask in the future, is there anywhere that lists a complete list of settings/profile options as I couldn?t see these listed in the main manual?
>
> ?
>
> Thanks,
>
> ?
>
> William
>
> ?

From admin at marcoteixeira.com  Wed Feb 17 09:35:21 2016
From: admin at marcoteixeira.com (Marco Teixeira)
Date: Wed, 17 Feb 2016 14:35:21 +0000
Subject: [Spce-user] Is there a full guide to parameters?
In-Reply-To: <DB5PR06MB155799F85D074AF802B23F32BEAE0@DB5PR06MB1557.eurprd06.prod.outlook.com>
References: <DB5PR06MB1557925C19D90666E04D90D6BEAD0@DB5PR06MB1557.eurprd06.prod.outlook.com>
 <CAD7smbj8ZxEEvfCTf6yoT54j8Rne98qeTVgQbYq+vnLZ_YUf3Q@mail.gmail.com>
 <DB5PR06MB155799F85D074AF802B23F32BEAE0@DB5PR06MB1557.eurprd06.prod.outlook.com>
Message-ID: <CAD7smbj+bZVTNW4-GmZ1PgfRGw7_YBe_PwLTi-_BOm6Z9AvrNg@mail.gmail.com>

:)
Yes you did. My bad for reading hastily.



On Wed, Feb 17, 2016 at 10:05 AM, William Hilsum <William at ezpcltd.com>
wrote:

> Thanks, but, I already said I had!
>
>
>
> It wasn?t too clear about the diffence between Max / max_total?
>
>
>
>
>
>
>
> On Tue, Feb 16, 2016 at 7:36 PM, William Hilsum <William at ezpcltd.com>
> wrote:
>
> Hi
>
>
>
> Whilst some parameters are self-explanatory and the documentation or help
> text explains, there are some which are pretty similar and the text isn?t
> too clear.
>
>
>
> Right now, I need to set per customer concurrent call limits and I?m
> struggling to understand the difference between:
>
>
>
> Concurrent_max
>
> Concurrent_max_per_account
>
> Concurrent_max_total
>
>
>
> There are also:
>
>
>
> Concurrent_max_out
>
> Concurrent_max_out_per_account
>
> Concurrent_max_out_total
>
>
>
> ? I can?t understand the need to set these differently from the above,
> but, after I know the first lot, I think I can guess what these are!
>
>
>
> This aside, so I don?t have to ask in the future, is there anywhere that
> lists a complete list of settings/profile options as I couldn?t see these
> listed in the main manual?
>
>
>
> Thanks,
>
>
>
> William
>
>
>
>
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
>
>
>
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20160217/e6483622/attachment-0001.html>

From matthias.hohl at telematica.at  Thu Feb 18 06:06:43 2016
From: matthias.hohl at telematica.at (Matthias Hohl)
Date: Thu, 18 Feb 2016 12:06:43 +0100 (CET)
Subject: [Spce-user] Notification sounds (sound_set) by calls from
	PSTN/Peering not working
Message-ID: <01e801d16a3c$72a89d50$57f9d7f0$@telematica.at>

Hello,

 

i post several days ago a problem, that there is no voice message playing,
if there are concurrent calls exceeded, so the caller just hear the ringing
tone and nothing else.

Today I did some more tests and found out the problem, but no solution for
it.

 

The problem just happen, if the call comes from PSTN/Peering.

If the caller is another subscriber on the server, the notification sounds
works perfectly.

 

So if somebody from PSTN is calling a local subscriber, and this local
subscriber is not online or busy or call limit exceeded or whatever, the
call goes to the application server but the caller just hear the normal
ringing tone and no notification voice until the caller hang up by himself.

So the caller from PSTN/Peering doesn't recognize that the callee will never
answer and get no information about that the callee is not available, or
busy, or whatever.

BUT if the callee get called from another local subscriber, the notification
about unavailable or busy or whatever, will be played correctly.

So the problem just happen, if the call comes from a Peering (PSTN).

 

So normally the sound "callee_offline.wav" or "callee_busy.wav" etc should
be played as well if the call comes from PSTN/peering.

I set the soundset correctly and also activate the loop function, but like I
wrote, it just works with local calls but not with PSTN/peering calls.

 

Maybe I have somewhere a setting false or whatever, don't know.

I also checked the config.yml but can't find any hint for solving this
problem.

 

Would be nice, if you could help me out with this problem.

 

THANKS!

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20160218/e0414366/attachment-0001.html>

From alutay at sipwise.com  Thu Feb 18 06:53:10 2016
From: alutay at sipwise.com (Alex Lutay)
Date: Thu, 18 Feb 2016 12:53:10 +0100
Subject: [Spce-user] Vulnerability Report CVE-2015-7547
Message-ID: <56C5B0A6.6000501@sipwise.com>

Hi all,

As reported by Google on their security blog recently,
a major security whole in glibc was discovered.

Affected systems: All NGCP versions

Please ensure you have appropriate Debian security repository enabled:
 - jessie based mr4.2.1+
> deb https://debian.sipwise.com/debian-security/ jessie-security main contrib non-free
 - wheezy based 3.0, 3.1, mr3.2.* - mr4.1.* (including mr3.8.* LTS)
> deb http://debian.sipwise.com/debian-security/ wheezy-security main contrib non-free
 - squeeze based 2.8 LTS
> deb http://debian.sipwise.com/debian/ squeeze-lts main

(you can use other non-Sipwise mirrors if you trust them,
while please verify you have latest/fixed packages versions there).

Ensure all the packages from glibc/eglibc sources are installed to the
fixed version. See the list of fixed versions here:
https://security-tracker.debian.org/tracker/CVE-2015-7547

All the Sipwise software are dynamically linked against glibc,
so all the services restart are necessary.

At the same time Sipwise doesn't have the information about the
statically linked software which can be installed on your servers,
so it is highly recommended to update all packages to the latest
available version:

>   apt-get update && apt-get upgrade && \
>   ngcp-update-db-schema && ngcp-update-cfg-schema && \
>   ngcpcfg apply "applying changes for CVE-2015-7547"

NOTE: please do not forget to update customtt if you have them before
applying new changes!

Additional Information:
> https://security-tracker.debian.org/tracker/CVE-2015-7547
> https://googleonlinesecurity.blogspot.co.at/2016/02/cve-2015-7547-glibc-getaddrinfo-stack.html
> https://sourceware.org/ml/libc-alpha/2016-02/msg00416.html

-- 
Alex Lutay
Head of Quality Assurance
Sipwise GmbH, Campus 21/Europaring F15
AT-2345 Brunn am Gebirge

Office: +43(0)13012036
Email: alutay at sipwise.com
Website: https://www.sipwise.com

Meet us @ ANGACOM: Hall 10.1 / booth N10
Exhibition and Congress for Broadband,
Cable & Satellite: 07 ? 09 June, 2016 in Cologne


From agranig at sipwise.com  Thu Feb 18 17:07:47 2016
From: agranig at sipwise.com (Andreas Granig)
Date: Thu, 18 Feb 2016 23:07:47 +0100
Subject: [Spce-user] Notification sounds (sound_set) by calls from
 PSTN/Peering not working
In-Reply-To: <01e801d16a3c$72a89d50$57f9d7f0$@telematica.at>
References: <01e801d16a3c$72a89d50$57f9d7f0$@telematica.at>
Message-ID: <56C640B3.8000402@sipwise.com>

Hi,

Maybe the peering server is ignoring the early media played by the system?

We've already thought about adding a config option to actually connect
the call and play the announcement within the connected call instead of
inside early media. Never followed through as it might have a regulatory
impact, since in that case costs are imposed on the calling party in
that case. It's on our radar, no specific release on when to do it though.

Andreas

On 02/18/2016 12:06 PM, Matthias Hohl wrote:
> Hello,
> 
>  
> 
> i post several days ago a problem, that there is no voice message
> playing, if there are concurrent calls exceeded, so the caller just hear
> the ringing tone and nothing else.
> 
> Today I did some more tests and found out the problem, but no solution
> for it.
> 
>  
> 
> The problem just happen, if the call comes from PSTN/Peering.
> 
> If the caller is another subscriber on the server, the notification
> sounds works perfectly.
> 
>  
> 
> So if somebody from PSTN is calling a local subscriber, and this local
> subscriber is not online or busy or call limit exceeded or whatever, the
> call goes to the application server but the caller just hear the normal
> ringing tone and no notification voice until the caller hang up by himself.
> 
> So the caller from PSTN/Peering doesn?t recognize that the callee will
> never answer and get no information about that the callee is not
> available, or busy, or whatever.
> 
> BUT if the callee get called from another local subscriber, the
> notification about unavailable or busy or whatever, will be played
> correctly.
> 
> So the problem just happen, if the call comes from a Peering (PSTN).
> 
>  
> 
> So normally the sound ?callee_offline.wav? or ?callee_busy.wav? etc
> should be played as well if the call comes from PSTN/peering.
> 
> I set the soundset correctly and also activate the loop function, but
> like I wrote, it just works with local calls but not with PSTN/peering
> calls.
> 
>  
> 
> Maybe I have somewhere a setting false or whatever, don?t know.
> 
> I also checked the config.yml but can?t find any hint for solving this
> problem.
> 
>  
> 
> Would be nice, if you could help me out with this problem.
> 
>  
> 
> THANKS!
> 
>  
> 
>  
> 
> 
> 
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
> 


From matthias.hohl at telematica.at  Thu Feb 18 17:52:44 2016
From: matthias.hohl at telematica.at (Matthias Hohl)
Date: Thu, 18 Feb 2016 23:52:44 +0100 (CET)
Subject: [Spce-user] Notification sounds (sound_set) by calls from
	PSTN/Peering not working
In-Reply-To: <56C640B3.8000402@sipwise.com>
References: <01e801d16a3c$72a89d50$57f9d7f0$@telematica.at>
 <56C640B3.8000402@sipwise.com>
Message-ID: <030c01d16a9f$0ec941f0$2c5bc5d0$@telematica.at>

Hello,

so you thinking, that the problem is at the Peering Server? That this one
doesn't allow the early media?
Is there any way to check, if the spce is playing the media right on peering
side?

Yah such a option maybe could be a good solution.
I will talk to my inbound peering provider, if they can check there config.

Thanks for the hint.


-----Urspr?ngliche Nachricht-----
Von: Spce-user [mailto:spce-user-bounces at lists.sipwise.com] Im Auftrag von
Andreas Granig
Gesendet: Donnerstag, 18. Februar 2016 23:08
An: spce-user at lists.sipwise.com
Betreff: Re: [Spce-user] Notification sounds (sound_set) by calls from
PSTN/Peering not working

Hi,

Maybe the peering server is ignoring the early media played by the system?

We've already thought about adding a config option to actually connect the
call and play the announcement within the connected call instead of inside
early media. Never followed through as it might have a regulatory impact,
since in that case costs are imposed on the calling party in that case. It's
on our radar, no specific release on when to do it though.

Andreas

On 02/18/2016 12:06 PM, Matthias Hohl wrote:
> Hello,
> 
>  
> 
> i post several days ago a problem, that there is no voice message 
> playing, if there are concurrent calls exceeded, so the caller just 
> hear the ringing tone and nothing else.
> 
> Today I did some more tests and found out the problem, but no solution 
> for it.
> 
>  
> 
> The problem just happen, if the call comes from PSTN/Peering.
> 
> If the caller is another subscriber on the server, the notification 
> sounds works perfectly.
> 
>  
> 
> So if somebody from PSTN is calling a local subscriber, and this local 
> subscriber is not online or busy or call limit exceeded or whatever, 
> the call goes to the application server but the caller just hear the 
> normal ringing tone and no notification voice until the caller hang up by
himself.
> 
> So the caller from PSTN/Peering doesn?t recognize that the callee will 
> never answer and get no information about that the callee is not 
> available, or busy, or whatever.
> 
> BUT if the callee get called from another local subscriber, the 
> notification about unavailable or busy or whatever, will be played 
> correctly.
> 
> So the problem just happen, if the call comes from a Peering (PSTN).
> 
>  
> 
> So normally the sound ?callee_offline.wav? or ?callee_busy.wav? etc 
> should be played as well if the call comes from PSTN/peering.
> 
> I set the soundset correctly and also activate the loop function, but 
> like I wrote, it just works with local calls but not with PSTN/peering 
> calls.
> 
>  
> 
> Maybe I have somewhere a setting false or whatever, don?t know.
> 
> I also checked the config.yml but can?t find any hint for solving this 
> problem.
> 
>  
> 
> Would be nice, if you could help me out with this problem.
> 
>  
> 
> THANKS!
> 
>  
> 
>  
> 
> 
> 
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
> 
_______________________________________________
Spce-user mailing list
Spce-user at lists.sipwise.com
https://lists.sipwise.com/listinfo/spce-user


From matthias.hohl at telematica.at  Fri Feb 19 08:06:48 2016
From: matthias.hohl at telematica.at (Matthias Hohl)
Date: Fri, 19 Feb 2016 14:06:48 +0100 (CET)
Subject: [Spce-user] Notification sounds (sound_set) by calls
	from	PSTN/Peering not working
In-Reply-To: <030c01d16a9f$0ec941f0$2c5bc5d0$@telematica.at>
References: <01e801d16a3c$72a89d50$57f9d7f0$@telematica.at>
 <56C640B3.8000402@sipwise.com>
 <030c01d16a9f$0ec941f0$2c5bc5d0$@telematica.at>
Message-ID: <7D181670-2B6B-48A9-83DD-799B3B35D576@telematica.at>

Fixed!
Was a problem by my carrier. They fixed that today.

Von meinem iPhone gesendet

> Am 18.02.2016 um 23:53 schrieb Matthias Hohl <matthias.hohl at telematica.at>:
> 
> Hello,
> 
> so you thinking, that the problem is at the Peering Server? That this one
> doesn't allow the early media?
> Is there any way to check, if the spce is playing the media right on peering
> side?
> 
> Yah such a option maybe could be a good solution.
> I will talk to my inbound peering provider, if they can check there config.
> 
> Thanks for the hint.
> 
> 
> -----Urspr?ngliche Nachricht-----
> Von: Spce-user [mailto:spce-user-bounces at lists.sipwise.com] Im Auftrag von
> Andreas Granig
> Gesendet: Donnerstag, 18. Februar 2016 23:08
> An: spce-user at lists.sipwise.com
> Betreff: Re: [Spce-user] Notification sounds (sound_set) by calls from
> PSTN/Peering not working
> 
> Hi,
> 
> Maybe the peering server is ignoring the early media played by the system?
> 
> We've already thought about adding a config option to actually connect the
> call and play the announcement within the connected call instead of inside
> early media. Never followed through as it might have a regulatory impact,
> since in that case costs are imposed on the calling party in that case. It's
> on our radar, no specific release on when to do it though.
> 
> Andreas
> 
>> On 02/18/2016 12:06 PM, Matthias Hohl wrote:
>> Hello,
>> 
>> 
>> 
>> i post several days ago a problem, that there is no voice message 
>> playing, if there are concurrent calls exceeded, so the caller just 
>> hear the ringing tone and nothing else.
>> 
>> Today I did some more tests and found out the problem, but no solution 
>> for it.
>> 
>> 
>> 
>> The problem just happen, if the call comes from PSTN/Peering.
>> 
>> If the caller is another subscriber on the server, the notification 
>> sounds works perfectly.
>> 
>> 
>> 
>> So if somebody from PSTN is calling a local subscriber, and this local 
>> subscriber is not online or busy or call limit exceeded or whatever, 
>> the call goes to the application server but the caller just hear the 
>> normal ringing tone and no notification voice until the caller hang up by
> himself.
>> 
>> So the caller from PSTN/Peering doesn?t recognize that the callee will 
>> never answer and get no information about that the callee is not 
>> available, or busy, or whatever.
>> 
>> BUT if the callee get called from another local subscriber, the 
>> notification about unavailable or busy or whatever, will be played 
>> correctly.
>> 
>> So the problem just happen, if the call comes from a Peering (PSTN).
>> 
>> 
>> 
>> So normally the sound ?callee_offline.wav? or ?callee_busy.wav? etc 
>> should be played as well if the call comes from PSTN/peering.
>> 
>> I set the soundset correctly and also activate the loop function, but 
>> like I wrote, it just works with local calls but not with PSTN/peering 
>> calls.
>> 
>> 
>> 
>> Maybe I have somewhere a setting false or whatever, don?t know.
>> 
>> I also checked the config.yml but can?t find any hint for solving this 
>> problem.
>> 
>> 
>> 
>> Would be nice, if you could help me out with this problem.
>> 
>> 
>> 
>> THANKS!
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> _______________________________________________
>> Spce-user mailing list
>> Spce-user at lists.sipwise.com
>> https://lists.sipwise.com/listinfo/spce-user
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user

From apogrebennyk at sipwise.com  Fri Feb 19 10:42:47 2016
From: apogrebennyk at sipwise.com (Andrew Pogrebennyk)
Date: Fri, 19 Feb 2016 16:42:47 +0100
Subject: [Spce-user] New sip:provider CE mr3.8.5 is available now
Message-ID: <56C737F7.6040508@sipwise.com>

Dear community!

This is to inform community about availability of the new SPCE mr3.8.5!
Please check release notes here:
https://www.sipwise.org/news/announcements/sipprovider-mr3-8-5-released/

mr3.8.5 is the next build in LTS release mr3.8 (62 bugfixes)
The InstallCD media, Vagrant box, Virtualbox, VMware and AMI images as
well as Docker hub container have been uploaded. As usual, please check
the handbook at https://www.sipwise.org/doc/mr3.8.5/spce/ for details.

Please report the new issueson this mailing list and thank you for the
bugreports and feedback you have already provided in the past!

Regards,
Andrew


From manwe at sipdoc.net  Fri Feb 19 16:52:16 2016
From: manwe at sipdoc.net (Jon Bonilla (Manwe))
Date: Fri, 19 Feb 2016 22:52:16 +0100
Subject: [Spce-user] ngcp-panel won't start after 3.8.5 upgrade
Message-ID: <20160219225216.58fc0426@multivac>

Hi all

Upgraded a 3.8.x system to 3.8.5 and now ngcp-panel won't start.

Please find attached the console message.



cheers,


Jon
-------------- next part --------------
console

root at spce01:~# /etc/init.d/ngcp-panel start
[....] Starting NGCP-Panel Webapp:Couldn't instantiate component "NGCP::Panel::Model::InterceptDB", "Attribute (schema_class) is required at /usr/lib/perl5/Moose/Meta/Attribute.pm line 514
        Moose::Meta::Attribute::initialize_instance_slot('Moose::Meta::Attribute=HASH(0x5c74cc0)', 'Moose::Meta::Instance=HASH(0x97d1b98)', 'NGCP::Panel::Model::InterceptDB=HASH(0x13adfdb8)', 'HASH(0x13adfba8)') called at /usr/lib/perl5/Class/MOP/Class.pm line 525
        Class::MOP::Class::_construct_instance('Moose::Meta::Class=HASH(0x97b23d0)', 'HASH(0x13adfba8)') called at /usr/lib/perl5/Class/MOP/Class.pm line 498
        Class::MOP::Class::new_object('Moose::Meta::Class=HASH(0x97b23d0)', 'HASH(0x13adfba8)') called at /usr/lib/perl5/Moose/Meta/Class.pm line 274
        Moose::Meta::Class::new_object('Moose::Meta::Class=HASH(0x97b23d0)', 'HASH(0x13adfba8)') called at /usr/lib/perl5/Moose/Object.pm line 28
        Moose::Object::new('NGCP::Panel::Model::InterceptDB', 'NGCP::Panel', 'HASH(0x133172c8)') called at constructor Catalyst::Model::DBIC::Schema::new (defined at /usr/share/perl5/Catalyst/Model/DBIC/Schema.pm line 586) line 4
        Catalyst::Model::DBIC::Schema::new('NGCP::Panel::Model::InterceptDB', 'NGCP::Panel', 'HASH(0x133172c8)') called at /usr/share/perl5/MooseX/Traits/Pluggable.pm line 139
        MooseX::Traits::Pluggable::_build_instance_with_traits('NGCP::Panel::Model::InterceptDB', 'NGCP::Panel::Model::InterceptDB', 'NGCP::Panel') called at /usr/share/perl5/MooseX/Traits/Pluggable.pm line 97
        MooseX::Traits::Pluggable::new_with_traits('NGCP::Panel::Model::InterceptDB', 'NGCP::Panel', 'HASH(0x13aa7410)') called at /usr/share/perl5/CatalystX/Component/Traits.pm line 145
        CatalystX::Component::Traits::COMPONENT('NGCP::Panel::Model::InterceptDB', 'NGCP::Panel', 'HASH(0x13aa6fd8)') called at /usr/lib/perl5/Class/MOP/Method/Wrapped.pm line 50
        Class::MOP::Method::Wrapped::__ANON__('NGCP::Panel::Model::InterceptDB', 'NGCP::Panel', 'HASH(0x13aa6fd8)') called at /usr/lib/perl5/Class/MOP/Method/Wrapped.pm line 91
        Catalyst::Model::DBIC::Schema::COMPONENT('NGCP::Panel::Model::InterceptDB', 'NGCP::Panel', 'HASH(0x13aa6fd8)') called at /usr/share/perl5/Catalyst.pm line 2612
        eval {...} called at /usr/share/perl5/Catalyst.pm line 2612
        Catalyst::setup_component('NGCP::Panel', 'NGCP::Panel::Model::InterceptDB') called at /usr/share/perl5/Catalyst.pm line 2539
        Catalyst::setup_components('NGCP::Panel') called at /usr/share/perl5/Catalyst.pm line 1177
        Catalyst::setup('NGCP::Panel') called at /usr/share/perl5/NGCP/Panel.pm line 186
        require NGCP/Panel.pm called at /usr/share/perl5/Module/Runtime.pm line 317
        Module::Runtime::require_module('NGCP::Panel') called at /usr/share/perl5/Class/Load.pm line 178
        Class::Load::__ANON__() called at /usr/share/perl5/Try/Tiny.pm line 71
        eval {...} called at /usr/share/perl5/Try/Tiny.pm line 67
        Try::Tiny::try('CODE(0x3165d80)', 'Try::Tiny::Catch=REF(0x3166338)') called at /usr/share/perl5/Class/Load.pm line 184
        Class::Load::try_load_class('NGCP::Panel', undef) called at /usr/share/perl5/Class/Load.pm line 39
        Class::Load::load_class('NGCP::Panel') called at /usr/share/perl5/Catalyst/ScriptRole.pm line 90
        Catalyst::ScriptRole::_run_application('Catalyst::Script::FastCGI=HASH(0x29d7248)') called at /usr/share/perl5/Catalyst/ScriptRole.pm line 68
        Catalyst::ScriptRole::run('Catalyst::Script::FastCGI=HASH(0x29d7248)') called at /usr/share/perl5/Catalyst/ScriptRunner.pm line 50
        Catalyst::ScriptRunner::run('Catalyst::ScriptRunner', 'NGCP::Panel', 'FastCGI') called at /usr/share/ngcp-panel/ngcp_panel_fastcgi.pl line 4"Compilation failed in require at /usr/share/perl5/Module/Runtime.pm line 317.
 at /usr/share/perl5/Catalyst/ScriptRunner.pm line 50
[FAIL] error ... failed!
 failed!

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: Firma digital OpenPGP
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20160219/03059c7b/attachment-0001.sig>

From alutay at sipwise.com  Fri Feb 19 17:40:14 2016
From: alutay at sipwise.com (Alex Lutay)
Date: Fri, 19 Feb 2016 23:40:14 +0100
Subject: [Spce-user] ngcp-panel won't start after 3.8.5 upgrade
In-Reply-To: <20160219225216.58fc0426@multivac>
References: <20160219225216.58fc0426@multivac>
Message-ID: <56C799CE.3000809@sipwise.com>

Hi Jon,

Please ensure you did not forget to run
ngcpc-update-cfg-schema and ngcpcfg apply
before starting ngcp-panel (in case if you upgrade it manually).

It looks like some configs were not generated properly,
please check /etc/ngcp-panel/ngcp_panel.conf
Maybe you have customtt there?
Or maybe some of packages were not updated? On hold? Modified?
Try 'ngcp-status' it can catch something.

I have downloaded fresh public vagrant mr3.8.5 and panel is running well
there, please compare the configs on vagrant and on your system.

P.S. please share the reason of the issue! Tnx!

On 02/19/2016 10:52 PM, Jon Bonilla (Manwe) wrote:
> Upgraded a 3.8.x system to 3.8.5 and now ngcp-panel won't start.
> Please find attached the console message.

-- 
Alexander Lutay
Head of Quality Assurance
Sipwise GmbH, Campus 21/Europaring F15
AT-2345 Brunn am Gebirge

Office: +43(0)13012036
Email: alutay at sipwise.com
Website: https://www.sipwise.com

Meet us @ ANGACOM: Hall 10.1 / booth N10
Exhibition and Congress for Broadband,
Cable & Satellite: 07 ? 09 June, 2016 in Cologne


From manwe at sipdoc.net  Fri Feb 19 17:50:20 2016
From: manwe at sipdoc.net (Jon Bonilla (Manwe))
Date: Fri, 19 Feb 2016 23:50:20 +0100
Subject: [Spce-user] ngcp-panel won't start after 3.8.5 upgrade
In-Reply-To: <56C799CE.3000809@sipwise.com>
References: <20160219225216.58fc0426@multivac> <56C799CE.3000809@sipwise.com>
Message-ID: <20160219235020.6ef4836d@multivac>

El Fri, 19 Feb 2016 23:40:14 +0100
Alex Lutay <alutay at sipwise.com> escribi?:

> Hi Jon,
> 
> Please ensure you did not forget to run
> ngcpc-update-cfg-schema and ngcpcfg apply
> before starting ngcp-panel (in case if you upgrade it manually).
> 
> It looks like some configs were not generated properly,
> please check /etc/ngcp-panel/ngcp_panel.conf
> Maybe you have customtt there?
> Or maybe some of packages were not updated? On hold? Modified?
> Try 'ngcp-status' it can catch something.
> 
> I have downloaded fresh public vagrant mr3.8.5 and panel is running well
> there, please compare the configs on vagrant and on your system.
> 
> P.S. please share the reason of the issue! Tnx!
> 
> On 02/19/2016 10:52 PM, Jon Bonilla (Manwe) wrote:
> > Upgraded a 3.8.x system to 3.8.5 and now ngcp-panel won't start.
> > Please find attached the console message.  
> 


Hi Alex

Thanks for the quick reply.

You're right. It's a customtt file. I have the new interception module section
missing in the config. I guess that's related to the new li integration. right?


cheers,

Jon



-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: Firma digital OpenPGP
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20160219/31a0ce95/attachment-0001.sig>

From axessofficetheo at gmail.com  Tue Feb 23 04:30:24 2016
From: axessofficetheo at gmail.com (Theo)
Date: Tue, 23 Feb 2016 11:30:24 +0200
Subject: [Spce-user] Clir - Hiding caller ID
Message-ID: <CA+9+E=UjB5=O3UsXw-idtf3TwVJpCpc_n3Y2ZiutrMW2cHDYVQ@mail.gmail.com>

Hi

I am having some issues hiding our caller ID through some interconnects.
Sipwise does add the privacy flag to the header but does this in the "from
header". The response from our interconnect partners is that this is not
according to RFC:

"the caller here attempted to anonymize their call using only the
displayname of the FROM header." They did not include a P-Asserted Identity
/ Privacy header. The displayname of the FROM header is optional to begin
with, and while it's recommended that it be displayed at the far-end UI,
the far-end carriers are not required to use it at all."

So - are they correct in saying this and if so, how would we hide the
number the correct way?

Thanks for any input
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20160223/d1bcaeda/attachment-0001.html>

From manwe at sipdoc.net  Tue Feb 23 05:14:36 2016
From: manwe at sipdoc.net (Jon Bonilla (Manwe))
Date: Tue, 23 Feb 2016 11:14:36 +0100
Subject: [Spce-user] Clir - Hiding caller ID
In-Reply-To: <CA+9+E=UjB5=O3UsXw-idtf3TwVJpCpc_n3Y2ZiutrMW2cHDYVQ@mail.gmail.com>
References: <CA+9+E=UjB5=O3UsXw-idtf3TwVJpCpc_n3Y2ZiutrMW2cHDYVQ@mail.gmail.com>
Message-ID: <20160223111436.52fddac1@multivac>

El Tue, 23 Feb 2016 11:30:24 +0200
Theo <axessofficetheo at gmail.com> escribi?:

> Hi
> 
> I am having some issues hiding our caller ID through some interconnects.
> Sipwise does add the privacy flag to the header but does this in the "from
> header". The response from our interconnect partners is that this is not
> according to RFC:
> 
> "the caller here attempted to anonymize their call using only the
> displayname of the FROM header." They did not include a P-Asserted Identity
> / Privacy header. The displayname of the FROM header is optional to begin
> with, and while it's recommended that it be displayed at the far-end UI,
> the far-end carriers are not required to use it at all."
> 
> So - are they correct in saying this and if so, how would we hide the
> number the correct way?
> 


When you hide the callerid and send a call to a peer, the ngcp system adds the
Privacy and the PAI headers by default.

When sending the call to a subscriber it does not. It only sends anonymous in
the from header.

could you paste one of those INVITE requests?


cheers,

Jon

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: Firma digital OpenPGP
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20160223/a900db9b/attachment-0001.sig>

From axessofficetheo at gmail.com  Tue Feb 23 06:08:37 2016
From: axessofficetheo at gmail.com (Theo)
Date: Tue, 23 Feb 2016 13:08:37 +0200
Subject: [Spce-user] Clir - Hiding caller ID
In-Reply-To: <20160223111436.52fddac1@multivac>
References: <CA+9+E=UjB5=O3UsXw-idtf3TwVJpCpc_n3Y2ZiutrMW2cHDYVQ@mail.gmail.com>
 <20160223111436.52fddac1@multivac>
Message-ID: <CA+9+E=U0Z1o=NNEE37UgtVgPTAJXikjp_Uv=eJwgayqbyPOtQA@mail.gmail.com>

Hi

I had another look - you are correct it seems. Apologies. It's the next
step in the chain that strips the flag hence it doesn't arrive upstream.

Thanks!



On Tue, Feb 23, 2016 at 12:14 PM, Jon Bonilla (Manwe) <manwe at sipdoc.net>
wrote:

> El Tue, 23 Feb 2016 11:30:24 +0200
> Theo <axessofficetheo at gmail.com> escribi?:
>
> > Hi
> >
> > I am having some issues hiding our caller ID through some interconnects.
> > Sipwise does add the privacy flag to the header but does this in the
> "from
> > header". The response from our interconnect partners is that this is not
> > according to RFC:
> >
> > "the caller here attempted to anonymize their call using only the
> > displayname of the FROM header." They did not include a P-Asserted
> Identity
> > / Privacy header. The displayname of the FROM header is optional to begin
> > with, and while it's recommended that it be displayed at the far-end UI,
> > the far-end carriers are not required to use it at all."
> >
> > So - are they correct in saying this and if so, how would we hide the
> > number the correct way?
> >
>
>
> When you hide the callerid and send a call to a peer, the ngcp system adds
> the
> Privacy and the PAI headers by default.
>
> When sending the call to a subscriber it does not. It only sends anonymous
> in
> the from header.
>
> could you paste one of those INVITE requests?
>
>
> cheers,
>
> Jon
>
>
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20160223/5dbba3a9/attachment-0001.html>

From admin at marcoteixeira.com  Wed Feb 24 18:06:55 2016
From: admin at marcoteixeira.com (Marco Teixeira)
Date: Wed, 24 Feb 2016 23:06:55 +0000
Subject: [Spce-user] Lua script errors
Message-ID: <CAD7smbiDmXjZhpUqn1nsZyhC6M5MnYXVin29MyUQur+7AanTuw@mail.gmail.com>

Hi,

Can anyone point me in the right direction on troubleshooting these errors
i'm seeing on proxy.log ?

Feb 24 23:00:16 sbc proxy[5325]: ERROR: app_lua [app_lua_api.c:672]:
app_lua_run(): error executing: del_dlg_profile_peer (err: 2)
Feb 24 23:00:16 sbc proxy[5325]: ERROR: app_lua [app_lua_api.c:674]:
app_lua_run(): error from Lua: /etc/kamailio/proxy/dlgcnt.lua:157: attempt
to concatenate global 'key' (a nil value)
Feb 24 23:00:16 sbc proxy[5325]: ERROR: <script>: Can't del peer[out]:3
profiles

# more /etc/ngcp_version
mr3.8.5

Tkx

---
?Marco
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20160224/8ba0641e/attachment-0001.html>

From vseva at sipwise.com  Thu Feb 25 06:47:11 2016
From: vseva at sipwise.com (Victor Seva)
Date: Thu, 25 Feb 2016 12:47:11 +0100
Subject: [Spce-user] Lua script errors
In-Reply-To: <CAD7smbiDmXjZhpUqn1nsZyhC6M5MnYXVin29MyUQur+7AanTuw@mail.gmail.com>
References: <CAD7smbiDmXjZhpUqn1nsZyhC6M5MnYXVin29MyUQur+7AanTuw@mail.gmail.com>
Message-ID: <56CEE9BF.8070801@sipwise.com>

On 02/25/2016 12:06 AM, Marco Teixeira wrote:
> Hi,
> 
> Can anyone point me in the right direction on troubleshooting these
> errors i'm seeing on proxy.log ?
> 
> Feb 24 23:00:16 sbc proxy[5325]: ERROR: app_lua [app_lua_api.c:672]:
> app_lua_run(): error executing: del_dlg_profile_peer (err: 2)
> Feb 24 23:00:16 sbc proxy[5325]: ERROR: app_lua [app_lua_api.c:674]:
> app_lua_run(): error from Lua: /etc/kamailio/proxy/dlgcnt.lua:157:
> attempt to concatenate global 'key' (a nil value)
> Feb 24 23:00:16 sbc proxy[5325]: ERROR: <script>: Can't del peer[out]:3
> profiles
> 
> # more /etc/ngcp_version 
> mr3.8.5

Confirmed, I'm working on a fix. I'll keep you posted.

Thanks for reporting.

-- 
Victor Seva
Software Engineer

Phone: +43(0)1 301 2029
Email: vseva at sipwise.com
Website: www.sipwise.com

Particulars according Austrian Companies Code paragraph 14
"Sipwise GmbH? - Europaring F15 ? 2345 Brunn am Gebirge
FN:305595f, Commercial Court Vienna, ATU64002206

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20160225/032c0d1d/attachment-0001.asc>

From vseva at sipwise.com  Thu Feb 25 09:13:27 2016
From: vseva at sipwise.com (Victor Seva)
Date: Thu, 25 Feb 2016 15:13:27 +0100
Subject: [Spce-user] Lua script errors
In-Reply-To: <56CEE9BF.8070801@sipwise.com>
References: <CAD7smbiDmXjZhpUqn1nsZyhC6M5MnYXVin29MyUQur+7AanTuw@mail.gmail.com>
 <56CEE9BF.8070801@sipwise.com>
Message-ID: <56CF0C07.408@sipwise.com>

On 02/25/2016 12:47 PM, Victor Seva wrote:
> Confirmed, I'm working on a fix. I'll keep you posted.

> ngcp-templates (3.8.5.6+0~mr3.8.5.6) unstable; urgency=medium
> 
>   [ Victor Seva ]
>   * [fe70fed] MT#17709 decrease redis counters if call forward fails, fix b09c6fd59430d
> 
>   [ Andrew Pogrebennyk ]
>   * [1f029b2] MT#17877 workaround wrong Referred-By domain from Yealink phones
> 
>   [ Sipwise Jenkins Builder ]
> 
>  -- Sipwise Jenkins Builder <jenkins at sipwise.com>  Thu, 25 Feb 2016 15:06:55 +0100

Released fix. Thanks for reporting


-- 
Victor Seva
Software Engineer

Phone: +43(0)1 301 2029
Email: vseva at sipwise.com
Website: www.sipwise.com

Particulars according Austrian Companies Code paragraph 14
"Sipwise GmbH? - Europaring F15 ? 2345 Brunn am Gebirge
FN:305595f, Commercial Court Vienna, ATU64002206

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20160225/79ef29bf/attachment-0001.asc>

From admin at marcoteixeira.com  Thu Feb 25 09:58:46 2016
From: admin at marcoteixeira.com (Marco Teixeira)
Date: Thu, 25 Feb 2016 14:58:46 +0000
Subject: [Spce-user] Lua script errors
In-Reply-To: <56CF0C07.408@sipwise.com>
References: <CAD7smbiDmXjZhpUqn1nsZyhC6M5MnYXVin29MyUQur+7AanTuw@mail.gmail.com>
 <56CEE9BF.8070801@sipwise.com> <56CF0C07.408@sipwise.com>
Message-ID: <CAD7smbjqP8-gjoUqttC5wGJ59H3oN8sOXv+n0Eh4eBFqmFe_MA@mail.gmail.com>

Victor... Sorry for lagging on replying back to you.

Do you still need me to test ?
This is in production and i rather not...

How to update ? (manual style apt-get ngcp-cfg apply ??)


---
?Marco


On Thu, Feb 25, 2016 at 2:13 PM, Victor Seva <vseva at sipwise.com> wrote:

> On 02/25/2016 12:47 PM, Victor Seva wrote:
> > Confirmed, I'm working on a fix. I'll keep you posted.
>
> > ngcp-templates (3.8.5.6+0~mr3.8.5.6) unstable; urgency=medium
> >
> >   [ Victor Seva ]
> >   * [fe70fed] MT#17709 decrease redis counters if call forward fails,
> fix b09c6fd59430d
> >
> >   [ Andrew Pogrebennyk ]
> >   * [1f029b2] MT#17877 workaround wrong Referred-By domain from Yealink
> phones
> >
> >   [ Sipwise Jenkins Builder ]
> >
> >  -- Sipwise Jenkins Builder <jenkins at sipwise.com>  Thu, 25 Feb 2016
> 15:06:55 +0100
>
> Released fix. Thanks for reporting
>
>
> --
> Victor Seva
> Software Engineer
>
> Phone: +43(0)1 301 2029
> Email: vseva at sipwise.com
> Website: www.sipwise.com
>
> Particulars according Austrian Companies Code paragraph 14
> "Sipwise GmbH? - Europaring F15 ? 2345 Brunn am Gebirge
> FN:305595f, Commercial Court Vienna, ATU64002206
>
>
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20160225/4702fb04/attachment-0001.html>

From admin at marcoteixeira.com  Thu Feb 25 10:05:56 2016
From: admin at marcoteixeira.com (Marco Teixeira)
Date: Thu, 25 Feb 2016 15:05:56 +0000
Subject: [Spce-user] Lua script errors
In-Reply-To: <CAD7smbjqP8-gjoUqttC5wGJ59H3oN8sOXv+n0Eh4eBFqmFe_MA@mail.gmail.com>
References: <CAD7smbiDmXjZhpUqn1nsZyhC6M5MnYXVin29MyUQur+7AanTuw@mail.gmail.com>
 <56CEE9BF.8070801@sipwise.com> <56CF0C07.408@sipwise.com>
 <CAD7smbjqP8-gjoUqttC5wGJ59H3oN8sOXv+n0Eh4eBFqmFe_MA@mail.gmail.com>
Message-ID: <CAD7smbi0dNp4fEMe-gCZN938CD5hTzKNBeEL4FDeyzRs=Ofh_w@mail.gmail.com>

Well, i wen't ahead and did:

apt-get update && apt-get upgrade && \
ngcp-update-db-schema && ngcp-update-cfg-schema && \
ngcpcfg apply

?Errors are gone. I do see sometimes warnings like these:
Feb 25 15:04:33 sbc proxy[20485]: WARNING: app_lua [app_lua_sr.c:100]:
lua_sr_log(): central:del[1:3] counter was -1
Feb 25 15:04:33 sbc proxy[20485]: WARNING: app_lua [app_lua_sr.c:100]:
lua_sr_log(): central:del[2:3] counter was -1

Is this normal ? Do i need to clear out redis counters or something ??


---
Cumprimentos / Best regards

Marco
---


On Thu, Feb 25, 2016 at 2:58 PM, Marco Teixeira <admin at marcoteixeira.com>
wrote:

> Victor... Sorry for lagging on replying back to you.
>
> Do you still need me to test ?
> This is in production and i rather not...
>
> How to update ? (manual style apt-get ngcp-cfg apply ??)
>
>
> ---
> ?Marco
>
>
> On Thu, Feb 25, 2016 at 2:13 PM, Victor Seva <vseva at sipwise.com> wrote:
>
>> On 02/25/2016 12:47 PM, Victor Seva wrote:
>> > Confirmed, I'm working on a fix. I'll keep you posted.
>>
>> > ngcp-templates (3.8.5.6+0~mr3.8.5.6) unstable; urgency=medium
>> >
>> >   [ Victor Seva ]
>> >   * [fe70fed] MT#17709 decrease redis counters if call forward fails,
>> fix b09c6fd59430d
>> >
>> >   [ Andrew Pogrebennyk ]
>> >   * [1f029b2] MT#17877 workaround wrong Referred-By domain from Yealink
>> phones
>> >
>> >   [ Sipwise Jenkins Builder ]
>> >
>> >  -- Sipwise Jenkins Builder <jenkins at sipwise.com>  Thu, 25 Feb 2016
>> 15:06:55 +0100
>>
>> Released fix. Thanks for reporting
>>
>>
>> --
>> Victor Seva
>> Software Engineer
>>
>> Phone: +43(0)1 301 2029
>> Email: vseva at sipwise.com
>> Website: www.sipwise.com
>>
>> Particulars according Austrian Companies Code paragraph 14
>> "Sipwise GmbH? - Europaring F15 ? 2345 Brunn am Gebirge
>> FN:305595f, Commercial Court Vienna, ATU64002206
>>
>>
>> _______________________________________________
>> Spce-user mailing list
>> Spce-user at lists.sipwise.com
>> https://lists.sipwise.com/listinfo/spce-user
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20160225/2e5b6f31/attachment-0001.html>

From noreply at sipwise.com  Thu Feb 25 11:38:18 2016
From: noreply at sipwise.com (Sipwise Repository Tracker)
Date: Thu, 25 Feb 2016 17:38:18 +0100
Subject: [Spce-user] FYI: Package update(s) in release mr3.8.3
Message-ID: <1456418298.497668.17444.nullmailer@deb1.sipwise.com>

One or more updates have been released in NGCP release mr3.8.3:

* captagent was updated from version 5.2.10.0-1+0~mr3.8.3.13 to version 5.2.11.0-1+0~mr3.8.3.14
* captagent-dbg was updated from version 5.2.10.0-1+0~mr3.8.3.13 to version 5.2.11.0-1+0~mr3.8.3.14

To apply the latest update(s) execute:

  apt-get update && apt-get upgrade && \
  ngcp-update-db-schema && ngcp-update-cfg-schema && \
  ngcpcfg apply manual system update

If you encounter any problems please report a bug at
the spce-user at lists.sipwise.com mailing list.

Further documentation is available at:

  http://www.sipwise.com/products/spce/documentation/

This is an automated mail by the Continuous Delivery platform at Sipwise.com


From noreply at sipwise.com  Thu Feb 25 11:39:47 2016
From: noreply at sipwise.com (Sipwise Repository Tracker)
Date: Thu, 25 Feb 2016 17:39:47 +0100
Subject: [Spce-user] FYI: Package update(s) in release mr3.8.4
Message-ID: <1456418387.701981.18092.nullmailer@deb1.sipwise.com>

One or more updates have been released in NGCP release mr3.8.4:

* captagent was updated from version 5.2.10.0-1+0~mr3.8.4.11 to version 5.2.11.0-1+0~mr3.8.4.12
* captagent-dbg was updated from version 5.2.10.0-1+0~mr3.8.4.11 to version 5.2.11.0-1+0~mr3.8.4.12

To apply the latest update(s) execute:

  apt-get update && apt-get upgrade && \
  ngcp-update-db-schema && ngcp-update-cfg-schema && \
  ngcpcfg apply manual system update

If you encounter any problems please report a bug at
the spce-user at lists.sipwise.com mailing list.

Further documentation is available at:

  http://www.sipwise.com/products/spce/documentation/

This is an automated mail by the Continuous Delivery platform at Sipwise.com


From noreply at sipwise.com  Thu Feb 25 11:41:08 2016
From: noreply at sipwise.com (Sipwise Repository Tracker)
Date: Thu, 25 Feb 2016 17:41:08 +0100
Subject: [Spce-user] FYI: Package update(s) in release mr3.8.5
Message-ID: <1456418468.050997.18341.nullmailer@deb1.sipwise.com>

One or more updates have been released in NGCP release mr3.8.5:

* captagent was updated from version 5.2.10.0-1+0~mr3.8.5.7 to version 5.2.11.0-1+0~mr3.8.5.8
* captagent-dbg was updated from version 5.2.10.0-1+0~mr3.8.5.7 to version 5.2.11.0-1+0~mr3.8.5.8

To apply the latest update(s) execute:

  apt-get update && apt-get upgrade && \
  ngcp-update-db-schema && ngcp-update-cfg-schema && \
  ngcpcfg apply manual system update

If you encounter any problems please report a bug at
the spce-user at lists.sipwise.com mailing list.

Further documentation is available at:

  http://www.sipwise.com/products/spce/documentation/

This is an automated mail by the Continuous Delivery platform at Sipwise.com


From noreply at sipwise.com  Thu Feb 25 11:46:43 2016
From: noreply at sipwise.com (Sipwise Repository Tracker)
Date: Thu, 25 Feb 2016 17:46:43 +0100
Subject: [Spce-user] FYI: Package update(s) in release mr4.2.1
Message-ID: <1456418803.864036.19389.nullmailer@deb1.sipwise.com>

One or more updates have been released in NGCP release mr4.2.1:

* captagent was updated from version 5.2.10.1-1+0~mr4.2.1.10 to version 5.2.11.1-1+0~mr4.2.1.11
* captagent-dbg was updated from version 5.2.10.1-1+0~mr4.2.1.10 to version 5.2.11.1-1+0~mr4.2.1.11

To apply the latest update(s) execute:

  apt-get update && apt-get upgrade && \
  ngcp-update-db-schema && ngcp-update-cfg-schema && \
  ngcpcfg apply manual system update

If you encounter any problems please report a bug at
the spce-user at lists.sipwise.com mailing list.

Further documentation is available at:

  http://www.sipwise.com/products/spce/documentation/

This is an automated mail by the Continuous Delivery platform at Sipwise.com


From admin at marcoteixeira.com  Thu Feb 25 12:55:41 2016
From: admin at marcoteixeira.com (Marco Teixeira)
Date: Thu, 25 Feb 2016 17:55:41 +0000
Subject: [Spce-user] FYI: Package update(s) in release mr3.8.5
In-Reply-To: <1456418468.050997.18341.nullmailer@deb1.sipwise.com>
References: <1456418468.050997.18341.nullmailer@deb1.sipwise.com>
Message-ID: <CAD7smbiyJMCbsaFq4a4iKKCs8Bob0uGmHQNV8O95FPU4C1CpRw@mail.gmail.com>

?Hi,
Minor cosmetic... "page not found"?

On Thu, Feb 25, 2016 at 4:41 PM, Sipwise Repository Tracker <
noreply at sipwise.com> wrote:

> Further documentation is available at:
>
>   http://www.sipwise.com/products/spce/documentation/
>




---
Cumprimentos / Best regards

Marco Teixeira
email/gtalk: admin at marcoteixeira.com
skype: admin-marcoteixeira.com
---
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20160225/fb59c9d8/attachment-0001.html>

From dgrotti at sipwise.com  Thu Feb 25 13:00:56 2016
From: dgrotti at sipwise.com (Daniel Grotti)
Date: Thu, 25 Feb 2016 19:00:56 +0100
Subject: [Spce-user] FYI: Package update(s) in release mr3.8.5
In-Reply-To: <CAD7smbiyJMCbsaFq4a4iKKCs8Bob0uGmHQNV8O95FPU4C1CpRw@mail.gmail.com>
Message-ID: <f7ef4e1f-1cc6-45ee-b127-28c02ed18767@email.android.com>

Oops... Typo.
Sipwise.org not .com

On Feb 25, 2016 6:55 PM, Marco Teixeira <admin at marcoteixeira.com> wrote:
>
> ?Hi,
> Minor cosmetic... "page not found"?
>
> On Thu, Feb 25, 2016 at 4:41 PM, Sipwise Repository Tracker <noreply at sipwise.com> wrote:
>>
>> Further documentation is available at:
>>
>> ? http://www.sipwise.com/products/spce/documentation/
>
>
>
>
>
> ---
> Cumprimentos / Best regards
>
> Marco Teixeira
> email/gtalk: admin at marcoteixeira.com
> skype: admin-marcoteixeira.com
> ---
>

From gavin.sweet at skyracktelecom.com  Fri Feb 26 05:27:10 2016
From: gavin.sweet at skyracktelecom.com (Gavin Sweet)
Date: Fri, 26 Feb 2016 10:27:10 -0000
Subject: [Spce-user] access to sipwise v 3.1 sw_vcs patch (not available in
	older branch on github)
Message-ID: <192901d17080$40a27b10$c1e77130$@skyracktelecom.com>

Hi - 

 

Can anyone please direct me/post here to the source for the sipwise v3.1
patch for sems - file name sw_vcs.patch? 

 

The oldest version in github here is 3.8

https://github.com/sipwise/sems/blob/mr3.8/debian/patches/sipwise/sw_vcs.pat
ch 

 

Fully appreciate that running on this old version is not ideal, but we are
not yet in a position to upgrade.

 

Thanks for your help,

 

Gavin

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20160226/c8a14393/attachment-0001.html>

From alutay at sipwise.com  Fri Feb 26 06:00:55 2016
From: alutay at sipwise.com (Alex Lutay)
Date: Fri, 26 Feb 2016 12:00:55 +0100
Subject: [Spce-user] access to sipwise v 3.1 sw_vcs patch (not available
 in older branch on github)
In-Reply-To: <192901d17080$40a27b10$c1e77130$@skyracktelecom.com>
References: <192901d17080$40a27b10$c1e77130$@skyracktelecom.com>
Message-ID: <56D03067.8070106@sipwise.com>

Dear Gavin,

1) sems in mr3.8 has version 1.6.0 while sems in v3.1 was 1.4.3

2) Sipwise didn't use quilt to manage patches that time,
so no patches available for NGCP v3.1

3) you can check branch 1.4.3+spce3.0 to see the sources for NGCP v3.1
https://github.com/sipwise/sems/tree/1.4.3+spce3.0

Have a good day!

On 02/26/2016 11:27 AM, Gavin Sweet wrote:
> Can anyone please direct me/post here to the source for the sipwise v3.1
> patch for sems ? file name sw_vcs.patch?
> 
> The oldest version in github here is 3.8
> 
> https://github.com/sipwise/sems/blob/mr3.8/debian/patches/sipwise/sw_vcs.patch
> 
> Fully appreciate that running on this old version is not ideal, but we
> are not yet in a position to upgrade.

-- 
Alex Lutay


From admin at marcoteixeira.com  Fri Feb 26 16:14:03 2016
From: admin at marcoteixeira.com (Marco Teixeira)
Date: Fri, 26 Feb 2016 21:14:03 +0000
Subject: [Spce-user] ngcp-sems error stack-trace
Message-ID: <CAD7smbiYH92qCFG3X7A9U05poV3KzSXinCU0171hC4chJs_KXA@mail.gmail.com>

Hello,

I'm seeing these errors today... could it have to do with yesterday updates
?
For the ngcp team, i do have the call sip signalling in PCAP if want...
This was the only error a saw...

# cat /etc/ngcp_version
mr3.8.5

# cat /var/log/ngcp/sems.log
Feb 26 13:19:35 sbc ngcp-sems[20733]: [#7f21994d4700] [reply,
AmBasicSipDialog.cpp:575] ERROR:  could not find any transaction matching
request cseq
Feb 26 13:19:35 sbc ngcp-sems[20733]: [#7f21994d4700] [reply,
AmBasicSipDialog.cpp:579] ERROR:  request cseq=398486202; reply code=500;
callid=0gQAAC8WAAACBAAALxYAACDxoSeF4diiPZAuWPTh7LGPP44+3WQKcfpQxTjqxiiV at REDACTED_IP;
local_tag=3A37C073-56D050AB0003A812-A037E700;
remote_tag=REDACTED_IP+1+c739f1b5+28fcc5c8
Feb 26 13:19:35 sbc ngcp-sems[20733]: [#7f21994d4700] [log_stacktrace,
log.cpp:218] ERROR: stack-trace(0/[0x54cf15]):
/usr/sbin/ngcp-sems(log_stacktrace+0x35) [0x54cf15]
Feb 26 13:19:35 sbc ngcp-sems[20733]: [#7f21994d4700] [log_stacktrace,
log.cpp:218] ERROR: stack-trace(1/[0x498712]):
/usr/sbin/ngcp-sems(_ZN16AmBasicSipDialog5replyERK12AmSipRequestjRKSsPK10AmMimeBodyS4_i+0xa82)
[0x498712]
Feb 26 13:19:35 sbc ngcp-sems[20733]: [#7f21994d4700] [log_stacktrace,
log.cpp:218] ERROR: stack-trace(2/[0x48c2cb]):
/usr/sbin/ngcp-sems(_ZN12AmB2BSession12onSipRequestERK12AmSipRequest+0x3eb)
[0x48c2cb]
Feb 26 13:19:35 sbc ngcp-sems[20733]: [#7f21994d4700] [log_stacktrace,
log.cpp:218] ERROR: stack-trace(3/[0x7f21a48416c8]):
/usr/lib/ngcp-sems/plug-in//sbc.so(_ZN7CallLeg12onSipRequestERK12AmSipRequest+0x68)
[0x7f21a48416c8]
Feb 26 13:19:35 sbc ngcp-sems[20733]: [#7f21994d4700] [log_stacktrace,
log.cpp:218] ERROR: stack-trace(4/[0x7f21a488b3f5]):
/usr/lib/ngcp-sems/plug-in//sbc.so(_ZN10SBCCallLeg12onSipRequestERK12AmSipRequest+0x4c5)
[0x7f21a488b3f5]
Feb 26 13:19:35 sbc ngcp-sems[20733]: [#7f21994d4700] [log_stacktrace,
log.cpp:218] ERROR: stack-trace(5/[0x511f27]):
/usr/sbin/ngcp-sems(_ZN11AmSipDialog13onRxReqSanityERK12AmSipRequest+0x97)
[0x511f27]
Feb 26 13:19:35 sbc ngcp-sems[20733]: [#7f21994d4700] [log_stacktrace,
log.cpp:218] ERROR: stack-trace(6/[0x49a35b]):
/usr/sbin/ngcp-sems(_ZN16AmBasicSipDialog11onRxRequestERK12AmSipRequest+0x7b)
[0x49a35b]
Feb 26 13:19:35 sbc ngcp-sems[20733]: [#7f21994d4700] [log_stacktrace,
log.cpp:218] ERROR: stack-trace(7/[0x4f888b]): /usr/sbin/ngcp-sems()
[0x4f888b]
Feb 26 13:19:35 sbc ngcp-sems[20733]: [#7f21994d4700] [log_stacktrace,
log.cpp:218] ERROR: stack-trace(8/[0x7f21a4894717]):
/usr/lib/ngcp-sems/plug-in//sbc.so(_ZN10SBCCallLeg7processEP7AmEvent+0x177)
[0x7f21a4894717]
Feb 26 13:19:35 sbc ngcp-sems[20733]: [#7f21994d4700] [log_stacktrace,
log.cpp:218] ERROR: stack-trace(9/[0x4ba9fc]):
/usr/sbin/ngcp-sems(_ZN12AmEventQueue13processEventsEv+0x6c) [0x4ba9fc]
Feb 26 13:19:35 sbc ngcp-sems[20733]: [#7f21994d4700] [log_stacktrace,
log.cpp:218] ERROR: stack-trace(10/[0x4fa267]):
/usr/sbin/ngcp-sems(_ZN9AmSession28processEventsCatchExceptionsEv+0x37)
[0x4fa267]
Feb 26 13:19:35 sbc ngcp-sems[20733]: [#7f21994d4700] [log_stacktrace,
log.cpp:218] ERROR: stack-trace(11/[0x4fcccf]):
/usr/sbin/ngcp-sems(_ZN9AmSession15processingCycleEv+0x5f) [0x4fcccf]
Feb 26 13:19:35 sbc ngcp-sems[20733]: [#7f21994d4700] [log_stacktrace,
log.cpp:218] ERROR: stack-trace(12/[0x4f7dd1]):
/usr/sbin/ngcp-sems(_ZN9AmSession3runEv+0x81) [0x4f7dd1]
Feb 26 13:19:35 sbc ngcp-sems[20733]: [#7f21994d4700] [log_stacktrace,
log.cpp:218] ERROR: stack-trace(13/[0x52c6cc]):
/usr/sbin/ngcp-sems(_ZN8AmThread6_startEPv+0x5c) [0x52c6cc]
Feb 26 13:19:35 sbc ngcp-sems[20733]: [#7f21994d4700] [log_stacktrace,
log.cpp:218] ERROR: stack-trace(14/[0x7f21a8c57b50]):
/lib/x86_64-linux-gnu/libpthread.so.0(+0x6b50) [0x7f21a8c57b50]
Feb 26 13:19:35 sbc ngcp-sems[20733]: [#7f21994d4700] [log_stacktrace,
log.cpp:218] ERROR: stack-trace(15/[0x7f21a7b6530d]):
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d) [0x7f21a7b6530d]


---
Marco
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20160226/ac6823e0/attachment-0001.html>

From admin at marcoteixeira.com  Fri Feb 26 18:12:25 2016
From: admin at marcoteixeira.com (Marco Teixeira)
Date: Fri, 26 Feb 2016 23:12:25 +0000
Subject: [Spce-user] System Statistics stopped working
In-Reply-To: <CAD7smbjKD9zohdQR7DbZB4W_Z4_nWM_MNiKY94h3rcQfv1d9UQ@mail.gmail.com>
References: <CAD7smbj1zw5O_-R16yyJB1+fNb=bqBSNWRXUvcx5zoTEmPnjiw@mail.gmail.com>
 <5624C307.8010404@sipwise.com>
 <CAD7smbgusq1rTY2bLZidfcvAuqbvAw1fqvFg_ZsSnTPyOY-X7A@mail.gmail.com>
 <CAD7smbjKD9zohdQR7DbZB4W_Z4_nWM_MNiKY94h3rcQfv1d9UQ@mail.gmail.com>
Message-ID: <CAD7smbh7CovFUp2-3Z+Ua6iM6Y_55v2zyO-8oup=OB9k-08iVg@mail.gmail.com>

Hello,

Getting back to this old issue... Back to basics.
- I installed a clean 3.8.3. Stats working ok.
- Changed default timezone from Europe/Vienna to GMT. Stats stopped
working...

Followed sugestion of deleting RRD files to allow regeneration...

===
root at spce:/var/lib/collectd/rrd# /etc/init.d/collectd stop
[ ok ] Stopping statistics collection and monitoring daemon: collectd.
root at spce:/var/lib/collectd/rrd# mv spce spce.bak
root at spce:/var/lib/collectd/rrd# ls -lap
total 12
drwxr-xr-x  3 root root 4096 Feb 26 23:10 ./
drwxr-xr-x  3 root root 4096 Feb 26 22:20 ../
drwxr-xr-x 48 root root 4096 Feb 26 22:30 spce.bak/
root at spce:/var/lib/collectd/rrd# /etc/init.d/collectd start
[ ok ] Starting statistics collection and monitoring daemon: collectd.
root at spce:/var/lib/collectd/rrd# ls -lapt
total 16
drwxr-xr-x 41 root root 4096 Feb 26 23:10 spce/
drwxr-xr-x  4 root root 4096 Feb 26 23:10 ./
drwxr-xr-x 48 root root 4096 Feb 26 22:30 spce.bak/
drwxr-xr-x  3 root root 4096 Feb 26 22:20 ../
root at spce:/var/lib/collectd/rrd#
===

?Did not work... Any more hints ?
Please ??


---
Marco
---


On Fri, Oct 23, 2015 at 1:59 AM, Marco Teixeira <admin at marcoteixeira.com>
wrote:

> Hi there,
>
> As it seems, i didn't catch these on the logs, on first time. Could this
> be it ?
> ntpd is running ... But i guess this only afects graphing ntp process ...
>
> === CUT
> Oct 23 00:27:09 localhost collectd[21512]: rrdtool plugin: Adjusting
> "RandomTimeout" to 0.000 seconds.
> Oct 23 00:27:09 localhost collectd[21512]: mysql plugin: Successfully
> connected to database <none> at server Localhost via UNIX socket (server
> version: 5.5.44-0+deb7u1-log, protocol version: 10)
> Oct 23 00:27:09 localhost collectd[21512]: recv(2) failed: Connection
> refused
> Oct 23 00:27:09 localhost collectd[21512]: ntpd plugin: ntpd_do_query
> (REQ_GET_KERNEL) failed with status -1
> Oct 23 00:27:09 localhost collectd[21512]: read-function of plugin `ntpd'
> failed. Will suspend it for 20 seconds.
>
>
>
>
> ---
> Cumprimentos / Best regards
>
> Marco
> ---
>
>
> On Thu, Oct 22, 2015 at 10:02 PM, Marco Teixeira <admin at marcoteixeira.com>
> wrote:
>
>> Well...
>>
>> One small corretion for future users getting to this, rrd files in
>> mr3.8.3 are on /var/lib/collectd/rrd/ $HOSTNAME
>>
>> Now, back to the problem in hand:
>> - collectd is fine
>> - rrd files have current timestamps
>> - "rrdtool fetch" works ok
>>
>> It seems something with graphics generation or saving... took a look at
>> the code in /usr/share/ngcp-panel/templates/statistics/lists.tt but i'm
>> having dificulties graspping it...
>> - there is a line "var tz_offset = [% tz_offset %];". Where does this
>> variable come from ? The system ?
>> - Are the graphics generated on the fly for display, or are they stored
>> somewhere else ?
>> - Does nginx have some timezone variable in the confs and not  copying
>> from the system ?
>>
>> ?thank you for your time...?
>>
>>
>> ---
>> Cumprimentos / Best regards
>>
>> Marco
>>
>>
>> On Mon, Oct 19, 2015 at 11:16 AM, Alex Lutay <alutay at sipwise.com> wrote:
>>
>>> Hi Marco,
>>>
>>> All system statistics are collected by collectd and are stored in RRD
>>> files located in /var/lib/collectd/rrd/spce/
>>>
>>> "Internally, RRDtool uses "seconds since the epoch" to keep track of
>>> time. This is the number of seconds since January first, 1970,
>>> midnight, UTC. When you are specifying a time in this format, it is UTC
>>> time automatically." (c) http://vandenbogaerdt.nl/rrdtool/timezone.php
>>>
>>> So, you need to check collecd log first to see new values are
>>> inserter properly, also you can manually extract RRD data using RRD
>>> tool fetch (to check content of RRD file).
>>>
>>> Finally you can move RRD files and restart collectd to init new
>>> statistics files. Then you can manually move old data in new RRD files
>>> if necessary.
>>>
>>> P.S. changing the timezone of server on the fly is not a good idea,
>>> AFAIK. As data in MySQL DB (like accounting, CDRs) stored in fields
>>> without timezone specified. Also MySQL works in server timezone by
>>> default.
>>>
>>> On 10/18/2015 10:22 PM, Marco Teixeira wrote:
>>> > Hello list,
>>> >
>>> > A couple weeks ago i lost system statistics... The page opens but
>>> > doesn't get pasted those loading progress circling dots... All of them,
>>> > on any variable i select on the dropdown box.
>>> >
>>> > I searched around on the logs, and found nothing.
>>> > Does anyone have a clue how to fix this ?
>>> >
>>> > # more /etc/ngcp_version
>>> > mr3.8.3
>>>
>>> --
>>> Alex Lutay
>>> _______________________________________________
>>> Spce-user mailing list
>>> Spce-user at lists.sipwise.com
>>> https://lists.sipwise.com/listinfo/spce-user
>>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20160226/5c041140/attachment-0001.html>

From admin at marcoteixeira.com  Fri Feb 26 18:16:06 2016
From: admin at marcoteixeira.com (Marco Teixeira)
Date: Fri, 26 Feb 2016 23:16:06 +0000
Subject: [Spce-user] System Statistics stopped working
In-Reply-To: <CAD7smbh7CovFUp2-3Z+Ua6iM6Y_55v2zyO-8oup=OB9k-08iVg@mail.gmail.com>
References: <CAD7smbj1zw5O_-R16yyJB1+fNb=bqBSNWRXUvcx5zoTEmPnjiw@mail.gmail.com>
 <5624C307.8010404@sipwise.com>
 <CAD7smbgusq1rTY2bLZidfcvAuqbvAw1fqvFg_ZsSnTPyOY-X7A@mail.gmail.com>
 <CAD7smbjKD9zohdQR7DbZB4W_Z4_nWM_MNiKY94h3rcQfv1d9UQ@mail.gmail.com>
 <CAD7smbh7CovFUp2-3Z+Ua6iM6Y_55v2zyO-8oup=OB9k-08iVg@mail.gmail.com>
Message-ID: <CAD7smbhxJ1Xu8s22qL9YVuVgY80paC1hqB+G8kf2FdGBGyK5dw@mail.gmail.com>

If i change back to Europe/Vienna, Statistics start displaying again... Not
even a reboot needed...
I'm guessing a hardcoded tz_offset variable somewhere on the panel coding
maybe ...


===
Current default time zone: 'Europe/Vienna'
Local time is now:      Sat Feb 27 00:12:48 CET 2016.
Universal Time is now:  Fri Feb 26 23:12:48 UTC 2016.
===


On Fri, Feb 26, 2016 at 11:12 PM, Marco Teixeira <admin at marcoteixeira.com>
wrote:

> Hello,
>
> Getting back to this old issue... Back to basics.
> - I installed a clean 3.8.3. Stats working ok.
> - Changed default timezone from Europe/Vienna to GMT. Stats stopped
> working...
>
> Followed sugestion of deleting RRD files to allow regeneration...
>
> ===
> root at spce:/var/lib/collectd/rrd# /etc/init.d/collectd stop
> [ ok ] Stopping statistics collection and monitoring daemon: collectd.
> root at spce:/var/lib/collectd/rrd# mv spce spce.bak
> root at spce:/var/lib/collectd/rrd# ls -lap
> total 12
> drwxr-xr-x  3 root root 4096 Feb 26 23:10 ./
> drwxr-xr-x  3 root root 4096 Feb 26 22:20 ../
> drwxr-xr-x 48 root root 4096 Feb 26 22:30 spce.bak/
> root at spce:/var/lib/collectd/rrd# /etc/init.d/collectd start
> [ ok ] Starting statistics collection and monitoring daemon: collectd.
> root at spce:/var/lib/collectd/rrd# ls -lapt
> total 16
> drwxr-xr-x 41 root root 4096 Feb 26 23:10 spce/
> drwxr-xr-x  4 root root 4096 Feb 26 23:10 ./
> drwxr-xr-x 48 root root 4096 Feb 26 22:30 spce.bak/
> drwxr-xr-x  3 root root 4096 Feb 26 22:20 ../
> root at spce:/var/lib/collectd/rrd#
> ===
>
> ?Did not work... Any more hints ?
> Please ??
>
>
> ---
> Marco
> ---
>
>
> On Fri, Oct 23, 2015 at 1:59 AM, Marco Teixeira <admin at marcoteixeira.com>
> wrote:
>
>> Hi there,
>>
>> As it seems, i didn't catch these on the logs, on first time. Could this
>> be it ?
>> ntpd is running ... But i guess this only afects graphing ntp process ...
>>
>> === CUT
>> Oct 23 00:27:09 localhost collectd[21512]: rrdtool plugin: Adjusting
>> "RandomTimeout" to 0.000 seconds.
>> Oct 23 00:27:09 localhost collectd[21512]: mysql plugin: Successfully
>> connected to database <none> at server Localhost via UNIX socket (server
>> version: 5.5.44-0+deb7u1-log, protocol version: 10)
>> Oct 23 00:27:09 localhost collectd[21512]: recv(2) failed: Connection
>> refused
>> Oct 23 00:27:09 localhost collectd[21512]: ntpd plugin: ntpd_do_query
>> (REQ_GET_KERNEL) failed with status -1
>> Oct 23 00:27:09 localhost collectd[21512]: read-function of plugin `ntpd'
>> failed. Will suspend it for 20 seconds.
>>
>>
>>
>>
>> ---
>> Cumprimentos / Best regards
>>
>> Marco
>> ---
>>
>>
>> On Thu, Oct 22, 2015 at 10:02 PM, Marco Teixeira <admin at marcoteixeira.com
>> > wrote:
>>
>>> Well...
>>>
>>> One small corretion for future users getting to this, rrd files in
>>> mr3.8.3 are on /var/lib/collectd/rrd/ $HOSTNAME
>>>
>>> Now, back to the problem in hand:
>>> - collectd is fine
>>> - rrd files have current timestamps
>>> - "rrdtool fetch" works ok
>>>
>>> It seems something with graphics generation or saving... took a look at
>>> the code in /usr/share/ngcp-panel/templates/statistics/lists.tt but i'm
>>> having dificulties graspping it...
>>> - there is a line "var tz_offset = [% tz_offset %];". Where does this
>>> variable come from ? The system ?
>>> - Are the graphics generated on the fly for display, or are they stored
>>> somewhere else ?
>>> - Does nginx have some timezone variable in the confs and not  copying
>>> from the system ?
>>>
>>> ?thank you for your time...?
>>>
>>>
>>> ---
>>> Cumprimentos / Best regards
>>>
>>> Marco
>>>
>>>
>>> On Mon, Oct 19, 2015 at 11:16 AM, Alex Lutay <alutay at sipwise.com> wrote:
>>>
>>>> Hi Marco,
>>>>
>>>> All system statistics are collected by collectd and are stored in RRD
>>>> files located in /var/lib/collectd/rrd/spce/
>>>>
>>>> "Internally, RRDtool uses "seconds since the epoch" to keep track of
>>>> time. This is the number of seconds since January first, 1970,
>>>> midnight, UTC. When you are specifying a time in this format, it is UTC
>>>> time automatically." (c) http://vandenbogaerdt.nl/rrdtool/timezone.php
>>>>
>>>> So, you need to check collecd log first to see new values are
>>>> inserter properly, also you can manually extract RRD data using RRD
>>>> tool fetch (to check content of RRD file).
>>>>
>>>> Finally you can move RRD files and restart collectd to init new
>>>> statistics files. Then you can manually move old data in new RRD files
>>>> if necessary.
>>>>
>>>> P.S. changing the timezone of server on the fly is not a good idea,
>>>> AFAIK. As data in MySQL DB (like accounting, CDRs) stored in fields
>>>> without timezone specified. Also MySQL works in server timezone by
>>>> default.
>>>>
>>>> On 10/18/2015 10:22 PM, Marco Teixeira wrote:
>>>> > Hello list,
>>>> >
>>>> > A couple weeks ago i lost system statistics... The page opens but
>>>> > doesn't get pasted those loading progress circling dots... All of
>>>> them,
>>>> > on any variable i select on the dropdown box.
>>>> >
>>>> > I searched around on the logs, and found nothing.
>>>> > Does anyone have a clue how to fix this ?
>>>> >
>>>> > # more /etc/ngcp_version
>>>> > mr3.8.3
>>>>
>>>> --
>>>> Alex Lutay
>>>> _______________________________________________
>>>> Spce-user mailing list
>>>> Spce-user at lists.sipwise.com
>>>> https://lists.sipwise.com/listinfo/spce-user
>>>>
>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20160226/70b5db98/attachment-0001.html>

From matthew at tenacit.net  Mon Feb 29 05:38:06 2016
From: matthew at tenacit.net (Matthew Ogden)
Date: Mon, 29 Feb 2016 12:38:06 +0200
Subject: [Spce-user] [22695407.548269] asterisk[27411]: segfault at 407 ip
 00007f26b6375133 sp 00007f26aff83760 error 6 in
 libmysqlclient_r.so.16.0.0[7f26b633f000+13e000]
Message-ID: <CAB4Z0mJw1oY6yYQPqeGjiByU_Uo_MTeP97O=KhpqZHGx5_MTGQ@mail.gmail.com>

Hi All

I'm trying to use VM in spce for the first time.

I'm getting the following problem:
Feb 29 12:31:27 spce kernel: [22695407.548269] asterisk[27411]: segfault at
407 ip 00007f26b6375133 sp 00007f26aff83760 error 6 in
libmysqlclient_r.so.16.0.0[7f26b633f000+13e000]

logged in syslog as soon as somoen calls 2000.

In asterisk I'm seeing (sanitized):

Connected to Asterisk 1.4.24.1-RSP (Community supported branch) currently
running on spce (pid = 27385)
Verbosity was 0 and is now 73
    -- Executing [abcSUBSCRIBER at sip_in:1]
Macro("SIP/sip.mydomain.net-011ead40", "voicemailowner_nopass|SUBSCRIBER")
in new stack
    -- Executing [s at macro-voicemailowner_nopass:1]
Answer("SIP/sip.mydomain.net-011ead40", "") in new stack
    -- Executing [s at macro-voicemailowner_nopass:2]
Set("SIP/sip.mydomain.net-011ead40", "TIMEOUT(digit)=5") in new stack
    -- Digit timeout set to 5
    -- Executing [s at macro-voicemailowner_nopass:3]
Set("SIP/sip.mydomain.net-011ead40", "TIMEOUT(response)=10") in new stack
    -- Response timeout set to 10
    -- Executing [s at macro-voicemailowner_nopass:4]
Wait("SIP/sip.mydomain.net-011ead40", "1") in new stack
    -- Executing [s at macro-voicemailowner_nopass:5]
VoiceMailMain("SIP/sip.mydomain.net-011ead40", "sSUBSCRIBER") in new stack
spce*CLI>


-- 





*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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20160229/540940b9/attachment-0001.html>

From matthew at tenacit.net  Mon Feb 29 05:43:11 2016
From: matthew at tenacit.net (Matthew Ogden)
Date: Mon, 29 Feb 2016 12:43:11 +0200
Subject: [Spce-user] [22695407.548269] asterisk[27411]: segfault at 407
 ip 00007f26b6375133 sp 00007f26aff83760 error 6 in
 libmysqlclient_r.so.16.0.0[7f26b633f000+13e000]
In-Reply-To: <CAB4Z0mJw1oY6yYQPqeGjiByU_Uo_MTeP97O=KhpqZHGx5_MTGQ@mail.gmail.com>
References: <CAB4Z0mJw1oY6yYQPqeGjiByU_Uo_MTeP97O=KhpqZHGx5_MTGQ@mail.gmail.com>
Message-ID: <CAB4Z0mLZM7aZ8h9Bz1qvC735EQfY-M9aRE34Nakycm7JXo8zFA@mail.gmail.com>

I'm on version 3, but I'm running Debian 6.0.10 still.

based on the other threads, you guys are saying upgrade?

On 29 February 2016 at 12:38, Matthew Ogden <matthew at tenacit.net> wrote:

> Hi All
>
> I'm trying to use VM in spce for the first time.
>
> I'm getting the following problem:
> Feb 29 12:31:27 spce kernel: [22695407.548269] asterisk[27411]: segfault
> at 407 ip 00007f26b6375133 sp 00007f26aff83760 error 6 in
> libmysqlclient_r.so.16.0.0[7f26b633f000+13e000]
>
> logged in syslog as soon as somoen calls 2000.
>
> In asterisk I'm seeing (sanitized):
>
> Connected to Asterisk 1.4.24.1-RSP (Community supported branch) currently
> running on spce (pid = 27385)
> Verbosity was 0 and is now 73
>     -- Executing [abcSUBSCRIBER at sip_in:1]
> Macro("SIP/sip.mydomain.net-011ead40", "voicemailowner_nopass|SUBSCRIBER")
> in new stack
>     -- Executing [s at macro-voicemailowner_nopass:1]
> Answer("SIP/sip.mydomain.net-011ead40", "") in new stack
>     -- Executing [s at macro-voicemailowner_nopass:2]
> Set("SIP/sip.mydomain.net-011ead40", "TIMEOUT(digit)=5") in new stack
>     -- Digit timeout set to 5
>     -- Executing [s at macro-voicemailowner_nopass:3]
> Set("SIP/sip.mydomain.net-011ead40", "TIMEOUT(response)=10") in new stack
>     -- Response timeout set to 10
>     -- Executing [s at macro-voicemailowner_nopass:4]
> Wait("SIP/sip.mydomain.net-011ead40", "1") in new stack
>     -- Executing [s at macro-voicemailowner_nopass:5]
> VoiceMailMain("SIP/sip.mydomain.net-011ead40", "sSUBSCRIBER") in new stack
> spce*CLI>
>
>
> --
>
>
>
>
>
> *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
>
>
>



-- 





*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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20160229/042018a4/attachment-0001.html>

From noreply at sipwise.com  Mon Feb 29 09:08:32 2016
From: noreply at sipwise.com (Sipwise Repository Tracker)
Date: Mon, 29 Feb 2016 15:08:32 +0100
Subject: [Spce-user] FYI: Package update(s) in release mr3.8.3
Message-ID: <1456754912.521359.14790.nullmailer@deb1.sipwise.com>

One or more updates have been released in NGCP release mr3.8.3:

* captagent was updated from version 5.2.11.0-1+0~mr3.8.3.14 to version 5.2.12.0-1+0~mr3.8.3.15
* captagent-dbg was updated from version 5.2.11.0-1+0~mr3.8.3.14 to version 5.2.12.0-1+0~mr3.8.3.15

To apply the latest update(s) execute:

  apt-get update && apt-get upgrade && \
  ngcp-update-db-schema && ngcp-update-cfg-schema && \
  ngcpcfg apply manual system update

If you encounter any problems please report a bug at
the spce-user at lists.sipwise.com mailing list.

Further documentation is available at:

  http://www.sipwise.org/products/spce/documentation/

This is an automated mail by the Continuous Delivery platform at Sipwise.com


From noreply at sipwise.com  Mon Feb 29 09:09:55 2016
From: noreply at sipwise.com (Sipwise Repository Tracker)
Date: Mon, 29 Feb 2016 15:09:55 +0100
Subject: [Spce-user] FYI: Package update(s) in release mr3.8.4
Message-ID: <1456754995.532091.15031.nullmailer@deb1.sipwise.com>

One or more updates have been released in NGCP release mr3.8.4:

* captagent was updated from version 5.2.11.0-1+0~mr3.8.4.12 to version 5.2.12.0-1+0~mr3.8.4.13
* captagent-dbg was updated from version 5.2.11.0-1+0~mr3.8.4.12 to version 5.2.12.0-1+0~mr3.8.4.13

To apply the latest update(s) execute:

  apt-get update && apt-get upgrade && \
  ngcp-update-db-schema && ngcp-update-cfg-schema && \
  ngcpcfg apply manual system update

If you encounter any problems please report a bug at
the spce-user at lists.sipwise.com mailing list.

Further documentation is available at:

  http://www.sipwise.org/products/spce/documentation/

This is an automated mail by the Continuous Delivery platform at Sipwise.com


From noreply at sipwise.com  Mon Feb 29 09:11:16 2016
From: noreply at sipwise.com (Sipwise Repository Tracker)
Date: Mon, 29 Feb 2016 15:11:16 +0100
Subject: [Spce-user] FYI: Package update(s) in release mr3.8.5
Message-ID: <1456755076.558468.15389.nullmailer@deb1.sipwise.com>

One or more updates have been released in NGCP release mr3.8.5:

* captagent was updated from version 5.2.11.0-1+0~mr3.8.5.8 to version 5.2.12.0-1+0~mr3.8.5.9
* captagent-dbg was updated from version 5.2.11.0-1+0~mr3.8.5.8 to version 5.2.12.0-1+0~mr3.8.5.9

To apply the latest update(s) execute:

  apt-get update && apt-get upgrade && \
  ngcp-update-db-schema && ngcp-update-cfg-schema && \
  ngcpcfg apply manual system update

If you encounter any problems please report a bug at
the spce-user at lists.sipwise.com mailing list.

Further documentation is available at:

  http://www.sipwise.org/products/spce/documentation/

This is an automated mail by the Continuous Delivery platform at Sipwise.com


From noreply at sipwise.com  Mon Feb 29 09:18:42 2016
From: noreply at sipwise.com (Sipwise Repository Tracker)
Date: Mon, 29 Feb 2016 15:18:42 +0100
Subject: [Spce-user] FYI: Package update(s) in release mr4.2.1
Message-ID: <1456755522.118207.16998.nullmailer@deb1.sipwise.com>

One or more updates have been released in NGCP release mr4.2.1:

* captagent was updated from version 5.2.11.1-1+0~mr4.2.1.11 to version 5.2.12.1-1+0~mr4.2.1.12
* captagent-dbg was updated from version 5.2.11.1-1+0~mr4.2.1.11 to version 5.2.12.1-1+0~mr4.2.1.12

To apply the latest update(s) execute:

  apt-get update && apt-get upgrade && \
  ngcp-update-db-schema && ngcp-update-cfg-schema && \
  ngcpcfg apply manual system update

If you encounter any problems please report a bug at
the spce-user at lists.sipwise.com mailing list.

Further documentation is available at:

  http://www.sipwise.org/products/spce/documentation/

This is an automated mail by the Continuous Delivery platform at Sipwise.com


From noreply at sipwise.com  Mon Feb 29 09:19:37 2016
From: noreply at sipwise.com (Sipwise Repository Tracker)
Date: Mon, 29 Feb 2016 15:19:37 +0100
Subject: [Spce-user] FYI: Package update(s) in release mr4.2.1
Message-ID: <1456755577.377592.17245.nullmailer@deb1.sipwise.com>

One or more updates have been released in NGCP release mr4.2.1:

* ngcp-db-schema was updated from version 4.2.1.1+0~mr4.2.1.1 to version 4.2.1.2+0~mr4.2.1.2

To apply the latest update(s) execute:

  apt-get update && apt-get upgrade && \
  ngcp-update-db-schema && ngcp-update-cfg-schema && \
  ngcpcfg apply manual system update

If you encounter any problems please report a bug at
the spce-user at lists.sipwise.com mailing list.

Further documentation is available at:

  http://www.sipwise.org/products/spce/documentation/

This is an automated mail by the Continuous Delivery platform at Sipwise.com


From noreply at sipwise.com  Mon Feb 29 09:22:04 2016
From: noreply at sipwise.com (Sipwise Repository Tracker)
Date: Mon, 29 Feb 2016 15:22:04 +0100
Subject: [Spce-user] FYI: Package update(s) in release mr3.8.5
Message-ID: <1456755724.240082.18051.nullmailer@deb1.sipwise.com>

One or more updates have been released in NGCP release mr3.8.5:

* ngcp-db-schema was updated from version 3.8.5.1+0~mr3.8.5.1 to version 3.8.5.2+0~mr3.8.5.2

To apply the latest update(s) execute:

  apt-get update && apt-get upgrade && \
  ngcp-update-db-schema && ngcp-update-cfg-schema && \
  ngcpcfg apply manual system update

If you encounter any problems please report a bug at
the spce-user at lists.sipwise.com mailing list.

Further documentation is available at:

  http://www.sipwise.org/products/spce/documentation/

This is an automated mail by the Continuous Delivery platform at Sipwise.com


From noreply at sipwise.com  Mon Feb 29 09:23:14 2016
From: noreply at sipwise.com (Sipwise Repository Tracker)
Date: Mon, 29 Feb 2016 15:23:14 +0100
Subject: [Spce-user] FYI: Package update(s) in release mr3.8.4
Message-ID: <1456755794.385043.18407.nullmailer@deb1.sipwise.com>

One or more updates have been released in NGCP release mr3.8.4:

* ngcp-db-schema was updated from version 3.8.4.1+0~mr3.8.4.1 to version 3.8.4.2+0~mr3.8.4.2

To apply the latest update(s) execute:

  apt-get update && apt-get upgrade && \
  ngcp-update-db-schema && ngcp-update-cfg-schema && \
  ngcpcfg apply manual system update

If you encounter any problems please report a bug at
the spce-user at lists.sipwise.com mailing list.

Further documentation is available at:

  http://www.sipwise.org/products/spce/documentation/

This is an automated mail by the Continuous Delivery platform at Sipwise.com


From admin at marcoteixeira.com  Mon Feb 29 10:20:30 2016
From: admin at marcoteixeira.com (Marco Teixeira)
Date: Mon, 29 Feb 2016 15:20:30 +0000
Subject: [Spce-user] System Statistics stopped working
In-Reply-To: <CAD7smbhxJ1Xu8s22qL9YVuVgY80paC1hqB+G8kf2FdGBGyK5dw@mail.gmail.com>
References: <CAD7smbj1zw5O_-R16yyJB1+fNb=bqBSNWRXUvcx5zoTEmPnjiw@mail.gmail.com>
 <5624C307.8010404@sipwise.com>
 <CAD7smbgusq1rTY2bLZidfcvAuqbvAw1fqvFg_ZsSnTPyOY-X7A@mail.gmail.com>
 <CAD7smbjKD9zohdQR7DbZB4W_Z4_nWM_MNiKY94h3rcQfv1d9UQ@mail.gmail.com>
 <CAD7smbh7CovFUp2-3Z+Ua6iM6Y_55v2zyO-8oup=OB9k-08iVg@mail.gmail.com>
 <CAD7smbhxJ1Xu8s22qL9YVuVgY80paC1hqB+G8kf2FdGBGyK5dw@mail.gmail.com>
Message-ID: <CAD7smbhXHey0dA=DhTcNHvBg9nm5EXrefPyrQ0h3g0BLrCsvPQ@mail.gmail.com>

Sorry to bump this up, but i really need to get this working... i imagine
it would be a simple thing to fix. I just don't know where...


On Fri, Feb 26, 2016 at 11:16 PM, Marco Teixeira <admin at marcoteixeira.com>
wrote:

> If i change back to Europe/Vienna, Statistics start displaying again...
> Not even a reboot needed...
> I'm guessing a hardcoded tz_offset variable somewhere on the panel coding
> maybe ...
>
>
> ===
> Current default time zone: 'Europe/Vienna'
> Local time is now:      Sat Feb 27 00:12:48 CET 2016.
> Universal Time is now:  Fri Feb 26 23:12:48 UTC 2016.
> ===
>
>
> On Fri, Feb 26, 2016 at 11:12 PM, Marco Teixeira <admin at marcoteixeira.com>
> wrote:
>
>> Hello,
>>
>> Getting back to this old issue... Back to basics.
>> - I installed a clean 3.8.3. Stats working ok.
>> - Changed default timezone from Europe/Vienna to GMT. Stats stopped
>> working...
>>
>> Followed sugestion of deleting RRD files to allow regeneration...
>>
>> ===
>> root at spce:/var/lib/collectd/rrd# /etc/init.d/collectd stop
>> [ ok ] Stopping statistics collection and monitoring daemon: collectd.
>> root at spce:/var/lib/collectd/rrd# mv spce spce.bak
>> root at spce:/var/lib/collectd/rrd# ls -lap
>> total 12
>> drwxr-xr-x  3 root root 4096 Feb 26 23:10 ./
>> drwxr-xr-x  3 root root 4096 Feb 26 22:20 ../
>> drwxr-xr-x 48 root root 4096 Feb 26 22:30 spce.bak/
>> root at spce:/var/lib/collectd/rrd# /etc/init.d/collectd start
>> [ ok ] Starting statistics collection and monitoring daemon: collectd.
>> root at spce:/var/lib/collectd/rrd# ls -lapt
>> total 16
>> drwxr-xr-x 41 root root 4096 Feb 26 23:10 spce/
>> drwxr-xr-x  4 root root 4096 Feb 26 23:10 ./
>> drwxr-xr-x 48 root root 4096 Feb 26 22:30 spce.bak/
>> drwxr-xr-x  3 root root 4096 Feb 26 22:20 ../
>> root at spce:/var/lib/collectd/rrd#
>> ===
>>
>> ?Did not work... Any more hints ?
>> Please ??
>>
>>
>> ---
>> Marco
>> ---
>>
>>
>> On Fri, Oct 23, 2015 at 1:59 AM, Marco Teixeira <admin at marcoteixeira.com>
>> wrote:
>>
>>> Hi there,
>>>
>>> As it seems, i didn't catch these on the logs, on first time. Could this
>>> be it ?
>>> ntpd is running ... But i guess this only afects graphing ntp process ...
>>>
>>> === CUT
>>> Oct 23 00:27:09 localhost collectd[21512]: rrdtool plugin: Adjusting
>>> "RandomTimeout" to 0.000 seconds.
>>> Oct 23 00:27:09 localhost collectd[21512]: mysql plugin: Successfully
>>> connected to database <none> at server Localhost via UNIX socket (server
>>> version: 5.5.44-0+deb7u1-log, protocol version: 10)
>>> Oct 23 00:27:09 localhost collectd[21512]: recv(2) failed: Connection
>>> refused
>>> Oct 23 00:27:09 localhost collectd[21512]: ntpd plugin: ntpd_do_query
>>> (REQ_GET_KERNEL) failed with status -1
>>> Oct 23 00:27:09 localhost collectd[21512]: read-function of plugin
>>> `ntpd' failed. Will suspend it for 20 seconds.
>>>
>>>
>>>
>>>
>>> ---
>>> Cumprimentos / Best regards
>>>
>>> Marco
>>> ---
>>>
>>>
>>> On Thu, Oct 22, 2015 at 10:02 PM, Marco Teixeira <
>>> admin at marcoteixeira.com> wrote:
>>>
>>>> Well...
>>>>
>>>> One small corretion for future users getting to this, rrd files in
>>>> mr3.8.3 are on /var/lib/collectd/rrd/ $HOSTNAME
>>>>
>>>> Now, back to the problem in hand:
>>>> - collectd is fine
>>>> - rrd files have current timestamps
>>>> - "rrdtool fetch" works ok
>>>>
>>>> It seems something with graphics generation or saving... took a look at
>>>> the code in /usr/share/ngcp-panel/templates/statistics/lists.tt but
>>>> i'm having dificulties graspping it...
>>>> - there is a line "var tz_offset = [% tz_offset %];". Where does this
>>>> variable come from ? The system ?
>>>> - Are the graphics generated on the fly for display, or are they stored
>>>> somewhere else ?
>>>> - Does nginx have some timezone variable in the confs and not  copying
>>>> from the system ?
>>>>
>>>> ?thank you for your time...?
>>>>
>>>>
>>>> ---
>>>> Cumprimentos / Best regards
>>>>
>>>> Marco
>>>>
>>>>
>>>> On Mon, Oct 19, 2015 at 11:16 AM, Alex Lutay <alutay at sipwise.com>
>>>> wrote:
>>>>
>>>>> Hi Marco,
>>>>>
>>>>> All system statistics are collected by collectd and are stored in RRD
>>>>> files located in /var/lib/collectd/rrd/spce/
>>>>>
>>>>> "Internally, RRDtool uses "seconds since the epoch" to keep track of
>>>>> time. This is the number of seconds since January first, 1970,
>>>>> midnight, UTC. When you are specifying a time in this format, it is UTC
>>>>> time automatically." (c) http://vandenbogaerdt.nl/rrdtool/timezone.php
>>>>>
>>>>> So, you need to check collecd log first to see new values are
>>>>> inserter properly, also you can manually extract RRD data using RRD
>>>>> tool fetch (to check content of RRD file).
>>>>>
>>>>> Finally you can move RRD files and restart collectd to init new
>>>>> statistics files. Then you can manually move old data in new RRD files
>>>>> if necessary.
>>>>>
>>>>> P.S. changing the timezone of server on the fly is not a good idea,
>>>>> AFAIK. As data in MySQL DB (like accounting, CDRs) stored in fields
>>>>> without timezone specified. Also MySQL works in server timezone by
>>>>> default.
>>>>>
>>>>> On 10/18/2015 10:22 PM, Marco Teixeira wrote:
>>>>> > Hello list,
>>>>> >
>>>>> > A couple weeks ago i lost system statistics... The page opens but
>>>>> > doesn't get pasted those loading progress circling dots... All of
>>>>> them,
>>>>> > on any variable i select on the dropdown box.
>>>>> >
>>>>> > I searched around on the logs, and found nothing.
>>>>> > Does anyone have a clue how to fix this ?
>>>>> >
>>>>> > # more /etc/ngcp_version
>>>>> > mr3.8.3
>>>>>
>>>>> --
>>>>> Alex Lutay
>>>>> _______________________________________________
>>>>> Spce-user mailing list
>>>>> Spce-user at lists.sipwise.com
>>>>> https://lists.sipwise.com/listinfo/spce-user
>>>>>
>>>>
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20160229/e89f2b86/attachment-0001.html>

From noreply at sipwise.com  Mon Feb 29 11:54:22 2016
From: noreply at sipwise.com (Sipwise Repository Tracker)
Date: Mon, 29 Feb 2016 17:54:22 +0100
Subject: [Spce-user] FYI: Package update(s) in release mr3.8.3
Message-ID: <1456764862.568571.4976.nullmailer@deb1.sipwise.com>

One or more updates have been released in NGCP release mr3.8.3:

* captagent was updated from version 5.2.12.0-1+0~mr3.8.3.15 to version 5.2.13.0-1+0~mr3.8.3.16
* captagent-dbg was updated from version 5.2.12.0-1+0~mr3.8.3.15 to version 5.2.13.0-1+0~mr3.8.3.16

To apply the latest update(s) execute:

  apt-get update && apt-get upgrade && \
  ngcp-update-db-schema && ngcp-update-cfg-schema && \
  ngcpcfg apply manual system update

If you encounter any problems please report a bug at
the spce-user at lists.sipwise.com mailing list.

Further documentation is available at:

  http://www.sipwise.org/products/spce/documentation/

This is an automated mail by the Continuous Delivery platform at Sipwise.com


From noreply at sipwise.com  Mon Feb 29 11:55:42 2016
From: noreply at sipwise.com (Sipwise Repository Tracker)
Date: Mon, 29 Feb 2016 17:55:42 +0100
Subject: [Spce-user] FYI: Package update(s) in release mr3.8.4
Message-ID: <1456764942.396067.5213.nullmailer@deb1.sipwise.com>

One or more updates have been released in NGCP release mr3.8.4:

* captagent was updated from version 5.2.12.0-1+0~mr3.8.4.13 to version 5.2.13.0-1+0~mr3.8.4.14
* captagent-dbg was updated from version 5.2.12.0-1+0~mr3.8.4.13 to version 5.2.13.0-1+0~mr3.8.4.14

To apply the latest update(s) execute:

  apt-get update && apt-get upgrade && \
  ngcp-update-db-schema && ngcp-update-cfg-schema && \
  ngcpcfg apply manual system update

If you encounter any problems please report a bug at
the spce-user at lists.sipwise.com mailing list.

Further documentation is available at:

  http://www.sipwise.org/products/spce/documentation/

This is an automated mail by the Continuous Delivery platform at Sipwise.com


From noreply at sipwise.com  Mon Feb 29 11:57:08 2016
From: noreply at sipwise.com (Sipwise Repository Tracker)
Date: Mon, 29 Feb 2016 17:57:08 +0100
Subject: [Spce-user] FYI: Package update(s) in release mr3.8.5
Message-ID: <1456765028.495443.5531.nullmailer@deb1.sipwise.com>

One or more updates have been released in NGCP release mr3.8.5:

* captagent was updated from version 5.2.12.0-1+0~mr3.8.5.9 to version 5.2.13.0-1+0~mr3.8.5.10
* captagent-dbg was updated from version 5.2.12.0-1+0~mr3.8.5.9 to version 5.2.13.0-1+0~mr3.8.5.10

To apply the latest update(s) execute:

  apt-get update && apt-get upgrade && \
  ngcp-update-db-schema && ngcp-update-cfg-schema && \
  ngcpcfg apply manual system update

If you encounter any problems please report a bug at
the spce-user at lists.sipwise.com mailing list.

Further documentation is available at:

  http://www.sipwise.org/products/spce/documentation/

This is an automated mail by the Continuous Delivery platform at Sipwise.com


From noreply at sipwise.com  Mon Feb 29 12:02:57 2016
From: noreply at sipwise.com (Sipwise Repository Tracker)
Date: Mon, 29 Feb 2016 18:02:57 +0100
Subject: [Spce-user] FYI: Package update(s) in release mr4.2.1
Message-ID: <1456765377.488080.6622.nullmailer@deb1.sipwise.com>

One or more updates have been released in NGCP release mr4.2.1:

* captagent was updated from version 5.2.12.1-1+0~mr4.2.1.12 to version 5.2.13.1-1+0~mr4.2.1.13
* captagent-dbg was updated from version 5.2.12.1-1+0~mr4.2.1.12 to version 5.2.13.1-1+0~mr4.2.1.13

To apply the latest update(s) execute:

  apt-get update && apt-get upgrade && \
  ngcp-update-db-schema && ngcp-update-cfg-schema && \
  ngcpcfg apply manual system update

If you encounter any problems please report a bug at
the spce-user at lists.sipwise.com mailing list.

Further documentation is available at:

  http://www.sipwise.org/products/spce/documentation/

This is an automated mail by the Continuous Delivery platform at Sipwise.com