asterisk users - Apr 2003 - sip registration problems

i installed yesterday asterisk cvs version and tried to register
asterisk as a sip ua with my proxy.  there was two problems that i was
not able to solve with the style of register line shown in the default
sip.conf:

register => foo:password@proxy.com

the first problem was that asterisk converted the host part of the
to/from uri from the domain name proxy.com to its ip address, which i
don't want to be done and don't know how to prevent it.

the second problem was that i could not figure out how i can give the
authentication username separately from the user part of the to/from uri
(foo).  

so the registration line syntax should be something like this:

register => uri:username:password

and then asterisk should make an srv lookup on _sip._udp + the host part
of the uri prefixed by to figure out where to send the registration
request.

is any of the above achievable now without changes in the code?

assuming that the above two problems get solved, the next thing that i
would like to try is to configure asterisk so that it forwards any calls
that it gest from the pstn side to the sip proxy and wise versa with a
possible pattern matching rewrite of the calling/called phone numbers
(user part of the from/uri on the sip side).  cisco calls this dial
plan configuration in their pstn/sip gws.

can that be easily done?  sip.conf showed examples where each number is
separately listed in it.

-- juha

On Fri, 11 Apr 2003, Juha Heinanen wrote:
> i installed yesterday asterisk cvs version and tried to register
> asterisk as a sip ua with my proxy.  there was two problems that i was
> not able to solve with the style of register line shown in the default
> sip.conf:
> 
> register => foo:password@proxy.com
> 
> the first problem was that asterisk converted the host part of the
> to/from uri from the domain name proxy.com to its ip address, which i
> don't want to be done and don't know how to prevent it.
It's new behaviour to do that - don't like it either and I think Mark
will
take a patch to adjust.

But in practice it doesn't seem to matter - at least for FWD, Packet8,
iConnecthere that I use.  They all seem to recognise who you are just by
reference to the username part of the From URI.

Does your proxy want to match the entire URI to recognise the user?
> the second problem was that i could not figure out how i can give the
> authentication username separately from the user part of the to/from uri
> (foo).  
> 
> so the registration line syntax should be something like this:
> 
> register => uri:username:password
Like register => jo@myhouse.com:bob:secret ?

I don't think it can currently be done...  I'm not so sure why you need
that, though?

Regards,
Steve

> register => foo:password@proxy.com
>
> the first problem was that asterisk converted the host part of the
> to/from uri from the domain name proxy.com to its ip address, which i
> don't want to be done and don't know how to prevent it.
Just check latest CVS as of this morning.
> the second problem was that i could not figure out how i can give the
> authentication username separately from the user part of the to/from uri
> (foo).
>
> so the registration line syntax should be something like this:
>
> register => uri:username:password
Is this something like the ;user=phone thing?  How is this supposed to be
applied?  You can send me a sip dump off-list of what this should look
like.
> and then asterisk should make an srv lookup on _sip._udp + the host part
> of the uri prefixed by to figure out where to send the registration
> request.
Is this just a regular gethostbyname() or is this something more complex?
Do you have a spec you can point to?
> assuming that the above two problems get solved, the next thing that i
> would like to try is to configure asterisk so that it forwards any calls
> that it gest from the pstn side to the sip proxy and wise versa with a
> possible pattern matching rewrite of the calling/called phone numbers
> (user part of the from/uri on the sip side).  cisco calls this dial
> plan configuration in their pstn/sip gws.
That's all extensions.conf.

Mark