Ok After a loooooooooooooooong time I got a time to have a look at my blog,
After I left my previous work place now it's being a quite a long time and many things happened during this time.
I joined exetel on 15th October last year.
Just like my previous carrier , in exetel I was focus more on VoIP+ linux related stuffs.
Had a wonderful time ever since I joined exetel , learn a lot and keen on working on new aspects of VoIP.
Ok there are so many stories to tell for this couple of months.
One of the most memorable incident was happened on 27th May 2010.
Now the story beginssssss.................. :)
I got about 10+ tree's to take care everyday on our VoIP server farm :)
sooo many tree's were there
first on I met was filbert then hazelnut
sooo whats the difference ???
then gradually mamoncillo , mongongo, pilinut , paradisenut etc :) among them i finally met sausagetree as well :D lol
It's sooo amazing about the philosophy behind our server naming......
sip1 is the heart of our voip network. basically it is the sip router which responsible of carry out all routing of sip call traffic in our network.
Ok When I join exetel the sip router which was there was a pretty much old guy who almost had various problems on scalability.
After couple of months pass , After I return to SL being in SYD for couple of weeks I was able to finish my first mission which is to deploy and upgrade the existing ACD system that we had.
After my first mission 2nd one was hit at me in a time that I never expected. On 27th ThursdAy
While I was walking towards my office in the morning I met 1 of my colleague and heard a bad news. All he say was "There's something wrong with voip ..."
sigh.....
I went to office within next couple of minutes and turned on my PC and check the status with my immediate manager and found that half of the voip network is not responding.
Since from the morning they have restart the sip server couple time , cause of sip1 being freeze after sometime.
Ok Now What to do ?????????
I got a call from my manager and what he said that we need to immediately swap server to a new one.
I got anacardium and All I had was the pretty old config from the sip1.
anacardium is equipped with latest sip server softwares.
And there are a hell of a lot of changes being made to the core of the software.
The worst thing was that my engagement was on next day. Being frank I got bit f..kd up for a moment :(
Then After couple minutes I started to concentrate on the task that has being given to me and it was a really urgent, important , difficult one though :'(
After struggling couple of hours I have completed setting up anacardium to replace sip1
sigh..........................................................................
Ok After I completed setting up anacardium all that was left was to swap the server ips and put anacardium to live. For that I had to wait till the sysadmins comes back to work from home.
Since it was really being late for the day I said to my manager that I gotta go. :(
He said "It's ok ..you can go.."
After that I came home and they have swap the server on mid night and anacardium was operating since then,
After I came back to work on monday , there was a small configuration miss on one of the modules that handle NAT traversing mechanism causing some people being not able to receive calls.
After couple of minutes I have figure out the cause and fixed it immediately.
Then for about two or three more days I had to work on fixing some stuff related to billing and etc.
last week sip1 shot dead, and we got tempnut2over it. I made tempnut2 a replica of anacardium,
sigh..........................................
Saturday, August 28, 2010
Subscribe to:
Posts (Atom)
