[Blink] Digest user

[Malcolm Caldwell]

On 29/04/2010, at 23:18, "Adrian Georgescu" <ag at ag-projects.com> wrote:

> Blink is using for Register the IP address for which it has a  
> default route. If you use a VPN it could be that is using a  
> different IP address.

Ok, this explains why it is not working at home over a VPN.

It does not explain why it fails at my work on a direct connection.  I  
will check the logs tomorrow while at work.

> Not sure if we can support this scenario because we will loose the  
> auto detection features when the IP address and default route  
> changes which is what normal users connected to the public Internet  
> need.

Unless it can be manually changed as an advanced option but the  
default is auto detection?

That said, I know that multiple interfaces make voip difficult.

Perhaps it could just say "if there is a static route that matches,  
register using that interface's address". But can that be automated?

> Adrian
>
> On Apr 29, 2010, at 3:17 PM, Malcolm Caldwell wrote:
>
>> Hi Adrian,
>>
>>> From: Adrian Georgescu <ag at ag-projects.com>
>>> Reply-To: <blink at lists.ag-projects.com>
>>> Date: Thu, 29 Apr 2010 13:18:36 +0200
>>> To: <blink at lists.ag-projects.com>
>>> Subject: Re: [Blink] Digest user
>>>
>>> If Register succeeds this time, than Blink works as far as
>>> Authentication with different username is concerned.
>>
>> That is exactly what I think is happening.
>>
>>> About not being able to receive calls:
>>>
>>> 1. Do you see the Invite coming in Blink? Check the Logs SIP window.
>>
>> Today, when I was at work looking at this I saw invites in the  
>> logs, but
>> they did not make sense (they said our callmanager was sending  
>> INVITEs to
>> private 172.X.X.X addresses).
>>
>> Tonight I tried to register through a VPN back to work, and cannot  
>> see
>> invites.
>>
>> What I an see is that BLINK is registered on our callmanager using  
>> the wrong
>> IP address: it picked the address of the local network, not the  
>> address of
>> the VPN connection.  This can be seen in the contact header.
>>
>> So, I think that blink is registering the wrong IP address.  I will  
>> try
>> tomorrow to find out where blink was getting that 172.X.X.X private  
>> address
>> from. (I did not think I had any interfaces up with private  
>> addresses)
>>
>> Here is the REGISTER that has the wrong IP (ie not the VPN address).
>>
>> SENDING: Packet 124, +0:23:11.657543
>> 2010-04-29 22:37:18.257835: 192.168.1.129:63001 -(SIP over UDP)->
>> SIP.SERVER.IP.ADDR:5060
>> REGISTER sip:pbx1.cdu.edu.au SIP/2.0
>> Via: SIP/2.0/UDP
>> 192.168.1.129:63001;rport;branch=z9hG4bKPjbNek-zd4VY- 
>> NZlX9UElrXFUzNg4aZA3W
>> Max-Forwards: 70
>> From: "u"  
>> <sip:XXXX at server.company.com>;tag=IF455wenJp6bvknmKl.x3SSvCmtZjwag
>> To: "u" <sip:XXXX at server.company.com>
>> Contact: <sip:koajntgp at 192.168.1.129:63001>
>> Call-ID: Krpq.k245qGhckA7kTOl883wh7XAoi9P
>> CSeq: 8 REGISTER
>> Route: <sip:SIP.SERVER.IP.ADDR;lr>
>> Expires: 600
>> User-Agent: blink-0.18.1
>> Content-Length:  0
>>
>>> 2. If no INVITE comes in then you can only check in Cisco Call
>>> Manager, what does it say?
>>>
>>> Regards,
>>> Adrian
>>>
>>>
>>> On Apr 29, 2010, at 10:16 AM, Malcolm Caldwell wrote:
>>>
>>>> Hi Adrian,
>>>>
>>>> I can confirm that the new version has this feature, but for some
>>>> reason it
>>>> is not working for me.
>>>>
>>>> It works in that I can register: I can see that it is registered
>>>> both on
>>>> cisco callmanager and in the Blink UI
>>>>
>>>> What does not work is I do not receive the calls.  I am fairly sure
>>>> the
>>>> issue is with blink.
>>>>
>>>> Perhaps I should capture some logs?
>>>>
>>>>
>>>>
>>>>> From: Adrian Georgescu <ag at ag-projects.com>
>>>>> Reply-To: <blink at lists.ag-projects.com>
>>>>> Date: Tue, 13 Apr 2010 15:22:24 +0200
>>>>> To: <blink at lists.ag-projects.com>
>>>>> Subject: Re: [Blink] Digest user
>>>>>
>>>>> We will add this feature into the next release.
>>>>>
>>>>> Adrian
>>>>>
>>>>> On Apr 13, 2010, at 3:04 PM, Malcolm Caldwell wrote:
>>>>>
>>>>>> Hello,
>>>>>>
>>>>>> Is it possible to register to a sip server using a digest
>>>>>> authentication user that is different from the sip address?
>>>>>>
>>>>>> I am trying to register blink against cisco call manager.   
>>>>>> While I
>>>>>> need to register as NNNN at address.of.server.com, where NNNN is an
>>>>>> extension number, I need to authenticate as a regular user.
>>>>>>
>>>>>> Is this currently possible?
>>>>>>
>>>>>> Malcolm Caldwell
>>>>>> _______________________________________________
>>>>>> Blink mailing list
>>>>>> Blink at lists.ag-projects.com
>>>>>> http://lists.ag-projects.com/mailman/listinfo/blink
>>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Blink mailing list
>>>>> Blink at lists.ag-projects.com
>>>>> http://lists.ag-projects.com/mailman/listinfo/blink
>>>>
>>>> _______________________________________________
>>>> Blink mailing list
>>>> Blink at lists.ag-projects.com
>>>> http://lists.ag-projects.com/mailman/listinfo/blink
>>>>
>>>
>>> _______________________________________________
>>> Blink mailing list
>>> Blink at lists.ag-projects.com
>>> http://lists.ag-projects.com/mailman/listinfo/blink
>>
>> _______________________________________________
>> Blink mailing list
>> Blink at lists.ag-projects.com
>> http://lists.ag-projects.com/mailman/listinfo/blink
>>
>
> _______________________________________________
> Blink mailing list
> Blink at lists.ag-projects.com
> http://lists.ag-projects.com/mailman/listinfo/blink