Kiran Bulusu’s Blog

Updated to the Firmware 31.x.y, I should say, I’m not all impressed with the performance..its slow and i can feel the difference..I use emoze for checking emails of all my accts incl outlook and it painfully slow when i invoke it..

On the positive, I no longer have the sound when the camera clicks..apparently theres a law in US which says whenever a camera clicks, it has to have a sound..

Second diff I noticed is,  I see PTT (push to talk) options ..not that I want to use it as radio , but feels good to know that N95 has so many features…

Hopefully, I will be able to uncover few more in coming weeks…

BTW, I had to change to EURO1 using NSS to test this firmware

You need to know the exact criteria why you are considering other tools else its waste of time for you/your team and for vendor as well. Some common pain points are
A.QOR (Quality of Results)
B.Turn Around Time (TAT ) and Stability of the tool
C.Reactive mode type of Support from Vendor/Poor Support/Long resolution to issues
D.Interoperability with other tools
E.Cost of licenses itself.

Single chips have become a commodity and some chips just cost less than a dollar or some
consumer electronics centric chips like wireless/3g/ etc might cost less than 10$ depending
on the volume…a can of coke seems to be more expensive than some components today,
so in what form can the semi vendor can add value and get profits? where is the value chain now?

Who said Nokia N95 VOIP + Magic Jack doesnt work

I have to admit that it took me 2 days to figure this out, but honestly
Nokia SIP client works. I googled and most posts in many symbian/nokia forums
suggested that Magic Jack never works with Nokia . Some blamed that Nokia SIP stack
implementation is broken, some said MJ isnt friendly etc…

Its not true,Some VOIP (especially windows based softphones ) can figure out
the DNS-SRV records (yes you read it right. Its not DNS, but its DNS-SRV DNS+STUN server )
and “realm” strings for the client to work.

1. Avoid communication black outs. This is a must. Please always keep the customer in loop. Whether its pre-sales or post-sales. Your customer needs to be aware of the progress you are making and you have to get his acknowledgment. This is tricky at times when the product is not fully matured yet and we need to fine tune before it starts delivering results. Even then , you have to present this “initial” results and then keep showing progress. This is very important.

If the customer doesnt know what you are working on, how much efforts you have made , he might be compelled to look at another company. You have make that “human” connection and keep him in the loop.

2. Stick to the findings of discovery process: If you deviate from this, customer will not agree when you present the results. The intent of whole “discovery process” is defeated. If you have to change for some reason, you need to get clear acknowledgment from customer.

3. Pre-Sales is very different from Post-Sales . Pre-Sales is to prove that product works and solves customers issues identified in “discovery process”. Deployment is real stress test to the product and can open doors to other products or open doors to the same product with other groups or departments . So the same strategies which worked for pre-sales might not work in deployment.