On Wed, May 13, 2009 at 2:30 AM, Mikael Aleksander Bjerkeland
<mikael@bjerkeland.com> wrote:
I've been looking for something like this as well, to make the outbound
event socket behave more like FastAGI and handle the logic.
El mié, 13-05-2009 a las 00:12 -0700, ibrahim tunali escribió:
> "nopark" option would be great. FS sends "100 trying" while opening socket
> and leg A waits other responses from socket. If I send pre-answer command it
> reply via 183 early media and activate RTP path.
>
> Regards,
> ibrahim
>
>
> David Knell wrote:
> >
> > Gotcha - but in the case where the call hasn't yet got to a point where
> > there's a 183 been sent then I guess this wouldn't apply - there
> > shouldn't be any audio from the far end at this point, nor would the far
> > end be expecting any.
> >
> > I'd suggest (and would volunteer to knock together a patch) adding a
> > 'nopark' option to the socket command, which doesn't park the call - nor
> > would it change existing behaviour. Obviously, in a situation like that
> > outlined by Ibrahim where the socket app handles all aspects of the
> > call, then it'll need to make sure that it signals ringing, answer or
> > whatever to make the call state flow work.
> >
> > --Dave
> >
> >
>