On the "Recorded Calls" page ie /dom_recordings.htm, the page number should be included in the URL

[5953lc]

On the "Recorded Calls" page ie /dom_recordings.htm, the page number should be included in the URL

If you select any page on this screen

page 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 4243 44 45 46 47 48 49 .... 1247 1248 1249 1250 1251 1252 1253 1254 12551256 1257 1258 1259 1260 1261 1262 1263 1264 1265 1266 1267 1268 1269 1270 1271 1272 1273 1274 1275 1276 1277 1278 12791280 1281 1282 1283 1284 1285

The url listed at the top of the browser will ALWAYS SAY "dom_recordings.htm", whether I'm on page 1, 50, or 1250.

I suggest adding the page # to the URL so:

when I'm on page 50 the URL at the top of the browser will be: /dom_recordings.htm_page_50.htm

or when I'm on page 951, the URL at the top of the browser will say: /dom_recordings.htm_page_951.htm

[Vodia PBX]

That would make it impossible to cache the site. an alternative would be the form ...htm?page=123 but like with most modern web pages REST is the way to go, where all that stuff happens behind the curtains.

[5953lc]

Ok.

 

How would your alternative work ? http://websiteurl.com/htm?page=123

 

How would it work with REST ?

 

I'm trying to pull up a particular date's recordings ?

 

Sometimes I know when the call cam in so I'm looking for a date and I have a start time as well....

 

Sometimes I even have a caller ID... not always though.

[Vodia PBX]

What you can generally do (not only with the PBX web sites) is to switch your browser in the debugger mode and watch what traffic is going back and forth with the PBX. Then you can easily spot the REST requests and their answers, usually nicely parsed for you to see the content right there. That will help to understand what is happening "under the hood" with the PBX, and it will also make easier to understand how we can make changes that will serve your needs. You can also script REST requests, e.g. with curl.

[5953lc]

So, in Chrome, go in to debugger mode and look for "REST" ?