IP Access Control

[Bill H]

Running 4.0.0.3204 (Linux)

 

This has happened twice.

 

The customer reports "No calls in or out"

 

After testing the lines I came across the IP Access Control setting and the PSTN Gateways' IP address was there and it had been blocked.

 

After I cleared it the pbx started working OK.

 

Has anyone else seen this???

 

Is this a bug and if so, is there a fix????

 

Thanks

[mattlandis]

I'm afraid this IP access control is going to be like Vista's UAC...

Don't get me wrong, i like it and i think having the option is great...but i'm afraid of the support it will cause. Perhaps the default should be disabled?

 

Matt

[polycom2080]

you can add allow ip 0.0.0.0/0 and it will auto be open for all ip address...

or if they have static ip just allow there ip address,

[mattlandis]

you are correct.

 

i'm thinking for our prospects testing pbxnsip...it's just another thing to tell them. but not that big...

 

Matt

[Bill H]

Protecting the CS-410 from unauthorized access is the goal here.

 

But why does the CS-410 lock out its own Internal FXO Gateway?

 

What internal condition does it sense that is causing this condition?

[Vodia PBX]

But why does the CS-410 lock out its own Internal FXO Gateway?

 

This is a flaw in the default config. We need to change this.

[Bill H]

This is a flaw in the default config. We need to change this.

 

 

OK...

 

The sooner the better for my customer.

 

The only way he knows that the CS-410 stopped working is when he notices there are no calls coming in.

 

 

This causes loss of business then revenue then faith and finally customer.

[mattlandis]

i wonder if this feature shouldn't be disabled in default config for all versions? (i know this is different issue than the cs410 gateway)

 

just a thot.

 

Matt

[mabbott]

I was just playing with this yesterday. You just need to add 127.0.0.1 mask:255.255.255.255 to the Allow list.