Use freeswitch.

On 11 September 2010 10:58, Jonas Gauffin jonas.gauffin@gmail.com wrote:

I have to build one, not use one. Hence the question..

Den 2010 9 11 10:27 skrev "RobertT" siniypin@gmail.com:

"Build a PBX" is not a very good term in order to tell you wether you can use a library or not.
Wether you can use a library or not depends much on your requirements for the PBX system.

It can without a doubt be used to implement a PBX system, since it is a sip-stack.
I won't even ask you why you need to build one, since you already have that set.
I am not aware of any PBX using pjsip, if anyone knows please tell.

Some interesting links might be:
http://trac.pjsip.org/repos/wiki/FAQ#high-perf
http://www.pjsip.org/high-performance-sip.htm
http://www.pjsip.org/docs.htm

Best regards,
Even André

On 11. sep. 2010, at 11.51, Jonas Gauffin wrote:

i agree!
RobertT a écrit :

__________ Information from ESET NOD32 Antivirus, version of virus signature database 5283 (20100716) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

i see only softphone using pjsip, like 3CX phone system in android, is
using pjmedia (100% sure

eaf@oyatel.no a écrit :

__________ Information from ESET NOD32 Antivirus, version of virus signature database 5283 (20100716) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

I think you should narrow down your question to specific components and
ask the question how to achive each component using the different
modules to pjproject exposes.  IMO the following components are a must
in a workable PBX framework.  You might get a better answer if you will
be more specific.

1. Registrar - (Yes)
2. SIP Proxy router (or B2BUA) - (Yes)
3. Media Server (Auto-attendant, MoH, Voicemail)  - (Yes) but i've seen
   post in this list that pjmedia is not wired and therefore would not
   perform well in a multi-channel environmnet
4. SIP Trunk compatibility layer (ISTP interoperability) - (Yes)
5. RTP Proxy for NAT traversal - (Yes)
6. Payload Transcoders - (Yes)
7. Device provisioning - (No)
8. ISDN interface (if you plan to support POTS in the PBX)  - (No)

Joegen

On Saturday, 11 September, 2010 02:58 PM, Jonas Gauffin wrote:

Joegen, I'm not clear with no 3?

Best regards,
 Benny

On Sun, Sep 12, 2010 at 12:22 PM, Joegen E. Baclor
joegen.baclor@gmail.com wrote:

Hey Benny,

Long time!  How are you doing?  I've seen post in the past that since
the media IO is performed using a single thread, that scaling it to a
vast number of channels may affect performance.  I'm just a noob
spectator in this list and in no way familiar with the code in this
regard so feel free to humiliate me publicly :-)

Joegen

On Monday, 13 September, 2010 01:09 PM, Benny Prijono wrote:

We're good, thanks! I'm still looking forward to seeing you again in
one of the next SIPits.

Right, that one. Actually, most pjmedia components are thread
agnostic, hence it can accommodate any threading models that the
designer chooses to achieve high performance. But, there is an
exception to this, i.e. the conference bridge, which need to work in
one thread, which makes sense since it needs to "synchronize" the
timing of all ports connected to it. Having said that, nothing
prevents you from creating multiple conference bridges and make each
of them use different thread.

Also when talking about pjmedia performance in this list, often we're
talking about PJSUA-LIB's media performance, which is a different
thing. The PJSUA-LIB's media performance has been explained in the
FAQ.

Best regards,
 Benny

On Mon, Sep 13, 2010 at 12:23 PM, Joegen E. Baclor
joegen.baclor@gmail.com wrote: