Messages

Hi:

Here are some images of the Jitsi configuration pages. As you can see, the password is from a later attempt when I'd changed it on the admin page to '201'. It failed identically whether I used the generated default and copied that into the phone or tried a simplified '201' password on both the server and the client. I've also attached the popup once the client has retried about 5 or 6 times and then given up.

Thanks for the interest!

Pab

Hi:

I thought I'd provide an update on my progress. I finally managed to spend a little time on this today.

Step 1: I have not managed to get my Jitsi softphone to authenticate against LMCE. However, that is discussed in another thread.

Step 2: Turns out that sambuca was right on the money. All that I needed to do was to enable the chan_unistim driver by adding the line "load => chan_unistim.so" to /etc/asterisk/modules.conf and then create /etc/asterisk/unistim.conf. I copied the template for the conf file from here: http://www.voip-info.org/wiki/view/Asterisk+UNISTIM+channels and made some modifications as per my terminals (I have 2: 1x i2004 and 1x 1120E). After a reboot of the system, I am able to make calls between the sets. I also tried dialing the MD's softphone, but didn't have much luck there. That said, I've not spent a whole lot of time on that.

Next, I'll maybe try and read up on how to create the template. I was also thinking that it would be nice to deploy the phones in the house so I guess I'll need to work something out for service to the outside world... I think I've found some TDM400 clones on eBay. Anyone have any luck with these?

Pab

Having now read up a little on the GSD, your suggestion makes sense. I've found the CGI script the Tomato gui invokes to enable/disable radio so I'll give this a try... when I get another chance to work on this.

Thanks for the reply, but I've tried it your way and didn't get any further. As I'm still in experimentation mode, I decided to download the 10.04 Beta1 ISO which I burned to a USB stick. The installation went well enough the second time around. Once it was up, I created a new 'Generic SIP softphone' device from the admin console and this time copied the number and password from the web admin page for the device into the Jitsi client. LMCE is still reporting '401 Unauthorized'.

I'm eager to understand how the asterisk interface (... is that the right terminology?) is meant to 'automagically' provision asterisk as you say. Is there any documentation on that? Maybe I can start debugging things a bit. I'd also appreciate hearing from anyone that has a softphone up and running.

Pab

Hi:

I'm trying to get 'any' softphone to register with LMCE and am not having much luck. For context, my LMCE install is a 1004 script based install.

I started off by following the 'Ekiga' wiki page instructions, but with changes to reflect new the newer version. So the first thing I did was to create a new 'Generic SIP softphone' device from the admin web interface, gave it 201 as the phone number, set a password and set the floor object type to 'Non-linuxmce phone'. I then installed the Ekiga client on my Windows 7 box, added a new account and filled in the relevant bits. Oh, following installation the wizard didn't ask about STUN (as per screenshots), but I did tick the 'Disable network detection' from the preferences. This failed to connect. A little Wiresharking later and I realised that Ekiga didn't even appear to be sending any SIP REGISTER messages to the core.

So then I downloaded and installed Jitsi and with this client (against the same 201 line), I see the REGISTER message in Wireshark. However, the core responds with a 401 (Unauthorized). From the core, I opened a terminal and started sniffing around in the /etc/asterisk folder. Upon grep'ing the entire directory for '201' I had only one hit in hints.conf. I don't know much about asterisk, but from some of the googling I've done, this doesn't look right. I also tried opening the asterisk console and issue the 'sip show peers' and it reports only the MD's default client (i.e. ext. 200).

In short, it looks like the device creation hasn't sinked up from the LMCE DB to the asterisk config. Any suggestions as to where to go from here?

Pab

Hi:

As I mentioned in another thread, I installed kubuntu 1004 last night and manually ran the LMCE install script. Everything went well, but at the end of it, I realized that I hadn't been given the opportunity to specify whether I wanted a core or a hybrid system. How should I have proceeded to setup a straight core only?

Pab

Hi:

I don't like keeping the wifi enabled all the time. I have my reasons, but I'll just leave it at that.

What I'd like is to have the ability to turn on the wifi when I want/need it and then turn it off again when I no longer need it. And obviously, I'd like to do it more easily than having to log into the router and do it the 'long' way. I thought this could be done using the orbiter(s) and/or an X10 remote control (by sending a code), etc.  I haven't managed to find anything in the forums on this idea so correct me if I'm wrong.

I am using the Tomato router firmware at the moment and might replace it with OpenWRT (or a derivative) if needed. I believe I've found the CLI to toggle the wifi state (need to test) so I'd next need to write a script to be invoked by 'something' to perform the toggling. I thought the 'something' might be to xPL enable the router... I've seen a few things on their forums suggesting this. This would leave a few things to resolve:

1. Is there an xPL device for LMCE? If not, I'd have to create one which I guess would need to act as a bridge between DCE and xPL. I think I read a vague reference to this idea someplace, but I haven't found much meat around the subject. Has any work been done to bridge xPL to LMCE/DCE?

2. Given that the router is on the external LAN, that means that the core would need to reach out via its external LAN interface in order to send the xPL message to the route. This is already starting feel like I'm stepping outside of what LMCE 'should' or rather 'should not' be doing... well maybe, maybe not... dunno.

I thought I'd ask for feedback on the basic idea before I set out on any project. I've still got plenty more to keep me busy anyway.

Cheers,
Pab

I should have mentioned, but I was on 810 when I posted this. Last night I decided to re-install and started with a fresh 1004 Kubuntu. After doing an update I ran the LMCE install script and it completed successfully.

I plan on having another go at installing the i2004 over the weekend. From a quick look at the admin web site, I see that there is still no i2004 or unistim device in 1004 so I've definitely got some work ahead of me. Before jumping in, I just want to clarify the steps I'll need to follow.

Step 1: Install and get a softphone working for testing purposes. Back on 0810, I didn't even manage to get that right to be honest. I tried installing Linphone as I noticed that it is a listed device in the LMCE admin site. I'd like to have something working there to gain some confidence and have something to test against. Once I have this working, I imagine that I should be able to make a call between Linphone and the hibrid's softphone extension?

Step 2: Install the chan_unistim library on the core's Asterisk installation. From my research, I need to provision each SIP line in the /etc/asterisk/unistim.conf file. Now, if I do this manually, should I expect this to work without the LMCE device template?

Step 3: Having thought about my question in 'step 2', am I correct in assuming that the purpose of my creating the LMCE device template for unistim phones would be to auto-provision the unistim.conf file? If so then I assume creating the template involves some scripting in order to auto-edit the conf file and populate the LMCE device DB table?

Step 4: If I'm right so far, then I imagine I should then delete the manual entry I created in step 2 in the unistim.conf file and them create the device "properly" from the LMCE admin web site?

Step 5 (down the road): Submit the template for evaluation and inclusion into the main LMCE build?

Question: Is the unistim phone device template the only LMCE artifact I need to code/create? I'm assuming that I don't have to also enhance the Asterisk interface template (assuming there is such a thing).

I know I've got some more reading ahead of me, guess I'm sort of thinking out loud to get my thoughts straight. Update: I've found the wiki document called Developing_a_DCE_Device (couldn't post the link) and admittedly haven't read this yet. I assume this is my 'bible' for the next few days?

Cheers,
Pab

Hi:

I have an older Nortel i2004 IP/Unistim based phone I'd like to try and use with LMCE. I've found some posts on Asterisks sites about building and installing the chan_unistim module, /etc/asterisk/unistim.conf file, etc. However, as I've found no posts here on the LCME forums I was wondering if there was any reason why this wouldn't be feasible or practical to attempt?

The first thing I noted is that although the chan_unistim module was apparently included in the 1.6 Asterisk stream, I see no logs (/var/log/asterisk) related to the module being loaded on LMCE. Is the LMCE Asterisk build custom? Has chan_unistim not been included?

Even if I build and install the module, do I risk running into other LMCE specific issues? I'm thinking along the lines of creating a new device from the web admin page. Will I need to create a new device template or some such?

I'm just getting started, but thought I'd check before going too far down this path.

pab