Conferencista: Gastón Draque "El desarrollo de aplicaciones para teléfonos de escritorio que se ejecutan en el teléfono en base a eventos internos o externos sin la necesidad de un servidor en el medio. Descripción de la experiencia en el proceso de desarrollo, desafíos y soluciones." ElastixWorld Santiago de Chile Octubre 2014

2. P H O N E A P P S . . .
F O R T H E D E S K – P H O N E

3. @gdraque
VoIP Integrator
 wife(1), kids(2), bills(*)
I work
 Asterisk
100% bIOdegradable

4. Asterisk?
ALIENS!

5. @1999 Mark Spencer | @markster
OS Telephony Toolkit
+1M Production systems
+170 Countries
Dual License (GPLv2,OEM)
Dual Support (Community/ )
: Aliens?

6. : OSs?

7. TDM PBX
IP PBX
Hybrid PBX
VoIP Gateway
Media App Server :)
: Uses?

8. Media Application Server

9. Privately held
@1999 by Mark Spencer
www.digium.com
Privately held
@1999 by E+J Landivar
www.palosanto.com

10. phone application engine
phone module for Asterisk
, DPMA AppEngine,

11. DPMA
+
[ ]
App
Engin
e
DPMA
, DPMA AppEngine,

12. [Fully supported]
[Fully supported]
[Fully supported]
[-digiumphones branch]
[Certified Only]
[NOT supported]
[NOT supported]
[NOT supported]
Asterisk 13 [LTS ]
Asterisk 12 [Standard]
Asterisk 11 [LTS +Certified]
Asterisk 10 [Standard]
Asterisk 1.8 [LTS +Certified]
Asterisk 1.6 [Standard][EOL]
Asterisk 1.4 [LTS] [EOL]
Asterisk 1.2 [EOL]
Versiones & DPMA
[Standard]
[LTS]
[Certified]

14. Digium Phones API

15. What? How?

16. Digium github

17. Remote Screen
Web app management
Access Logs via Web

20. /

21. /

22. /

23. /

24. /
Logging from application
Ad-hoc
Granular
No filtering required
PBX logging not required

25. phones en el call-center
DPMA
Provisioning
Hotdesking
Queues
Extended Queues
Visual VM

26. phones en el call-center
DPMA
Provisioning
Hotdesking
Queues
Extended Queues
Visual VM
?
?
?
?
?

27. AMI
AMI Events
AMI Actions
Custom
Daemon
Request
JSONRest API
Request
Publish
Architecture

28. MWI via SIP
No Access to the SIP layer
No Visual Voicemail

29. MWI via SIP
No Access to the SIP layer
No Visual Voicemail
digium.phone.mwi :
1. SIP NOTIFY
2. Phone system triggers mwi Event
3. Application listener executes call to middleware
4. Middleware send JSON with updated data
5. Application stores information locally (non-volatile)

30. Store x pages locally (zillion-vms-user)
Run searches remotely
Implement VM actions (playback, delete, forward,
move) via the Rest API middleware component

31. No MAC special option for SIP UA
non-retrievable MAC when != LAN
No Access to SIP Layer
/

32. No MAC special option for SIP UA
non-retrievable MAC when != LAN
No Access to SIP Layer >> Use digium.app.config.xml
When == LAN , then use ucarp and single dummy sip peer
When != LAN, then use MAC based sip peer to dummy context
Hotdesking app process:
1. UI Extended libraries: login form [ user/pin]
2. NetRequest class: phone sends request to Rest API
3. Middleware server checks values
1. Correct: Send OK message, phone displays success and waits.
2. Middleware rebuilds phone prov.file and sends SIP NOTICY digium-check-cfg
/

33. /

34. No Queues generic data
No Agent data
No Queue Stats

35. No Queues generic data
No Agent data
No Queue Stats
Use F and B applications. F for status and B for actions
Link F&B via custom events and nvshared memory
B: Use polling on middleware server to update status
B: Use event driven actions to pause, unpause, login and logout
agent
B: Use middleware server to get queue stats from Asterisk
B: User middleware server to get queue stats from 3rd Party Call-
centre

36. No Queues generic data
No Agent data
No Queue Stats
Main API components to get advantage from:
digium.app.config.xml
digium.app.exitAfterBackground
digium.event.*
digium.readFile

37. The future ahead

38. The future ahead