Hello All, Please take my comment as a comment and not legal guidance as any legal guidance needs to come from your own legal counsel based on our terms of service. But, that clause is in our ToS as App Engine is not built to be or regulated as a telecommunication service and as such anyone who would fall under telecommunication regulations would likely not pass an audit. I know that sounded cryptic but I'm trying to be as precise as possible without telling you what to do :)
I hope that helps and I hope you'll understand if you want more clarification it might be hard to give, Greg D'Alesandre Senior Product Manager, Google App Engine On Mon, Jan 21, 2013 at 11:21 PM, Kalle Pokki <kallepo...@gmail.com> wrote: > Perhaps the legal wording is there only because telecommunications > operators may also be required to provide emergency calls, which probably > cannot be guaranteed with enough certainty with app engine sitting in the > middle of the system. And by providing access to PSTN you may be considered > as a telecommunications operator. > > I doubt google would try to stop the original poster from implementing the > call back button. > > > On Tuesday, January 22, 2013 6:54:59 AM UTC+2, Sologoub wrote: >> >> What's weird is the story on app engine blog seems to contradict this: >> http://googleappengine.**blogspot.com/2012/12/** >> developer-insights-mobile-**voucher-sales.html<http://googleappengine.blogspot.com/2012/12/developer-insights-mobile-voucher-sales.html> >> >> "URL Fetch API to link to third-party API’s such as sending SMS’s and >> integration to mobile networks for airtime voucher purchase" >> >> This is exactly how one would work with Twilio/Troop/Plivo in order to >> send SMS or make calls. I've been focusing on App Engine without realizing >> such use cases are not welcome, but the REST APIs seem like such a good fit >> here. >> >> Hope someone from GAE team can clarify. >> >> On Sunday, January 20, 2013 11:51:11 PM UTC-8, Marc Heinken wrote: >> > In earlier (around 2009) versions of the ToS that section reads like >> this: >> > >> > >> > You agree not to use the XMPP API to operate or to enable any >> telecommunications service or in connection with any applications that >> allow users to place calls to or receive calls from any public switched >> telephone network. >> > >> > >> > That seems reasonable to me. After all, looking at the heavy usage >> restrictions of the channel API, realtime-communication isn't the >> infrastructure's biggest forte and running a telephony system on top of >> XMPP could be considered misuse. >> > >> > >> > I don't think Google Voice is that big a profit center to justify such >> restrictions. Maybe it's some kind of regulation I don't know about. >> > >> > >> > Does that section really disallow ANY type of interaction of an >> appengine hosted site with ANY other web based application that connects to >> the PSTN even if that interaction is only part of the client side >> HTML/Javascript code and does NOT happen inside appengine? >> > If so, would that include interacting with Google Voice? How about >> embedding a skype call button or a SIP-URL in my HTML? >> > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/google-appengine/-/l6CfaNFanIYJ. > > To post to this group, send email to google-appengine@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
