If you are looking to use this as an endpoint then you must treat it as such in your dialplan. You are trying to use it as an application. To use it as an endpoint you treat it like sofia or skype and use the bridge command or something along those lines and then your destination is "<endpoint>/<user/account indentifier>" where endpoint is the name that you give your endpoint.

Regards,
   Kevin Green


On Sun, Oct 11, 2009 at 2:40 PM, Francisco Scaramanga <scaram@hotmail.de> wrote:
 
I wrote a new module and defined an endpoint interface in the following way:
 
 
 *module_interface = switch_loadable_module_create_module_interface(pool, modname);
 
 mod_skel_endpoint_interface = switch_loadable_module_create_interface(*module_interface, SWITCH_ENDPOINT_INTERFACE);
mod_skel_endpoint_interface->interface_name = "mod_skel_interface";
mod_skel_endpoint_interface->io_routines = &mod_skel_io_routines;
mod_skel_endpoint_interface->state_handler = &mod_skel_event_handlers;
 
Futhermore I implemented the io_routines and state_handler of the interface
 
The problem is that my call back functions are never called, for instance
 
static switch_status_t channel_on_init(switch_core_session_t *session)
{
...
}
 
Is there something more I must do except to define and implement the endpoint interface?
 
My dialplan is:
 
<extension name="test">
        <condition field="destination_number" expression="54505">
             <action application="mymod_skel" data=""/>
        </condition>
</extension>
Schneller, einfacher und noch mehr Fun – mit Windows 7

_______________________________________________
FreeSWITCH-dev mailing list
FreeSWITCH-dev@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev
http://www.freeswitch.org