Then you use just "username". I don't think the MD5 is critical - the auth=username:[EMAIL PROTECTED] is what chan_sip2 uses.
You must not use port=5060 in sip.conf - it has to be port=5052. You also have to do funny things with the externip - point it to the *internal* address and use "nat=yes" as per my example. It seems to need to think it is coming via NAT. Otherwise it may register and fail the second proxy_auth_required. It is all very strange. If you change the username.brz in my example to your username (as seen by ethereal) and normal password and give that a try. Also note the fact that btinternet.com and sip.btcommunicator.net can not be used interchangeably and it is fussy which is used where. I put a "81.144.106.4 btinternet.com" line into my /etc/hosts file. This is the address of sip.btcommunicator.bt.net. But if you put host=sip.btcommunicator.bt.net into the sip.conf file, authentication fails. Put a host=btinternet.com in sip.conf which will then connect to the right machine using the wrong name and this works! The implementaion of domains and servers seems a bit odd. Peter -----Original Message----- From: Robert Boardman [mailto:[EMAIL PROTECTED] Sent: 11 October 2004 18:30 To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: Re: [Asterisk-Users] RE: bt communicator` Hi Peter, just a couple of quick questions if the my ethereal trace only shows [EMAIL PROTECTED] do I need the .brz? is the MD5sum in the ethereal trace, as I have compared all combinations of MD5sum with the ethereal trace and cannot see it any where? Still cannot register, any advice would be greatly appreciated Regards Robb Whisker, Peter wrote: >Hi Robert; > >First, you have to use the SIP2 channel code (chan_sip2.c) from >http://bugs.digium.com/bug_view_page.php?bug_id=0000759 as this does the >proxy-authenticate properly. > >Get the module, follow the build instructions, and add "noload=chan_sip.so" >to stop the old code loading. It will autoload the new one. > >You need to know the username that the Yahoo Communicator uses. Ethereal or >similar will trace SIP for you. The username I type into communicator has >".brz" appended by the Communicator for some reason. The password is the one >you type into communicator but I had to "MD5" it. Comment below password >shows how. > >[general] >;port = 5060 ; Port to bind to >port = 5052 ; change to 5052 as 5060 will not >authorise on BTCommunicator >; Note if you want local SIP on 5060, you need to use siproxd or similar to >redirect (unless anyone knows otherwise) >pedantic=no >disallow=all ; Disallow all codecs >allow=alaw ; Allow codecs in order of preference ; BT >uses a-law >allow=ulaw >allow=gsm >;allow=ilbc >defaultexpirey=1200 ; Change for BT as it objects to 3600 - >note deliberate spelling error > >register => >[EMAIL PROTECTED]:[EMAIL PROTECTED] > >; Need to state externip as the internal address otherwise BT won't work - >something to do with NAT >;externip = 195.13x.xx.xx >externip = 192.168.10.250 >localnet = 192.168.10.0/255.255.255.0 >;. >;. >;. > >[bt] >type=friend >nat=yes >disallow=all >allow=alaw >canreinvite=no >username=[username].brz >authuser=[username].brz >fromdomain=btinternet.com >fromuser=[username].brz >auth=[username]:[EMAIL PROTECTED] ; I didn't have the >.brz here and it works? >md5secret=6eb36df5f5d94381973b6090b30e0f59 >host=btinternet.com >;outboundproxy=sip.btcommunicator.bt.net ;not needed >;outboundproxyport=5060 ;not needed >;MD5 >;alambil:/etc/asterisk# echo -n >"[EMAIL PROTECTED]:btinternet.com:[password]" | md5sum >;6eb36fd5f5d94381973b6090b30e0f59 - > >Once this worked, I didn't change it. There are probably unneeded lines >above. > >Regards >Peter > > >-----Original Message----- >From: Robert Boardman [mailto:[EMAIL PROTECTED] >Sent: 09 October 2004 21:40 >To: Whisker, Peter >Subject: bt communicator` > > >Hi Peter > >I have been following your post but didn't see the other emails about >getting it working until now!! > >Could you please send me the details for the chan_sip2 method > >Thanks >Robb > >This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you. >_______________________________________________ >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 This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you. _______________________________________________ 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
