Re: [reSIProcate-users] Using hostname in RR/Via causing send to fail
- From: Andrew Wood <ajwood@xxxxxxx>
- Date: Mon, 02 Mar 2009 22:13:20 +0000
Hi Adam
When I start up the proxy it prints out:
INFO | 20090302-230201.199 | | RESIP:DNS | 1077209024 |
dns/AresDns.cxx:141 | DNS initialization: found 1 name servers
INFO | 20090302-230201.199 | | RESIP:DNS | 1077209024 |
dns/AresDns.cxx:144 | name server: 192.168.254.200
INFO | 20090302-230201.200 | | RESIP:TRANSPORT | 1077209024 |
UdpTransport.cxx:42 | Creating UDP transport host=192.168.254.202
port=5060 ipv4=1
.202 is the proxy IP. The round-robin host name resolves to both .202 &
.201. The DNS server found is correct.
I have a C++ std::string containing the servers hostname which I use to
build a record route & Via. If I initialise it to "192.168.254.202"
everything works but if I initialise it to "sip.xswitch.local" I get the
aforementioned error.
sip.xswitch.local is setup on the DNS-- if I do host sip.xswitch.local
at the Linux shell i get:
sip.xswitch.local has address 192.168.254.202
sip.xswitch.local has address 192.168.254.201
I've just double checked - the proxy program is given two commandline
arguments- the IP address (192.168.254.202) which resip binds to at
startup & the round robin hostname which is used ONLY to generate Via &
Record-Route headers. If i pass them both as IP's it works, but an IP
and a hostname fails :S
Andrew
Adam Roach wrote:
Andrew:
What I'm reading in the log you've sent is that you're asking to send
the message via UDP from port 5060 using any available interface. The
transport selector can't find any provisioned transport meeting those
criteria.
Can you double-check the part of your code where you add transports to
the stack and ensure that the proxy has a UDP transport operating on
port 5060?
/a