Topic: SAIL 366 - New DPS feature

[SARK devs]

Hello all,

SAIL 366 has a brand new feature which we'd like you to test.  It's called Dynamic Proxy Server (DPS).  Here's what it does;

If a phone is connected and registered to SARK/SAIL then you can log directly in to it from the SARK/SAIL extensions panel in server-manager.  Simply click on the status icon for the phone (that's the "connected" icon) and the phone browser app will fire up in the server-manager window.  

We've been using this feature for a few weeks and have found it hugely valuable when remotely supporting medium to large customers.  It means that a support technician can be logged on to the server manager (using https) from a remote support location and he/she can then use DPS to log in to any individual phone on the customer's site to customize/restart/diagnose it.  We aren't aware of any other Asterisk workbench which currently supports this idea of secure remote log-in to individual phones.

The Proxy is truly dynamic and uses a recursive mod_rewrite stanza within apache.  It is pure voodoo and we're not sure we fully understand it ourselves! We'd appreciate it if there are any mod_rewrite experts out there who'd like to look it over and give their advice/guidance as to whether it can be improved.

The following phone types are currently known to work;

All Snoms, all Aastras, all Grandstreams.  All Sipura/Linksys units (including ATA's) work but currently, cannot be updated (i.e. the update screens don't work properly through the proxy).  We have also done limited testing on Mitel 52xx units and they appear to have the same update issue as the Linksys/Sipura units.  

We have only tested remotely on systems running in server-gateway mode.  Server-only appears to work fine locally.

SAIL -366 is available from here...

ftp://81.149.154.14/Pre-Releases/

...and you install it in the normal way.

There's a few screenshots of it working here...

ftp://81.149.154.14/shots

Let us know how you get on with this.

Kind Regards

Selintra

[psoren]

Hi,

If i try to access my SPA2K or SPA3K i get this: (from the server manager)

Not Found

The requested URL /192.168.0.10/ was not found on this server.

If i look at your screenshots, i can also see that you have more panel options than me. Is there any reconfigure commands that need to be run?

Per

[stephen noble]

try
/etc/e-smith/events/actions/navigation-conf 2>/dev/null

[edit]
err, actually I'm also missing the bottom two

operator panel
cdr database

[psoren]

try
/etc/e-smith/events/actions/navigation-conf 2>/dev/null

Still no good, actually all the "state" links seems broken, also the one for my X-Lite on one of the PC's

Per

[SARK devs]

err, actually I'm also missing the bottom two

You're ahead of us stephen - the "loop" proxying to FOP and STAT aren't quite ready yet! - you will have them in 367/368.  The shots were taken from a bleeding edge server which has a bit more on it than vanilla 366.


Per

You need to run console save - it looks like your httpd.conf has not been refreshed with the rewrite engine stuff.

signal-event console-save.

You shouldn't need to run navigation because there are no new nav panels in this release (despite the misleading screen shot - see above).

Kind Regards

Jeff

[psoren]

Per

You need to run console save - it looks like your httpd.conf has not been refreshed with the rewrite engine stuff.

signal-event console-save.

Didn't help....

Per

[psoren]

You need to run console save - it looks like your httpd.conf has not been refreshed with the rewrite engine stuff.

signal-event console-save.

DUH!! That actually broke something in the webserver.....

Some of the manager panels and webmail just died giving this response:

Not Found

The requested URL /MARKERMARKERMARKERMARKERMARKERMARKERMARKERMARKERMARKERMARKERMARKERMARKERMARKERMARKERMARKERMARKERMARKERMARKERMARKERMARKERwebmail/ was not found on this server.

I uninstalled Sail 366, did console save and it worked again. I reinstalled 354 and still good.

Per

[SARK devs]

Hi Per

The response you got was as a result of using a non-standard or mis-spelled manager uri.  The fix depends upon you always calling the server-manager with

https://your.domain.name/server-manager

Any other value after the / will give the recursive "markermarkermarker" uri.  Do you have other non-standard panels running under the server-manager?

I hope I explained that properly.

Kind Regards

Jeff

[hervep]

Hi Jeff,

Without being 100% sure at this stage, I think 'DPS' to break other things. I did not had the time to look into deep detail until now, but as far as I can see, contribs as 'phpmyadmin' or 'phpsysinfo' are not reachable anymore ( https://servername.domain.com/phpsysinfo/ = not reachable ).

I *think* there can be a relation with the update from SAIL-358 to -366, I cannot remember I did something else in between.

Kind regards,

Hervé

[SARK devs]

Hi Herve

We think you are correct.  We develop on a completely vanilla SME platform which we recreate each time we build a new release.  It has no add-ons or other contribs.  It looks as though we need to do some more development on DPS before we release it to the community so we will withdraw -366 for now.

However, just from the feedback we've had, we think we know what needs doing to make DPS more "community friendly".  

Thanks to all who tested.

Please regress your SAIL installs back to -358 (rpm -e) and we'll get back with you when we've applied what we've learned from your testing.




Kind Regards

Selintra