Hi Douglas,
Explanation about Roles page
1.In roles page following observation:
1.If we Enable Basic system role then all the services in
the Basic system roles will be enabled(valid one)..After that if we
enable SIP Router role then all services in the SIP router roles will be
enabled but some services present in the Basic system role will be
disabled or unchecked...So same behavior is seen for other roles
too(Unified messaging and Call center--At the same time IM and call
center services can't be enabled)..whether its a valid behavior or is it
an issue
2.Regarding Authorization code
No authorization code feature is present in Feature
Tab..Because(May be) no Acc code service is present in any roles...
3.If we restart mongodb(/etc/init.d/mongod restart) then the services
like proxy,registrar and mongodb will not be running..Then again we want
to start all the services manually...Please check the attached file
4.For the logs what you asked for other quiries, I will send it once
we complete each scenario...
Regards,
Kumaran T
Douglas Hubler wrote:
On Thu, Mar 15, 2012 at 5:40 AM, Kumaran
<[email protected]> wrote:
In Fresh 4.6 installation(latest build-14thMar) by default most of the services
will be disabled....So we want enable it manually in server->Roles
page....Whether we should enable all the roles present in the page or only certain
roles?
you start a question here, but i cannot tell what it is
Because of following
1.If we enable Sip router roles then certain services in the Basic System
roles and in other roles will be disabled
this a question? if so, then answer is : no
2.If we try to configure without enabling the roles then Internal Exception
try to isolate this and send log.
3.If we enable call center then certain roles in IM will be disabled and vice
versa
this a question? if so, then answer is : no
4.So we can't enable all the services at a time....
right, not all services work yet, as per task list
Other Observation:
5.Authorization code services is not present in any roles
y, it's almost like we need "Kitchen Sink" role for that one. ;) Some
sort of catch all. Need to think about that...
6.Call to 100 and 101 is not going through(482 loops detected)
try to isolate this and send log.
7.If conference is created then we want restart mongodb and send profiles to server...Then following
error message "IMDB regeneration" and "Configuration"-"Internal Error
can't call something : sipx-test.ttplservices.com/176.25.3.201:27017/local" and
again send profiles to make it to work..
try to isolate this and send log.
8.If we restart mongodb(/etc/init.d/mongod restart) then the services like
proxy,registrar and mongodb will not be running..then again we want to start
it...
this is unclear to me what you mean
_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev/
[root@sipx-test sipxpbx]# /etc/init.d/sipxproxy status
sipXproxy (pid 13851) is running...
[root@sipx-test sipxpbx]# /etc/init.d/sipxregistrar status
sipregistrar (pid 13735) is running...
[root@sipx-test sipxpbx]# /etc/init.d/mongod status
mongod (pid 13680) is running...
[root@sipx-test sipxpbx]# /etc/init.d/mongod restart
Stopping mongod: [ OK ]
Starting mongod: forked process: 13919
all output going to: /var/log/mongo/mongod.log
[ OK ]
[root@sipx-test sipxpbx]# /etc/init.d/mongod status
mongod dead but subsys locked
[root@sipx-test sipxpbx]# /etc/init.d/mongod start
Starting mongod: forked process: 13958
all output going to: /var/log/mongo/mongod.log
[ OK ]
[root@sipx-test sipxpbx]# /etc/init.d/mongod status
mongod (pid 13958) is running...
[root@sipx-test sipxpbx]# /etc/init.d/sipxregistrar status
sipregistrar dead but pid file exists
[root@sipx-test sipxpbx]# /etc/init.d/sipxproxy status
sipXproxy dead but pid file exists
[root@sipx-test sipxpbx]# /etc/init.d/sipxregistrar start
[root@sipx-test sipxpbx]# /etc/init.d/sipxregistrar status [ OK ]
sipregistrar (pid 14000) is running...
[root@sipx-test sipxpbx]# /etc/init.d/sipxproxy start
[root@sipx-test sipxpbx]# /etc/init.d/sipxproxy status [ OK ]
sipXproxy (pid 14048) is running...
[root@sipx-test sipxpbx]#
_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev/
