On 7/20/07, Daniel Sigurgeirsson <[EMAIL PROTECTED]> wrote: > A notification about the DTMF code must be passed upwards when detected, > and in Stipus version he uses the mpFlowGraph variable defined inside > MpResource - but that variable isn't necessarily initialized, and > MpRtpInputAudioConnection doesn't seem to know about the flow graph, hence > it probably won't be able to tell MprDecodeInBandDtmf about the flowgraph > etc. So the third question is: what is the preferred way to accomplish this? > As I understood then some rewrite of the messaging framework was in the > pipeline, but I simply don't remember what the status on that is. >
There is a resource notification framework in place, but requires resources to know about the flowgraph they are in. When notification needs to be made, they post a notification to the flowgraph. It is my understanding that users of sipXmediaLib will mostly just know about flowgraphs. With the new topology flowgraph one can choose the default flowgraph, with standard resources and layout, but can also customize it (note this is not ready for prime-time yet), so generally, users of sipXmediaLib do not know about the resources themselves. Therefore, notification needs to be passed through the flowgraph. It is my assumption that the flowgraph pointer in MpResource should always be initialized after a resource is connected into a flowgraph. If it is not, then this is a problem. Can someone point to a place where this is not the case? Thanks! -- Keith Kyzivat SIPez LLC. SIP VoIP, IM and Presence Consulting http://www.SIPez.com tel: +1 (617) 273-4000
_______________________________________________ sipxtapi-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/
