[Blink] Digest user

Malcolm Caldwell malcolm.caldwell at cdu.edu.au
Fri Apr 30 01:51:35 CEST 2010


Hi Adrian,

I now have the log from my work, although the packets are not the same as I
say yesterday.  (I wish I had saved them).  However, calls are not working,
and this trace shows that:

RECEIVED: Packet 19, +0:03:05.878643
2010-04-30 09:01:52.947054: SIP.SERVER.IP.ADDR:5060 -(SIP over UDP)->
MY.MAC.IP.ADDR:59181
INVITE sip:fcuzryxa at MY.MAC.IP.ADDR:59181 SIP/2.0
Date: Thu, 29 Apr 2010 23:31:54 GMT
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER,
SUBSCRIBE, NOTIFY
From: 
<sip:YYYY at SIP.SERVER.IP.ADDR>;tag=94d7ad56-fdc6-40a9-bd8e-772b8995b8b6-47099
214
Allow-Events: presence
Supported: timer,resource-priority,replaces
Min-SE:  1800
Remote-Party-ID: 
<sip:YYYY at 138.80.6.4;x-cisco-callback-number=YYYY>;party=calling;screen=yes;
privacy=off
Content-Length: 0
User-Agent: Cisco-CUCM7.0
To: <sip:XXXX at MY.MAC.IP.ADDR>
Contact: <sip:YYYY at SIP.SERVER.IP.ADDR:5060>;video;audio
Expires: 180
Call-ID: 63b1d680-bda116ea-b7-406508a at SIP.SERVER.IP.ADDR
Via: SIP/2.0/UDP SIP.SERVER.IP.ADDR:5060;branch=z9hG4bKc721379491
CSeq: 101 INVITE
Send-Info: conference
Max-Forwards: 70
Alert-Info: <file://Bellcore-dr1/>

SENDING: Packet 20, +0:03:05.884585
2010-04-30 09:01:52.952996: MY.MAC.IP.ADDR:59181 -(SIP over UDP)->
SIP.SERVER.IP.ADDR:5060
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 
SIP.SERVER.IP.ADDR:5060;received=SIP.SERVER.IP.ADDR;branch=z9hG4bKc721379491
Call-ID: 63b1d680-bda116ea-b7-406508a at SIP.SERVER.IP.ADDR
From: 
<sip:XXXX at SIP.SERVER.IP.ADDR>;tag=94d7ad56-fdc6-40a9-bd8e-772b8995b8b6-47099
214
To: <sip:YYYY at MY.MAC.IP.ADDR>
CSeq: 101 INVITE
Server: blink-0.18.1
Content-Length:  0

SENDING: Packet 21, +0:03:05.885202
2010-04-30 09:01:52.953613: MY.MAC.IP.ADDR:59181 -(SIP over UDP)->
SIP.SERVER.IP.ADDR:5060
SIP/2.0 488 Not Acceptable Here
Via: SIP/2.0/UDP 
SIP.SERVER.IP.ADDR:5060;received=SIP.SERVER.IP.ADDR;branch=z9hG4bKc721379491
Call-ID: 63b1d680-bda116ea-b7-406508a at SIP.SERVER.IP.ADDR
From: 
<sip:YYY at SIP.SERVER.IP.ADDR>;tag=94d7ad56-fdc6-40a9-bd8e-772b8995b8b6-470992
14
To: <sip:XXXX at MY.MAC.IP.ADDR>;tag=BWDW2PzZBclDCna1Okj-cGhVYo-EA7kf
CSeq: 101 INVITE
Server: blink-0.18.1
Content-Length:  0


I am not sure what blink finds unacceptable.

As to:  ³We had this and we took it out as people were no able to understand
what is going on when it did not work because they set a wrong IP address.²:
There are more options in blink than in any other SIP client I have ever
seen.  Many of those will break blink as well.  Why can¹t the IP address go
in as an ³advanced² option, with some kind of scary name like ³Non-standard
bind address².  And add a ³reset to default² button.  I am no UI expert, but
I think it might work.


From: Adrian Georgescu <ag at ag-projects.com>
Reply-To: <blink at lists.ag-projects.com>
Date: Thu, 29 Apr 2010 16:29:13 +0200
To: <blink at lists.ag-projects.com>
Subject: Re: [Blink] Digest user


On Apr 29, 2010, at 4:09 PM, Malcolm Caldwell wrote:

> 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?

We had this and we took it out as people were no able to understand what is
going on when it did not work because they set a wrong IP address.

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

Blink is designed to run on public Internet like Skype.

Indeed some advanced features can be lost but compared with the gains ....

Adrian



> 
> 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
> _______________________________________________
> 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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ag-projects.com/pipermail/blink/attachments/20100430/85b628ee/attachment.html>


More information about the Blink mailing list