VoIP Phones - sipml5: Difference between revisions
mNo edit summary |
No edit summary |
||
| (4 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
<indicator name="VoIPConfiguring">[[File:menu-voip.svg|link=:Category:VoIP Phones|30px|Back up to the VoIP Configuring page]]</indicator> |
|||
==Notes== |
==Notes== |
||
2023-03-10: This HMTL5 SIP demo no longer appears to function. It sends WebSockets requests to ns313841.ovh.net which no longer appears to be active. |
|||
OLDER NOTES:<br /> |
|||
This is a pure HTML5 and Javascript SIP client (scary!), see: [http://sipml5.org/ sipml5.org] |
This is a pure HTML5 and Javascript SIP client (scary!), see: [http://sipml5.org/ sipml5.org] |
||
| Line 7: | Line 10: | ||
==Further Notes Whilst Getting This Working== |
==Further Notes Whilst Getting This Working== |
||
When using the sipml5 demo, we |
When using the sipml5 demo, we the client registering not from the browser's IP, but a third party, 188.165.231.30 i.e.: |
||
1:16:25 Z.Voiceless 12:16:25 188.165.231.30 IM-client/OMA1.0 sipML5-v1.2013.08.10B |
1:16:25 Z.Voiceless 12:16:25 188.165.231.30 IM-client/OMA1.0 sipML5-v1.2013.08.10B |
||
This is a little concerning, as means we've given our SIP password over to someone else :-) |
This is a little concerning, as means we've given our SIP password over to someone else :-) This will be down to the web server needing to proxy the SIP in some when to bypass XSS (Cross-site scripting) restrictions in Javascript. |
||
This needs more testing... |
|||
==Configuration== |
==Configuration== |
||
| Line 42: | Line 46: | ||
[[Category:VoIP]][[Category:Configuring]] |
|||
[[Category:VoIP Phones|sipml5]] |
|||
Latest revision as of 22:53, 10 March 2023
Notes
2023-03-10: This HMTL5 SIP demo no longer appears to function. It sends WebSockets requests to ns313841.ovh.net which no longer appears to be active.
OLDER NOTES:
This is a pure HTML5 and Javascript SIP client (scary!), see: sipml5.org
We have so far managed to register OK, but unable to place a call. A traffic capture on the client shows various STUN messages, but then no INVITES are sent to the call server. At the moment we're a bit stuck, but happy for others to try it and to let us know how it goes.
Further Notes Whilst Getting This Working
When using the sipml5 demo, we the client registering not from the browser's IP, but a third party, 188.165.231.30 i.e.:
1:16:25 Z.Voiceless 12:16:25 188.165.231.30 IM-client/OMA1.0 sipML5-v1.2013.08.10B
This is a little concerning, as means we've given our SIP password over to someone else :-) This will be down to the web server needing to proxy the SIP in some when to bypass XSS (Cross-site scripting) restrictions in Javascript.
This needs more testing...
Configuration
| sipml5 VoIP Client Settings | |
|---|---|
| Setting | Value |
| Display Name: | Your name |
| Private Identity | Your number, inc +44 |
| Public Identity | sip:YOURNUMBER@voiceless.aa.net.uk |
| Password | Your SIP Password |
| Realm | voiceless.aa.net.uk |
