Domenico Chierico
2012-12-12 10:05:34 UTC
I've start testing on 4.6 and I'm experiencing some problems with snom (3xx
series) provisioning.
1) usually (as indicated on the wiki) i use the port 8090 to let the phone
access the configuration file, but seems that this port is blocked from the
standard firewall configuration (is acceptable to change that stuff to
"cluster only" as default).
I just discovered that file are accessible throught porta 80, should we
change the url removing ":8090" or is better to use that port for static
files?
2) snom need to be configured through dhcp to require a specific file name,
to match with the one generated by sipxecs. For this I usually use a class
specification that just affect snom parameters. Can this solution be
considered valid, if so I can try to write a patch to support automatic
snom class definition into dhcpd.
thanks
Domenico Chierico
series) provisioning.
1) usually (as indicated on the wiki) i use the port 8090 to let the phone
access the configuration file, but seems that this port is blocked from the
standard firewall configuration (is acceptable to change that stuff to
"cluster only" as default).
I just discovered that file are accessible throught porta 80, should we
change the url removing ":8090" or is better to use that port for static
files?
2) snom need to be configured through dhcp to require a specific file name,
to match with the one generated by sipxecs. For this I usually use a class
specification that just affect snom parameters. Can this solution be
considered valid, if so I can try to write a patch to support automatic
snom class definition into dhcpd.
thanks
Domenico Chierico