Message sent to connect channels. There are two forms: one for incoming and one for outgoing channels.
Sent by incoming channel with its CallEndPoint in userData field. In response, recipient should connect its CallEndPoint to CallEndPoint given in userData.
- CallEndPoint of calling channel
- Driver of incoming channel
- channel id.
- module-specific caller name
- the number that was originally called
- the module and module-specific address that is expected (by means of the routing decision) to service the call
- the number of the caller
- the routing context selected by the current call
- direction of the message, module-wise (i.e. the module that emits the message will set it to 'outgoing' and the module receiving it will see it as 'incoming')
- the maximum pre-answer time for this call expressed in miliseconds. use this parameter to fail the call with a "noanswer" error that can be diverted later.
- the maximum duration for this call expressed in miliseconds. use this parameter for the prepaid applications.
- comma separated list of parameters that will be copied from this message to the chan.startup generated by the outgoing call leg. only channels derived from the Channel class implement this behaviour by default, external scripts have to copy the parameters themselves.
autoanswer, autoring, autoprogress
- Auto append Answered, Ringing and Progress _signalling_ messages to Accept after successfull routing
At least for Yate-0.9-CVS, driver has been renamed to module.
Sent to have some module make an outgoing call to destination given in target parameter from source given in callto.
- Number to call, requests routing
- Called protocol/address description, bypasses routing