Actually, I did the test myself. Blink client does not consider "chat call" as 
an active call and hence not transferable.
As the client already supports transfer of audio/video calls, how easy it is to 
enable the same for chat calls.

Please advise.
Thanks
Pranathi

-----Original Message-----
From: Pranathi Venkatayogi 
Sent: Wednesday, May 10, 2017 12:48 PM
To: 'Blink Support Forum' <blink@lists.ag-projects.com>
Cc: 'Adrian Georgescu' <a...@ag-projects.com>; Mick McGrellis 
<mmcgrel...@cyracom.com>
Subject: Blink on MS Windows does not send invite on REFER

Attaching small-sized relevant logs. CallId is: 
3135dc8d7bba4165b9de7c43dbb47c86 The client does not send "Invite" to referred 
party. 

What am I missing here.

Thanks
Pranathi

-----Original Message-----
From: Pranathi Venkatayogi
Sent: Tuesday, May 09, 2017 4:59 PM
To: 'Blink Support Forum' <blink@lists.ag-projects.com>
Cc: 'Adrian Georgescu' <a...@ag-projects.com>; Mick McGrellis 
<mmcgrel...@cyracom.com>
Subject: Blink on MS Windows does not send invite on REFER

Hi,
  From Kamailio I am sending "refer" to blink client to talk to sip address 
also served by a blink client. 
  What I am seeing is the client does all the necessary things - sending 
NOTITY, BYEing existing call, but does not issue new INVITE to the referred sip 
address. 

  Attached is the sip trace and core library trace. 
  
  Can someone point to what is a miss here. Should I be specifying 
"method=invite" in the Refer-To below?
  
  Something strange is out-of-context the client sends 180 ringing to some 
weird call that does not exist at all.

REFER sip:71594386@10.11.200.59:49376 SIP/2.0
Via: SIP/2.0/UDP 
10.99.52.17;branch=z9hG4bKe202.381f7c53000000000000000000000000.0
To: 
<sip:span...@devtranslation.sms-test.cyracom.com>;tag=d5dc6387cc90420a8e13420680735d0b
From: 
<sip:cu...@devtranslation.sms-test.cyracom.com>;tag=769084f759004d76a80df05519884f9f
CSeq: 1 REFER
Call-ID: 81cf806b48cf4c4facff9d95b1c8125b
Max-Forwards: 70
Content-Length: 0
User-Agent: kamailio (4.4.5 (x86_64/linux))
Referred-By: sip:control...@kamailio.org
Refer-To: <sip:age...@devtranslation.sms-test.cyracom.com>
Contact: <sip:control...@kamailio.org:5060>

Weird Ringing message::
2017-05-09 13:50:28.145843 [blink.exe 8300]: SENDING: Packet 36, +0:00:31.060211
10.0.0.12:49376 -(SIP over UDP)-> 10.99.52.17:5060
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 
10.99.52.17;received=10.99.52.17;branch=z9hG4bK5ebc.d7c881c1000000000000000000000000.0
Call-ID: 10935f2172b30104-31423@10.99.52.17
From: <sip:control...@kamailio.org>;tag=81abcfa665f4477d891155a55da95f50-965c
To: 
<sip:71594386@10.11.200.59;alias=10.11.200.59~49376~1>;tag=3d0b5b8474fd4fdc9b8033c72eca3040
CSeq: 10 INVITE
Server: Blink 3.0.0 (Windows)
Contact: <sip:71594386@10.11.200.59:49376;alias=10.11.200.59~49376~1>
Allow: SUBSCRIBE, NOTIFY, PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, MESSAGE, 
REFER
Content-Length:  0

Thanks,
Pranathi

_______________________________________________
Blink mailing list
Blink@lists.ag-projects.com
http://lists.ag-projects.com/mailman/listinfo/blink

Reply via email to