Menu

#113 dns srv lookup for TLS when not compiled with TLS

ver 1.1.x
closed-invalid
core (125)
5
2006-12-18
2006-10-24
Anonymous
No

Here's my problem; I'm setting up a connection over a
remote PSTN-GW. This GW sends me a 200 OK and expects
an ACK back.

However, when the openser.cfg reaches the loose_route
part of the config it attempts to do it's t_relay. As
part of that it takes the domain of the gw-server and
looks for srv records in DNS. All well, as it should I
guess - though I would think that SRV lookups were only
done during INVITEs.

HOWEVER! My server is a non-TLS server, and the first
srv record it tries to look for is _sips._tcp... That's
right, secure tls.

The problem is... it finds a srv record for TLS and
says WHEE forgetting that it is not configured (or even
compiled) for TLS operations! Meaning it tries to send
the ACK back to the gateway using TLS... which of
course won't work as the gateway server hasn't set up
any TLS connection with us.

So, the thing to do to fix this is obviously NOT dnsing
for _sips when TLS is not enabled. However, this
requires source modification right? There's not a
parameter or variable I can set somewhere?

Discussion

  • Bogdan-Andrei Iancu

    • assigned_to: nobody --> bogdan_iancu
     
  • Bogdan-Andrei Iancu

    • status: open --> open-invalid
     
  • Bogdan-Andrei Iancu

    Logged In: YES
    user_id=1275325
    Originator: NO

    Hi there,

    there is something strange in your post. Are you sure you have no TLS support compiled? it is quite impossible for openser to perform a sips.tcp SRV lookup without the TLS support compiled and enabled - see the resolve.c file, line 936. looking at the code, I see no way how to happen what you are describing.

    can you provide more info? trace, debug logs, whatever else..?

    regards,
    bogdan

     
  • Bogdan-Andrei Iancu

    Logged In: YES
    user_id=1275325
    Originator: NO

    unable to reproduce and no other input received from the submitter.

     
  • Bogdan-Andrei Iancu

    • status: open-invalid --> closed-invalid
     

Log in to post a comment.