Leif, Le dimanche 15 novembre 2009 à 22:44 +0100, Eric van der Vlist a écrit : > Leif, > > Le dimanche 15 novembre 2009 à 16:18 -0500, Leif Madsen a écrit : > > > I'm not sure you've provided enough of the trace here. It finds the peer, > > but > > rejects it with a 401 Unauthorized, which is not uncommon. And I don't see > > any > > authentication information in the first INVITE. This is why the 401 is sent > > back, as the WWW-Authenticate line contains the realm and nonce which > > should be > > used by the other end to generate the authentication, and then send another > > INVITE back with authentication.
After you've brought my attention to a potential authentication issue, I did some more researches in that direction and found out that I had been caught by this migration issue: http://forums.whirlpool.net.au/forum-replies-archive.cfm/1133054.html If I add insecure=port,invite declarations in my sip.conf, my incoming calls appear to come through. Weirdly, they seem to be coming from the context I am using to define outgoing calls rather than the one for ingoing ones (like in asterisk 1.4), but I guess that's another issue! Thanks, Eric -- Eric van der Vlist <[email protected]> Dyomedea (http://dyomedea.com) _______________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
