[Spce-user] New sip:provider CE mr4.0.1 is now available
brian.quandt at gmail.com
Mon Aug 3 13:46:25 EDT 2015
Does not solve the problem.
I've tested on multiple machines in the oregon AWS zone.
Looks like a resolver/DNS problem somewhere outside my box.
On Sun, Aug 2, 2015 at 11:27 PM, Victor Seva <vseva at sipwise.com> wrote:
> On 08/03/2015 03:47 AM, Brian Quandt wrote:
> > This was from your AMI instance (nope din't muck with apt after getting
> > things to run).
> > ngcp-ce-mr3.8.2 (ami-17142e27)
> Then we missed something. Our fault.
> > root at ip-10-220-196-230:/home/admin# apt-cache policy ngcp-ngcp-ce
> > ngcp-ngcp-ce:
> > Installed: 188.8.131.52+0~mr184.108.40.206
> > Candidate: 220.127.116.11+0~mr18.104.22.168
> > Version table:
> > *** 22.214.171.124+0~mr126.96.36.199 0
> > 100 /var/lib/dpkg/status
> Please change your /etc/apt/sources.list.d/sipwise.list to:
> deb [arch=amd64] http://deb.sipwise.com/spce/mr3.8.2/ wheezy main
> 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 --------------
An HTML attachment was scrubbed...
More information about the Spce-user