|
Voxalot Support Support for the Voxalot service. |
|
Thread Tools | Display Modes |
04-16-2007, 02:38 AM | #11 |
Junior Member
Join Date: Apr 2007
Posts: 1
Thanks: 0 Thanked 0 Times in 0 Posts |
I suppose we do not need to worry about roaming SMS, as roaming voice call charges are usually large enough to negate any benefit you'd get by callback.
As for the format: 1. We could use the from/caller ID to identify initiating mobile. We could then restrict username to a registered mobile number. 2. So keeping it simple, the actual SMS could just be: callback [from] [to] eg. callback 004412345678 004412345679 Would be good to be able to specify different source and destination numbers, instead of being limited to the mobile - although may be bit of a risk. could be reduced by adding [username] [pin] callback [from] [to] and matching the source mobile number with that pre-registered.. just an idea. |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
VoIP callback server (feature request) | rybshik | Voxalot Support | 11 | 12-17-2007 04:37 PM |
How many bytes will be used with a mobile callback? | hust | Voxalot Support | 0 | 04-16-2007 01:10 PM |
Feature Request (Web Callback 2.0) | sunray73 | Voxalot Support | 29 | 01-20-2007 01:59 AM |
web callback feature request | apoff | Voxalot Support | 1 | 12-27-2006 12:40 AM |
web callback - another feature request | stangri | Voxalot Support | 3 | 12-18-2006 07:59 AM |