General
-
:) What should I be aware of to develop telephony applications. Can some one suggest me Thanx in advance
What kind of telephony device/ PABX are you developing for? Does it support TAPI, OAI or it's own format? Telephony is fun, but it can be hard work because each device tends to have its own quirks and ways of doing thngs. Michael Programming is great. First they pay you to introduce bugs into software. Then they pay you to remove them again.
-
:) What should I be aware of to develop telephony applications. Can some one suggest me Thanx in advance
Rule #1: There is more bullshit in telephony than any other field I've ever worked in. Rule #2: Telephony "standards" will make your hair stand on end. They tend to be very long and detailed, but with a caveat that you can claim compliance by following a tiny portion. Unfortunately, vendors aren't always forthcoming on what items they didn't bother with. That being said, you have to decide what problem you are solving. There is no such thing a "standard" telephony application. (God, I feel like I'm back at my previous company banging my head against the wall.) Joe
-
Rule #1: There is more bullshit in telephony than any other field I've ever worked in. Rule #2: Telephony "standards" will make your hair stand on end. They tend to be very long and detailed, but with a caveat that you can claim compliance by following a tiny portion. Unfortunately, vendors aren't always forthcoming on what items they didn't bother with. That being said, you have to decide what problem you are solving. There is no such thing a "standard" telephony application. (God, I feel like I'm back at my previous company banging my head against the wall.) Joe
Joe Woodbury wrote: Rule #2: Telephony "standards" will make your hair stand on end. They tend to be very long and detailed, but with a caveat that you can claim compliance by following a tiny portion. Unfortunately, vendors aren't always forthcoming on what items they didn't bother with. I'm glad it's not only me who has this problem. Sometimes you think they don't want to sell their phone systems. I think there would be a big market for CTI enabled applications, if only the PABX providers would get their fingers out. Michael Programming is great. First they pay you to introduce bugs into software. Then they pay you to remove them again.
-
Joe Woodbury wrote: Rule #2: Telephony "standards" will make your hair stand on end. They tend to be very long and detailed, but with a caveat that you can claim compliance by following a tiny portion. Unfortunately, vendors aren't always forthcoming on what items they didn't bother with. I'm glad it's not only me who has this problem. Sometimes you think they don't want to sell their phone systems. I think there would be a big market for CTI enabled applications, if only the PABX providers would get their fingers out. Michael Programming is great. First they pay you to introduce bugs into software. Then they pay you to remove them again.
I have had the same problems. The last year or so I have been programming TAPI stuff to different PBX'es. (that can be quite a challenge) - Anders Money talks, but all mine ever says is "Goodbye!"
-
:) What should I be aware of to develop telephony applications. Can some one suggest me Thanx in advance