I solved (sort of accidentally) the authentication problem . (configuration problem of the userdb).
The clients are all in the same subnet. They all know of each other via /etc/hosts (ping, ssh, whatever other protocol works, so connectivity is not a problem, and no NAT is in between) Still, I cannot initiate a SIP session. I attached the config files. You can see below what yxa prints while in debug mode when I try to initiate a call: """ 2009-03-14 12:11:34.906 normal<0.491.0>:z9hG4bK-yxa-7fwxs4ikwikm6e+b7mnzza-UAS INVITE: INVITE sip:ga...@gottingen.student.com.dtu.dk<sip%3aga...@gottingen.student.com.dtu.dk>[client=udp: 192.168.34.146:5065, from=<sip:riem...@gottingen.student.com.dtu.dk<sip%3ariem...@gottingen.student.com.dtu.dk>>, to=<sip:ga...@gottingen.student.com.dtu.dk<sip%3aga...@gottingen.student.com.dtu.dk> >] 2009-03-14 12:11:34.911 normal<0.490.0>:z9hG4bK-yxa-7fwxs4ikwikm6e+b7mnzza: incomingproxy: From: address requires authentication 2009-03-14 12:11:34.913 normal<0.491.0>:z9hG4bK-yxa-7fwxs4ikwikm6e+b7mnzza-UAS INVITE: Responding '407 Proxy Authentication Required' 2009-03-14 12:11:34.923 normal<0.491.0>:z9hG4bK-yxa-7fwxs4ikwikm6e+b7mnzza-UAS INVITE: Response '407 Proxy Authentication Required' to request INVITE sip:ga...@gottingen.student.com.dtu.dk<sip%3aga...@gottingen.student.com.dtu.dk>ACK-ed 2009-03-14 12:11:34.934 normal<0.494.0>:z9hG4bK-yxa-dewgpmysa85uimbbfrwoow-UAS INVITE: INVITE sip:ga...@gottingen.student.com.dtu.dk<sip%3aga...@gottingen.student.com.dtu.dk>[client=udp: 192.168.34.146:5065, from=<sip:riem...@gottingen.student.com.dtu.dk<sip%3ariem...@gottingen.student.com.dtu.dk>>, to=<sip:ga...@gottingen.student.com.dtu.dk<sip%3aga...@gottingen.student.com.dtu.dk> >] 2009-03-14 12:11:34.944 normal<0.493.0>:z9hG4bK-yxa-dewgpmysa85uimbbfrwoow: incomingproxy: Proxy INVITE -> sip:ga...@192.168.34.148:5061;transport=udp 2009-03-14 12:11:34.947 normal<0.495.0>:z9hG4bK-yxa-dewgpmysa85uimbbfrwoow-UAC INVITE: Sending INVITE sip:ga...@192.168.34.148:5061;transport=udp (to tcp: 192.168.34.148:5061) 2009-03-14 12:11:34.954 normal<0.495.0>:z9hG4bK-yxa-dewgpmysa85uimbbfrwoow-UAC INVITE: Transport layer failed sending INVITE sip:ga...@192.168.34.148:5061;transport=udp to tcp:192.168.34.148:5061, pretend we got an '503 Service Unavailable' 2009-03-14 12:11:34.958 normal<0.494.0>:z9hG4bK-yxa-dewgpmysa85uimbbfrwoow-UAS INVITE: Responding '500 No reachable destination' 2009-03-14 12:11:34.970 normal<0.494.0>:z9hG4bK-yxa-dewgpmysa85uimbbfrwoow-UAS INVITE: Response '500 No reachable destination' to request INVITE sip:ga...@gottingen.student.com.dtu.dk<sip%3aga...@gottingen.student.com.dtu.dk>ACK-ed """ Best regards and thanks for the help 2009/3/13 Fredrik Thulin <f...@it.su.se> > Costin-Tiberiu RADU wrote: > >> Checked. >> >> And partially solved the problem. >> >> The problem is that the server does not want to register ekiga. >> >> On the other hand wehn I tried with kphone the registration worked. >> >> However, when trying to place a call, even if all the parties registrated >> successfully (both received a 200 OK message) the server sais that it does >> not know how to find the other party. >> >> (and yes I checked the logs, and the configs, and the next step is digging >> through the source files to >> > > Can you perhaps share logs showing these two problems? > > YXA is usually very interoperable with clients, so Ekiga should work as > well as anything else. > > If there is a NAT between your clients and the registrar (incomingproxy), > you might want to try setting up an outgoingproxy application and configure > your clients to REGISTER through the outgoingproxy. > > /Fredrik >
incomingproxy.config
Description: Binary data
userdb
Description: Binary data
_______________________________________________ Yxa-devel mailing list Yxa-devel@lists.su.se https://lists.su.se/mailman/listinfo/yxa-devel
