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