[Blink] Digest user

[Adrian Georgescu]

Malcolm,

Blink was designed to work against IETF based SIP implementations.

Related to the setup of the fixed IP address question, people who do  
need such thing they also need many other things as well in practice.  
It is the pandora box of interoperability problems when you try to use  
a standards based solution against a custom setup environment with  
private VPN, custom network settings, and proprietary PBX extensions.  
What you solve in one site cannot be used in another where you bump  
into another type of problem.

As you see, the number of problems you are reporting increase by the  
day and the reasons are simply in your custom environment. For such  
environment your vendor must deliver something fine tuned for that  
environment.

Blink is meant to be used only on public internet against a public SIP  
server and not private corporate environments with custom PBX  
solutions, these solutions always need custom SIP device  
implementations.

Adrian


On Apr 30, 2010, at 8:52 AM, Malcolm Caldwell wrote:

> Hi Adrian,
>
> CISCO do claim to support third party SIP clients, and I have  
> registered softphones against it in the past.
>
> I don’t know why in this case there is no SDP, and I will look into  
> this further.
>
>
>
> From: Adrian Georgescu <ag at ag-projects.com>
> Reply-To: <blink at lists.ag-projects.com>
> Date: Fri, 30 Apr 2010 08:47:57 +0200
> To: <blink at lists.ag-projects.com>
> Subject: Re: [Blink] Digest user
>
>
> On Apr 30, 2010, at 1:51 AM, Malcolm Caldwell wrote:
>
>> 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-47099214
>>  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/>
>
> There is no SDP with any type of supported media in this Invite.
>
> You are using Blink against a non-standard compliant corporate PBX  
> solution that works only with approved phone devices by Cisco.
>
> What do you want to see happening except rejecting it?
>
> Adrian
>
>
> _______________________________________________
> 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/07f1487d/attachment.html>