On May 31, 2007, at 3:54 PM, Mikael Bjerkeland wrote: > We also need to incorporate the functionality of the current > T38Gateway > application in our new dial application so we can do both fax and > voice > in the same app. This should be taken into consideration when > designing > a new Dial app. Perhaps this change is a milestone for the project?
As previously stated, the aim here is to clean up (and simplify) the argument list of the Dial() command. Steve Underwood assured me that there are no additional arguments required for T.38. Also, please note that it is by no means certain that the future Dial () command will be implemented as an application. As has been pointed out, the facility of originating calls is such a basic service, it ought to reside in the core of the server and it should be exposed as a proper C API. Now, once all the dialing is being done within the core, what is there left to be done within a dial application? The only thing that remains is the passing of arguments to the API residing in the core. Yet what is the point of having an application if it doesn't really do anything? I therefore believe that Dial() should be a built-in command whose only purpose should be to pass arguments to an API in the core. Some have pointed out that it may be desirable to be able to override Dial() with a custom application. Fair enough. However, that alone is still not a good reason to make the default command an application. It would make more sense to allow the overriding of built-in commands with custom applications. rgds benjk _______________________________________________ Callweaver-dev mailing list [email protected] http://lists.callweaver.org/mailman/listinfo/callweaver-dev
