Re: JTAPI Object relation in PBX for trunk

Or perhaps it could be written as a service provider under the GJTAPI =20
framework (https://sourceforge.net/projects/gjtapi/) :^)


Richard

--=20
Richard Deadman
Deadman Consulting Inc.
mailto:[email protected]
613-220-2469
http://www.deadman.ca


Quoting Elliot Otchet <[email protected]>:

> You could think of it this way (if it helps).
>
> FXS =3D Terminal with 1 channel + a feature set
> ISDN =3D Terminal with 1 or more channels + a different feature set
> SIP =3D Terminal with 1 or more channels + a different feature set.
>
> Depending on the PBX you are writing a provider for will largely dictate h=
ow
> you will need to "manage" the terminals.  For instance, with the open sour=
ce
> 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 JTA=
PI
> 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 clea=
r.
> 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
>
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D
> To unsubscribe, send email to [email protected] and include in the bod=
y
> of the message "signoff JTAPI-INTEREST".  For general help, send email to
> [email protected] and include in the body of the message "help".
>
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D
> To unsubscribe, send email to [email protected] and include in the bod=
y
> of the message "signoff JTAPI-INTEREST".  For general help, send email to
> [email protected] and include in the body of the message "help".
>

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
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".