ComSIPL has a "working" XMPP to SIP gateway server now

 

This new server "xmpp_s" allows XMPP (Jabber clients) to send messages to SIP clients.  Below is a screenshot of a Pidgin Jabber client logging on and registering to the xmpp_s gateway.

ComSIPL fix

I just released COMSIPL 0.8.8 that squashes the really annoying subscription update bug for client presence. I was really making the check more complicated than need be. The fix was reducing this if statement check to this:

  if (strcmp(watcher_dn[loop], watcher_dn[numOfWatchers])==0 && 
      strcmp(watching_dn[loop],watching_dn[numOfWatchers])==0 &&   
      strcmp(watcher_ip[loop], watcher_ip[numOfWatchers])==0 ){

The logic finds the previous subscription(s), but does not step on the current subscription that was just written, then marking the matching row values:

watcher's DN

watching DN

watcher's client ID

watcher's tag

watcher's IP
as "expired"

There is still a lot to do with Presence and expanding the functionality to fit more clients. Also want to clean up the admin interface a lot more.

Current status of ComSIPL

 ComSIPL now has three main executibles:

1) sipl    sipl is the SIP Listener, SIP Text and Call Manager, and the SIP Registrar

2) sipp   sipp is the SIP Presence Broker

3) admini admini is the administrative console

I will likely release ComSIPL 0.8.5 today. The biggest reason for not make this a 0.9.0 release is that some clients are not accepting the NOTIFY presence packet from sipp presence broker.

ComSIPL Progress

ComSIPL is progressing nicely.  Cisco device support and a TFTP: Trivial File Transfer Protocol is being developed.  TFTP is used to load different configurations into Cisco phones and gateways before they start the SIP communication.  

I would like at least a primitive, but functional TFTP server that will support Cisco's IP Communicator by version 9.0.  If I can get Cisco Jabber to work, that would be great also.

The admin interface continues to improve and get better.  It already has expanded into managing the TFTP and the SIP server.

Likely to continue support of Cisco products, a functional XMMP server will also have to be developed for presence.  

ComSIPL name change and release bump.

 ComSIPL, formally named VoIPSIPL, has reached the milestone of 0.7.0.  Lots of new features.

VoIPSIPL reaches 0.5

VoIPSIPL is not at release 0.5 and has muliple SIP phone clients that have been tested working for both Windows and Linux.

Registration and Call setup and placing are functioning.


Todo:

Admin interface
Route Patterns
SIP Trunks
ACD calling like Hunt Groups.