I've been wanting to have a discussion for a while in reference to Messaging as it's functions are here and will surely be evolving over time.
Starting with how we contact users:
Since a devices route is invite format we need the full and lengthy user_ ID of our contact. Alt methods are npan lpan e164. During my playtime I realized that an alias would be ideal as copy/paste works for web based apps but coming into handset and mobile messaging it is cumbersome. In addition users only know the extensions of their Dir users based on extension, assuming they're using some user portal. So the point is we need to pull contacts easily or have a method to contact people easier. Security is a main concern also.
During some tests, I can push a Presence ID through to certain apps: "nurango" <use...@nurango.tld> "Message from nurango".
Depending on the App, it would make the most sense to enforce auth on the domain level for security reasons, but then what if I want to receive messages from outside of my organization?
"Message from: "Luis" <lu...@2600hz.com> "Hello there".
The concern of course with aliases is that I can send a message to my accounting department for example: Message from "Bob" - "Hey I need the company credit card number to buy that thing!" .. When really the SIP URI is "Bob" <an...@ima.pirate.tld> , most users would never notice this. Arguably this could or should be done many ways at the App level but with the amount of open source tools out there it isn't as flexible a solution.
Ideas: (assuming im not missing something)
Could we just use the Presence ID of the user? This would omit devices without user accounts, but would be easier to input someones extension opposed to username. The masquerade security issue still stands especially if the app accepts anon SIP calls, but it will speed things up to start..
Please somebody correct me if I'm wrong, the contact methods look like they can be changed by manipulating the Global FS chat plan in crossbar?
I would be curious to know if the 2600hz team has noodled around this topic?
Thanks,
Matt