[asterisk-bugs] [Asterisk 0015760]: [patch] extension is not recognized in register statement

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15760 
====================================================================== 
Reported By:                steinwej
Assigned To:                tilghman
====================================================================== 
Project:                    Asterisk
Issue ID:                   15760
Category:                   Channels/chan_sip/Registration
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.6.0.14-rc1 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): 1.6.0 
SVN Revision (number only!): 213784 
Request Review:              
====================================================================== 
Date Submitted:             2009-08-22 05:20 CDT
Last Modified:              2009-08-28 05:50 CDT
====================================================================== 
Summary:                    [patch] extension is not recognized in register
statement
Description: 
Asterisk SVN-branch-1.6.0-r213180

two asterisk boxes are connected via SIP. dynamic peers

System A:
register => sip_peer_b:secret_b:sip_peer_b at 192.168.2.20:8060/sip_peer_a

[sip_peer_a]
type=friend
secret=secret_a
context=from_sip
fromuser=sip_peer_b
host=dynamic
;port=8060
disallow=all
nat=yes
canreinvite=no
qualify=no
allow=alaw


System B: (vice versa)

register => sip_peer_a:secret_a:sip_peer_a at 192.168.2.21:8060/sip_peer_b

[sip_peer_b]
type=friend
secret=secret_b
context=from_sip
fromuser=sip_peer_a
host=dynamic
;port=8060
disallow=all
nat=yes
canreinvite=no
qualify=no
allow=alaw


After sip reload the reg. contact should contain the extension callback.
But it is registered as "s". like:
Reg. Contact : sip:s at 192.168.2.21:8060
====================================================================== 

---------------------------------------------------------------------- 
 (0109775) steinwej (reporter) - 2009-08-28 05:50
 https://issues.asterisk.org/view.php?id=15760#c109775 
---------------------------------------------------------------------- 
I 've tested the above configuration against trunk and yes, it parses the
config correctly. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-08-28 05:50 steinwej       Note Added: 0109775                          
======================================================================