[Blink] Blink client - wrong IP address in VIA field (SIP messages)
Adrian Georgescu
ag at ag-projects.com
Sat Apr 20 17:29:21 CEST 2013
I don't recall by heart, but this topic has been discussed on the forum before as this solution always worked. Please find this topic in Blink forum history.
Adrian
On Apr 20, 2013, at 5:24 PM, Dinu wrote:
> Hi Adrian,
>
> Can you please tell me what line must be added ?
>
> Thanks,
> Dinu
>
> On 20.04.2013 18:23, Adrian Georgescu wrote:
>> We do not know if there will be afix, but you can make it work today by adding a line in the asterisk config.
>>
>> Adrian
>>
>> On Apr 20, 2013, at 5:11 PM, Dinu wrote:
>>
>>> So will be a fix for this issue ?
>>>
>>> On 19.04.2013 10:06, Saúl Ibarra Corretgé wrote:
>>>> Hi,
>>>>
>>>> Yes, the IP address in the Via header is not correct, this is known issue. However, as you can see, rport (RFC 3581) is being used so your IP PBX should be sending replies to the received IP/port, not the ones advertised in the Via header.
>>>>
>>>> On Apr 19, 2013, at 8:26 AM, Dinu G wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> I'm using your latest Blink lite version on a windows 7 (64 bit) OS PC which has 2 interfaces (WAN and LAN).
>>>>> I'm trying to register a client to an IP PBX from the LAN but the registration fails. The PC has IP address 10.0.49.235 and the PBX 10.0.49.231.
>>>>>
>>>>> From the logs I've noticed the VIA field is set wrong , is set
>>>>>
>>>>> REGISTER sip:10.0.49.231 SIP/2.0
>>>>> Via: SIP/2.0/UDP [WAN_IP]:56583;rport;branch=z9hG4bKPj72aed0253fb5429e8b09a370b8dda0c3
>>>>> Max-Forwards: 70
>>>>> From: "blink" <sip:1112 at 10.0.49.231>;tag=f70484bf6fb04fc1b966bc0503f063e5
>>>>> To: "blink" <sip:1112 at 10.0.49.231>
>>>>> Contact: <sip:54193206 at 10.0.49.235:56583>;+sip.instance="<urn:uuid:42646514-ac34-4925-ace0-6f282236b773>"
>>>>> Call-ID: c2e5cb47c9cf4cddbf4fa805f22e235f
>>>>> CSeq: 1 REGISTER
>>>>> Expires: 600
>>>>> Supported: gruu
>>>>> User-Agent: Blink 0.3.0 (Windows)
>>>>> Content-Length: 0
>>>>> 47882107mS SIP Reg/Opt Rx: phone
>>>>> REGISTER sip:10.0.49.231 SIP/2.0
>>>>> Via: SIP/2.0/UDP [WAN_IP]:56583;rport;branch=z9hG4bKPj72aed0253fb5429e8b09a370b8dda0c3
>>>>> Max-Forwards: 70
>>>>> From: "blink" <sip:1112 at 10.0.49.231>;tag=f70484bf6fb04fc1b966bc0503f063e5
>>>>> To: "blink" <sip:1112 at 10.0.49.231>
>>>>> Contact: <sip:54193206 at 10.0.49.235:56583>;+sip.instance="<urn:uuid:42646514-ac34-4925-ace0-6f282236b773>"
>>>>> Call-ID: c2e5cb47c9cf4cddbf4fa805f22e235f
>>>>> CSeq: 1 REGISTER
>>>>> Expires: 600
>>>>> Supported: gruu
>>>>> User-Agent: Blink 0.3.0 (Windows)
>>>>> Content-Length: 0
>>>>> 47882107mS Sip: SIPDialog c768fc70 created, size 1
>>>>> 47882107mS Sip: SIP REG: Remote worker. No remote worker license for user Extn1112.
>>>> Looks like this has nothing to do with the Via header.
>>>>
>>>>> 47882107mS SIP Reg/Opt Tx: phone
>>>>> SIP/2.0 606 Not Acceptable
>>>>> Via: SIP/2.0/UDP [WAN_IP]:56583;rport;branch=z9hG4bKPj72aed0253fb5429e8b09a370b8dda0c3
>>>>> From: "blink" <sip:1112 at 10.0.49.231>;tag=f70484bf6fb04fc1b966bc0503f063e5
>>>>> To: "blink" <sip:1112 at 10.0.49.231>;tag=6ad6b1941e96d205
>>>>> Call-ID: c2e5cb47c9cf4cddbf4fa805f22e235f
>>>>> CSeq: 1 REGISTER
>>>>> User-Agent: IP Office 9.0 (107558)
>>>>> Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,REFER,NOTIFY,INFO,SUBSCRIBE,REGISTER,PUBLISH
>>>>> Supported: timer
>>>>> Server: IP Office 9.0 (107558)
>>>>> Content-Length: 0
>>>>> 47882107mS SIP Tx: UDP 10.0.49.231:5060 -> 10.0.49.235:56583
>>>>> SIP/2.0 606 Not Acceptable
>>>>> Via: SIP/2.0/UDP [WAN_IP]:56583;rport;branch=z9hG4bKPj72aed0253fb5429e8b09a370b8dda0c3
>>>>> From: "blink" <sip:1112 at 10.0.49.231>;tag=f70484bf6fb04fc1b966bc0503f063e5
>>>>> To: "blink" <sip:1112 at 10.0.49.231>;tag=6ad6b1941e96d205
>>>>> Call-ID: c2e5cb47c9cf4cddbf4fa805f22e235f
>>>>> CSeq: 1 REGISTER
>>>>> User-Agent: IP Office 9.0 (107558)
>>>>> Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,REFER,NOTIFY,INFO,SUBSCRIBE,REGISTER,PUBLISH
>>>>> Supported: timer
>>>>> Server: IP Office 9.0 (107558)
>>>>> Content-Length: 0
>>>>>
>>>>> It seems there is an issue with the Blink client as the zoiper or x-lite client does not have this issue.
>>>>>
>>>>> Regards,
>>>>> Dinu _______________________________________________
>>>>> Blink mailing list
>>>>> Blink at lists.ag-projects.com
>>>>> http://lists.ag-projects.com/mailman/listinfo/blink
>>>> --
>>>> Saúl Ibarra Corretgé
>>>> AG Projects
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> 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
>
More information about the Blink
mailing list