11 Jun
2005
11 Jun
'05
9:07 a.m.
Hi Serusers,
I have a problem with DNS resolution in SIP/SDP "Connection Information"
/ "ConnectionAddress". Maybe somebody can help me:
In the network we use SIP-UAs that are integrated into ADSL-Modems from
Allied Telesyn (AT RG 634).
The SIP-client itself works OK. But when the unit is given a system-name
in the configuration, it will always use its DNS-name instead of its
IP-addr as "Connection Address" in the "Connection Information" in SDP
in INVITE and corresponding OK messages.
Now we want to add SIP-UAs that are NOT capable of resolving DNS-Names
in the "Connection Address" field.
Alle messages pass through SER of course and the SDP-part so far remains
unchanged.
Now my question to the list:
Is there a simple way of forcing SER to do the DNS-resolution of in
incoming message, put in the IP-address in "Connection Address" and
forward it to the other UA?
Thanks a lot in advance!
Gerhard
12 Jun
12 Jun
2:29 a.m.
Forcing SER to do stuff in order to fix problem UA implementation, I don't
think this is a good approach. Using FQDN as connection information in SDP
is the recommended approach in RFC 2327, though few UA do this. I would
suggest you contact the vendor to fix the UA that can't work with DNS.
Have a look on the fix_nated_sdp() function in nathelper. I haven't tried
this before but it might work. However, there is no guarantee. Let us know
if it works.
-----Original Message-----
From: Gerhard Zweimüller
Sent: Saturday, 11 June 2005 11:07 PM
To: serusers(a)lists.iptel.org
Subject: [Serusers] DNS Resolution of SDP-"Connection Address" at SER
Hi Serusers,
I have a problem with DNS resolution in SIP/SDP "Connection
Information"
/ "ConnectionAddress". Maybe somebody can help me:
In the network we use SIP-UAs that are integrated into
ADSL-Modems from
Allied Telesyn (AT RG 634).
The SIP-client itself works OK. But when the unit is given a
system-name
in the configuration, it will always use its DNS-name instead of its
IP-addr as "Connection Address" in the "Connection
Information" in SDP
in INVITE and corresponding OK messages.
Now we want to add SIP-UAs that are NOT capable of resolving
DNS-Names
in the "Connection Address" field.
Alle messages pass through SER of course and the SDP-part so
far remains
unchanged.
Now my question to the list:
Is there a simple way of forcing SER to do the DNS-resolution of in
incoming message, put in the IP-address in "Connection Address" and
forward it to the other UA?
Thanks a lot in advance!
Gerhard
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
5:11 a.m.
Zeus Ng wrote:
Forcing SER to do stuff in order to fix problem UA
implementation, I
don't think this is a good approach. Using FQDN as connection
information in SDP is the recommended approach in RFC 2327, though
few UA do this. I would suggest you contact the vendor to fix the UA
that can't work with DNS.
Well, we already do help the UA with nathelper, right? The thing is, the
telco model is to control all the components that are part of the service,
often dump endpoints and a smart (and complicated) network. The Internet
model is to have smart endpoints and a "dump" (simple) network. When a
standard has not matured enough, you get all sorts of endpoints. I don't
think helping them out a bit is that bad. It is bad if you get a complicated
and hard to maintain network (i.e. ser.cfg). However, this is short-term,
until the dust settles and the endpoints start to behave.
Have a look on the fix_nated_sdp() function in
nathelper. I haven't
tried this before but it might work. However, there is no guarantee.
Let us know if it works.
It will be better chance to develop the functionality in a new module. If
this is of interest to anybody else, making a separate module means you can
submit it as a contribution and maintain it yourself. If you extend
nathelper, you have to convince the maintainer to take it on and take over
maintainance...
g-)
-----Original Message-----
From: Gerhard Zweimüller
Sent: Saturday, 11 June 2005 11:07 PM
To: serusers(a)lists.iptel.org
Subject: [Serusers] DNS Resolution of SDP-"Connection Address" at SER
Hi Serusers,
I have a problem with DNS resolution in SIP/SDP "Connection
Information"
/ "ConnectionAddress". Maybe somebody can help me:
In the network we use SIP-UAs that are integrated into
ADSL-Modems from
Allied Telesyn (AT RG 634).
The SIP-client itself works OK. But when the unit is given a
system-name
in the configuration, it will always use its DNS-name instead of its
IP-addr as "Connection Address" in the "Connection
Information" in SDP
in INVITE and corresponding OK messages.
Now we want to add SIP-UAs that are NOT capable of resolving
DNS-Names
in the "Connection Address" field.
Alle messages pass through SER of course and the SDP-part so
far remains
unchanged.
Now my question to the list:
Is there a simple way of forcing SER to do the DNS-resolution of in
incoming message, put in the IP-address in "Connection Address" and
forward it to the other UA?
Thanks a lot in advance!
Gerhard
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
6963
days inactive
6964
days old
2 comments
3 participants
participants (3)
-
Gerhard Zweimüller -
Greger V. Teigre -
Zeus Ng