Re: JTAPI Object relation in PBX for trunk

You could think of it this way (if it helps).

FXS = Terminal with 1 channel + a feature set
ISDN = Terminal with 1 or more channels + a different feature set
SIP = Terminal with 1 or more channels + a different feature set.

Depending on the PBX you are writing a provider for will largely dictate how
you will need to "manage" the terminals.  For instance, with the open source
PBX Asterisk, they are all equivalents in that they are all discrete
channels (or Terminal identifiers).  In this model, channels - like
Terminals in JTAPI make and receive calls.  We don't need to worry so much
as to how they do this, but more so about what to do with the calls being
placed or received.  That is largely handled by the PBX dialplan (or a JTAPI
application :-)).

I hope this helps.  I'd be interested in understanding which PBX you're
writing a JTAPI implementation for.  Maybe we could turn it into an open
source project.

Regards,

Elliot



-----Original Message-----
From: Discussion list for Java Telephony API
[mailto:[email protected]] On Behalf Of Prakash Kamliya
Sent: Wednesday, January 09, 2008 6:11 AM
To: [email protected]
Subject: [JTAPI] JTAPI Object relation in PBX for trunk

Hi List,

I just gone through the JTAPI specification. Still the picture is not clear.
I wan 
to develop JTAPI interface for PBX system. I can say that FXS is Terminal
but 
what about the trunk present in the PBX like, what should I relate the SIP 
trunk or ISDN trunk ??

Thanks in advance. 

Prakash 

===========================================================================
To unsubscribe, send email to [email protected] and include in the body
of the message "signoff JTAPI-INTEREST".  For general help, send email to
[email protected] and include in the body of the message "help".

===========================================================================
To unsubscribe, send email to [email protected] and include in the body
of the message "signoff JTAPI-INTEREST".  For general help, send email to
[email protected] and include in the body of the message "help".