Hey all,
Alex has been doing some good cleanup work on Asterisk-IM. A first beta release is now available on the beta plugins page:
http://www.jivesoftware.org/wildfire/plugins-beta.jsp
It’‘s working well on our own server so far. Time will tell if some of the most dreaded bugs are finally fixed, such as the presence getting out of sync. Depending on how well the beta goes, the final 1.2.0 shouldn’'t be too far behind.
Regards,
Matt
To add to what Matt said, I would highly recommend backing up your phone db tables before downloading the beta. I am pretty sure I have everything running fine on this front but it is better to be safe than sorry.
Thanks,
Alex
hi all i’'m mike and this is my first post
i’'m on wildfire from 2 days (wow this sounds weird …)
well … i’'ve tested the asterisk-im 1.2.0 beta on wildfire 3.0.1, 3.1.0 beta 2 and the 19th september night build
on all of them i have the same problem:
on the asterisk-im plugin manager, i can ‘‘add server’’ but nothing shows on the main asterisk-im page
the info.log file seems fine:
2006.09.19 20:43:38 Initializing phone plugin
2006.09.19 20:43:38 Initializing Asterisk Manager connection
2006.09.19 20:43:50 Connecting to uplink port 5038
2006.09.19 20:43:50 Connected via Asterisk Call Manager/1.0
2006.09.19 20:43:50 Successfully logged in
2006.09.19 20:43:50 Determined Asterisk version: Asterisk 1.2
2006.09.19 20:43:50 Adding new queue myqueue
i’'m doing those tests trying to fix the ‘‘always on phone’’ problem.
my platform is debian sarge and jvm is jre1.5.0_06
let me know if i can help somehow
thanks for supporting and for the great work!
Hi,
I’'ve been testing the 1.2.0 beta and am not able to edit a mapping. When I hit save it says Operation Complete in green at the top but the values do not change. No errors are logged in log files or console.
Dear Sirs
reinstalling the wildfire server using mysql as the external db, made the asterisk-im 1.2.0 beta show the asterisk servers
but the ‘‘always on phone’’ problem still persist … i’'m using the client ‘‘Coccinella’’
here are some logs:
2006.09.19 22:15:37 Initializing phone plugin
2006.09.19 22:15:38 Initializing Asterisk Manager connection
2006.09.19 22:15:57 Connecting to uplink port 5038
2006.09.19 22:15:57 Connected via Asterisk Call Manager/1.0
2006.09.19 22:15:57 Successfully logged in
2006.09.19 22:15:57 Determined Asterisk version: Asterisk 1.2
2006.09.19 22:15:57 Adding new queue myqueue
2006.09.19 22:18:35 Adding channel SIP/1-081ccc30
2006.09.19 22:18:36 Adding channel SIP/2-081d2290
2006.09.19 22:18:36 Adding channel SIP/2-081d2290
2006.09.19 22:18:37 OnPhoneTask called for user PhoneUser{id=3, username=’‘mike2’’}
2006.09.19 22:18:37 OnPhoneTask called for user PhoneUser{id=1, username=’‘mike’’}
2006.09.19 22:18:37 Linking channels SIP/1-081ccc30 and SIP/2-081d2290
2006.09.19 22:18:41 Unlinking channels SIP/1-081ccc30 and SIP/2-081d2290
2006.09.19 22:18:41 Removing channel SIP/2-081d2290 due to hangup
2006.09.19 22:18:41 OnPhoneTask called for user PhoneUser{id=3, username=’‘mike2’’}
2006.09.19 22:18:41 Removing channel SIP/1-081ccc30 due to hangup
2006.09.19 22:18:41 OnPhoneTask called for user PhoneUser{id=1, username=’‘mike’’}
uff … hope that helps … (note that this is OT, here i’'m talking about the patched asterisk-im, not this 1.2.0 beta)
having Spark and the Wildfire server on the same machine, causes strange conflicts:
it works till you enable asterisk-im, then it goes on timeout.
this behaviour was noted on wildfire server versions from 3.0 to 19/9 night builds.
the wonderful ‘‘Coccinella’’ im client, does not handle the ‘‘on phone’’ status correctly:
it suffers the ‘‘always on phone’’ bug; i’'m talking about the stable binary version with voip, on linux and on windows (at least emulated via wine)
so:
i confirm that
Wildfire 3.0.1 + Spark 2.0.1 + jre1.5.0_06 + asterisk 1.2.10-BRIstuffed-0.3.0-PRE-1s + asterisk-im taken from here: http://couplet.be/temp/status_fix/asterisk-im.jar
does not suffer the ‘‘always on phone’’ bug.
Hey Mike,
Thanks for the info. Do you see anything appearing in the error logs?
Thanks again,
Alex
huh ?
this is the info.log from sip/1 (mike) to sip/2 (mike2) :
2006.09.19 22:53:05 Adding channel SIP/1-081a3810
2006.09.19 22:53:05 Adding channel SIP/2-081cbdd0
2006.09.19 22:53:05 Adding channel SIP/2-081cbdd0
2006.09.19 22:53:05 OnPhoneTask called for user PhoneUser{id=2, username=’‘mike2’’}
2006.09.19 22:53:05 OnPhoneTask called for user PhoneUser{id=1, username=’‘mike’’}
2006.09.19 22:53:05 Linking channels SIP/1-081a3810 and SIP/2-081cbdd0
2006.09.19 22:53:08 Unlinking channels SIP/1-081a3810 and SIP/2-081cbdd0
2006.09.19 22:53:08 OnPhoneTask called for user PhoneUser{id=2, username=’‘mike2’’}
2006.09.19 22:53:08 Removing channel SIP/2-081cbdd0 due to hangup
2006.09.19 22:53:09 OnPhoneTask called for user PhoneUser{id=1, username=’‘mike’’}
2006.09.19 22:53:09 Removing channel SIP/1-081a3810 due to hangup
(which works)
My question was in where it is not working. Is there anything in your error.log?
Thanks,
Alex
ic
yes i had something in the warn.log iirc complaining about wrong tsl stuff
now it’'s late but let me know if you want that i replicate this behaviour (tomorrow) (which i think you can replicate running wildfire and spark on the same machine)
also keep in mind that i’'m talking about the patched asterisk-im, not this 1.2.0 beta
So, I don’‘t think I followed you running on the same machine with the patched version doesn’'t work? But it does on beta 1.2.0?
Thanks,
Alex
nope, i just wanted to let the community know that when running the wildfire server and the spark client on the same machine, you will have login problems, now that i’'ve splitted them, all works fine, with the patched asterisk-im and also the 1.2.0 beta,
i wanted to share my experience with the community, even if that may be OT.
talking about asterisk-im 1.2.0 beta, there may be a bug:
as already noted by other testers, if you are using the embedded database, you will not be able to save the asterisk manager info.
using an external database, in my case mysql, works.
so, resuming, i confirm that with 1.2.0 beta:
embedded db has problems
‘‘on phone’’ status works fine
placing a call from contacts works fine
placing a call with ‘‘Dial number’’ works fine
receiving a call makes ‘‘on phone’’ status change accordingly.
now, i’‘m headbunging on wildfire + asterisk-im + spark, because i didn’'t want to write an asterisk cti from scratch.
what i found in wildfire, after only 2 days, is far more than i could desire, almost 90% of the features i was hunting for.
so here is my wishlist, i’‘m going to accomplish it because i have to do it for job: i’'m payed for it.
of course the results will be licensed under gpl and, i hope, integrated into the main asterisk-im and spark trunk.
of course, any help from the depelopment team, and the authors of asterisk-im and spark will be greatly appreciated!
so here comes the roadmap:
clicking on spark, in Spark->Preferences, i think that sould be added an icon on the navigation on the left, something like ‘‘Dialing’’ or ‘‘CTI’’ with the ability to setup some of the features below
like ADM ( http://adm.hamnett.org ), when the spark client, connected as an user mapped to a phone, receives a phone call, a popup could be created, containing info about the caller.
like ADM, the action of receiving a call, should be optionally mapped to an action, configured in the CTI Preferences described before. the action could be, for example, to open the browser with an url like http://someurl/printCallerIdInfo.php?id=�llerid% . you know, for crm integration
it would be nice if, also in the Preferences options, the user would optionally let his other contacts to let them know with which caller id they are on phone
like the Coccinella client, it will be helpful to have an address book. The way is done in Coccinella is approssimative: only the name and the telephone number … it would be better to centralize the user base on the jabber server side. not sure about that.
about that point, maybe the “User Properties” on the wildfire server could be extended.
in fact i don’‘t understand why if you edit your properties on Spark, with “Edit my Profile”, they could be viewed from another client, even Coccinella, even the avatar works well, but on the wildfire server side, you don’‘t get those info; you can’‘t edit them and you can’'t create them.
Simply extending those fields, would accomplish the ‘‘commercial’’ user base problem.
i mean, you could create on the server a group named something like ‘‘Customers’’ or ‘‘Customers - $BrandName’’ and its contacts would be searchable from the ‘‘back-end’’ users, and used from the caller popup feature.
this includes on the other hand, the ability for the ‘‘Customers’’ to login your wildfire jabber server, but, hey, this is a feature
what do you think ? every cent will be appreciated
ok, about the ability to change “User Properties” from the wildfire server, i answer to myself: the User Properties are the login info,
the “Profile” you change from Spark, is the vCard.
That’‘s nice and coherent and it’'s even better!
having the ability to create vCards from server would provide the tool to display the info popup i was talking before.
this is getting OT, i’'ll take it somewhere else and shut up
biomike,
The next Spark release (2.0.3) will have a fixed version of Asterisk-IM. That will provide the following features:
Incoming call screenpop with callerID.
Ability to dial based on vcard information.
So, a big step closer to what you’‘re looking for. I like some of your other ideas. We’'ll definitely consider them for future releases.
Regards,
Matt
Hi Mike,
Is there any chance of getting an early look at 2.0.3? I’'ve tried building the latest version of spark in SVN with the asterisk-im-client.jar built from asterisk-im trunk and am not seeing the call notifications popup.
Also, about my previous post. In asterisk-im 1.2.0 beta on the sever side I cannot update phone mappings. When I select a mapping to edit, the Device field does not get populated and is called “Phone” and not “Device.” When you commit it says "Operation Completed’’ but nothing changes. Maybe there’'s a problem in edit because it is using the wrong field (i.e. mistaken device for phone?)
The field is in fact mislabeled in the beta, though this hasn’'t prevented me from being able to add devices. Can you check your error log and see if there are any exceptions? My hunch is that there is an exception being swallowed - the upgrade scripts may not have run smoothly or something along those lines.
Thanks,
Alex
Adding entries always works, editing always fails. Is it possible that when you add you do an INSERT without specifying the column names? Just giving it a sequence of paramaters – so the “phone”/“device” mislabel will go unnoticed during an insert?
I’'m not seeing anything in the logs during a “failed” update.
This is the schema for my tables:
mysql> show create table phonedevice;
*----
*----
| Table | Create Table
*----
*----
| phonedevice | CREATE TABLE phonedevice (
deviceID bigint(20) NOT NULL,
device varchar(255) NOT NULL,
extension varchar(255) NOT NULL,
callerId varchar(255) default NULL,
isPrimary int(11) NOT NULL,
userID bigint(20) default NULL,
serverID bigint(20) NOT NULL,
PRIMARY KEY (deviceID)
) ENGINE=InnoDB DEFAULT CHARSET=latin1 |
*----
*----
1 row in set (0.00 sec)
mysql> show create table phoneuser;
*----
*----
| Table | Create Table
*----
*----
| phoneuser | CREATE TABLE phoneuser (
userID bigint(20) NOT NULL,
username varchar(255) NOT NULL,
PRIMARY KEY (userID),
UNIQUE KEY username (username)
) ENGINE=InnoDB DEFAULT CHARSET=latin1 |
*----
*----
1 row in set (0.00 sec)
mysql> show create table phoneserver;
*----
*----
| Table | Create Table
*----
*----
| phoneserver | CREATE TABLE phoneserver (
serverID bigint(20) NOT NULL,
serverName varchar(255) NOT NULL,
hostname varchar(255) NOT NULL,
port int(11) NOT NULL,
username varchar(255) NOT NULL,
password varchar(255) NOT NULL,
PRIMARY KEY (serverID),
UNIQUE KEY serverName (serverName)
) ENGINE=InnoDB DEFAULT CHARSET=latin1 |
*----
*----
1 row in set (0.00 sec)
There is a problem with the UI in update where the “Phone”/device isn’'t populated when you click edit are you repopulating your desired device so that the form is complete?
Thanks,
Alex
Yes, i’'ve tried both ways with and without filling in the Phone textfield with a desired value.