10-11-2010 10:26 AM - edited 03-13-2019 07:11 PM
Hi,
I need to please know how to send an HTTP MIB request to a certain DMP to simulate a "remote" key click if I don't now have a remote handy. Say I want to test the Yellow button after it is programmed. Can anyone help with the HTTP command string for this example?
Thanks
Solved! Go to Solution.
10-14-2010 06:32 AM
The Command to change or assign the button to a specific task is
correct.
The Command to execute the RED button is also correct for the DEFAULT
setting (which is "r"). Once you change the assignment to another value
the command (with the "r") is not correct and will not work.
The "irasrv" is what controls the remote command mappings. In this example; when
you press RED button, it interprets it and it is what sends to the "xfake" service "r",
which is mapped to the RED press button. So when you send a command directly to "xfake",
you are completely bypassing the "irasrv". And there is no way to send a keypress
directly into the "irasrv".
In summary, what this is saying the there is no way to send a command to the "irasrv"
(which is the infrared service for reading the remote control commands). We can
bypass this service to the next step to simulate the commands using the "xfake" service.
These are the commands in the second discussion thread that I posted.
the DEFAULT "xfake" commands work. But when you change them some may NOT work
based on the values that were changed in the key mappings.
In your case, the CAST string can not be passed in a MIB to the "xfake" service.
This has to do with commands and syntax in your remapped values.
The key mappings "do" work. I have tested them with a physical remote without issues.
Cheers!
T.
10-11-2010 10:44 AM
Check out my previous threads:
Execute Remote Command
https://supportforums.cisco.com/thread/2040917?tstart=0
Configure Remote Button
https://supportforums.cisco.com/thread/2042481?tstart=0
If this answers your question, Please take time to mark this
discussion answered & rate the response.
Thank You!
T.
10-13-2010 09:14 AM
Hi,
Thanks for the great post links. I am abit confised here though. Let me use an example to make things cleared for us:
I need to configure the RED buttons on launch CAST.
So here is what I did:
Configure RED button:
Review Configuration
https://admin:default@a.b.c.d:7777/get_param?p=irasrv.key*
Save Configuration & Reboot
https://admin:default@a.b.c.d:7777/set_param?mib.save=1&mng.reboot=1
All done with no issues and I replace the variables with the correct values.
Now comes the part where I want to simulate the clicking of the RED button and here is where I
get confused. In your second post (Execute Remote Command) it appears that for me to simulate
the click I need to use the HTTP MIB
https://admin:default@a.b.c.d:7777/set_param?mng.command=write+xfake+r
but when I do it doesn't work.
If I go ahead and use HTTP MIB irasrv.key_RED T_STRING ira add 1 xfake 1 RED r
https://admin:default@a.b.c.d:7777/set_param?irasrv.key_RED=ira%20add%201%20xfake%201%20RED%20 , it removes the RED button configuration done in the FIRST step.
What am I doing wrong?
PS: I have attached my current key mapping.
Thanks
10-13-2010 09:10 PM
Ok, thinking this thru again... It doesn't make sense what you are trying
to do. Think thru the logic...
* Configuring and assigning the Colored buttons on the remote to access web pages
and Cast isn't a bad idea and it can be useful.
We can configure this and when a user presses a colored button everything
works as expected.
* Now, you want to "simulate" someone hitting the colored button by sending
a mib to do this. Doesn't make sense. All you have to do is send a mib
to the DMP to display whatever the content is configured for the colored button.
For example,
The Red Button is configured to go to the Cast html. So when the Red button
is pressed on the remote the DMP displays the Cast page. Works great.
Lets say the Blue button goes to "www.cisco.com" so now you want to
simulate someone pushing the blue button well there is no need just send
a mib to the DMP to go to "www.cisco.com"
T.
10-14-2010 05:57 AM
Hi,
Yes what you are saying is logical. The simulation part however is just for testing that things work right as I don't have a remote handy now.
But in anycase, I still wish to undestand more and clear my confusion about the two commands and whether they overlap:
and
https://admin:default@a.b.c.d:7777/set_param?irasrv.key_RED=ira%20add%201%20xfake%201%20RED%20r
Was the order correct for the steps I posted in my previous post?
Thanks
10-14-2010 06:32 AM
The Command to change or assign the button to a specific task is
correct.
The Command to execute the RED button is also correct for the DEFAULT
setting (which is "r"). Once you change the assignment to another value
the command (with the "r") is not correct and will not work.
The "irasrv" is what controls the remote command mappings. In this example; when
you press RED button, it interprets it and it is what sends to the "xfake" service "r",
which is mapped to the RED press button. So when you send a command directly to "xfake",
you are completely bypassing the "irasrv". And there is no way to send a keypress
directly into the "irasrv".
In summary, what this is saying the there is no way to send a command to the "irasrv"
(which is the infrared service for reading the remote control commands). We can
bypass this service to the next step to simulate the commands using the "xfake" service.
These are the commands in the second discussion thread that I posted.
the DEFAULT "xfake" commands work. But when you change them some may NOT work
based on the values that were changed in the key mappings.
In your case, the CAST string can not be passed in a MIB to the "xfake" service.
This has to do with commands and syntax in your remapped values.
The key mappings "do" work. I have tested them with a physical remote without issues.
Cheers!
T.
10-14-2010 06:42 AM
Thanks Tomas.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: