[Spce-user] Intro

[Jeremie Chism]

Hey mike sorry for the late response. I've been running like crazy.
 I use vitelity with the rules I sent you with no problem. I apply the rule
to the peer because vitelity requires a different rule than voip
innovations. This normalizes everything coming from the particular peer. In
vitelity you have a static trusted Ip and not register correct?  Also you
aren't trying to register your subscriber to vitelity through peer
registration?

On Wednesday, May 8, 2013, Skyler wrote:

> scratch that. I forgot that peering rule is not required for inbound.
> Looking again. brb.
>
> On 5/8/2013 11:49 AM, Skyler wrote:
>
> go into "Viteleity Inbound" peering group. Under 'Peering Rules' you see
> a yellow highlighted error. Click the + to add a blank rule.
>
> Test again.
>
> Skyler
>
> On 5/8/2013 11:37 AM, Mike Hammett wrote:
>
> No dice and here's my results.
>
>
>
> -----
> Mike Hammett
> Intelligent Computing Solutions
> http://www.ics-il.com
>
> ----- Original Message -----
> From: "Skyler" <skchopperguy at gmail.com>
> To: spce-user at lists.sipwise.com
> Sent: Wednesday, May 8, 2013 11:45:26 AM
> Subject: Re: [Spce-user] Intro
>
> Mike,
>
>    No there isn't. Best thing is to:
>
> ngrep-sip b -d any -qt -W byline port 5060 > /tmp/vitelity-problem.txt
>
> Then email that to the list.
>
> BTW, looking at your congestion.txt and seeing the other suggestions to
> re-write rule(s). Seems you are trying to strip the leading '1', but
> from what I see, you need to add a '1'. Like so:
>
> ^([2-9][0-9]+)$   1\1   10-digits to e164
>
> Put the above into your rewrite rule set, then ensure the set is enabled
> for the subscriber AND the Vitelity peer(s).
>
> Once confirmed, run a test call while running the ngrep above and send
> to the list.
>
> --Skyler
>
> On 5/8/2013 9:02 AM, Mike Hammett wrote:
>
> That didn't pan out for me either.
>
> Is there some sort of debugging that has more verbosity than ngcp-sip?
>
>
>
> -----
> Mike Hammett
> Intelligent Computing Solutions
> http://www.ics-il.com
>
> ----- Original Message -----
> From: "Kevin Masse" <kmasse at questblue.com>
> To: "Mike Hammett" <sipwise at ics-il.net>, spce-user at lists.sipwise.com
> Sent: Tuesday, May 7, 2013 4:31:15 PM
> Subject: RE: [Spce-user] Intro
>
> Mike, try to verify this:
>
> Do you have a Peering Server for Vitelity
> You should have a Peering Server Vitel-Inbound with an IP that you
> are instructed to use from Vitelity
>
> Then a Peering Rule under that Peering Server
> In this area just put a 1 in the Callee Prefix nothing in Callee
> Pattern or Caller Pattern
>
> Then in REWRITE RULES
>
> Set the following in Outbound Rewrite Rules for Callee   (YES I did
> say Outbound Rewrite Rules, don’t think of it the way it may appear)
>
> Match Pattern: ^(1|)([1-9][0-9][0-9]+)$   Replacement Pattern:
> \2     Description:  Take off the 1
>
> Now inbounds calls should arrive and work with either your e164
> number assigned to the subscriber /OR/ your alias number assigned to
> that subscriber.
>
>
> Vitelity was quite clear with their error message sent to you with
> the call fail notification.
> That indicates that you are close.
>
> Now, there is one reason that most will agree with in the forum.
> This is offered for free and basically do your best to figure out.
>
> Sipwise offers paid services and a commercial product which will work
> out of the box.  I think if they truly offered all the answers in a
> manual it could be more difficult to offer their commercial product /
> pro product.
>
> I am with you and most others, a good detailed screen shot with
> examples it really missing.
>
> Let me know how you make out with the above.  Using vitelity is
> really straight forward once you get the above setting working.
>
> The examples I provided you are with us running it a SBC mode we do
> not connect any devices to sipwise and only route traffic to asterisk
> boxes in the field for our clients.  No SIP devices register to our
> configuration.  We use trusted sources and send traffic to the end
> user PBX.
>
> I hope this helps.
>
> Kevin
>
>
>
> -----Original Message-----
> From: spce-user-bounces at lists.sipwise.com
> [mailto:spce-user-bounces at lists.sipwise.com] On Behalf Of Mike Hammett
> Sent: Tuesday, May 07, 2013 4:44 PM
> To: spce-user at lists.sipwise.com
> Subject: Re: [Spce-user] Intro
>
> I did change it over to IP authentication. The inbound calls hit my
> SIPwise box, but it rejects them. I don't have any devices associated
> with it, but I do have VM setup. Ideas?
>
> BTW: Maybe a beginner\quick setup guide and then a more advanced
> manual or set of wiki articles for the more advanced topics? The
> basics should include what I have to do to connect to origination and
> termination peers, provision a client device and have incoming calls
> route to that client a
>
>

-- 
Jeremie Chism
Triton Communications
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20130508/e5e25258/attachment-0001.html>