Support for multiple numbers per user
| Project: | SMS Framework |
| Version: | 6.x-2.x-dev |
| Component: | SMS User |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
We'd like to be able to support multiple phone numbers per user, but it looks like this functionality is being stripped out of sms_user.module.
Some of our users have numbers in different countries, and others have their own phone, plus a work phone. Also, it's fairly common outside of the US for people to have several pre-paid SIM cards (i.e. several different cell numbers), and switch between them throughout the day to take advantage of different carriers' rates.
It looks like the current schema would still allow us to store multiple numbers per user, so mainly there would need to be some discussion on how to load multiple numbers into the $user object. Also it might be good to allow users to label their numbers and/or designate a primary number.
#1
Related issue, I noticed that sms_user delta is only halfway removed, it's still present in some modules like sms_sendtophone and sms_actions.
#2
Yes I'm willing to revisit this. The delta field was stripped out in sms_user.module but can be re-added if an good to handle multiple numbers is developed. This includes a user interface where we would be able to switch on support for multiple numbers.
#3
Hi Will, mfb, this issue keeps coming up in the vozmob workshops, so I can say for sure that at least in our use case it would be great to have this functionality. I'm guessing that it will be useful for ALL drupal projects that are seriously trying to integrate mobile posts. Tracking the issue and suggestions for UI here: http://dev.vozmob.net/issues/229
re: UI,
The secondary / tertiary / etc phones, we just store so that we can post anything that comes from them to the user's blog.
To change which phone is primary, ideally the user can just drag the one they want to the top of the list (same UI like positioning blocks in order on a page).
#4
+1 for this functionality