[asterisk-bugs] [Asterisk 0011717]: Register statement works differently using the plain text file or the Asterisk Realtime Architecture

[noreply at bugs.digium.com]

The following issue has been RESOLVED. 
====================================================================== 
http://bugs.digium.com/view.php?id=11717 
====================================================================== 
Reported By:                AlexB
Assigned To:                qwell
====================================================================== 
Project:                    Asterisk
Issue ID:                   11717
Category:                   Channels/chan_sip/General
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     resolved
Asterisk Version:           1.2.26 
SVN Branch (only for SVN checkouts, not tarball releases): N/A  
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
Resolution:                 won't fix
Fixed in Version:           
====================================================================== 
Date Submitted:             01-09-2008 12:23 CST
Last Modified:              01-15-2008 11:44 CST
====================================================================== 
Summary:                    Register statement works differently using the plain
text file or the Asterisk Realtime Architecture
Description: 
In Asterisk 1.2.26 there is a different behaviour for the following syntax
of register statement using the plain text file or the Asterisk Realtime
Architecture:

register = **user**:**password**@sip_proxy

Please have a look at sip.conf:

[general]
allowoverlap = yes
realm = *****
bindport = 5060
bindaddr = 0.0.0.0
srvlookup = yes
tos = lowdelay
disallow = all
allow = alaw
trustrpid = no
dtmfmode = auto
externip = ***.***.***.***
localnet = 192.168.0.0/255.255.0.0
canreinvite = yes
rtcachefriends = yes
qualify = yes
register = **user**:**password**@sip_proxy

[sip_proxy]
type=friend
context=provider_1
secret=**password**
username=**user**
fromdomain=123.123.123.123
fromuser==**user**
host=123.123.123.123
insecure=very

It looks like the example in sip.conf.sample (see below) and of course it
works like a charm in Asterisk 1.2.26 as well as previous versions.

;register => 2345:password at sip_proxy/1234
;
;    Register 2345 at sip provider 'sip_proxy'.  Calls from this provider
;    connect to local extension 1234 in extensions.conf, default context,
;    unless you configure a [sip_proxy] section below, and configure a
;    context.
;    Tip 1: Avoid assigning hostname to a sip.conf section like
[provider.com]
;    Tip 2: Use separate type=peer and type=user sections for SIP
providers
;           (instead of type=friend) if you have calls in both directions

;[sip_proxy]
; For incoming calls only. Example: FWD (Free World Dialup)
; We match on IP address of the proxy for incoming calls
; since we can not match on username (caller id)
;type=peer
;context=from-fwd
;host=fwd.pulver.com

;[sip_proxy-out]
;type=peer                              ; we only want to call out, not be
called
;secret=guessit
;username=yourusername                  ; Authentication user for outbound
proxies
;fromuser=yourusername                  ; Many SIP providers require
this!
;fromdomain=provider.sip.domain
;host=box.provider.com
;usereqphone=yes                        ; This provider requires
";user=phone" on URI
;call-limit=5                           ; permit only 5 simultaneous
outgoing calls to this peer
;outboundproxy=proxy.provider.domain    ; send outbound signaling to this
proxy, not directly to the peer
;port=80                                ; The port number we want to
connect to on the remote side


Unfortunately, using ARA (see mappings below) of Asterisk 1.2.26, the
register statement doesn't work anymore.

extconfig.conf:
sip.conf => mysql,asterisk,ast_config
sipusers => mysql,asterisk,sip_buddies
sippeers => mysql,asterisk,sip_buddies

It is because the following query returns no rows:

[15:22] Alex: res_config_mysql.c:140 realtime_mysql: MySQL RealTime:
Retrieve SQL: SELECT * FROM sip_buddies WHERE name = 'sip_proxy' AND host =
'dynamic'

Since we're trying to register to a remote server, host can't be dynamic!
However no more queries are performed.

In Asterisk 1.2.25 the query was:
[15:21] Alex: res_config_mysql.c:140 realtime_mysql: MySQL RealTime:
Retrieve SQL: SELECT * FROM sip_buddies WHERE name = 'sip_proxy'

This way Asterisk 1.2.26 can't register to the remote server and/or dial
that peer.
====================================================================== 

---------------------------------------------------------------------- 
 qwell - 01-15-08 11:44  
---------------------------------------------------------------------- 
Please reopen if you can reproduce on the latest version of 1.4. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
01-15-08 11:44  qwell          Status                   feedback => resolved
01-15-08 11:44  qwell          Resolution               open => won't fix   
01-15-08 11:44  qwell          Assigned To               => qwell           
01-15-08 11:44  qwell          Note Added: 0076984                          
======================================================================