[Spce-user] Intro

[Mike Hammett]

*nods* That's what I was going to do.



-----
Mike Hammett
Intelligent Computing Solutions
http://www.ics-il.com

----- Original Message -----
From: "Andreas Granig" <agranig at sipwise.com>
To: spce-user at lists.sipwise.com
Sent: Monday, May 6, 2013 9:23:33 AM
Subject: Re: [Spce-user] Intro

Hi guys,

There is a wiki page we started long ago to collect various peering 
provider examples, however there is only one there yet:

http://sipwise.com/doc/wiki/doku.php?id=spce:peering

Probably you could add your settings there? That would be awesome!

Thanks,
Andreas

On 05/06/2013 03:00 PM, Jeremie Chism wrote:
> You are correct. The peering rule is for outbound only. I will send you
> my vitality rewrite rules.
>
> On Monday, May 6, 2013, Mike Hammett wrote:
>
>     "The NGCP will however allow inbound calls from the servers in this
>     group even without peering rules."
>
>     I created no Peering Rules for my Vitelity inbound group because
>     this said SipWise accepts inbound calls.
>
>     There are no Rewrite Rules.
>
>
>
>     -----
>     Mike Hammett
>     Intelligent Computing Solutions
>     http://www.ics-il.com
>
>     ----- Original Message -----
>     From: "Jeremie Chism" <jchism2 at gmail.com <javascript:;>>
>     To: "Mike Hammett" <sipwise at ics-il.net <javascript:;>>
>     Cc: spce-user at lists.sipwise.com
>     Sent: Monday, May 6, 2013 7:34:23 AM
>     Subject: Re: [Spce-user] Intro
>
>     It's a rewrite rule. What is happening is what vitality is sending
>     you is not matching up. I have a rewrite rule for vitality I can
>     send you. Also did you do the accept all rule for your vitality peer.
>
>     Sent from my iPhone
>
>     On May 6, 2013, at 7:01 AM, Mike Hammett <sipwise at ics-il.net> wrote:
>
>      > =====
>      > A call to your DID 815981XXXX  from 815739XXXX has failed at
>     5:48am on 05/06/2013 MDT. We received 'CONGESTION'  when attempting
>     to route the call to your server or device. This number is
>     configured to route to the peer 65.182.XXX.XXX.
>      >
>      > This error usually means your server or device does not recognize
>     the number being dialed. If using asterisk, make sure you have the
>     correct inbound context specified on your inbound trunk and that you
>     have correctly added an inbound route/extension logic for this DID.
>      > =====
>      >
>      > So apparently whatever I did is wrong.
>      >
>      >
>      >
>      > -----
>      > Mike Hammett
>      > Intelligent Computing Solutions
>      > http://www.ics-il.com
>      >
>      > ----- Original Message -----
>      > From: "Mike Hammett" <sipwise at ics-il.net>
>      > To: spce-user at lists.sipwise.com
>      > Sent: Monday, May 6, 2013 6:23:41 AM
>      > Subject: Re: [Spce-user] Intro
>      >
>      > I did see where to change to IP based authentication and did so.
>     Why is IP authentication preferred over user authentication? Well,
>     other than it is more complicated to do this with SIPWise.
>      >
>      > I haven't tested it yet, but I made two peer groups, one for
>     inbound and one for outbound. I didn't create any peering rules for
>     the inbound group.
>      >
>      >
>      >
>      > -----
>      > Mike Hammett
>      > Intelligent Computing Solutions
>      > http://www.ics-il.com
>      >
>      > ----- Original Message -----
>      > From: "Kevin Masse" <kmasse at questblue.com>
>      > To: "Skyler" <skchopperguy at gmail.com>, spce-user at lists.sipwise.com
>      > Sent: Monday, May 6, 2013 6:08:15 AM
>      > Subject: Re: [Spce-user] Intro
>      >
>      > Good morning, I noticed something that needs to be addressed when
>     using Vitelity.
>      >
>      >>>> Proxy: sip28.vitelity.net <http://sip28.vitelity.net>
>     (66.241.99.27)
>      >>>> Outbound Proxy: outbound.vitelity.net
>     <http://outbound.vitelity.net>
>      >
>      > Not all accounts with Vitelity will use the same inbound and
>     outbound settings.
>      > Vitelity may send you traffic from any of the following
>      > 64.2.142.0/24 <http://64.2.142.0/24>
>      > 66.241.99.0/24 <http://66.241.99.0/24>
>      >
>      > If you are using settings provided by another Vitelity user it
>     may not be the same as yours.  Make sure you know what your
>     provisioned for with Vitelity and use those settings.
>      >
>      > Additionally it is not suggested to use registration with
>     providers. If you can avoid it, use IP Authentication.  In the
>     Vitelity portal go to the support link, then click on sub accounts.
>     You will be able to setup your IP there for IP Authentication.
>      >
>      > Thanks,
>      > Kevin
>      >
>      >
>      >
>      > -----Original Message-----
>      > From: spce-user-bounces at lists.sipwise.com
>     [mailto:spce-user-bounces at lists.sipwise.com] On Behalf Of Skyler
>      > Sent: Monday, May 06, 2013 4:14 AM
>      > To: spce-user at lists.sipwise.com
>      > Subject: Re: [Spce-user] Intro
>      >
>      > Woops, apparently I need sleep. sry.
>      >
>      > On 5/5/2013 9:53 PM, Skyler wrote:
>      >> Jeremie,
>      >>
>      >>  Do you also have user/pass on your vitality peer?
>      >>
>
>
>
> --
> Jeremie Chism
> Triton Communications
>
>
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> http://lists.sipwise.com/listinfo/spce-user
>

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