Re: [sipx-users] FW: Alarm SPX00016: The ITSP Account could not be reached

2012-02-09 Thread Gerald Drouillard
On 2/9/2012 8:02 AM, Philippe Laurent wrote: > Thanks Gerald! Working on the set up today after end-of-business > day. I'm assuming that for IP Auth that I will have to port forward > 5080 to 5060? > > No. 5080 to 5080 -- Regards -- Gerald Drouillard Technol

Re: [sipx-users] FW: Alarm SPX00016: The ITSP Account could not be reached

2012-02-09 Thread Gerald Drouillard
On 2/9/2012 7:43 AM, Tony Graziano wrote: > If your firewall is configured correctly, why would NAT be set to YES. > Normally it would be set to NO if sipXbridge is in use and advertising > a public IP address (behind NAT). It has always been suggested to have > the provider DISABLE or TURN OFF NAT

Re: [sipx-users] FW: Alarm SPX00016: The ITSP Account could not be reached

2012-02-09 Thread Philippe Laurent
Thanks Gerald! Working on the set up today after end-of-business day. I'm assuming that for IP Auth that I will have to port forward 5080 to 5060? Tony, your input is appreciated as well. I will review the firewall settings to ensure that something isn't configured a bit wonky. Philippe On Thu,

Re: [sipx-users] FW: Alarm SPX00016: The ITSP Account could not be reached

2012-02-09 Thread Gerald Drouillard
On 2/9/2012 7:50 AM, Tony Graziano wrote: > for those of you who experience this problem, what is your > registration interval setting? With some ITSP's who have given me this > headache, I found lowering my setting (sometimes 180) really reduced > the problem (voxitas, etc.). It didn't change the

Re: [sipx-users] FW: Alarm SPX00016: The ITSP Account could not be reached

2012-02-09 Thread Tony Graziano
for those of you who experience this problem, what is your registration interval setting? With some ITSP's who have given me this headache, I found lowering my setting (sometimes 180) really reduced the problem (voxitas, etc.). On Thu, Feb 9, 2012 at 7:43 AM, Tony Graziano wrote: > On Thu, Feb 9,

Re: [sipx-users] FW: Alarm SPX00016: The ITSP Account could not be reached

2012-02-09 Thread Tony Graziano
On Thu, Feb 9, 2012 at 7:13 AM, Gerald Drouillard wrote: > On 2/8/2012 10:48 PM, Philippe Laurent wrote: > > Gerald - > > After repeated hours and iterations, and I'm at the point where I know I'm > missing something. > > I'll swallow my pride and say that I don't quite get how to do what you've >

Re: [sipx-users] FW: Alarm SPX00016: The ITSP Account could not be reached

2012-02-09 Thread Gerald Drouillard
On 2/8/2012 10:48 PM, Philippe Laurent wrote: Gerald - After repeated hours and iterations, and I'm at the point where I know I'm missing something. I'll swallow my pride and say that I don't quite get how to do what you've proposed (IP Auth with Voip.ms + SIP URI + what you've done on the

Re: [sipx-users] FW: Alarm SPX00016: The ITSP Account could not be reached

2012-02-08 Thread Philippe Laurent
Gerald - After repeated hours and iterations, and I'm at the point where I know I'm missing something. I'll swallow my pride and say that I don't quite get how to do what you've proposed (IP Auth with Voip.ms + SIP URI + what you've done on the firewall to make it happen). I looked back at the li

Re: [sipx-users] FW: Alarm SPX00016: The ITSP Account could not be reached

2012-02-07 Thread Gerald Drouillard
On 2/7/2012 2:12 AM, Tony Graziano wrote: > realize you cannot do call transfers with the above mentioned method, > so your mileage may vary. Yes you can! You have the have the DID configured to come in on 5080. Example voip.ms SIP URI: {DID}@pbx1.example.com:5080 or {DID}@youripaddress:5080 >

Re: [sipx-users] FW: Alarm SPX00016: The ITSP Account could not be reached

2012-02-06 Thread Tony Graziano
realize you cannot do call transfers with the above mentioned method, so your mileage may vary. On Mon, Feb 6, 2012 at 9:31 PM, Gerald Drouillard wrote: > On 2/6/2012 3:10 PM, Nathaniel Watkins wrote: >> Has anyone else seen the below behavor?  I seem to get this about once a day >> - one minu

Re: [sipx-users] FW: Alarm SPX00016: The ITSP Account could not be reached

2012-02-06 Thread Gerald Drouillard
On 2/6/2012 3:10 PM, Nathaniel Watkins wrote: > Has anyone else seen the below behavor? I seem to get this about once a day > - one minute later I get a message that the ITSP account has recovered. > > I was quick on the draw today - so as soon as the first email came in - I > dialed my cell pho

Re: [sipx-users] FW: Alarm SPX00016: The ITSP Account could not be reached

2012-02-06 Thread Sébastien QUESSON
gt; > From: "Michael Picher" > > To: "Discussion list for users of sipXecs software" > > > > Sent: Monday, February 6, 2012 10:16:26 PM > > Subject: Re: [sipx-users] FW: Alarm SPX00016: The ITSP Account > > could not > > be reached > &g

Re: [sipx-users] FW: Alarm SPX00016: The ITSP Account could not be reached

2012-02-06 Thread Tony Graziano
; primary service. >> >> -Original Message----- >> From: sipx-users-boun...@list.sipfoundry.org >> [mailto:sipx-users-boun...@list.sipfoundry.org] On Behalf Of Nathaniel >> Watkins >> Sent: Monday, February 06, 2012 12:11 PM >> To: Discussion list for us

Re: [sipx-users] FW: Alarm SPX00016: The ITSP Account could not be reached

2012-02-06 Thread Sébastien QUESSON
l Picher" > To: "Discussion list for users of sipXecs software" > > Sent: Monday, February 6, 2012 10:16:26 PM > Subject: Re: [sipx-users] FW: Alarm SPX00016: The ITSP Account could > not be reached > Ditto here guys... I tried tracking this down with them and

Re: [sipx-users] FW: Alarm SPX00016: The ITSP Account could not be reached

2012-02-06 Thread Michael Picher
consider a reliable career for > primary service. > > -Original Message- > From: sipx-users-boun...@list.sipfoundry.org > [mailto:sipx-users-boun...@list.sipfoundry.org] On Behalf Of Nathaniel > Watkins > Sent: Monday, February 06, 2012 12:11 PM > To: Discussion list for

Re: [sipx-users] FW: Alarm SPX00016: The ITSP Account could not be reached

2012-02-06 Thread Todd Hodgen
ssage- From: sipx-users-boun...@list.sipfoundry.org [mailto:sipx-users-boun...@list.sipfoundry.org] On Behalf Of Nathaniel Watkins Sent: Monday, February 06, 2012 12:11 PM To: Discussion list for users of sipXecs software Subject: [sipx-users] FW: Alarm SPX00016: The ITSP Account could not be reac

Re: [sipx-users] FW: Alarm SPX00016: The ITSP Account could not be reached

2012-02-06 Thread Philippe Laurent
I get the same error once or twice a day at one location, but strangely not at any other locations. All connect to the newyork.voip.ms instance, all have the same firewall and rules in place. I have yet to determine a cause (and clearly a solution). Philippe On Mon, Feb 6, 2012 at 3:10 PM, Natha

[sipx-users] FW: Alarm SPX00016: The ITSP Account could not be reached

2012-02-06 Thread Nathaniel Watkins
Has anyone else seen the below behavor? I seem to get this about once a day - one minute later I get a message that the ITSP account has recovered. I was quick on the draw today - so as soon as the first email came in - I dialed my cell phone as a long distance call - sure enough, it was routed