Aleksandar's computer workshop
Let's see what Aleksandar was fixing today.
My findings, tips & tricks related to computers, internet, programming and other stuff I was working with.

How to fix Windows Photo Gallery Yellow Tint Background Problem on Windows 7

February 21, 2010 02:43 by Aleksandar

When displaying and viewing photos in Windows Photo Gallery of Windows 7, some monitors or LCD flat panel displays may have a strange problem in which the images will be shown with a orange or yellowish tinge in photos background, affecting the display natural color of pictures to become something like Sepia effect. The entire window on Windows photo gallery appears to be colored in slightly yellowish tint, and is therefore appear darker, including the panels on either side of the photo display which which appear yellow on the desktop but are white in actual.The yellow tinted photos may also affect other default image viewer in Windows 7. In some case, the problem goes away when the photos are viewed in slideshow mode, or in some other image manipulation tool such as Adobe Photoshop, Paint or Paint.NET or photo management utility such as XnView.

The symptom is likely to occur after update of incompatible monitor driver, especially on Samsung LCD flat panel monitor driver update via Windows Update. The cause for the error is the usage of incorrect color profile for the monitor in Color Management setting.

To solve the problem and restore normal colors in Windows Photo Gallery, you can try one of the resolutions below. 

  1. Control Panel in icon mode
     

  2. Color Management

  3. Select your display device

  4. Check the box “Use my setting for this device”

  5. Click Add

  6. Choose “sRGB IEC61966-2.1” (this is the color profile that IE is using)

  7. Set it as default

 

Exit from all dialogs and reboot your computer, and the color problem on Windows Photo Gallery is fixed.

If your system doesn’t have sRGB IEC61966-2.1 profile under the ICC Profiles, you can download the color profile here http://www.color.org/srgbprofiles.xalter.

Tip for advanced users: You can open Color Management via command line using %systemroot%\system32\colorcpl.exe

 

 


Free desktop sharing tool full of features. Remote support, web conference, online demonstration

August 11, 2009 17:33 by Aleksandar

Mikogo is a free desktop sharing tool full of features to assist you in conducting the perfect online meeting or web conference.
Take advantage of the opportunity to share any screen content or application over the Internet in true color quality with up to 10 participants simultaneously, while still sitting at your desk.

Mikogo can be employed for a range of professional, academic, or personal uses, including:

  • online meetings
  • web conferences
  • product demonstrations
  • web presentations
  • remote support
  • webinars
  • and more!  

Provide online technical support for your customers. Conduct product demonstrations for business customers. Use Mikogo to discuss and edit a current team project. The ideal tool for free online group collaboration.

Most important: it’s FREE for both commercial and private use.

http://www.mikogo.com

 


How to solve mystery of not sent CallerID via SIP in Asterisk

July 7, 2009 19:59 by Aleksandar

Today I was helping my colleague to find a reason why outgoing calls did not send out correct CallerID and all calls are shown as private on destination device.

First we checked the extensions.conf which does decent job and looks like this:

[forward]
exten => _X.,1,NoOp("going to do a forward to number")
exten => _X.,n,SetCallerPres(allowed)
exten => _X.,n,Set(CALLERID(num)=${IF($["${CALLERID(num):0:1}" = "0"]?"${CALLERID(num):1}":"${CALLERID(num)}")})
exten => _X.,n,Set(CALLERID(num)=${IF($["${CALLERID(num):0:1}" = "0"]?"${CALLERID(num):1}":"${CALLERID(num)}")})
exten => _X.,n,Set(CALLERID(num)=${IF($["${CALLERID(num):0:2}" = "31"]?"00${CALLERID(num)}":"${CALLERID(num)}")})
exten => _X.,n,Set(CALLERID(num)=${IF($["${CALLERID(num):0:4}" = "0031"]?"${CALLERID(num)}":"0031${CALLERID(num)}")})
exten => _X.,n,Set(CALLERID(name)=${CALLERID(num)})
exten => _X.,n,NoOp("************************ dialing ******************************************")
exten => _X.,n,NoOp(${CALLERID(all)})
exten => _X.,n,Dial(SIP/voipprovider/${DTNUM},25,r)
exten => _X.,n,Playback(silence/1)
exten => _X.,n,Dial(ZAP/r2/${DTNUM},15,r)
exten => _X.,n,NoOp("going to try once with backup number")
exten => _X.,n,Playback(silence/1)
exten => _X.,n,Dial(SIP/voipprovider/${DTBNUM},25,r)
exten => _X.,n,Playback(silence/1)
exten => _X.,n,Hangup

exten => s,1,NoOp("s 1 End")
exten => s,n,Hangup

exten => h,1,NoOp("h 1 End")
exten => h,n,DeadAGI(end_call.agi)
exten => h,n,Hangup

exten => t,1,NoOp("t 1 End")
exten => t,n,Hangup


Actual problem is setting in Sip.conf

[voipprovider]
username=***** <---- put your own stuff here
secret=****** <---- put your own stuff here
type=peer
qualify=no
nat=yes
insecure=very
host=sip.voicetrading.com
fromuser=someusername  <--- problem is here

canreinvite=no
allow=alaw
dtmfmode=inband
realm=voicetrading.com


Due to this one line which sets the fromuser value all outgoing calls had hidden/private CallerID. After removing this line code in extensions started working properly and all calls started to have correct CallerID.


Solving problems with the MS header "SOAPAction"

June 8, 2009 23:45 by Aleksandar

Today I have faced some errors during implementation of some 3rd party SOAP service. Proxy was made with received WSDL file using this command:

"c:\Program Files\Microsoft Visual Studio 8\SDK\v2.0\Bin\wsdl.exe" /language:VB  /protocol:SOAP /namespace:testNamespace sampleservice.wsdl /server

Command above will convert WSDL file to ASMX server proxy class file.

After first test I got this error:

The methods testMethod1 and testMethod2 use the same SOAPAction ''. When the RoutingStyle of the XML Web service is SoapAction, SOAPAction values must be unique across methods on the XML Web service. You can change the SOAPAction with the Action parameter to the SoapDocumentMethod or SoapRpcMethod attributes, or you can specify a RoutingStyle of RequestElement on the XML Web service.

In order to fix this problem add line marked with bold green color in class definition:

Imports System.Web.Services
Imports System.Web.Services.Protocols
Imports System.ComponentModel

<System.CodeDom.Compiler.GeneratedCodeAttribute("wsdl", "2.0.50727.42"), _
System.Web.Services.Protocols.SoapDocumentService(RoutingStyle:=SoapServiceRoutingStyle.RequestElement), _
System.Web.Services.WebServiceAttribute([Namespace]:="testNamespace"), _
System.Web.Services.WebServiceBindingAttribute(Name:="TestSoapBinding", [Namespace]:="testNamespace")> _
Public Class testWebService

' your class code comes here 

End Class