Caller ID Superfecta

Easy to do. Try source_send_to_URL in rev 216

Oh Man that is COOL.

Patrick, we need a example use syntax -

Ok check r219 I took a stab at the syntax example.

put the source as the last one.
enter the url/file.php you want to call.
click debug and you will see the syntax:
url/file.php?thenumber=123465&CLID=theclid

[rockinthesixstring]

Ok, so I put this in the URL field but it only took a short bit of the string http://192.168.0.115:2345/xbmcCmds/xbmcHttp?command=ExecBuiltIn is supposed to be http://192.168.0.115:2345/xbmcCmds/xbmcHttp?command=ExecBuiltIn&parameter=XBMC.Notification%28Incoming%20Call%2C&thenumber

Patrick - where is the char limit imposed? I dont see it in the data source.

Since I dont see any character limits, Im guessing we have an escapment problem with the ampersand character, and most likely all the rest.

Patrick - can we pass the URL_Adress parameter through a php escapement command?

the clid is sanitized before being sent to the url.

We can do an htmlentities encode to change space and other characters with a &#

However, in this case it seems more an SQL database problem as the line entered in the option was not stored properly.

Also, this specific syntax will probably not work either as it seems that this url does require not a ?thenumber&clid at the end.

To provide a fit all module will be tough as each module is different.
However it should be easy to modify a module for a specific application.

We just need to have the required parameters, and we can create a custom made send_to_xbmc.

We probably should be sanitizing before we save user entered parameters to the data base. This may be thie first time we run itno this problem, but doubtful the last.

Thoughts?

[rockinthesixstring]

XBMC has pretty basic requirements. All you have to do is send a string

http://192.168.0.115:2345/xbmcCmds/xbmcHttp?command=ExecBuiltIn&parameter=XBMC.Notification(This%20Is%20Line%20One%2CThis%20is%20line%20two)

PLease give this a try

Im pretty sure we need some variant of `addslashes ( string $str )` in the current alpha to get it to work right.

[rockinthesixstring]

If I run my number through the debug, I get this output

Send to XBMC: http://192.168.0.115:2345/xbmcCmds/xbmcHttp?command=ExecBuiltIn&parameter=XBMC.Notification(4039754852%2cChase Florell (Mobile))

then if I enter this portion into the querystring, I get my popup on the Media Player.

http://192.168.0.115:2345/xbmcCmds/xbmcHttp?command=ExecBuiltIn&parameter=XBMC.Notification(4039754852%2cChase Florell (Mobile))

However, the debug test AND a live phone call do NOT popup the info.

This is the final and correct syntax for xbmc notifications.
http://federationrnd:8080/xbmcCmds/xbmcHttp?command=ExecBuiltIn&parameter=XBMC.Notification(7615648954%2cJerry Freedman)

Alpha v3 I think needs some escapement for the ampersand character.

try rev 223.

Also try to it with uncommenting the urlencode line.

With the current SVN build I get this in debug, and no pop up on the media player:

Send to XBMC: http://federationrnd:8080/xbmcCmds/xbmcHttp?command=ExecBuiltIn¶meter=XBMC.Notification(7601234567,Sams Jade Factory)

Note the paragraph symbol in the middle.

With the encode line unremarked I get this in debug:

Couldn't resolve host 'http%3A%2F%2Ffederationrnd%3A8080%2FxbmcCmds%2FxbmcHttp%3Fcommand%3DExecBuiltIn%26parameter%3DXBMC.Notification%287601234567%2CSam+Jade+Factory%29'

r223 w/out the encode url is very close.

When I cut ans paste the debug version, and fix only the part thats messed up (The ampersand and the start of the word parameter, it works as expected. The ampersand needs to be escaped somehow.

http://federationrnd:8080/xbmcCmds/xbmcHttp?command=ExecBuiltIn&parameter=XBMC.Notification(7601234567,Sames Jade Factory)

The ampersand needs to be escaped somehow.

Ok - this actually looks perfect in debug:

$url=$run_param['URL_address'].'/xbmcCmds/xbmcHttp?command=ExecBuiltIn&#38parameter=XBMC.Notification('.$thenumber.','.$first_caller_id.')';

But it does NOT create the desire results in XBMC. If you cut and paste the debug results into a browser - it DOES make XBMC do what is expected.

could you try rev 225

all the static part of the url is using standard characters that should not create problems. I've tried just to urlencode the CLID part (to encode the space, etc...).

Try also by uncommenting the $url line.

Success!

r225 works as expected.
Requestor also asks that we format the CID number in a pretty way.
(xxx)xxx-xxxx

I see a potential problem when trying to format the cid number for astehtics.

The requestor asked for (xxx) xxx-xxxx, but thats ionly good for north american style numbers.

Can we provide a pretty-fication process that will be smart enough to format worldwide numbers in a meaningful way? It wont do to try and force all numbers into the USA style display -

This destination (XBMC) may be secured with a login id/password. If it is, then this datasource will fail.

I have asked the requestor to provide syntax examples for the url thatinclude authentcation. If we get this info - I suggest we add configuration items to support it.

see rev 227
formatting option

Brilliant. Formatting option works perfectly.

The debug display for this data source is pretty messed up looking. Can that be addressed without breaking the source?

the debug shows exactly the http string that will be sent. That was useful for our debug.
If you want to declutter, we can change the debug by just writing: called server FQDN/IP:port and without anything else.

try rev 229.

This case is CLOSED to further comment. XBMC now has stand alone tickets, like any other source.