All,
This is related to the following bug reports:
http://bugs.digium.com/bug_view_page.php?bug_id=0002024 http://bugs.digium.com/bug_view_page.php?bug_id=0002017
This is not an iConnect specific problem, but a chan_sip change. As it turns out, type=user does not seem to work in the latest CVS (since June) for authentication against inbound--at least not in the way the documentation describes.
What we have resorted to in our offices is have two type=peer contexts in sip.conf defined, the first being outbound, the second being inbound.
Believe it or not, the order of these peers matters as chan_sip appears to take the LAST defined context as the authentication peer if you have a static host or dns name in the host= field.
So, to summarize:
1) chan_sip.c has changed recently the authentication against type=peer and type=user
2) Registration statements that used to work now need to have a matching peer in sip.conf, however, the documentation states that chan_sip will first match type=user and if none is found type=peer. In real life testing with CVS-HEAD from August 4, this did not work.
3) What did work is creating an outbound peer with the authentication information such as username, secret, etc. (same as before) and a separate inbound peer with just the context,type=peer, host=, and any other codec preferences etc for the inbound leg.
4) This inbound peer has to be AFTER the outbound context otherwise, chan_sip will authenticate against the outbound peer instead of the inbound peer.
5) NOTE that the syntax of the registration statement has changed slightly as well (see wiki) and may need to be modified.
On Aug 9, 2004, at 8:57 PM, Sathya Weerasooriya wrote:
Raj, yes your post helped me.
Just to complete the whole thing and clarify the problem that was
posted by Greg Blakely;
First, if there is no outbound iconnect section in sip.conf, my incomingcalls work fine (as long as my "register"statements exist in the top section).
But, when I add an outbound section, using either 'peer' or 'friend,' myincoming calls begin to fail again with the '407Proxy Authentication' error.
When there is a context created in SIP.CONF for iconnect outgoing, we should
point it correctly to extensions.conf. Reason is now the incoming too land
in this context.
Thanks
Sathya
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Raj Sent: Monday, August 09, 2004 5:29 AM To: [EMAIL PROTECTED] Subject: Re: [Asterisk-Users] iconnect inbound - so do we know how to fix it
May be you can find the solution in my post:
http://lists.digium.com/pipermail/asterisk-users/2004-August/ 058014.html
Raj
--- Vladyslav <[EMAIL PROTECTED]> wrote:
Try to comment out in your sip.conf ;qualify=yes
On Mon, 2004-08-09 at 06:52, Sathya Weerasooriya wrote:Just wondering whether we have a resolution to iconnect incoming problem, which started few days ago.
Cheers SW-- Best regards Vlad
_______________________________________________ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
__________________________________ Do you Yahoo!? New and Improved Yahoo! Mail - 100MB free storage! http://promotions.yahoo.com/new_mail
_______________________________________________ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
_______________________________________________ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
