[jitsi-dev] Development direction questions


#1

Development Team and members,

I am looking to create some enhancements/plugins to Jitsi for SIP, XMPP and SFDC.

First, looking to implement Broadsoft's Shared Call Appearances from their Release 13.0 Version 1 doc to work with Kamailio's SCA module.
Question(s) on this one is...would it be better to implement it directly into the SIP protocol or make it a plugin? I am looking at the docs and don't see any examples of extending a protocol via plugins, just a NEW protocol. I do see the dtmf, xcap and such that is directly implemented to the protocol. What do you suggest? This plugin will also allow for automatic presence changes to XMPP (Openfire with Asterisk-IM) to allow presence changes in app_queue (That's my vision).

The second enhancement is a plugin to Jitsi for SFDC. First, is there one? I would use Header like P-SFDC-CASENUM to pass it via the SIP protocol (Invite most likely) and then it would pass that to the SFDC agent plugin to screen pop (lack of a better term) the case. Other P headers could be used for more info, I am just in a concept stage at the moment. I would assume this would be a plugin but a listener would be used for certain headers.

Your options, suggestions, comments or "Your total off base".

Thanks,

Kevin Adams
https://github.com/TheGrandWazoo
kevin.adams@ksatechnologies.com


#2

Hey Kevin,

Development Team and members,

I am looking to create some enhancements/plugins to Jitsi for SIP,
XMPP and SFDC.

That's the spirit!

First, looking to implement Broadsoft's Shared Call Appearances from
their Release 13.0 Version 1 doc to work with Kamailio's SCA module.
Question(s) on this one is...would it be better to implement it
directly into the SIP protocol or make it a plugin?

Depends on exactly what you want to do. I am not aware of exactly how that SCA module works. A plugin would be easier to maintain, a patch would be easier to write.

I am looking at
the docs and don't see any examples of extending a protocol via
plugins, just a NEW protocol.

Yes. Extending it through a plugin would most likely require you to also write the code that would make the protocol use that plugin.

I maintain my statement from above though.

I do see the dtmf, xcap and such that
is directly implemented to the protocol. What do you suggest? This
plugin will also allow for automatic presence changes to XMPP
(Openfire with Asterisk-IM) to allow presence changes in app_queue
(That's my vision).

Hmmm ... this sounds like something that should reside on the server side.

Or, you could implement the state changes within the client.

The second enhancement is a plugin to Jitsi for SFDC. First, is
there one?

Not sure what SFDC is.

Emil

ยทยทยท

On 09.12.13, 14:35, Kevin S. Adams wrote:

I would use Header like P-SFDC-CASENUM to pass it via the
SIP protocol (Invite most likely) and then it would pass that to the
SFDC agent plugin to screen pop (lack of a better term) the case.
Other P headers could be used for more info, I am just in a concept
stage at the moment. I would assume this would be a plugin but a
listener would be used for certain headers.

Your options, suggestions, comments or "Your total off base".

Thanks,

Kevin Adams https://github.com/TheGrandWazoo
kevin.adams@ksatechnologies.com

_______________________________________________ dev mailing list
dev@jitsi.org Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

--
https://jitsi.org