Summary:	ASTERISK-05272: Changes between 1.2-beta1 and latest CVS HEAD make all SIP calls from PROXY fail..
Reporter:	Stephen Lombard (grumpy)	Labels:
Date Opened:	2005-10-10 04:45:10	Date Closed:	2011-06-07 14:02:36
Priority:	Major	Regression?	No
Status:	Closed/Complete	Components:	Channels/chan_sip/Interoperability
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:
Description:	Using SER as a front-end proxy and dialling an invalid extension I get this on Asterisk 1.2beta1 Oct 10 17:30:36 WARNING[29605]: pbx.c:2278 __ast_pbx_run: Channel 'SIP/digitronix.sip.digitronix.com.au-086718e0' sent into invalid extension '900' in context 'digitronix.pstn.digitronix.com.au', but no invalid handler However, the same extension on CVS HEAD (as of 10 October 2005) gives: Oct 10 17:30:36 WARNING[29918]: pbx.c:2362 __ast_pbx_run: Channel 'SIP/digitronix.sip.digitronix.com.au-086718e0' sent into invalid extension '900' in context 'digitronix.pstn.digitronix.c', but no invalid handler Valid extensions on Asterisk 1.2-beta1 pass through perfectly between SER and Asterisk but irrespective of the extension, whether valid or not, fail on the latest CVS HEAD.
Comments:	By: Stephen Lombard (grumpy) 2005-10-10 05:14:29 I guess further to that, here's how the truncting of the domain (always last 5 characters) affects things: Oct 10 17:30:36 WARNING[29918]: pbx.c:2362 __ast_pbx_run: Channel 'SIP/digitronix.sip.digitronix.com.au-086718e0' sent into invalid extension '900' in context 'digitronix.pstn.digitronix.c', but no invalid handler Oct 10 17:30:36 WARNING[30232]: pbx.c:2362 __ast_pbx_run: Channel 'SIP/ham.sip.digitronix.com.au-086718e0' sent into invalid extension '900' in context 'ham.pstn.digitronix.c', but no invalid handler Always the last 5 characters being truncated irrespective of the domain's length... By: Olle Johansson (oej) 2005-10-10 12:07:24 According to the instructions, you need to provide a complete SIP debug for SIP bugs you report. By: Olle Johansson (oej) 2005-10-11 23:39:02 And for this, we will need to see your dialplan and sip.conf as well. Thank you for a quick reply, since we are eager to find this bug. By: Olle Johansson (oej) 2005-10-13 16:26:28 We will close this if we do not get a reply soon, since we can't replicate it. By: BJ Weschke (bweschke) 2005-10-13 19:11:08 Can we have a copy of ser.cfg too so we can get close to reproducing the environment to reproduce? By: twisted (twisted) 2005-10-17 23:11:12 grumpy:  we need more information.  If you cannot provide the requested information, please at least let us know what we can do to reproduce the issue.   Thanks By: Olle Johansson (oej) 2005-10-20 01:41:58 No answer from reporter. Please re-open if you have responses.