Max: That is certainly one way to do it. However, that would mean carrying more variables (and space) in the opbx_channels struct whether the variables were necessary or not.
The opbx_channel struct already references tech and tech_pvt. With the appropriate definition of the respective structs all data elements are already available to "chan". My approach would simply cause minor changes in each in the channel driver source and a simple addition to the channel.h of a "partial" struct that would be common to all channel pvt structs. If I missed something in your description.. please let me know. Are you suggesting that these "channel variables" already exist and that I missed them? J Max CtRiX wrote: > Jac Barben ha scritto: > >> I'd like to propose that at least some elements of the channel >> specific pvt data be normalized and required at the top of each >> structure such that they can be reached more conveniently via 3rd >> party modules. Off-hand references to incoming IP, RTP ports and >> lock variables would be good candidates. >> >> Any thoughts? > > Use channel variables. > > Set them in the channel and retrieve them in the application. > > This is the less intrusive and most compatible way to go. > > Max > _______________________________________________ Callweaver-dev mailing list [email protected] http://lists.callweaver.org/mailman/listinfo/callweaver-dev
