guiguan
-
Posts
136 -
Joined
-
Last visited
-
Days Won
6
Content Type
Blogs
Gallery
Downloads
Events
Profiles
Forums
Articles
Media Demo
Everything posted by guiguan
-
I ordered one online, but unfortunately I still haven't received it even after waiting for 1 month. Crappy Harvey Norman in AUS
-
Uni Call v5.01 available for download v5.01 (20/05/13) Minor bug fixes: now even if a TARGET is not identified in Apple Contacts, user's preferences of the TARGET's call options will be learnt as well
-
LOL, I thought you are in US because you are using Google Voice/Talk. But never mind.
-
Ya, good to know it works for you.
-
You are welcome. LOL, you got THREE devices! What a busy man
-
Hey avk_tp. Now I have added GrowlVoice to Uni Call. Please go and test it out. Unfortunately, it seems we don't have Google Voice available in Australia, so I am not able to tell whether it works or not. Please let me know any problems.
-
Hey Djay. Now I have added the device selection feature for Phone Amego in Uni Call. You can use the following command to select a mobile device: callp TARGET /Laurel-SG You can find your device labels under Phone Amego Preferences: Manage Aliases for Device Labels You can assign an easy to remember alias to a complicated device label. For example: callp --map ip to "Guan's iPhone" yes Then in the future you can make a bluetooth phone call through device "Guan's iPhone" as follows: callp TARGET /ip To remove the assigned alias: callp --unmap ip yes
-
Hi Davide. How's going? Now I have added both SIP and PushDialer to Uni Call. Please download and try them out. Bugs might exist. Please let me know. Hope you will like them!
-
Hi everyone! Uni Call v5.0 is now available. Please upgrade now. Important note: please manually remove directory ~/Library/Caches/net.guiguan.Uni-Call after the upgrade. v5.0 (19/05/13)Added SIP Call component Added PushDialer Call component Added GrowlVoice Call component Update for Phone Amego Call: the user can select which bluetooth device to use ("callp TARGET /DEVICE_ALIAS_OR_DEVICE_LABEL") for making a phone call. The user can also assign an easy to remember alias to a complicated device label. Now the user can completely enable/disable call components through "call --enable"/"call --disable". When a call component is disabled, its corresponding Alfred Preferences will be automatically removed; later when it is enabled again, its Alfred Preferences will then be automatically restored. The thumbnail cache folder is now moved from ~/Library/Caches/net.guiguan.Uni-Call/thumbnails to ~/Library/Application Support/Alfred 2/Workflow Data/net.guiguan.Uni-Call/thumbnails, which ensures that Uni Call will be uninstalled with Alfred 2. Added a persistent configuration file config.plist in ~/Library/Application Support/Alfred 2/Workflow Data/net.guiguan.Uni-Call. The reason why this config.plist is not placed inside Uni Call workflow folder but in Workflow Data folder is to make sure that the user's configurations will stay unchanged after future workflow upgrades.
-
Viber doesn't have a public api nor a URL scheme for Uni Call to use atm. So I am not able to add support for Viber at this stage. BTW, I have done the SIP Call component. Will release to you guys soon during the weekend.
-
I can integrate GrowlVoice with my workflow. What do you think?
-
Do we have a Google Voice client on Mac other than through Gmail web interface to dial out a Google Voice phone call?
-
Cheers. I will work on it during the coming weekend.
-
Atm, Phone Amego doesn't provide a public API for third party softwares, like Uni Call, to control that. However, if you really want this functionality, you can email Phone Amego's author and suggest him to provide an option in its Url Scheme for selecting a device to use. Then, I can add it in Uni Call for you
-
Please download the new version. Special thanks to Djay for helping me haunt down the evil bug. v4.21 (14/05/13)Minor bug fixes: now handles spaces in POSIX path to the workflow. Before, those spaces could cause problem for Uni Call Basestation to launch Uni Call. Minor bug fixes: Skype Call can now correctly generate notifications in Mac OS X Notification Centre.
-
Nice. LOL. Also, thanks for your support. Bed time for me again
-
Thanks man. I think I might have found the bug. You got a space "../Alfred 2/.." in the path to the workflow, and that causes the problem. I have now handled that. Please try the new version: http://cl.ly/103C3P0m1w2q Finger crossed
-
Same from the Console
-
v4.2 and v4.1 are quite different. I have changed the architecture so the new version can handle consecutive requests twice as fast (only 50% of the original time needed). Now, I have generated two versions for you: First, try http://cl.ly/2C3W3t121V1r first. See if it works. If so, then the problem is that the connection timeout is too short, and the new 5 seconds is more appropriate. If not, then try http://cl.ly/0F3b3a1G2d2R which will output some debug logs. Please paste here You are my valuable user resources. LOL
-
Also, can you type the following command in your Terminal and paste the result here: lsof -i -P | grep -i "28642" I reckon something on your Mac is blocking the TCP port 28642 that Uni Call is trying to use.
-
Okay. The problem is the Uni Call (server) part didn't launch. Let's try to launch it manually: 1. Go to Uni Call workflow folder 2. Then open your Terminal, type "cd ", then drag the Uni Call workflow folder to the terminal, and hit return 3. Type "./bin/Uni\ Call" to start the server. Observe any log message and paste here. (if the server runs, it will terminate itself after 5 min. you can use ctrl+c to terminate the server running) 4. If no error log message found, try "call some_target" in your Alfred and see if it works
-
From your Alfred, type Console to launch the Apple Console app Then in the console window, click the bottom right button "Now". Go back to Alfred and type "call something". Copy and paste anything related to either Alfred or Uni Call here, so I can help you. Not at all, bro. You are always welcome.
-
From v4.2, Uni Call is basically two parts: the client (Uni Call Basestation) and the server (Uni Call). Your problem seems to be the client didn't connect to the server properly. There must be some long messages in your Console (Applications/Utilities/Console.app). Can you find them? Okay, bed time for me. Talk to you tomorrow.
-
Oh, damn. I thought you r professional. Haha. It's 2:36 AM in the morning for me now. I can generate some screenshots for you tomorrow. But for now, I think I should go back to sleep.