This is about an accident which recently took place with our employees whose negligence could have cost their lives. Our two staff members went to Rajarhat Apartments on Sunday, 5th December for routine check. Debabrata Bhattarcharya and Bablu Mandal were returning and it was totally dark as it was 6.30pm. They were not wearing any helmets and Debabrata was on the driving seat. The accident occurred in the midst of their journey. Debabrata couldn’t see the manhole which was on his way and hence the bike tripped over. They both fell on the road. Debabrata got up and found that there were a lot of bruises on his body but he was more shocked to see his friend Bablu, facing a serious injury. Bablu was found unconscious and was taken to the nearest hospital via Auto Rickshaw with the help of the local people. They reached Seva Hospital near City Centre and found that there was a major internal bleeding on Bablu’s head. He was then transferred to NRS Hospital at Sealdah for a CT Scan. After that he went through an operation and the doctors have advised him a week’s rest at home.

Meanwhile, Grmtech bore all the expenses incurred for the treatment of his staff and now due to God’s grace, he is out of danger and is recovering very fast. Hope this story sends a message to all the readers that they should always wear a helmet and ride safely.

Needless to say, we were skeptical about how we would explain the vast scope of our work
when we were told that Prof. Janat would come to our Kolkata office on June 09th to understand
Grmtech’s work, the different departments, and its people and culture. The different department
heads, with a few team members, explained their departments, their working, and their
aspirations to him. We were pleasantly surprised that so learned and experienced a man was so
down to earth, and asked questions whenever he did not understand anything that we explained.

Though he had come directly from the airport after seeing our Rajarhat site, and it being a long
day of discussions, he took a lively interest in understanding the working of Grmtech. Our work
was new to him, as he had never been associated with this industry before. We were not sure if
he would ultimately decide to be part of our BOD.

It is an achievement and honour for Grmtech that Prof Janat decided to be a part of Grmtech, from July 11th. As our MD rightly pointed out, Grmtech now has double the confidence to take on more challenges, as we have knowledge and approachability combined with a keen interest backing us now.

Thank you Sir for deciding to be a part of us.

Introducing…

The new monitoring system in the Sys Admin Department. Four consecutive monitors with the advance monitoring tools are fully loaded to provide the best monitoring service to the tech team. The monitoring system includes-

1. Smokeping Network Analyzer tool that monitors the VOIP Phones, Workstations, Network Switches and the Internet Sharing Servers and represent the analysis graph.

2. Realtime monitoring graph that reflects the internet connectivity and consumption of all the ISS.

3. Realtime Call Monitor that shows the number of incoming live calls along with the Agent as well as Group Statistics and

4.  Finally the Zabbix Monitor that keeps an eye at the whole galaxy of servers and websites of our company all the time and informs the current status of the clients connected to it.

If so happens, always start asterisk from asterisk user:-


#su asterisk
#asterisk

We should not use any custom user and of course not “root” user. If we start asterisk as any non-asterisk user, various functionalities may be affected like our custom applications may not get permissions to execute asteisk cli commands.

For ex. If we run asterisk as root, then php apps running via apache, when execute asterisk cli commands, get following error:-
Unable to connect to remote asterisk (does /var/run/asterisk/asterisk.ctl exist?)

Run this command
#ls -l /var/run/asterisk/asterisk.ctl
srwxr-xr-x 1 root root 0 Aug 3 04:55 /var/run/asterisk/asterisk.ctl

As shown in the above result, non root users have no write permission.

Hence stop the asterisk using following command:-
#asterisk -rx "stop gracefully"
When asterisk will stop, use above mentioned process of starting asterisk as asterisk user.

1. Record Incoming Call On Demand. Record Outgoing Call On Demand
   Extensions in this class:  8001, 8002, 8003, 8004, 8005 (total 5 in number)
2. Record All Incoming Call. Record All Outgoing Call
   Extensions in this class:  9001, 9002, … , 9145 (total 145 in number)

To avoid manual configuration of each extension, I had taken following steps:-

1. Execute following queries on asterisk database (mysql):
   UPDATE asterisk.users SET recording='out=Adhoc|in=Adhoc' WHERE extension IN (8001, 8002, 8003, 8004, 8005)
UPDATE asterisk.users SET recording='out=Always|in=Always' WHERE extension >= 9001 AND extension <= 9145

   The above queries updates the recording setting for extensions in database. The effect for extension 8001 may be seen at http://Your-Asterisk-Freepbx-Server-Domain-Name/admin/config.php?type=setup&display=extensions&extdisplay=8001

2. Open each extension page and press the submit button. Finally click “Apply Configuration Changes” so that the changes may be propagated in running asterisk server