Jump to content

Register Sipgate failed at second time


zazi
 Share

Recommended Posts

Hello,

 

I like to use my Sipgate account to register my telephone number for calls at PBXNSIP. Everthing works fine at the first time when I start my system and every service loads. After a while (maybe 3-5 minutes) the connection to the sipgate-server gets lost and when PBXNSIP tries to re-register it, it will fail after a while with the code 408 (timeout).

So here is an excerpt from the log, when the systems tries to connect to sipgate:

 

[9] 2008/11/23 15:47:52: Resolve 108: url sip:sipgate.de

[9] 2008/11/23 15:47:52: Resolve 108: naptr sipgate.de

[8] 2008/11/23 15:47:54: DNS: Add dns_naptr sipgate.de (ttl=60)

[9] 2008/11/23 15:47:54: Resolve 108: naptr sipgate.de

[9] 2008/11/23 15:47:54: Resolve 108: srv tls _sips._tcp.sipgate.de

[8] 2008/11/23 15:47:55: DNS: Add dns_srv _sips._tcp.sipgate.de (ttl=60)

[9] 2008/11/23 15:47:55: Resolve 108: srv tls _sips._tcp.sipgate.de

[9] 2008/11/23 15:47:55: Resolve 108: srv tcp _sip._tcp.sipgate.de

[8] 2008/11/23 15:47:57: DNS: Add dns_srv _sip._tcp.sipgate.de (ttl=60)

[9] 2008/11/23 15:47:57: Resolve 108: srv tcp _sip._tcp.sipgate.de

[9] 2008/11/23 15:47:57: Resolve 108: srv udp _sip._udp.sipgate.de

[9] 2008/11/23 15:47:57: Resolve 108: a udp sipgate.de 5060

[9] 2008/11/23 15:47:57: Resolve 108: udp 217.10.79.9 5060

[9] 2008/11/23 15:47:57: Resolve 108: a udp sipgate.de 5060

[9] 2008/11/23 15:47:57: Resolve 108: udp 217.10.79.9 5060

[8] 2008/11/23 15:47:57: Trunk 4 (Sipgate) has outbound proxy udp:217.10.79.9:5060

[9] 2008/11/23 15:47:57: Resolve 109: url sip:sipgate.de

[9] 2008/11/23 15:47:57: Resolve 109: naptr sipgate.de

[9] 2008/11/23 15:47:57: Resolve 109: srv tls _sips._tcp.sipgate.de

[9] 2008/11/23 15:47:57: Resolve 109: srv tcp _sip._tcp.sipgate.de

[9] 2008/11/23 15:47:57: Resolve 109: srv udp _sip._udp.sipgate.de

[9] 2008/11/23 15:47:57: Resolve 109: a udp sipgate.de 5060

[9] 2008/11/23 15:47:57: Resolve 109: udp 217.10.79.9 5060

[7] 2008/11/23 15:47:57: SIP Tx udp:217.10.79.9:5060:

REGISTER sip:sipgate.de SIP/2.0

Via: SIP/2.0/UDP 192.168.1.106:7060;branch=z9hG4bK-13feb7b5bd0c5e02fe358ddd30aa471f;rport

From: "[my Sipgate SIP-ID]" <sip:[my Sipgate SIP-ID]@sipgate.de>;tag=26837

To: "[my Sipgate SIP-ID]" <sip:[my Sipgate SIP-ID]@sipgate.de>

Call-ID: 9n20y1a1@pbx

CSeq: 13324 REGISTER

Max-Forwards: 70

Contact: <sip:[my Sipgate SIP-ID]@192.168.1.106:7060;transport=udp;line=a87ff679>;+sip.instance="<urn:uuid:c26897eb-2bf3-4c04-9bd3-99854322a6b9>"

User-Agent: pbxnsip-PBX/3.0.1.3023

Expires: 3600

Content-Length: 0

 

 

[7] 2008/11/23 15:47:57: SIP Tr udp:217.10.79.9:5060:

REGISTER sip:sipgate.de SIP/2.0

Via: SIP/2.0/UDP 192.168.1.106:7060;branch=z9hG4bK-13feb7b5bd0c5e02fe358ddd30aa471f;rport

From: "[my Sipgate SIP-ID]" <sip:[my Sipgate SIP-ID]@sipgate.de>;tag=26837

To: "[my Sipgate SIP-ID]" <sip:[my Sipgate SIP-ID]@sipgate.de>

Call-ID: 9n20y1a1@pbx

CSeq: 13324 REGISTER

Max-Forwards: 70

Contact: <sip:[my Sipgate SIP-ID]@192.168.1.106:7060;transport=udp;line=a87ff679>;+sip.instance="<urn:uuid:c26897eb-2bf3-4c04-9bd3-99854322a6b9>"

User-Agent: pbxnsip-PBX/3.0.1.3023

Expires: 3600

Content-Length: 0

 

[8] 2008/11/23 15:48:54: DNS: dns_naptr sipgate.de expired

[8] 2008/11/23 15:48:55: DNS: dns_srv _sips._tcp.sipgate.de expired

[8] 2008/11/23 15:48:57: DNS: dns_srv _sip._tcp.sipgate.de expired

 

9] 2008/11/23 15:49:27: Resolve 114: url sip:sipgate.de

[9] 2008/11/23 15:49:27: Resolve 114: naptr sipgate.de

[8] 2008/11/23 15:49:28: DNS: Add dns_naptr sipgate.de (ttl=60)

[9] 2008/11/23 15:49:28: Resolve 114: naptr sipgate.de

[9] 2008/11/23 15:49:28: Resolve 114: srv tls _sips._tcp.sipgate.de

[8] 2008/11/23 15:49:30: DNS: Add dns_srv _sips._tcp.sipgate.de (ttl=60)

[9] 2008/11/23 15:49:30: Resolve 114: srv tls _sips._tcp.sipgate.de

[9] 2008/11/23 15:49:30: Resolve 114: srv tcp _sip._tcp.sipgate.de

[8] 2008/11/23 15:49:31: DNS: Add dns_srv _sip._tcp.sipgate.de (ttl=60)

[9] 2008/11/23 15:49:31: Resolve 114: srv tcp _sip._tcp.sipgate.de

[9] 2008/11/23 15:49:31: Resolve 114: srv udp _sip._udp.sipgate.de

[9] 2008/11/23 15:49:31: Resolve 114: a udp sipgate.de 5060

[9] 2008/11/23 15:49:31: Resolve 114: udp 217.10.79.9 5060

[9] 2008/11/23 15:49:31: Resolve 114: a udp sipgate.de 5060

[9] 2008/11/23 15:49:31: Resolve 114: udp 217.10.79.9 5060

[8] 2008/11/23 15:49:31: Trunk 4 (Sipgate) has outbound proxy udp:217.10.79.9:5060

[9] 2008/11/23 15:49:31: Resolve 115: url sip:sipgate.de

[9] 2008/11/23 15:49:31: Resolve 115: naptr sipgate.de

[9] 2008/11/23 15:49:31: Resolve 115: srv tls _sips._tcp.sipgate.de

[9] 2008/11/23 15:49:31: Resolve 115: srv tcp _sip._tcp.sipgate.de

[9] 2008/11/23 15:49:31: Resolve 115: srv udp _sip._udp.sipgate.de

[9] 2008/11/23 15:49:31: Resolve 115: a udp sipgate.de 5060

[9] 2008/11/23 15:49:31: Resolve 115: udp 217.10.79.9 5060

[7] 2008/11/23 15:49:31: SIP Tx udp:217.10.79.9:5060:

REGISTER sip:sipgate.de SIP/2.0

Via: SIP/2.0/UDP 192.168.1.106:7060;branch=z9hG4bK-fe1f9eda3c0b1f20fca77eecf3a00894;rport

From: "[my Sipgate SIP-ID]" <sip:[my Sipgate SIP-ID]@sipgate.de>;tag=26837

To: "[my Sipgate SIP-ID]" <sip:[my Sipgate SIP-ID]@sipgate.de>

Call-ID: 9n20y1a1@pbx

CSeq: 13326 REGISTER

Max-Forwards: 70

Contact: <sip:[my Sipgate SIP-ID]@192.168.1.106:7060;transport=udp;line=a87ff679>;+sip.instance="<urn:uuid:c26897eb-2bf3-4c04-9bd3-99854322a6b9>"

User-Agent: pbxnsip-PBX/3.0.1.3023

Expires: 3600

Content-Length: 0

 

 

[7] 2008/11/23 15:49:32: SIP Tr udp:217.10.79.9:5060:

REGISTER sip:sipgate.de SIP/2.0

Via: SIP/2.0/UDP 192.168.1.106:7060;branch=z9hG4bK-fe1f9eda3c0b1f20fca77eecf3a00894;rport

From: "[my Sipgate SIP-ID]" <sip:[my Sipgate SIP-ID]@sipgate.de>;tag=26837

To: "[my Sipgate SIP-ID]" <sip:[my Sipgate SIP-ID]@sipgate.de>

Call-ID: 9n20y1a1@pbx

CSeq: 13326 REGISTER

Max-Forwards: 70

Contact: <sip:[my Sipgate SIP-ID]@192.168.1.106:7060;transport=udp;line=a87ff679>;+sip.instance="<urn:uuid:c26897eb-2bf3-4c04-9bd3-99854322a6b9>"

User-Agent: pbxnsip-PBX/3.0.1.3023

Expires: 3600

Content-Length: 0

 

[7] 2008/11/23 15:49:47: SIP Tr udp:217.10.79.9:5060:

REGISTER sip:sipgate.de SIP/2.0

Via: SIP/2.0/UDP 192.168.1.106:7060;branch=z9hG4bK-fe1f9eda3c0b1f20fca77eecf3a00894;rport

From: "[my Sipgate SIP-ID]" <sip:[my Sipgate SIP-ID]@sipgate.de>;tag=26837

To: "[my Sipgate SIP-ID]" <sip:[my Sipgate SIP-ID]@sipgate.de>

Call-ID: 9n20y1a1@pbx

CSeq: 13326 REGISTER

Max-Forwards: 70

Contact: <sip:[my Sipgate SIP-ID]@192.168.1.106:7060;transport=udp;line=a87ff679>;+sip.instance="<urn:uuid:c26897eb-2bf3-4c04-9bd3-99854322a6b9>"

User-Agent: pbxnsip-PBX/3.0.1.3023

Expires: 3600

Content-Length: 0

 

 

[5] 2008/11/23 15:50:01: Registration on trunk 4 (Sipgate) failed. Retry in 60 seconds

 

 

I replaced my sipgate sip-id with [my sigate sip-id].

192.168.1.106 is the IP of the PBXNSIP system and 7060 the port I used for it.

I can also get the snippets of successful registration from PBXNSIP with sipgate and also the configuration of that trunk.

 

cheers zazi

Link to comment
Share on other sites

Looks bad... :huh:

 

If there is absolutely nothing coming back then maybe your firewall blocks the traffic? Even if sipgate does not offer SBC service (which is neccessary to run the PBX behind all kinds of NAT unless you have a routable IPv4 or IPv6 address, see http://en.wikipedia.org/wiki/Session_Border_Controller), their edge proxy should respond with something.

Link to comment
Share on other sites

As I mentioned, here is the excerpt of the log, when it connects successful.

 

[9] 2008/11/23 16:11:31: Resolve 3: url sip:sipgate.de

[9] 2008/11/23 16:11:31: Resolve 3: naptr sipgate.de

[8] 2008/11/23 16:11:32: DNS: Add dns_naptr sipgate.de (ttl=60)

[9] 2008/11/23 16:11:32: Resolve 3: naptr sipgate.de

[9] 2008/11/23 16:11:32: Resolve 3: srv tls _sips._tcp.sipgate.de

[8] 2008/11/23 16:11:34: DNS: Add dns_srv _sips._tcp.sipgate.de (ttl=60)

[9] 2008/11/23 16:11:34: Resolve 3: srv tls _sips._tcp.sipgate.de

[9] 2008/11/23 16:11:34: Resolve 3: srv tcp _sip._tcp.sipgate.de

[8] 2008/11/23 16:11:35: DNS: Add dns_srv _sip._tcp.sipgate.de (ttl=60)

[9] 2008/11/23 16:11:35: Resolve 3: srv tcp _sip._tcp.sipgate.de

[9] 2008/11/23 16:11:35: Resolve 3: srv udp _sip._udp.sipgate.de

[8] 2008/11/23 16:11:35: DNS: Add dns_srv _sip._udp.sipgate.de 0 0 sipgate.de 5060 (ttl=19219)

[9] 2008/11/23 16:11:35: Resolve 3: srv udp _sip._udp.sipgate.de

[9] 2008/11/23 16:11:35: Resolve 3: a udp sipgate.de 5060

[8] 2008/11/23 16:11:35: DNS: Add dns_a sipgate.de 217.10.79.9 (ttl=7862)

[9] 2008/11/23 16:11:35: Resolve 3: a udp sipgate.de 5060

[9] 2008/11/23 16:11:35: Resolve 3: udp 217.10.79.9 5060

[9] 2008/11/23 16:11:35: Resolve 3: a udp sipgate.de 5060

[9] 2008/11/23 16:11:35: Resolve 3: udp 217.10.79.9 5060

[8] 2008/11/23 16:11:35: Trunk 4 (Sipgate) has outbound proxy udp:217.10.79.9:5060

[9] 2008/11/23 16:11:35: Resolve 4: url sip:sipgate.de

[9] 2008/11/23 16:11:35: Resolve 4: naptr sipgate.de

[9] 2008/11/23 16:11:35: Resolve 4: srv tls _sips._tcp.sipgate.de

[9] 2008/11/23 16:11:35: Resolve 4: srv tcp _sip._tcp.sipgate.de

[9] 2008/11/23 16:11:35: Resolve 4: srv udp _sip._udp.sipgate.de

[9] 2008/11/23 16:11:35: Resolve 4: a udp sipgate.de 5060

[9] 2008/11/23 16:11:35: Resolve 4: udp 217.10.79.9 5060

[7] 2008/11/23 16:11:35: SIP Tx udp:217.10.79.9:5060:

REGISTER sip:sipgate.de SIP/2.0

Via: SIP/2.0/UDP 192.168.1.106:7060;branch=z9hG4bK-9cf51e6e48f77b785723e86e1dec4449;rport

From: "[my Sipgate SIP_ID]" <sip:[my Sipgate SIP_ID]@sipgate.de>;tag=46466

To: "[my Sipgate SIP_ID]" <sip:[my Sipgate SIP_ID]@sipgate.de>

Call-ID: ln1f246s@pbx

CSeq: 26009 REGISTER

Max-Forwards: 70

Contact: <sip:[my Sipgate SIP_ID]@192.168.1.106:7060;transport=udp;line=a87ff679>;+sip.instance="<urn:uuid:c26897eb-2bf3-4c04-9bd3-99854322a6b9>"

User-Agent: pbxnsip-PBX/3.0.1.3023

Expires: 3600

Content-Length: 0

 

 

[7] 2008/11/23 16:11:35: SIP Rx udp:217.10.79.9:5060:

SIP/2.0 401 Unauthorized

Via: SIP/2.0/UDP 192.168.2.100:7060;branch=z9hG4bK-9cf51e6e48f77b785723e86e1dec4449;rport=7060

From: "[my Sipgate SIP_ID]" <sip:[my Sipgate SIP_ID]@sipgate.de>;tag=46466

To: "[my Sipgate SIP_ID]" <sip:[my Sipgate SIP_ID]@sipgate.de>;tag=8367f0f887e3954243ec30fa0f5db288.6e3c

Call-ID: ln1f246s@pbx

CSeq: 26009 REGISTER

WWW-Authenticate: Digest realm="sipgate.de", nonce="492973d31fc3982ac267611b4db6ff3593c9b7d1"

Content-Length: 0

 

 

[8] 2008/11/23 16:11:35: Answer challenge with username [my Sipgate SIP_ID]

[9] 2008/11/23 16:11:35: Resolve 5: udp 217.10.79.9 5060 udp:1

[7] 2008/11/23 16:11:35: SIP Tx udp:217.10.79.9:5060:

REGISTER sip:sipgate.de SIP/2.0

Via: SIP/2.0/UDP 192.168.1.106:7060;branch=z9hG4bK-200fb471786ba657704995c99944ff82;rport

From: "[my Sipgate SIP_ID]" <sip:[my Sipgate SIP_ID]@sipgate.de>;tag=46466

To: "[my Sipgate SIP_ID]" <sip:[my Sipgate SIP_ID]@sipgate.de>

Call-ID: ln1f246s@pbx

CSeq: 26010 REGISTER

Max-Forwards: 70

Contact: <sip:[my Sipgate SIP_ID]@192.168.1.106:7060;transport=udp;line=a87ff679>;+sip.instance="<urn:uuid:c26897eb-2bf3-4c04-9bd3-99854322a6b9>"

User-Agent: pbxnsip-PBX/3.0.1.3023

Authorization: Digest realm="sipgate.de",nonce="492973d31fc3982ac267611b4db6ff3593c9b7d1",response="5cb893f95205f2e7402de3ce0e0133e7",username="[my Sipgate SIP_ID]",uri="sip:sipgate.de",algorithm=MD5

Expires: 3600

Content-Length: 0

 

 

[9] 2008/11/23 16:11:35: Message repetition, packet dropped

[7] 2008/11/23 16:11:35: SIP Rx udp:217.10.79.9:5060:

SIP/2.0 200 OK

Via: SIP/2.0/UDP 192.168.1.106:7060;branch=z9hG4bK-200fb471786ba657704995c99944ff82;rport=7060

From: "[my Sipgate SIP_ID]" <sip:[my Sipgate SIP_ID]@sipgate.de>;tag=46466

To: "[my Sipgate SIP_ID]" <sip:[my Sipgate SIP_ID]@sipgate.de>;tag=8367f0f887e3954243ec30fa0f5db288.4e5b

Call-ID: ln1f246s@pbx

CSeq: 26010 REGISTER

Contact: <sip:[my Sipgate SIP_ID]@192.168.1.106:7060;transport=udp;line=a87ff679>;expires=600

Content-Length: 0

 

 

[2] 2008/11/23 16:11:35: Trunk status Sipgate (4) changed to "200 OK"

 

(Refresh interval 600 seconds)

[8] 2008/11/23 16:11:36: No from address for sending text email

[8] 2008/11/23 16:12:32: DNS: dns_naptr sipgate.de expired

[8] 2008/11/23 16:12:34: DNS: dns_srv _sips._tcp.sipgate.de expired

[8] 2008/11/23 16:12:35: DNS: dns_srv _sip._tcp.sipgate.de expired

 

 

 

cheers zazi

 

PS: I will try out the link you've posted.

Link to comment
Share on other sites

What you can try is to set the "Keepalive Time" explicitly to something like 30 seconds and see if that makes a difference. 600 seconds is too long for NAT unless sipgate sends some keep-alive traffic. But not all firewalls treat keep-alive traffic from the outside as valid keep-alive, maybe you are the lucky one with such a firewall.

Link to comment
Share on other sites

Yeah, I checked out again my other test PBX (3CX Phone System). There the registration will be refreshed after my configurated period of time successfully. So maybe it has something to with my configuration at PBXNSIP, or I don't know. 3CX make use of the STUN server of Sipgate. Unfortunatelly, this isn't any more available at PBXNSIP. The big disadvantage of 3CX is that it does not work together with MS Speech Server 2007. PBXNSIP does it, fortunatelly.

So here is the configuration of my SIP registration in PBXNSIP:

 

Name:

Type: SIP Registration

Direction Inbound and outbound

 

--------------------------------------------------------------------------------

 

Display Name: [my Sipgate SIP-ID]

Account: [my Sipgate SIP-ID]

Domain: sipgate.de

Username: [my Sipgate SIP-ID]

Password: [my Sipgate SIP-password]

Password (repeat): [my Sipgate SIP-password]

Outbound Proxy: sipgate.de

CO Lines: -

Dialog Permissions: -

Codec Preference: -

Proposed Duration (s): 3600

Keepalive Time: 600

Send email on status change: yes

Strict RTP Routing: no

Avoid RFC4122 (UUID): no

Accept Redirect: yes

Interpret SIP URI always as telephone number: yes

 

--------------------------------------------------------------------------------

 

Prefix: -

Global: no

Trunk ANI: [my external phone number of my Sipgate account]

Remote Party/Privacy Indication: Remote-Party-ID

Failover Behavior: No failover

Is Secure: no

ICID (RFC 3455): -

 

--------------------------------------------------------------------------------

 

Send call to extension: -

Assume that call comes from user: -

Ringback: Media checked

 

 

Hope that will help to analyse the problem.

 

cheers zazi

Link to comment
Share on other sites

Hm, I tried out the 30 seconds variant, but after the first refresh the registration get lost. I disabled my firewall. It could just something to do with my router. I can check the system tomorrow somewhere else. However, I can only mentioned that a re-registration in 3CX works.

 

Nevertheless, thanks a lot for help.

 

cheers zazi

Link to comment
Share on other sites

Okay, I figured out the task, which is responsible for kicking my registration. Therefore, I have to explain the situation of my development/ test state. My test goal is, to phone a IVR hosted on a MS Speech Server which is connect with the PBXNSIP. The first test: calling the application from a softphone, which is connected to PBXNSIP succeed. Now it is time for establishing the routes from the sipgate phone number to the speech application (but I do not really know how to that :huh: ).

So I tried different configuration and test them with a phone call. Always after that phone calls, the sipgate registration get lost. Before I initiate a call, everything is fine. I checked that out with Wireshark (after 30 seconds the registration refreshes successfully).

 

So it depend more or less indirectly on the sipgate registration.

 

cheers zazi

Link to comment
Share on other sites

Yeah, I checked out again my other test PBX (3CX Phone System). There the registration will be refreshed after my configurated period of time successfully. So maybe it has something to with my configuration at PBXNSIP, or I don't know. 3CX make use of the STUN server of Sipgate. Unfortunatelly, this isn't any more available at PBXNSIP. The big disadvantage of 3CX is that it does not work together with MS Speech Server 2007. PBXNSIP does it, fortunatelly.

 

Yes, in the beginning we also offered STUN support for clients behind NAT. There was a hope five years ago that STUN would solve the problem overcoming the routing problems with SIP. But we just drowned in support explaining customers what the difference between full-cone NAT and symmetrical NAT is and asking customers to try new routers. That's it! STUN is not the solution.

 

Today it looks like SBC will will win the race and IPv6, that's the "inconvenient truth", will be the only way to have true peer-to-peer SIP media. Also outbound looks promising (see http://tools.ietf.org/html/draft-ietf-sip-outbound), this will solve a lot more problems that the 2003 STUN did. Of course, we put everthing into the pbxnsip PBX already :huh: .

 

I don't believe that a free, home-compiled SIP proxy and some good marketing is enough to build the ITSP money printing machine. The truth is that a lot more is required and carriers do have to spend money for SIP equipment. Time will tell, and customers are making their vote on good and bad service. Also, a big question mark is QoS. Some say that a solid carrier need to have control over it, otherwise voice hickups when emails are being uploaded are only a question of time. At times when 100 MBit/s are available for a few bucks, there is no easy answer for this.

 

Keepalive Time: 600

 

I would try setting that to 30.

Link to comment
Share on other sites

Thanks a lot for the information about STUN. Nevertheless I'm running my system (as I maybe decribed in my post above) with a keep-alive time of 30 seconds. At the beginning it works really good and renew the registration after every 30 seconds. When I dial my sipgate number from my hardware phone to connect to my MS Speech Server application (yeah, the routing works now fine), the registration get lost after this call and only a reboot of my system with in general a new IP from my router (I used DHCP locally) will help. Anyway, that can't be the solution. When I have a look at the output from Wireshark it seams that the DNS of my dsl modem can not resolve the connection to sipgate, but that happends also before, or?

The PBX send REGISTER to sipgate, but sipgate do not answer with 401 that the PBX can send REGISTER with the authorisation (in my opinion from the analysis of the Wireshark output).

If it will help I can upload the log file of Wireshark.

 

I think it is a little bit strange.

 

Cheers zazi

Link to comment
Share on other sites

Thanks a lot for the information about STUN. Nevertheless I'm running my system (as I maybe decribed in my post above) with a keep-alive time of 30 seconds. At the beginning it works really good and renew the registration after every 30 seconds. When I dial my sipgate number from my hardware phone to connect to my MS Speech Server application (yeah, the routing works now fine), the registration get lost after this call and only a reboot of my system with in general a new IP from my router (I used DHCP locally) will help. Anyway, that can't be the solution. When I have a look at the output from Wireshark it seams that the DNS of my dsl modem can not resolve the connection to sipgate, but that happends also before, or?

The PBX send REGISTER to sipgate, but sipgate do not answer with 401 that the PBX can send REGISTER with the authorisation (in my opinion from the analysis of the Wireshark output).

If it will help I can upload the log file of Wireshark.

 

I think it is a little bit strange.

 

Cheers zazi

 

Is your DSL router doing DNS? There are many DSL routers that are not able to deal with non-DNS A requests (SRV, NAPTR, AAAA).

 

In general, if you have to get a new IP address then I would really really recommend trying another router. There is just so much buggy stuff in the low-end router market that you can burn a lot of time pinpointing the problem just to find out that the NAT implementation was just a little bit toooo pragmatic.

Link to comment
Share on other sites

Oh, I think dsl modem tries do resolved them and when it can not resolve the hostname, it routes it to a further machine outside. The issue is that without a phone call the registration refreshes all the time successfully, it is still only after a phone call.

However, I've tried it at my university and it works - so it is only a local problem of our combination/ configuration at home (because if every thing of our architecture fits - the combination of PBXNSIP + MS Speech Server etc. - we get a Windows Server 2003 at the university, where we can host our applications).

 

Thanks a lot for all your help.

 

Cheers zazi

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...