[asterisk-bugs] [Asterisk 0015202]: Parsing of register statements in sip.conf fails when transport is used without extension
Asterisk Bug Tracker
noreply at bugs.digium.com
Fri Jun 19 16:19:56 CDT 2009
The following issue has been ASSIGNED.
======================================================================
https://issues.asterisk.org/view.php?id=15202
======================================================================
Reported By: okrief
Assigned To: dvossel
======================================================================
Project: Asterisk
Issue ID: 15202
Category: Channels/chan_sip/Registration
Reproducibility: always
Severity: major
Priority: normal
Status: assigned
Asterisk Version: 1.6.1.0
Regression: No
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2009-05-27 01:31 CDT
Last Modified: 2009-06-19 16:19 CDT
======================================================================
Summary: Parsing of register statements in sip.conf fails
when transport is used without extension
Description:
In sip.conf, next line works ok
register => trunk4ipbx:passtrunk4ipbx @192.168.100.129
Replacing the above line with the one bellow, produces error message
printed below
register => udp: //trunk4ipbx:passtrunk4ipbx @192.168.100.129
May 26 17:58:42] NOTICE[2859]: chan_sip.c:20169 sip_parse_host: '/' is not
a valid port number on line 25 of sip.conf. using default.
[May 26 17:58:42] WARNING[2859]: chan_sip.c:6560 sip_register: Format for
registration is [transport
://]user[:secret[:authuser]]@domain[:port][/extension][~expiry] at line 25
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
2009-06-19 16:19 dvossel Status feedback => assigned
2009-06-19 16:19 dvossel Assigned To => dvossel
======================================================================
More information about the asterisk-bugs
mailing list