Forum OpenACS Q&A: Re: Web-Based SMS Notifications Service Using OpenACS

Collapse
3: Re: Web-Based SMS Notifications Service Using OpenACS (response to 1)
Posted by Jun Yamog on 09/28/03 10:02 AM
Hi Jackson,

Simon Millward did something very similar while his company (OpenMSG) was alive.  But I guess this code may have gone away with OpenMSG too.

Try to dig the forums.  Simon did say what his new company is in his last post.

https://openacs.org/shared/community-member?user_id=8237

https://openacs.org/forums/message-view?message_id=105595

Collapse
4: Re: Web-Based SMS Notifications Service Using OpenACS (response to 3)
Posted by Peter Harper on 10/02/03 03:18 PM
Hi folks,

To clarify Jun's posting, we (OpenMSG) essentially built AolServer modules for:
- Queueing messages.
  - Multiple queues (multiple outbound/inbound)
  - Replication across an Aolserver cluster for failover.
    - This also implemented functionality where a clustered server could queue messages locally, but get serviced by a single server within the cluster. Useful if you have multiple servers but only one GSM modem, for instance.
- GSM Modem driver
  - Send and receieve functionality.
  - Multiple device support (i.e, supports more than one GSM modem at a time).  We've had up to eight hanging off the back of a PC.

And an OpenACS front end for:
- Managing the queues
- Assigning interface instances to process queues, starting/stopping queues etc.
- Some support for interfacing to existing Internet based SMS gateways.

We built quite a few applications that used this, but they were never fully integrated into the OpenACS.  The main reason for this was that we never had enough time to untangle the Notifications package 😉  Also, requiring the extra AolServer modules was always going to add additional complexity to the OpenACS installation.

I don't have access to the code right at this minute, but I'll have a dig around at some point over the next couple of weeks and can make it available somewhere if people want?

Cheers,