On 9/29/10 3:21 PM, Tony Graziano wrote:
I'm not exposing a vulnerability. SIP is vulnerable due to a very
specific "basic" config, scanning for open port 5060. Behind a
firewall or not... I'm simply suggesting that people consider using a
different access code for the default service than *81
> [mailto:sipx-users-boun...@list.sipfoundry.org] On Behalf Of Kyle Haefner
> Sent: Wednesday, September 29, 2010 12:10 PM
> To: Tony Graziano
> Cc: Discussion list for users of sipXecs software
> Subject: Re: [sipx-users] Anyone in a position to test authorization code
> on
> 4.3 i
Yes, but thats an alias and easily removed or changed... [?]
I don't know though, a lot of Universities are publishing their sip
directories. I think the whole "with me having local access to your voice
vlan, let me show you how i can record your calls" type of security scare
thing going on, soone
undry.org] On Behalf Of Kyle Haefner
Sent: Wednesday, September 29, 2010 12:10 PM
To: Tony Graziano
Cc: Discussion list for users of sipXecs software
Subject: Re: [sipx-users] Anyone in a position to test authorization code on
4.3 install?
I really think that open SIP uris to the Internet are going
: Discussion list for users of sipXecs software
Subject: Re: [sipx-users] Anyone in a position to test authorization code on
4.3 install?
See what I mean, beeps aren't always that obvious? :)
On Wed, Sep 29, 2010 at 12:01 PM, Tony Graziano
wrote:
> Nevermind. It was a PICNIC issue. I forgot to
I really think that open SIP uris to the Internet are going to be a
short lived thing. I think that in future if you want to call someone
outside of your domain you'll need to present either a personal
certificate from a trusted third party, or a certificate signed to
your domain and your domain i
I pointed that out specifically for you Kyle. While I agree with you, my
"spidey senses" tingle at the thought of revealing what someone has dialed
in "human speak:...". Having been one to speak to customers toll fraud back
in my carrier telecom days...
In my tests, I placed a DID number on the al
See what I mean, beeps aren't always that obvious? :)
On Wed, Sep 29, 2010 at 12:01 PM, Tony Graziano
wrote:
> Nevermind. It was a PICNIC issue. I forgot to use the daned access code!
> That's what those two beeps mean...
>
> (I smacked the back of my head for that one).
>
> On Wed, Sep 29, 2010
Nevermind. It was a PICNIC issue. I forgot to use the daned access code!
That's what those two beeps mean...
(I smacked the back of my head for that one).
On Wed, Sep 29, 2010 at 1:55 PM, Douglas Hubler wrote:
> On Wed, Sep 29, 2010 at 1:50 PM, Tony Graziano
> wrote:
> > I find dialing media s
On Wed, Sep 29, 2010 at 1:50 PM, Tony Graziano
wrote:
> I find dialing media services is an issue (VM or AA).
>
> Dialinf internal users and pstn numbers seem fine. I get two beeps dialing
> media services.
>
> Should that work?
Should, can you post back the offending log entries.
___
Sep 29 13:43:01 2010
Subject: Re: [sipx-users] Anyone in a position to test authorization code on
4.3 install?
On Wed, Sep 29, 2010 at 12:37 PM, Tony Graziano
wrote:
> Normal until you
>
> Yum install sipxacccode
ok, i fixed this for next time
___
On Wed, Sep 29, 2010 at 12:37 PM, Tony Graziano
wrote:
> Normal until you
>
> Yum install sipxacccode
ok, i fixed this for next time
___
sipx-users mailing list
sipx-users@list.sipfoundry.org
List Archive: http://list.sipfoundry.org/archive/sipx-users/
...@list.sipfoundry.org
To: Discussion list for users of sipXecs software
Sent: Wed Sep 29 13:20:53 2010
Subject: Re: [sipx-users] Anyone in a position to test authorization code on
4.3 install?
Cool, calls to account extension now work...
I think the chimes are unclear, Is there a reason not to have a voice
prompt
myitdepartment.net/gethelp/
>
> - Original Message -
> From: sipx-users-boun...@list.sipfoundry.org
>
> To: Discussion list for users of sipXecs software
>
> Sent: Wed Sep 29 12:36:03 2010
> Subject: Re: [sipx-users] Anyone in a position to test authorization code on
Customers:
http://www.myitdepartment.net/gethelp/
- Original Message -
From: sipx-users-boun...@list.sipfoundry.org
To: Discussion list for users of sipXecs software
Sent: Wed Sep 29 12:36:03 2010
Subject: Re: [sipx-users] Anyone in a position to test authorization code on
4.3 install?
Just
Just did yum update on 4.3.
I get this when I set up an authcode
File replication: sipxacccode.properties9/29/10 9:12 AM 9/29/10 9:12
AM Failed
File replication: authcodes.xml 9/29/10 9:12 AM 9/29/10 9:12 AM Failed
Kyle
On Wed, Sep 29, 2010 at 6:28 AM, Tony Graziano
wrote:
> O
OK. I tested this on yesterday afternoon's build.
It seemed to work. I also added an alias to that field (a DID number) and it
worked this way also:
Add DID to alias for Authorization Codes, Call DID from PSTN. Immediately
got chime tones, entered is access code and #. Got ding. Dialed internal
e
On Mon, Aug 16, 2010 at 1:23 PM, Douglas Hubler wrote:
> Only known documentation AFAIK
> http://track.sipfoundry.org/browse/XX-8501
I tested this last night works fine, quick notes if anyone want to try
it if you're running 4.3 testing
Step 1: run
yum install sipxacccode
Step 2: Restart sipxe
Only known documentation AFAIK
http://track.sipfoundry.org/browse/XX-8501
___
sipx-users mailing list
sipx-users@list.sipfoundry.org
List Archive: http://list.sipfoundry.org/archive/sipx-users/
19 matches
Mail list logo
