SAP PoSDM technical guide

_____________________________________________________________________________________

_____________________________________________________________________________________

Meeting the Current Credit Crunch Head On... 5 ways it can be done

_____________________________________________________________________________________

_____________________________________________________________________________________

Use your Pocket PC PDA as a VOIP phone

Step by step guide for setting up VOIP softphone on the PocketPC phone
Prerequisites:
i. PocketPC phone 2003 and above
ii. WiFi internet
iii. VOIP softphone a/c

Steps:
1. Start wireless on PocketPC phone
2. Open internet explorer
3. download the softphone from :
http://www.sjphone.org/softphone/SJphone-PPC2003-303c.exe





4. On the PocketPC, goto
a. Start -> Programs -> SJphone
b. Press Menu -> Options
c. Go to tab “Profiles”
d. Press “New” button
e. Enter following values in the fields on the screen
f. “General” Tab
 Name = vonage
 Type = SIPProxy
g. “SIPProxy” tab
 Proxy domain = 216.115.20.41
 Port = 5061
 User domain = sphone.vopr.vonage.net
 Register with proxy = X (check)
 Proxy is strict outbound = blank
 Leave the rest of the values as default and save
2. Set the following values for login:
 Account name = VOIP softphone #
 Password = password as received for the softphone
3. Press “Menu -> Services -> select the “vonage” service created

When successfully logged in, the screen will display the message “SIP : registered as …”
Dial the # and enjoy the free calls!

SOA - is it about technology, personality or reality?

Lunch discussion with a group of wizards aka enterprise architects lead to this blog.. how do businesses view SOA?

Is this a technology buzzword, a way for personalities to behave or business reality?



Business gurus define businesses as a product of people, process and technology (maybe not in that order).

In that context, as a change agent where does SOA fit in ?

Depends, I guess.
For most businesses, it appears like its a new 3 letter buzzword from IT vendors to sell them same technology in a new way.
Some of the organizations have taken steps to embrace it and have defined groups / sponsors in their domains , who will champion it and drive it thru the IT foodchain.
Probably, this is most common pattern in SOA implementations, though unfortunately, it is like drinking coolade from IT vendors fountain, as they would like us to drink it.

Services should be more in the business processes and how they are used, rather than what ERP or middleware or technology enables it.
Very few organizations ( that I know of ) who are embracing it as a change in the way they do their day to day business processes.
Why should they?
Well, the most compelling way to emphasize this is:
The businesses today are continously looking at their business processes, ripping them to pieces and sending them to "units" who can best do them, and then, bringing it all together, again.

In these business value chains, the organizations and partners (vendors / customers / employees), must quickly figure out what is the role which they can play, effectively and reliably. Also, they must define clearly, how others can use these roles flexibly.
These 2 steps to me, provides a measure of how services oriented an organization will be and probably, how far they will go.

With that approach, technology probably is the least of issues (tough though it maybe). I believe it should be driven into business processes, with key people as the agents for the change.