search for: invalidcalls

...d can receive calls very well. The problem happens when any user tries to make an outbound call. The proxy replies with a "401 Unauthorized" and * don't try another INVITE including credentials. Here is part of the content of sip.conf. [general] port = 5061 bindaddr = *.IP context = invalidcalls ;This account is used for inbound and outbound calls register => myuser:mypass@mydomain/999 [mydomain] type=peer host=myproxy context=sip username=myuser secret=mypass fromuser=myuser fromdomain=mydomain [user1] type=friend host=dynamic defaultip=default.IP username=user1 secret=secret1 dtmfm...

...; Couldn't connect to the demo site exten => 500,4,Goto(s,6) ; Return to the start over message. [sip-unauthorized] ;An important point here, if you do not have a sip aware ;firewall and are just using port forwarding then ensure ;that your context points to somewhere like invalidcalls. ;If you do not do this then someone could call one of your ;extensions direct from the Internet. If you had an FXO card ;in the machine, this could lead to them being able to make PSTN calls!! ;[from http://www.automated.it/guidetoasterisk.htm#_Toc49248767] exten => s,1,Answer exten...

I am configuring an asterisk server and I want to test the incoming configuration with my FXS handsets. I have the FXS lines able to call eachother and they can connect out the FXO lines. I changed the context for the FXS lines to "incoming" so that they would be able to test the setup for incoming calls. For the incoming context I have: [incoming] exten => s,1,Wait(1) exten

This is release 0.9.27 of Wine, a free implementation of Windows on Unix. What's new in this release: - Better support for noexec kernels. - Better Dwarf support in dbghelp. - Several Winsock fixes. - Various code cleanups. - Lots of bug fixes. Because of lags created by using mirrors, this message may reach you before the release is available at the public sites. The sources will