[Blink] How to add contact and see the presence status of the account?

Yuming Zheng zhengyumingnanjing at gmail.com
Fri Feb 1 07:33:31 CET 2013


PING 85.17.186.7 (85.17.186.7): 56 data bytes
64 bytes from 85.17.186.7: icmp_seq=0 ttl=47 time=321.015 ms
64 bytes from 85.17.186.7: icmp_seq=1 ttl=47 time=319.978 ms
64 bytes from 85.17.186.7: icmp_seq=2 ttl=47 time=314.562 ms
64 bytes from 85.17.186.7: icmp_seq=3 ttl=47 time=315.900 ms
64 bytes from 85.17.186.7: icmp_seq=4 ttl=47 time=314.369 ms
64 bytes from 85.17.186.7: icmp_seq=5 ttl=47 time=311.976 ms
64 bytes from 85.17.186.7: icmp_seq=6 ttl=47 time=316.642 ms
^C
--- 85.17.186.7 ping statistics ---
7 packets transmitted, 7 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 311.976/316.349/321.015/2.963 ms


2013/2/1 Yuming Zheng <zhengyumingnanjing at gmail.com>

> PING 81.23.228.129 (81.23.228.129): 56 data bytes
> 64 bytes from 81.23.228.129: icmp_seq=0 ttl=47 time=425.537 ms
> 64 bytes from 81.23.228.129: icmp_seq=1 ttl=47 time=421.851 ms
> 64 bytes from 81.23.228.129: icmp_seq=2 ttl=47 time=424.498 ms
> 64 bytes from 81.23.228.129: icmp_seq=3 ttl=47 time=422.074 ms
> 64 bytes from 81.23.228.129: icmp_seq=4 ttl=47 time=408.391 ms
> 64 bytes from 81.23.228.129: icmp_seq=5 ttl=47 time=404.770 ms
> 64 bytes from 81.23.228.129: icmp_seq=6 ttl=47 time=408.804 ms
> 64 bytes from 81.23.228.129: icmp_seq=7 ttl=47 time=410.108 ms
> 64 bytes from 81.23.228.129: icmp_seq=8 ttl=47 time=424.665 ms
> 64 bytes from 81.23.228.129: icmp_seq=9 ttl=47 time=410.240 ms
> 64 bytes from 81.23.228.129: icmp_seq=10 ttl=47 time=419.216 ms
> 64 bytes from 81.23.228.129: icmp_seq=11 ttl=47 time=410.845 ms
> 64 bytes from 81.23.228.129: icmp_seq=12 ttl=47 time=411.619 ms
> 64 bytes from 81.23.228.129: icmp_seq=13 ttl=47 time=408.834 ms
> 64 bytes from 81.23.228.129: icmp_seq=14 ttl=47 time=422.183 ms
> 64 bytes from 81.23.228.129: icmp_seq=15 ttl=47 time=417.830 ms
> ^C
> --- 81.23.228.129 ping statistics ---
> 16 packets transmitted, 16 packets received, 0.0% packet loss
> round-trip min/avg/max/stddev = 404.770/415.717/425.537/6.896 ms
>
>
> 2013/2/1 Yuming Zheng <zhengyumingnanjing at gmail.com>
>
>> Sure, Blink uses only TCP or TLS transports for signaling, Presence
>> Agent must use TCP/TLS.
>>
>> Always Use My Proxy checked on,
>>  Primary Proxy set to proxy.sipthor.net:5060;transport=tcp
>> and Alternate Proxy set to proxy.sipthor.net:5061;transport=tls
>>
>> GOT: Registration failed: Request Timeout(408)
>>
>> Activity:
>> 2013-02-01 14:10:56   Initializing SIP SIMPLE Client SDK 0.31.1, core
>> version 160
>>
>> 2013-02-01 14:10:56   Build 9275 from January 11th, 2012
>>
>> 2013-02-01 14:10:56   Acoustic Echo Canceller is enabled
>>
>> 2013-02-01 14:11:00   Account('sunhong at sip2sip.info') activated
>>
>> 2013-02-01 14:11:00   SIP User Agent Blink Lite 2.0.2 (MacOSX)
>>
>> 2013-02-01 14:11:00   SIP Device ID
>> urn:uuid:c1bfefa0-640c-451a-b443-cd4e6cd663ba
>>
>> 2013-02-01 14:11:07   Using XCAP root https://xcap.sipthor.net/xcap-rootfor account
>> sunhong at sip2sip.info
>>
>> 2013-02-01 14:11:07   XCAP server capabilities: org.openxcap.watchers,
>> rls-services, resource-lists, xcap-caps, org.openxcap.dialog-rules,
>> org.openmobilealliance.pres-content, org.openxcap.purge,
>> org.openmobilealliance.pres-rules, pidf-manipulation, pres-rules,
>> org.openmobilealliance.xcap-directory
>>
>> 2013-02-01 14:11:11   Account('sunhong at sip2sip.info') failed to register
>> at sip:85.17.186.7:5060;transport=tcp: Request Timeout (408)
>>
>> 2013-02-01 14:11:21   Account('sunhong at sip2sip.info') failed to register
>> at sip:81.23.228.129:5060;transport=tcp: Request Timeout (408)
>>
>> 2013-02-01 14:11:22   Account('sunhong at sip2sip.info') failed to
>> register: No more routes to try (retrying in 1.42 seconds)
>>
>> 2013-02-01 14:11:33   Account('sunhong at sip2sip.info') failed to register
>> at sip:81.23.228.129:5060;transport=tcp: Request Timeout (408)
>>
>> 2013-02-01 14:11:43   Account('sunhong at sip2sip.info') failed to register
>> at sip:85.17.186.7:5060;transport=tcp: Request Timeout (408)
>>
>> 2013-02-01 14:11:43   Account('sunhong at sip2sip.info') failed to
>> register: No more routes to try (retrying in 3.92 seconds)
>>
>> 2013-02-01
>>
>>
>>
>> and SIP:
>>
>> 2013-02-01 14:18:28.523987: DNS lookup A proxy.sipthor.net succeeded,
>> ttl=30: 81.23.228.129, 85.17.186.7
>>
>>
>> SENDING: Packet 99, +0:07:27.830330
>>
>> 2013-02-01 14:18:28.610108: 172.22.198.48:54670 -(SIP over tcp)->
>> 81.23.228.129:5060
>>
>> *REGISTER sip:sip2sip.info SIP/2.0*
>>
>> Via: SIP/2.0/tcp 172.22.198.48:54670
>> ;rport;branch=z9hG4bKPjhWrZ3biubCmlddbRMUM0glWg61Clbg9G
>>
>> Max-Forwards: 70
>>
>> From: "sunhong" <sip:sunhong at sip2sip.info
>> >;tag=rS7m0pbuqcXp9JZ48vxemUsJZb3wXj9A
>>
>> To: "sunhong" <sip:sunhong at sip2sip.info>
>>
>> Contact: <sip:59762038 at 172.22.198.48:54666
>> ;transport=tcp>;+sip.instance="<urn:uuid:c1bfefa0-640c-451a-b443-cd4e6cd663ba>"
>>
>> Call-ID: 8Kt2IkEphuR9wlDUFZgR6cJeaETUiv1P
>>
>> CSeq: 1 REGISTER
>>
>> Expires: 600
>>
>> Supported: gruu
>>
>> User-Agent: Blink Lite 2.0.2 (MacOSX)
>>
>> Content-Length:  0
>>
>>
>> SENDING: Packet 100, +0:07:37.959864
>>
>> 2013-02-01 14:18:38.739642: 172.22.198.48:54669 -(SIP over tcp)->
>> 85.17.186.7:5060
>>
>> *REGISTER sip:sip2sip.info SIP/2.0*
>>
>> Via: SIP/2.0/tcp 172.22.198.48:54669
>> ;rport;branch=z9hG4bKPj5csB.IhTc9GgwJliDGhsG7XoiwgTK08E
>>
>> Max-Forwards: 70
>>
>> From: "sunhong" <sip:sunhong at sip2sip.info
>> >;tag=kFqN0wwkrFmKkObGeeI8iS9HhHKQqcrf
>>
>> To: "sunhong" <sip:sunhong at sip2sip.info>
>>
>> Contact: <sip:59762038 at 172.22.198.48:54666
>> ;transport=tcp>;+sip.instance="<urn:uuid:c1bfefa0-640c-451a-b443-cd4e6cd663ba>"
>>
>> Call-ID: ikLy1jbod5DzTpD83g-NbCvDVuztGQMQ
>>
>> CSeq: 1 REGISTER
>>
>> Expires: 600
>>
>> Supported: gruu
>>
>> User-Agent: Blink Lite 2.0.2 (MacOSX)
>>
>> Content-Length:  0
>>
>>
>> 2013-02-01 14:18:41.528766: DNS lookup A proxy.sipthor.net succeeded,
>> ttl=30: 81.23.228.129, 85.17.186.7
>>
>> 2013-02-01 14:18:46.488119: DNS lookup A proxy.sipthor.net succeeded,
>> ttl=30: 81.23.228.129, 85.17.186.7
>>
>> 2013-02-01 14:18:48.077780: DNS lookup A proxy.sipthor.net succeeded,
>> ttl=30: 81.23.228.129, 85.17.186.7
>>
>> 2013-02-01 14:18:48.912154: DNS lookup A proxy.sipthor.net succeeded,
>> ttl=30: 81.23.228.129, 85.17.186.7
>>
>> 2013-02-01 14:19:10.785555: DNS lookup A proxy.sipthor.net succeeded,
>> ttl=30: 85.17.186.7, 81.23.228.129
>>
>>
>>
>>
>> 2013/1/31 Adrian Georgescu <ag at ag-projects.com>
>>
>>> You should use TCP for outbound proxy.
>>>
>>> Adrian
>>>
>>> On Jan 31, 2013, at 4:01 AM, Yuming Zheng wrote:
>>>
>>> FYI,
>>>
>>> Activity logs after starting the clients:
>>>
>>> 013-01-31 10:56:07   Initializing SIP SIMPLE Client SDK 0.31.1, core
>>> version 160
>>> 2013-01-31 10:56:07   Build 9275 from January 11th, 2012
>>> 2013-01-31 10:56:07   Acoustic Echo Canceller is enabled
>>> 2013-01-31 10:56:11   Account('sunhong at sip2sip.info') activated
>>> 2013-01-31 10:56:11   SIP User Agent Blink Lite 2.0.2 (MacOSX)
>>> 2013-01-31 10:56:11   SIP Device ID
>>> urn:uuid:c1bfefa0-640c-451a-b443-cd4e6cd663ba
>>> 2013-01-31 10:56:12   Account('sunhong at sip2sip.info') registered
>>> contact "sip:68352741 at 172.22.198.67:63514" at 85.17.186.7:5060;transport=udp
>>> for 600 seconds
>>> 2013-01-31 10:56:13   Using XCAP root https://xcap.sipthor.net/xcap-rootfor account
>>> sunhong at sip2sip.info
>>> 2013-01-31 10:56:13   XCAP server capabilities: org.openxcap.watchers,
>>> rls-services, resource-lists, xcap-caps, org.openxcap.dialog-rules,
>>> org.openmobilealliance.pres-content, org.openxcap.purge,
>>> org.openmobilealliance.pres-rules, pidf-manipulation, pres-rules,
>>> org.openmobilealliance.xcap-directory
>>>
>>> AND XCAP:
>>> 2013-01-31 10:56:11.048389 XCAP manager of account sunhong at sip2sip.infochanged state from Stopped to Initializing
>>> 2013-01-31 10:56:13.806963 Using XCAP root
>>> https://xcap.sipthor.net/xcap-root for account sunhong at sip2sip.info
>>> 2013-01-31 10:56:13.806963 XCAP server capabilities:
>>> org.openxcap.watchers, rls-services, resource-lists, xcap-caps,
>>> org.openxcap.dialog-rules, org.openmobilealliance.pres-content,
>>> org.openxcap.purge, org.openmobilealliance.pres-rules, pidf-manipulation,
>>> pres-rules, org.openmobilealliance.xcap-directory
>>> 2013-01-31 10:56:13.812392 XCAP manager of account sunhong at sip2sip.infochanged state from Initializing to Fetching
>>> 2013-01-31 10:56:18.160254 XCAP manager of account sunhong at sip2sip.infochanged state from Fetching to Updating
>>> 2013-01-31 10:56:18.168717 XCAP manager of account sunhong at sip2sip.infochanged state from Updating to Insync
>>> 2013-01-31 10:56:18.190933 XCAP manager of account sunhong at sip2sip.infochanged state from Insync to Updating
>>> 2013-01-31 10:56:18.193079 XCAP manager of account sunhong at sip2sip.infochanged state from Updating to Insync
>>> 2013-01-31 10:56:24.047081 XCAP manager of account sunhong at sip2sip.infochanged state from Insync to Fetching
>>> 2013-01-31 10:56:29.097763 XCAP manager of account sunhong at sip2sip.infochanged state from Fetching to Insync
>>> 2013-01-31 10:58:27.478649 XCAP manager of account sunhong at sip2sip.infochanged state from Insync to Fetching
>>> 2013-01-31 10:58:31.744476 XCAP manager of account sunhong at sip2sip.infochanged state from Fetching to Insync
>>>
>>>
>>>
>>>
>>> 2013/1/31 Yuming Zheng <zhengyumingnanjing at gmail.com>
>>>
>>>> Check the Availability settings, Publish My Availability is setting to
>>>> true.
>>>> And after digging deeper.When modify the presenct status from Available
>>>> to Busy,
>>>> A SUBSCRIBE sip message send out
>>>> .But when try Add Contact or modify an exist friend,cannot see any SIP
>>>> message send out.
>>>>
>>>> My setting is:
>>>>
>>>> Sip Signaling
>>>> Receive Incoming Calls checked on,
>>>> Always Use My Proxy  checked on,
>>>> Primary Proxy set to proxy.sipthor.net:5060;transport=udp
>>>> shou we use tcp or tls here?
>>>>
>>>> Availability
>>>> Publish My Availability checked on,
>>>>
>>>> XCAP Storage
>>>> Enabled checked on,
>>>> Root URI set to https://xcap.sipthor.net/xcap-root/
>>>>
>>>> NAT Traversal
>>>> Use ICE checked on,
>>>> Use MSRP Relay For outbound not checked ,do not know what should be
>>>> with the RSRP Relay item below it,
>>>> STUN Server set to stun.xten.com and port is 3478.
>>>>
>>>> Best Regard,
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> 2013/1/30 Adrian Georgescu <ag at ag-projects.com>
>>>>
>>>>>
>>>>> On Jan 30, 2013, at 10:45 AM, Yuming Zheng wrote:
>>>>>
>>>>> Hello Sir,
>>>>>
>>>>> I am using blink lite 2.0.2,when I add my friend of sip2sip.info,he
>>>>> can appear on the group.
>>>>> and even I can set the avatar image of my friend.
>>>>>
>>>>> But I can not see the presence status of my friend.Should he receive a
>>>>> new contact requests
>>>>> with my subscription?
>>>>>
>>>>>
>>>>> Yes, he should.
>>>>>
>>>>> Or this feature is not supported by blink lite?
>>>>>
>>>>>
>>>>> It is supported.  Can you check if presence enabled for your account
>>>>> in its advances properties?
>>>>>
>>>>> If it still doe snot work, please paste the messages from the Activity
>>>>> logs after starting the clients to support at ag-projects.com and we can
>>>>> dig deeper into the cause.
>>>>>
>>>>>
>>>>> Best Regard,
>>>>>
>>>>> Frank.zheng
>>>>> _______________________________________________
>>>>> 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/20130201/f30568a4/attachment.html>


More information about the Blink mailing list