Why Reinvent Wheels? Asterisk is currently the only open source PBX capable of addressing multiple media, PSTN, SS7, SIP, IAX2 etc...
Why not choose to use one of the available channels to control asterisk rather than invent a new stack?
You could choose the manager API, xmlrpc, plain text extension files, SQL etc...
OK maybe I'm asterisk biased put surely there is more to telephony than just a SIP stack?
Asterisk could be a good framework to build upon. It is currently missing a "good" UI and integration with other services. Drupal could make a very good front-end to build a more complete system upon. I think I would like to see some analysis/justification for starting over. As bailsbails mentions, there are a number of areas of Asterisk integration that could fit into Drupal
On the other hand, if what is meant is the softphone end of things, Asterisk doesn't ship that part. A good softphone that is open and portable might be a great addition to Drupal. It should support SIP and IAX.
The post in the Asterisk group was more clear than what was in the charter here.
If I am now parsing correctly, this effort would build APIs that could communicate with Asterisk and other PBXs and provide the list of services mentioned in the charter rather than implementing a new PBX mechanism from the ground up. If this is correct, perhaps a better phrasing would be "Our goal is to create a voice-over-internet-protocol (VoIP) platform that interoperates with existing VOIP PBX implementations toprovide ..." The charter needs to be tightened up a bit but this could be an interesting project.
Sorry for the misleading statement in the description of the Voip Drupal group.
Our goal is to build a platform connecting Drupal with existing VoIP servers (Asterisk, FreeSwitch and others), making it easier for developers to create web services that a) make use of internet telephony capabilities (voice blasts, conference calls, voicemail groups, etc.), and b) are accessible via regular touchtone phones.
Since November 2009, we've been meeting with volunteers on a weekly basis. We came up with a new architecture for the system and have just started coding. Now we need all the volunteers that we can get, especially if you already have experience with VoIP.
Let me know if you have any questions and/or would be interested in joining our team, ok?
Comments
Why Reinvent Wheels?
Why Reinvent Wheels? Asterisk is currently the only open source PBX capable of addressing multiple media, PSTN, SS7, SIP, IAX2 etc...
Why not choose to use one of the available channels to control asterisk rather than invent a new stack?
You could choose the manager API, xmlrpc, plain text extension files, SQL etc...
OK maybe I'm asterisk biased put surely there is more to telephony than just a SIP stack?
I think I'm missing something
I think I'm missing something as well.
Asterisk could be a good framework to build upon. It is currently missing a "good" UI and integration with other services. Drupal could make a very good front-end to build a more complete system upon. I think I would like to see some analysis/justification for starting over. As bailsbails mentions, there are a number of areas of Asterisk integration that could fit into Drupal
On the other hand, if what is meant is the softphone end of things, Asterisk doesn't ship that part. A good softphone that is open and portable might be a great addition to Drupal. It should support SIP and IAX.
Can someone explain what I'm missing?
The post in the Asterisk
The post in the Asterisk group was more clear than what was in the charter here.
If I am now parsing correctly, this effort would build APIs that could communicate with Asterisk and other PBXs and provide the list of services mentioned in the charter rather than implementing a new PBX mechanism from the ground up. If this is correct, perhaps a better phrasing would be "Our goal is to create a voice-over-internet-protocol (VoIP) platform that interoperates with existing VOIP PBX implementations toprovide ..." The charter needs to be tightened up a bit but this could be an interesting project.
Yes, you are right! :)
Hello dougm and all,
Sorry for the misleading statement in the description of the Voip Drupal group.
Our goal is to build a platform connecting Drupal with existing VoIP servers (Asterisk, FreeSwitch and others), making it easier for developers to create web services that a) make use of internet telephony capabilities (voice blasts, conference calls, voicemail groups, etc.), and b) are accessible via regular touchtone phones.
An early description of these ideas might be found in here: http://groups.drupal.org/node/34210/
Since November 2009, we've been meeting with volunteers on a weekly basis. We came up with a new architecture for the system and have just started coding. Now we need all the volunteers that we can get, especially if you already have experience with VoIP.
Let me know if you have any questions and/or would be interested in joining our team, ok?
Leo