> Somewhere in my mail archive I have a permission from Broadsoft or
> Cylantro to implement this - before they
> published it as a draft. They wanted Asterisk to include this
> functionality. After that, they published it openly
> as a draft, so there should be no problems.
It's probably also su
> Caveats: There's still a few issues to clear up, namely 'pedantic'
> dialog lookups need to be addressed, and there's an occasional timing
> issue between the rtp stuff, and dialog destruction. It happens about
> as often as asterisk crashes in trunk from a bad peer pointer, btw,
> both problems
Steve,
This is work that has been on my wishlist for a very long time. Thank
you!
I hope to get time to test drive this soon and have some ideas on how
to do it.
We need to discuss the dialog matching to se fix it once and for all,
there's a lot
of open issues I have there on my list from
2 jan 2008 kl. 19.57 skrev Raj Jain:
> Now it makes sense. I agree that you do need to extend SIP one way
> or another to acheive the correct key telephone system
> functionality, because RFC 4235 support alone is not sufficient for
> many use cases.
>
> I personally think this is very valu
2 jan 2008 kl. 15.58 skrev Raj Jain:
> Gene,
>
> I'm trying to better understand what you've developed. It seems that
> you're trying to share Asterisk SLA trunks w/ a different system
> (Broadsoft). Is the following a correct representation of your
> architecture?
>
>
> | SLA Trunks
>
