Call Flow Requirements
Recently I was involved in exercises determining the technical capabilities of some conceptual product offerings. During that exercise, one point became very apparant to me, the point being that bi-directional call flows do NOT have bi-direcitonal requirements.
Voice is a bi-directional form of communication, but the requirements to facilitate the voice session vary greatly if you are the calling or the called party. For instance, in a previous post, I blogged the Relevance Engine by Iotum. The products that could be created by this technology are nearly all exclusively in-bound from the prespective of the subscriber. Presence, status, etc are not applicable in the out-bound call scenarios. This may be an obvious point with regards to a 'Relevance Engine' discussion, but oftentimes is not appreciated when discussion FMC, toll-free, etc.
Requirements are different for A-to-B, from B-to-A. Let it be said, let it be so! ;)
Adam "voiploser" Uzelac
Voice is a bi-directional form of communication, but the requirements to facilitate the voice session vary greatly if you are the calling or the called party. For instance, in a previous post, I blogged the Relevance Engine by Iotum. The products that could be created by this technology are nearly all exclusively in-bound from the prespective of the subscriber. Presence, status, etc are not applicable in the out-bound call scenarios. This may be an obvious point with regards to a 'Relevance Engine' discussion, but oftentimes is not appreciated when discussion FMC, toll-free, etc.
Requirements are different for A-to-B, from B-to-A. Let it be said, let it be so! ;)
Adam "voiploser" Uzelac
-Subscribe to the voip musings of voiploser and friends-
-*voiploser frappr map*-

0 Comments:
Post a Comment
<< Home