On 16.10.2012, at 13:11, Juha Heinanen wrote: > Juha Heinanen writes: > >>> in fact, next_hop should support domain names just the same (A & SRV >>> records). Have you tried it out? >> >> no, i haven't. if next_hop does support domain names, then your >> next_hop_1st_req patch would be exactly what i was looking for. i'll >> give it a try after lunch break. > > raphael, > > with patched sems, i gave this kind config a try: > > next_hop=sip:internal.test.fi:5070 > next_hop_1st_req=yes > > when sbc tried to send the request out, i got to syslog: > > Oct 16 14:08:54 siika sems[10851]: [#7fece2f73700] [set_destination_ip, > trans_layer.cpp:747] ERROR: Unresolvable Request URI domain > > and sems responded with 478 Unresolvable destination. > > domain name internal.test.fi is in dns: > > $ host internal.test.fi > internal.test.fi has address 127.0.0.1 > > why did sems fail to resolve next_hop uri? >
Good question… Can you see whether a DNS request is sent or not? How does 'dig' respond? Did SEMS' resolver output anything before the above error message? Maybe some debug output? I could try it out myself in the next days. I'm quite busy now… -Raphael. > -- juha > > _______________________________________________ > Sems mailing list > [email protected] > http://lists.iptel.org/mailman/listinfo/sems _______________________________________________ Sems mailing list [email protected] http://lists.iptel.org/mailman/listinfo/sems
