R: [Asterisk-Users] Configure asterisk for outgoing.. need
authuser parameter?
Chris A. Icide
chris at netgeeks.net
Wed May 19 09:28:45 MST 2004
JT,
I've not yet tested (played) with setting the realm yet, but I plan
to. However, one would think that realm should be a per-entry setting
versus a global setting, or perhaps both.
The problem that really arises is when you try to use asterisk as a local
UA "proxy". I don't mean proxy in the official term, but just as a
description of what it is doing. In other words, you have several accounts
which are some sort of gateway service, be it PSTN, or some other
gateway. You would normally register a specific UA to these (ata-18X,
sipura, cisco 79xx, etc.). However to "simplify" the end user experience,
you stick an asterisk server in front of the UA devices and allow it to
route calls as needed freeing the UA user from having to remember what line
to dial out on for what, etc.
In this case, we have an issue that may come up, where we need to register
with the service as a specific realm. Now as you well know, the register
statement doesn't support alot of the things it should, including being
able to set realm per register.
I've always thought there needed to be a much better format for register
that currently exists.
perhaps type=x (user|peer|friend|register)
forgive me if I'm somewhat out of date on sip.conf, as I've been somewhat
busy, but there are a few other things that should be available (if it
hasn't been added recently) to both a register in this format as well as
the normal SIP UA definitions:
bindaddr=a.b.c.d (defines the interface IP to register or accept traffic
for this client/server)
realm= (per entry realm definition)
shared=x (no|yes\numeric value)
The shared statement would of course require significant changes (perhaps
Olle has done this is chan_sip2), but this would define whether or not
multiple UA's are able to register to the same sip entry and perhaps limit
the number of shared registrations - this of course to allow asterisk in
the future to support notify/subscribe shared line presentation)
Anyway, I'm sure this ground has been covered many times, but just in case
one of these somehow has not been brought up, I figured I would give the
topic a bump.
-Chris
On 01:00 AM 5/19/2004, John Todd wrote:
>Tony -
> For what it's worth, I haven't been able to make the "realm="
>setting do diddly-squat. I think it's broken, but I don't have time
>to test enough to put useful/valid data into the bugtracker.
>
> If anyone can show me a "Digest" line that has a realm= that was
>changed with the global realm= setting in the current CVS, I'm
>interested in learning the syntax you used...
>
>JT
More information about the asterisk-users
mailing list