Hi All,
I have noticed that the requirement for serweb is php 4.3 and over. I'm using php 4.2.2 on a redhat 8 box. Has any got it working on 4.2.2? or do I need to upgrade to 4.3?
regards,
Zak
__________________________________________________________________ Introducing the New Netscape Internet Service. Only $9.95 a month -- Sign up today at http://isp.netscape.com/register
Netscape. Just the Net You Need.
New! Netscape Toolbar for Internet Explorer Search from anywhere on the Web and block those annoying pop-ups. Download now at http://channels.netscape.com/ns/search/install.jsp
xirak@netscape.net writes:
I have noticed that the requirement for serweb is php 4.3 and over. I'm using php 4.2.2 on a redhat 8 box. Has any got it working on 4.2.2? or do I need to upgrade to 4.3?
i noticed this too. it would be ok to require 4.3 if serweb server would not need to run on the same host as the proxy, where i don't want to use unstable debian.
my understanding is that serweb server needs fifo access and thus needs to run on the proxy host. perhaps i'm wrong?
what comes to fifo access more generally, i don't think it is a good idea to use fifo to create registrations. the reason is that fifo access will bypass allow_register check and may be also min/max registration time check. perhaps serweb could be modified to use sipsak and real register requests instead?
-- juha
At 01:38 PM 5/19/2004, Juha Heinanen wrote:
xirak@netscape.net writes:
I have noticed that the requirement for serweb is php 4.3 and over. I'm using php 4.2.2 on a redhat 8 box. Has any got it working on 4.2.2? or do I need to upgrade to 4.3?
i noticed this too. it would be ok to require 4.3 if serweb server would not need to run on the same host as the proxy, where i don't want to use unstable debian.
my understanding is that serweb server needs fifo access and thus needs to run on the proxy host. perhaps i'm wrong?
you are right.
what comes to fifo access more generally, i don't think it is a good idea to use fifo to create registrations. the reason is that fifo access will bypass allow_register check and may be also min/max registration time check. perhaps serweb could be modified to use sipsak and real register requests instead?
I don't necessarily agree. FIFO is a way for applications without SIP stack to access SER/SIP internals. I don't think that building in a communication stack in management applications, especially of RFC3261 complexity, has a good ratio effort/outcome. Registration restrictions can be handled by the application.
-jiri
Jiri Kuthan writes:
I don't necessarily agree. FIFO is a way for applications without SIP stack to access SER/SIP internals.
fifo is fine for accessing ser internals for administrative/monitoring reasons by the operator of the proxy. but is not practically possible to let end users access the web server on (public) proxy host, which thus prohibits the applicability of fifo for end user related tasks. it is a security and performance issue.
perhaps there could be a "fifo proxy" running on the proxy (or registrar) host to which would communicate with fifo clients running on the public web server hosts?
I don't think that building in a communication stack in management applications, especially of RFC3261 complexity, has a good ratio effort/outcome. Registration restrictions can be handled by the application.
in general, i agree with you, but what comes specifically to registrations, it would seem to me that it would be easier to modify serweb to use sipsak than it would be to modify serweb to do the checks.
-- juha
At 02:42 PM 5/19/2004, Juha Heinanen wrote:
in general, i agree with you, but what comes specifically to registrations, it would seem to me that it would be easier to modify serweb to use sipsak than it would be to modify serweb to do the checks.
That depends on point of view. I think equivalents of allow_register and min/max registration time check are fairly easy in serweb.
-jiri
Jiri Kuthan writes:
That depends on point of view. I think equivalents of allow_register and min/max registration time check are fairly easy in serweb.
ok, i'll give up on arguing for sipsak registrations.
however, end user web server running on public proxy host still remains a show stopper. my suggestion to that is to make fifo server listen a given tcp port in addition to listening the fifo file.
-- juha
-
Jiri Kuthan -
Juha Heinanen -
xirak＠netscape.net