Hi,
> Very interesting scenario. So, for your example above, your application
> has loaded sipXtapi.dll, and has called sipxInitialize only once, and has
> called sipxLineAdd multiple times (once for each user)? Correct? If this
> is the case, I may not be able to provide much help.
[Not Windows, but the idea is the same.] Yes that is correct. By diabling
the "focus" concept of sipXtapi, there are now simultaneous calls flowing
through sipXtapi. As we're using our own flow graph (no speaker of mic,
just two branches FromNet -> Dejitter -> ToATM and FromATM -> ToNet) we
have a cheap gateway.
> I've never tried something like this before, however, (and I apologize if
> I am telling you something you already know) - our unit tests (
> sipXtapiTest.exe) provide examples of placing and receiving calls on
> different ports within the same process. The unit tests invoke
> sipxInitialize mutliple times, each time with a different port value that
> the user agent instance binds to.
That's what we're trying right now: one instance for incoming calls (bound
to the default port 5060), and once instance for outgoing calls (i.e. those
coming from the ATM backend). This way ATM can call ATM: the second sipX
instance will connect the first.
Our main concern with this is the additional number of threads and
processor/memory resources required, as everything is running on a 50Mhz
embedded board, and should support upto 6 simultaneous calls :-(
Herman
-----------------------------------------------------------------
Herman Kuiper - m: [EMAIL PROTECTED] - w: http://www.frontier.nl
Beech Ave 162 - 1119 PS Schiphol-Rijk - t/f: 020-6589034/6142816
_______________________________________________
sipxtapi-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/
