On 08/11/2011 02:03 AM, Jim Boykin wrote:
We have difficulty setting up the incoming termination for our clients. Both the ends are using asterisk. The problem is unless we use fromuser at client end, it does not work properly as expected.Below is a configuration at our end. The problem is that whenever call is received from the client, it goes to default context instead of 'dallas' context. Also, the ${CDR(accountcode)} variable remains empty. Now, If we set fromuser field at the client end, then everything starts working, however, in that case, it overrides the callerid.
This is a known and well-understood problem caused by the method that Asterisk users for SIP authentication; the 'From' header in the incoming INVITE is used *both* for determining which user is placing the call and for Caller ID. As you note, if you have the real Caller ID in that header, then Asterisk can't use it for matching to a user in sip.conf, and thus can't authenticate the call properly.
The solution for this is to use 'sendrpid' on the sending end and 'trustrpid' on the receiving end; this will configure Asterisk to transfer the Caller ID information in a Remote-Party-ID (or P-Asserted-Identity, depending on the version you are using) header, allowing the From header to be used solely for authentication.
-- Kevin P. Fleming Digium, Inc. | Director of Software Technologies Jabber: [email protected] | SIP: [email protected] | Skype: kpfleming 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA Check us out at www.digium.com & www.asterisk.org -- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
