Benjamin on Asterisk Mailing Lists <[EMAIL PROTECTED]> writes: > An entry of type peer on the local Asterisk has to be matched with > an entry of type user on the remote Asterisk. Likewise, an entry of > type user on the local Asterisk has to be matched with an entry of > type peer on the remote Asterisk.
This is what I do between the two Asterisks I run, as well as for my connection to FWD. It works fine. However, I notice that when an incoming call arrives, it's logged on the Asterisk console as originating at the _peer_, not the _user_. With this in place: [general] register => USER:[EMAIL PROTECTED] [iaxfwd] type=user context=default auth=rsa inkeys=freeworlddialup host=iax2.fwdnet.net [iaxfwd-gw] type=peer username=USER auth=md5 secret=PASS host=iax2.fwdnet.net qualify=yes ...everything looks great. I've got the registry in place, the user is defined to use the specified key for authentication, and the peer is reachable. Calls in either direction work. However, incoming calls are shown as coming from, say, IAX2/[EMAIL PROTECTED]/5. If I remove the host= line from the [iaxfwd] entry, incoming calls fail, so it is obviously _using_ that entry to authenticate FWD. This feels like a bug to me. Or have I misunderstood something? -tih -- Tom Ivar Helbekkmo, Senior System Administrator, EUnet Norway Hosting www.eunet.no T +47-22092958 M +47-93013940 F +47-22092901 FWD 484145 _______________________________________________ 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
