Re: could not register (method not allowed)

Am 28.07.2014 um 22:57 schrieb Eugen Dedu:
> On 28/07/14 22:48, Thomas Hill wrote:
>> Am 28.07.2014 um 22:42 schrieb Eugen Dedu:
>>> On 28/07/14 22:38, Thomas Hill wrote:
>>>> Am 28.07.2014 um 21:54 schrieb Eugen Dedu:
>>>>> On 28/07/14 20:50, Thomas Hill wrote:
>>>>>> Am 26.07.2014 um 15:26 schrieb Eugen Dedu:
>>>>>>> On 26/07/14 11:59, Thomas Hill wrote:
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> I am trying to use ekiga on the same machine as my asterisk
>>>>>>>> server is
>>>>>>>> running on.
>>>>>>>> (note: my asterisk configuration is working fine as I can
>>>>>>>> register the
>>>>>>>> account from a windows laptop using X-lite. I would however 
>>>>>>>> like to
>>>>>>>> switch to ekiga and have it running on my linux server which is up
>>>>>>>> 24/7).
>>>>>>>>
>>>>>>>> I am aware that asterisk and ekiga can not both be using port
>>>>>>>> 5060 and
>>>>>>>> therefore changed the port ekiga is using to 5061 using the
>>>>>>>> gconf-editor. However still no success.
>>>>>>>
>>>>>>> First of all, please use ekiga version 4, it is better.
>>>>>>>
>>>>>>> Otherwise, your log is too short, it does not present the REGISTER
>>>>>>> exchange to see where the problem is.
>>>>>
>>>>> You do not have any account in ekiga.  If you wish to call an account
>>>>> on ekiga.net, like 500, you need an ekiga.net account.
>>>>>
>>>>> Note also that you need to have "Network detection" (or smth like
>>>>> that) on in Preferences.
>>>>>
>>>> okay. Set network detection to on in preferences. Now I am able to
>>>> receive incoming calls; however outgoing calls do not work and I am
>>>> receiving message remote user busy. When registering using the SAME
>>>> account from my Windows laptop I can place outgoing calls with no
>>>> problem. Can you please point me in the right direction here as well?
>>>> Thanks a lot in advance for your continued help.
>>>
>>> You need to give me a new log...  Use gzip or zip to compress it.
>>>
>> when trying to create another log I am now getting segmentation fault
>
> Try -d 3, elsewhere -d 2, elsewhere -d 1, hoping that the crash will 
> disappear.
>
okay, now I could also place an outgoing call - GREAT!
Observation: I am only able to do this when
a) starting ekiga from the command line in a root terminal session (when 
just selecting ekiga from the menu I am getting remote computer busy 
when trying to place the call -> strange, isn't it?)
b) when placing the first call I need to append the IP address to the 
extension for it to work the first time. On consecutive calls I do not 
need to enter the full string including the IP again, just the extension 
I want to call suffices...