I have successfully setup a Cisco 7970 on Pluto and can use it fine as a telephone, but I cannot get the orbiter to run. I select the "services" button on the phone and then choose "Orbiter" and I am presented with a screen that says PLUTO ORBITER and at the bottom I get an error that says "Connection reset by peer"
Can anyone guide me as to where I start looking to troubleshoot this? This feature is going to pretty much seal the deal on a job we're working on and I'd love to have the leverage. Thank you!
Quote from: "adns"I have successfully setup a Cisco 7970 on Pluto and can use it fine as a telephone, but I cannot get the orbiter to run. I select the "services" button on the phone and then choose "Orbiter" and I am presented with a screen that says PLUTO ORBITER and at the bottom I get an error that says "Connection reset by peer"
Can anyone guide me as to where I start looking to troubleshoot this? This feature is going to pretty much seal the deal on a job we're working on and I'd love to have the leverage. Thank you!
Hi,
sorry for jumping in. I'm also very interested how cisco 7970 performs as Plut Orbiter. Can you please keep us posted and maybe even put some info on wiki, specially on sucess. I'd love to see few photos as well.
Do you use it with Pluto's Asterisk ? What are your experiences ?
Do you know where can I get some more info about that phone - particularly what OS, what apps can run, etc.... ?
Regarding your problem - I'd start with exploring DCERouter logs to see what happens when Orbiter tries to connect... It may help to solve it...
Thanks in advance and good luck,
regards,
Rob.
I know Cisco but I don't know Linux so someone may need to guide me a bit.
I've been viewing the logs at http://dcerouter/pluto-admin/index.php?section=fullLog&deviceID=2
The problem is that I don't even see anything show up here when I reboot the phone. Is there another log I should be looking at?
Quote from: "adns"I know Cisco but I don't know Linux so someone may need to guide me a bit.
I've been viewing the logs at http://dcerouter/pluto-admin/index.php?section=fullLog&deviceID=2
The problem is that I don't even see anything show up here when I reboot the phone. Is there another log I should be looking at?
It seems like phone cannot comunicate over network. Maybe you could check dhcp logs to see if phone requests IP on boot, and then see what happens....
Can you ping from/to phone to check if network is ok ?
Regards,
Rob.
The phone can definitely communicate with the network as it obtains an IP fine and I can use it to make phone calls. It's only the Orbiter portion that isn't working. When I choose the Orbiter button under Services I get the Pluto logo on the screen with a message at the bottom that says "Connection reset by peer."
Is there a way I can view the logs in realtime? On a Cisco router I would just telnet in and run a "show debug" command.
I'm still having the same problem. If anyone could help shed some light on the subject I would appreciate it. Thank you!
I have the same problem. The phone works fine, but when I try to launch the orbiter, I see the "pluto orbiter" logo and I get "connection reset by peer .
My logs give me:
*** /var/log/pluto//26_LaunchProxy_Orbiter.sh.log ***
13 10/10/06 0:32:22.118 TCPIP: Accepting incoming connection on socket 8, port 3451, from IP 192.168.80.1.
05 10/10/06 0:32:22.118 Received IMAGE 26, but device hasn't identified itself yet.
10 10/10/06 0:32:22.141 Socket::ReceiveData failed, bytes left 0 m_Socket: 8 Incoming_Conn Socket 8 192.168.80.1
10 10/10/06 0:32:22.141 Socket::ReceiveString2 ReceiveData failed m_Socket: -1 Incoming_Conn Socket 8 192.168.80.1
05 10/10/06 0:32:22.141 TCPIP: Closing connection to -1 (Proxy_Orbiter) 0x81dcae0 m_Socket: -1
13 10/10/06 0:32:22.141 Removing socket 0x81dcae0 from socket listener
22 10/10/06 0:32:22.142 Stale Command handler 136170208 for -1 closed.
13 10/10/06 0:32:28.051 TCPIP: Accepting incoming connection on socket 8, port 3451, from IP 192.168.80.1.
05 10/10/06 0:32:28.052 Received IMAGE 26, but device hasn't identified itself yet.
10 10/10/06 0:32:28.074 Socket::ReceiveData failed, bytes left 0 m_Socket: 8 Incoming_Conn Socket 8 192.168.80.1
10 10/10/06 0:32:28.074 Socket::ReceiveString2 ReceiveData failed m_Socket: -1 Incoming_Conn Socket 8 192.168.80.1
05 10/10/06 0:32:28.074 TCPIP: Closing connection to -1 (Proxy_Orbiter) 0x81dcae0 m_Socket: -1
13 10/10/06 0:32:28.074 Removing socket 0x81dcae0 from socket listener
22 10/10/06 0:32:28.074 Stale Command handler 136170208 for -1 closed.
How can the device identify itself ?
Yesterday I tested Cisco 7970 in my .40 installation. I setup it without any problems. After connection to the LAN the Core Orbiter displayed a message about finding a new device. I pressed button 'Use it' or similar. After 5 minutes the new message appeared on the Orbiter. It said about finish of configuring of phone and suggested to restart router. After restart the orbiter appreared on the phone screen.
There is an only one issue in the new version of pluto. You cannot reload router (only 'Force reload' works) if some packages are downloaded or installed. If you use pluto-admin interface to reload router you see that command to reaload send successful. But you cannot see that router is not reloaded because it's busy. Try to use some orbiter to reload router: on-screen or web orbiter.
Also, be sure that Cisco Orbiter was created correctly. Try to rebuild it and reload router. it seem that your problem related with it.
I took a few fotos of Cisco7079 Orbiter. You can see them here http://www.flickr.com/photos/smartblog/tags/cisco7079/. You can also see the Plutohome Orbiter on Nokia770 - http://www.flickr.com/photos/smartblog/tags/nokia770/.
I finally got it to work.
Not sure how exactly, but something like this:
- re-configured the device manually with /usr/bin/pluto/configure_cisco7970.pl
- re-generated the orbiter in pluto admin
- restarted
then the phone started working. It makes a really nice orbiter !