Jim Boykin
2011-Aug-11 07:03 UTC
[asterisk-users] Problem setting for incoming termination
Hi, 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. [dallas] type=user username=dallas secret=somepassword host=dynamic nat=no disallow=all allow=g729 allow=ulaw allow=alaw accountcode=411 context=dallas This is the configuration at client end. [outgoing] type=peer username=dallas secret=somepassword host=<ipaddress> nat=no disallow=all allow=g729 allow=ulaw allow=alaw We do not require the client to register, neither we want them to use fromuser field. I think we are doing some silly mistake since this should be a simple configuration used by many. Please help Thanks Jim
Jim Boykin
2011-Aug-11 09:39 UTC
[asterisk-users] Problem setting for incoming termination
Anyone? On Thu, Aug 11, 2011 at 12:33 PM, Jim Boykin <boykinjim at gmail.com> wrote:> Hi, > > 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. > > [dallas] > type=user > username=dallas > secret=somepassword > host=dynamic > nat=no > disallow=all > allow=g729 > allow=ulaw > allow=alaw > accountcode=411 > context=dallas > > > This is the configuration at client end. > > [outgoing] > type=peer > username=dallas > secret=somepassword > host=<ipaddress> > nat=no > disallow=all > allow=g729 > allow=ulaw > allow=alaw > > We do not require the client to register, neither we want them to use > fromuser field. I think we are doing some silly mistake since this > should be a simple configuration used by many. Please help > > Thanks > Jim >
Jim Boykin
2011-Aug-11 11:29 UTC
[asterisk-users] Problem setting for incoming termination
The problem seems like asterisk is not authenticating at all. It accept the default invite and transfer it to default contact. ANy help. On Thu, Aug 11, 2011 at 12:33 PM, Jim Boykin <boykinjim at gmail.com> wrote:> Hi, > > 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. > > [dallas] > type=user > username=dallas > secret=somepassword > host=dynamic > nat=no > disallow=all > allow=g729 > allow=ulaw > allow=alaw > accountcode=411 > context=dallas > > > This is the configuration at client end. > > [outgoing] > type=peer > username=dallas > secret=somepassword > host=<ipaddress> > nat=no > disallow=all > allow=g729 > allow=ulaw > allow=alaw > > We do not require the client to register, neither we want them to use > fromuser field. I think we are doing some silly mistake since this > should be a simple configuration used by many. Please help > > Thanks > Jim >
Kevin P. Fleming
2011-Aug-12 12:51 UTC
[asterisk-users] Problem setting for incoming termination
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: kfleming at digium.com | SIP: kpfleming at digium.com | Skype: kpfleming 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA Check us out at www.digium.com & www.asterisk.org