[Blink] Config problems with 1&1 SIP provider

Adrian Georgescu ag at ag-projects.com
Sun Feb 27 17:10:15 CET 2011


It first glance, it looks like the SIP server of 1und1 is not able to perform NAT traversal for their SIP customers behind NAT. Most likely they expect the SIP clients to either use STUN or a SIP ALG in their border router to solve the NAT traversal. Both these techniques are poor and unreliable, 1und1 should have a properly configured SIP server instead and fix the NAT traversal for their clients automatically.

There is nothing wrong in Blink, is the SIP service at fault here, it should just work with any kind of IP address public or private without any special setup in the client side.

Adrian

On Feb 27, 2011, at 4:56 PM, Robert M. Münch wrote:

> Am 25.02.2011 um 14:21 schrieb Adrian Georgescu:
> 
>> Can you paste the information from the sip trace window?
> 
> Hi Adrian, here we go:
> 
> I added the xxx entries. The "RFC1918" error rhythm continues than...
> 
> 
> 
> 2011-02-27 16:53:29.783054: DNS lookup NAPTR sip.1und1.de failed: DNS response contains no answer
> 2011-02-27 16:53:29.785031: DNS lookup NAPTR sip.1und1.de failed: DNS response contains no answer
> 2011-02-27 16:53:29.862016: DNS lookup SRV _sips._tcp.sip.1und1.de failed: DNS record does not exist
> 2011-02-27 16:53:29.863891: DNS lookup SRV _sips._tcp.sip.1und1.de failed: DNS record does not exist
> 2011-02-27 16:53:29.940556: DNS lookup SRV _sip._tcp.sip.1und1.de failed: DNS record does not exist
> 2011-02-27 16:53:29.942433: DNS lookup SRV _sip._tcp.sip.1und1.de failed: DNS record does not exist
> 2011-02-27 16:53:29.984701: DNS lookup SRV _sip._udp.sip.1und1.de succeeded, ttl=168: 0 0 5060 1und1-2.sip.1und1.de., 0 0 5060 1und1-1.sip.1und1.de.
> 2011-02-27 16:53:29.991612: DNS lookup SRV _sip._udp.sip.1und1.de succeeded, ttl=168: 0 0 5060 1und1-2.sip.1und1.de., 0 0 5060 1und1-1.sip.1und1.de.
> 
> SENDING: Packet 1, +0:00:00
> 2011-02-27 16:53:29.987279: 192.168.1.25:56864 -(SIP over UDP)-> 212.227.67.197:5060
> REGISTER sip:sip.1und1.de SIP/2.0
> 
> SENDING: Packet 2, +0:00:00.006584
> 2011-02-27 16:53:29.993863: 192.168.1.25:56864 -(SIP over UDP)-> 212.227.67.197:5060
> SUBSCRIBE sip:49721xxx7734 at sip.1und1.de SIP/2.0
> 
> RECEIVED: Packet 3, +0:00:00.019618
> 2011-02-27 16:53:30.006897: 212.227.67.197:5060 -(SIP over UDP)-> 192.168.1.25:56864
> SIP/2.0 403 Keine RFC1918-IPs erlaubt
> 
> RECEIVED: Packet 4, +0:00:00.028656
> 2011-02-27 16:53:30.015935: 212.227.67.197:5060 -(SIP over UDP)-> 192.168.1.25:56864
> SIP/2.0 401 Unauthorized
> 
> SENDING: Packet 5, +0:00:00.028929
> 2011-02-27 16:53:30.016208: 192.168.1.25:56864 -(SIP over UDP)-> 212.227.67.197:5060
> SUBSCRIBE sip:49721xxx7734 at sip.1und1.de SIP/2.0
> 
> SENDING: Packet 6, +0:00:00.030107
> 2011-02-27 16:53:30.017386: 192.168.1.25:56864 -(SIP over UDP)-> 212.227.18.134:5060
> REGISTER sip:sip.1und1.de SIP/2.0
> 
> RECEIVED: Packet 7, +0:00:00.050366
> 2011-02-27 16:53:30.037645: 212.227.18.134:5060 -(SIP over UDP)-> 192.168.1.25:56864
> SIP/2.0 403 Keine RFC1918-IPs erlaubt
> 
> _______________________________________________
> Blink mailing list
> Blink at lists.ag-projects.com
> http://lists.ag-projects.com/mailman/listinfo/blink
> 




More information about the Blink mailing list