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
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
Normal until you
Yum install sipxacccode
First
Tony Graziano, Manager
Telephone: 434.984.8430
Fax: 434.984.8431
Email: tgrazi...@myitdepartment.net
LAN/Telephony/Security and Control Systems Helpdesk:
Telephone: 434.984.8426
Fax: 434.984.8427
Helpdesk Contract
Cool, calls to account extension now work...
I think the chimes are unclear, Is there a reason not to have a voice prompt?
1. Please enter your authorization code.
2. The code you entered is incorrect, please try again.
3. Authorization code accepted, please dial the number after the tone.
I like having the chimes instead. A little more discreet in the event
someone is dialing for disa fraud.
I would venture to suggest digging therough the files in the rpm to see if
they were recorded the way you are hearing them.
Tony Graziano, Manager
Telephone:
On Wed, Sep 29, 2010 at 12:37 PM, Tony Graziano
tgrazi...@myitdepartment.net 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:
On Wed, Sep 29, 2010 at 1:50 PM, Tony Graziano
tgrazi...@myitdepartment.net 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
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 dhub...@ezuce.com wrote:
On Wed, Sep 29, 2010 at 1:50 PM, Tony Graziano
See what I mean, beeps aren't always that obvious? :)
On Wed, Sep 29, 2010 at 12:01 PM, Tony Graziano
tgrazi...@myitdepartment.net 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).
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 alias
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
They seemed to work for the Road Runner. Maybe they are
a different tone?
-Original Message-
From: sipx-users-boun...@list.sipfoundry.org
[mailto:sipx-users-boun...@list.sipfoundry.org] On Behalf Of Kyle Haefner
Sent: Wednesday, September 29, 2010 11:23 AM
To:
If you are going to expose a security vulnerability like this, I'd recommend
only allowing access to a trunk that has a finite ld value. For instance, a
prepaid like VOIP.ms, so that when they have exceeded the $100 of long
distance on the account in 15 minutes, calls don't go through any longer.
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, sooner
Agreed.
Ouch, this is a good example of limiting the seriousness of an attack with
some basic firewalling up front. It won't go away, but the effects will
certainly be lessened.
On Wed, Sep 29, 2010 at 3:16 PM, Todd Hodgen thod...@frontier.com wrote:
If you are going to expose a security
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,
On Mon, Aug 16, 2010 at 1:23 PM, Douglas Hubler dhub...@ezuce.com 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
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/
18 matches
Mail list logo
