[Spce-user] Asterisk SIP Trunk to Sipwise - Subscriber or something else?

Kevin Masse kmasse at questblue.com
Thu Dec 27 08:30:55 EST 2012


Good morning Jon and thank you for your answers.

 

Another user was assisting me along and we did resolve the banning issue.

 

Additionally you comment on the global setting set to yes was an excellent recommendation.  I did what you said immediately. That worked without an issue.

 

The list user Jeremie was very helpful last night in cleaning up my miscellaneous issues.

 

At this point I am only down to one issue that I believe to be my last step to an outbound call from the Asterisk SIP Trunk.

 

I have Asterisk sending calls to the SIPWISE with the following pattern.  1NXXNXXXXXX (cc)(ac)(sn) for USA calls.

 

I know for sure I am struggling with the rewrite rules so the call can then be sent off to my carrier.

 

Inbound Rewrite Rules for Caller

Inbound Rewrite Rules for Callee

Outbound Rewrite Rules for Caller

Outbound Rewrite Rules for Callee

 

 

 

I think if there was a sample of the rewrite rule for USA dialing and perhaps international dialing I would have this.

 

Thank you for your response and Jeremie last night.  We are getting very close.

 

Thanks

Kevin

 

 

 

-----Original Message-----
From: spce-user-bounces at lists.sipwise.com [mailto:spce-user-bounces at lists.sipwise.com] On Behalf Of Jon Bonilla (Manwe)
Sent: Thursday, December 27, 2012 4:23 AM
To: spce-user at lists.sipwise.com
Subject: Re: [Spce-user] Asterisk SIP Trunk to Sipwise - Subscriber or something else?

 

El Wed, 26 Dec 2012 15:56:02 -0500

"Kevin Masse" <kmasse at questblue.com <mailto:kmasse at questblue.com> > escribió:

 

 

 

Hi Kevin

 

> 

> Here is a simple breakdown of the situation.

> 

>  

> 

> Installation of sipwise was done by following full install 

> instructions provided.  There were no errors in this process.

> 

>  

> 

> ·         Inbound calls are routing to Asterisk Box via Subscriber e.164

> number match.  This works without any issues.   (no nat, asterisk is sitting

> on public IP)  This is working because I have the Asterisk box 

> allowing anonymous SIP calls for testing avoiding having to register the trunk.

 

Are you allowing unauthenticated calls from spce peer or globally? If it's the second you should remove that. Use the "insecure" setting in sip.conf, but never "allowguest"

 

Example for a 1.4 box (should more or less work the same for newer versions)

 

[spce]

type=peer

host=1.2.3.4

insecure=invite,port

fromuser=user_at_spce

fromdomain=domain_at_spce

defaultuser=user_at_spce

context=sip_in

;Optional

;nat=no

;qualify=no

;disallow=all

;allow=alaw

 

 

> 

> ·         Inbound calls are routing to a telephone registered as a subscriber

> directly to sipwise.  This works without any issues.  (NAT in use, 

> telephone is behind router)

> 

> ·         Outbound calls from the telephone registered as a subscriber

> directly to sipwise are working perfect.  No issues here.

> 

>  

> 

> The issue I am having is the SIP trunk registering to sipwise and 

> getting banned every time I make a call attempt.

> 

>  

 

What's your register line, you sip peer configuration at sip.conf and what's the ngrep-sip of those registrations?

 

> 

> The configuration sample provide here appear straight forward but I 

> need to understand the process a little better.

> 

>  

> 

> 1st Do I want my Asterisk box to register to the sipwise as a 

> subscriber with the subscriber name and password?

 

If you have a static public ip you can leave the asterisk as subscriber but don't register it (you can fake a permanent contact for it) 

 

 

 

YOu can also trust the ip address and don't request authentication (check the trusted preferences.) But don't make it because you have asterisk configuration problems. Better to debug them first.

 

 

> 

> 2nd Do I want my Asterisk box to register to the sipwise server as 

> something else to be able to make outbound calls?

> 

 

As subscriber.

 

 

>  

> 

> What ends up happening when I try all of the sip trunk settings in the 

> list examples is the Asterisk box ends up getting banned under System

> Administration à Security Bans à Users   (The IP is not getting banned just

> the user)

> 

 

The user won't be bale to make calls (the authentication process is never reached for banned users) until the ban expires because it's banned. This prevents brute force attacks against user/password.

 

 

>  

> 

> I can provide lots of information but it may not be needed if the 

> above 2 questions have an answer.  I can keep reading from there.

> 

>  

> 

> Happy Holidays!

> 

 

Same to you! Merry christmas!

 

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20121227/15251045/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 20091 bytes
Desc: image001.png
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20121227/15251045/attachment-0001.png>


More information about the Spce-user mailing list