[Blink] router configuration?

Thu Jan 27 23:30:39 CET 2011

Philippe,

Blink sends the requests out and it gets no replies back. Is your router or your provider that blocks the SIP requests. Google for SIP-ALG problem, if the problem is in your router you may be able to fix it by disabling the so called 'SIP support' in the router.

Regards,
Adrian

On Jan 27, 2011, at 9:32 PM, Philippe Faes wrote:

> Hi Adrian,
> 
> I only have Blink turned on. No other SIP clients at the same time.
> In the log, I get:
> 
> SENDING: Packet 41, +0:01:41.066466
> 2011-01-27 21:29:47.899168: 10.0.0.22:56532 -(SIP over UDP)-> 195.130.154.224:5060
> REGISTER sip:195.130.154.224 SIP/2.0
> 
> SENDING: Packet 42, +0:02:18.272735
> 2011-01-27 21:30:25.105437: 10.0.0.22:56532 -(SIP over UDP)-> 195.130.154.224:5060
> REGISTER sip:195.130.154.224 SIP/2.0
> 
> SENDING: Packet 43, +0:02:18.772830
> 2011-01-27 21:30:25.605532: 10.0.0.22:56532 -(SIP over UDP)-> 195.130.154.224:5060
> REGISTER sip:195.130.154.224 SIP/2.0
> 
> SENDING: Packet 44, +0:02:19.773553
> 2011-01-27 21:30:26.606255: 10.0.0.22:56532 -(SIP over UDP)-> 195.130.154.224:5060
> REGISTER sip:195.130.154.224 SIP/2.0
> 
> SENDING: Packet 45, +0:02:21.774014
> 2011-01-27 21:30:28.606716: 10.0.0.22:56532 -(SIP over UDP)-> 195.130.154.224:5060
> REGISTER sip:195.130.154.224 SIP/2.0
> 
> SENDING: Packet 46, +0:02:25.774425
> 2011-01-27 21:30:32.607127: 10.0.0.22:56532 -(SIP over UDP)-> 195.130.154.224:5060
> REGISTER sip:195.130.154.224 SIP/2.0
> 
> SENDING: Packet 47, +0:02:41.610731
> 2011-01-27 21:30:48.443433: 10.0.0.22:56532 -(SIP over UDP)-> 195.130.154.224:5060
> SUBSCRIBE sip:92657142 at 195.130.154.224 SIP/2.0
> 
> SENDING: Packet 48, +0:02:42.111221
> 2011-01-27 21:30:48.943923: 10.0.0.22:56532 -(SIP over UDP)-> 195.130.154.224:5060
> SUBSCRIBE sip:92657142 at 195.130.154.224 SIP/2.0
> 
> SENDING: Packet 49, +0:02:43.110705
> 2011-01-27 21:30:49.943407: 10.0.0.22:56532 -(SIP over UDP)-> 195.130.154.224:5060
> SUBSCRIBE sip:92657142 at 195.130.154.224 SIP/2.0
> 
> SENDING: Packet 50, +0:02:43.335338
> 2011-01-27 21:30:50.168040: 10.0.0.22:56532 -(SIP over UDP)-> 195.130.154.224:5060
> INVITE sip:+3292230230 at 195.130.154.224 SIP/2.0
> 
> SENDING: Packet 51, +0:02:43.835609
> 2011-01-27 21:30:50.668311: 10.0.0.22:56532 -(SIP over UDP)-> 195.130.154.224:5060
> INVITE sip:+3292230230 at 195.130.154.224 SIP/2.0
> 
> SENDING: Packet 52, +0:02:44.835924
> 2011-01-27 21:30:51.668626: 10.0.0.22:56532 -(SIP over UDP)-> 195.130.154.224:5060
> INVITE sip:+3292230230 at 195.130.154.224 SIP/2.0
> 
> SENDING: Packet 53, +0:02:45.111347
> 2011-01-27 21:30:51.944049: 10.0.0.22:56532 -(SIP over UDP)-> 195.130.154.224:5060
> SUBSCRIBE sip:92657142 at 195.130.154.224 SIP/2.0
> 
> SENDING: Packet 54, +0:02:46.836276
> 2011-01-27 21:30:53.668978: 10.0.0.22:56532 -(SIP over UDP)-> 195.130.154.224:5060
> INVITE sip:+3292230230 at 195.130.154.224 SIP/2.0
> 
> SENDING: Packet 55, +0:02:49.112247
> 2011-01-27 21:30:55.944949: 10.0.0.22:56532 -(SIP over UDP)-> 195.130.154.224:5060
> SUBSCRIBE sip:92657142 at 195.130.154.224 SIP/2.0
> 
> SENDING: Packet 56, +0:02:50.835784
> 2011-01-27 21:30:57.668486: 10.0.0.22:56532 -(SIP over UDP)-> 195.130.154.224:5060
> INVITE sip:+3292230230 at 195.130.154.224 SIP/2.0
> 
> SENDING: Packet 57, +0:02:53.111754
> 2011-01-27 21:30:59.944456: 10.0.0.22:56532 -(SIP over UDP)-> 195.130.154.224:5060
> SUBSCRIBE sip:92657142 at 195.130.154.224 SIP/2.0
> 
> SENDING: Packet 58, +0:02:57.112514
> 2011-01-27 21:31:03.945216: 10.0.0.22:56532 -(SIP over UDP)-> 195.130.154.224:5060
> SUBSCRIBE sip:92657142 at 195.130.154.224 SIP/2.0
> 
> SENDING: Packet 59, +0:02:58.835680
> 2011-01-27 21:31:05.668382: 10.0.0.22:56532 -(SIP over UDP)-> 195.130.154.224:5060
> INVITE sip:+3292230230 at 195.130.154.224 SIP/2.0
> 
> SENDING: Packet 60, +0:03:01.112708
> 2011-01-27 21:31:07.945410: 10.0.0.22:56532 -(SIP over UDP)-> 195.130.154.224:5060
> SUBSCRIBE sip:92657142 at 195.130.154.224 SIP/2.0
> 
> SENDING: Packet 61, +0:03:05.113078
> 2011-01-27 21:31:11.945780: 10.0.0.22:56532 -(SIP over UDP)-> 195.130.154.224:5060
> SUBSCRIBE sip:92657142 at 195.130.154.224 SIP/2.0
> 
> SENDING: Packet 62, +0:03:09.113416
> 2011-01-27 21:31:15.946118: 10.0.0.22:56532 -(SIP over UDP)-> 195.130.154.224:5060
> SUBSCRIBE sip:92657142 at 195.130.154.224 SIP/2.0
> 
> SENDING: Packet 63, +0:03:13.114206
> 2011-01-27 21:31:19.946908: 10.0.0.22:56532 -(SIP over UDP)-> 195.130.154.224:5060
> SUBSCRIBE sip:92657142 at 195.130.154.224 SIP/2.0
> 
> SENDING: Packet 64, +0:03:14.835483
> 2011-01-27 21:31:21.668185: 10.0.0.22:56532 -(SIP over UDP)-> 195.130.154.224:5060
> INVITE sip:+3292230230 at 195.130.154.224 SIP/2.0
> 
> 
> --
> Philippe Faes
> 
> 
> 
> On Thu, Jan 27, 2011 at 6:33 PM, Adrian Georgescu <ag at ag-projects.com> wrote:
> Hi Philipe,
> 
> What do you see in the Logs window?  Go to Menu Window -> SIP -> Logs.
> 
> Adrian
> 
> On Jan 26, 2011, at 4:08 PM, Philippe Faes wrote:
> 
>> I am running Blink on my Mac. It works fine in the office network, but not in my home network (ADSL). I get timeout errors each time I try to call a phone number. I have a SIP account from a provider.
>> Another  SIP client (on my iPhone) works fine, even in my home network.
>> 
>> I might need to configure the router (opening extra ports?) , but I don't know where to look.
>> 
>> thanks
>> 
>> Philippe
>> 
>> _______________________________________________
>> 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/20110127/19cea50d/attachment.html>