Re: [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: kflem...@digium.com | SIP: kpflem...@digium.com | 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
Re: [asterisk-users] Problem setting for incoming termination
12 aug 2011 kl. 14:51 skrev Kevin P. Fleming:
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.
Or stop using type=user and type=friend, and stick to type=peer and ASterisk
will only match on IP+port address.
/O
--
_
-- 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
[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
--
_
-- 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
Re: [asterisk-users] Problem setting for incoming termination
Anyone?
On Thu, Aug 11, 2011 at 12:33 PM, Jim Boykin boykin...@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
--
_
-- 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
Re: [asterisk-users] Problem setting for incoming termination
Best Regards,
Mahesh Katta
*BUZZ**WORKS* Business Services Private Limited
BANGALORE | CHENNAI | HYDERABAD | MUMBAI| DELHI
201, Crystal Tower, 75 Gundavali Cross Lane, Andheri Kurla Road, Andheri (E)
Mumbai 400069
GSM +91.97029.70779 | Phone +91.22.4229.2634 | Fax +91.22.4229.2634
Web http://www.buzzworks.com
On Thu, Aug 11, 2011 at 3:09 PM, Jim Boykin boykin...@gmail.com wrote:
Anyone?
On Thu, Aug 11, 2011 at 12:33 PM, Jim Boykin boykin...@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
how you connect this both server with over the internet or any ?
--
_
-- 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
--
_
-- 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
Re: [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 boykin...@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
--
_
-- 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
Re: [asterisk-users] Problem setting for incoming termination
for start you could disable guest access in sip.conf, I guess you do not
need it
On 2011.08.11 14:29, Jim Boykin wrote:
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 boykin...@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
--
_
-- 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
--
_
-- 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
