Summary:ASTERISK-16186: Context names ending on space are not processed correctly.
Reporter:Hans Bos (hansbos)Labels:
Date Opened:2010-06-01 12:45:26Date Closed:2010-06-01 12:55:54
Versions:Frequency of
Description:If a call arives for a peer whose context name end on a space, e.g. "Trunk ",
then you receive the following message:
Call from 'xxxxx' to extension 'xxxxx' rejected because extension not found.

The call is rejected.

If the space is removed everything works.

I had this problem with 1.4.22 and 1.4.31


In the log I see:
[Jun  1 10:56:46] VERBOSE[2349] logger.c: Looking for xxxxx in Trunk (domain xxx.xxx.xxx.xxx)
[Jun  1 10:56:46] VERBOSE[2349] logger.c:
[Jun  1 10:56:46] VERBOSE[2349] chan_sip.c: Call from 'xxxxx' to extension 'xxxx' rejected because extension not found.

Comments:By: Paul Belanger (pabelanger) 2010-06-01 12:55:35

This is a configuration issue; not a bug.

[trunk] ; Valid

[trunk ] ; Not valid.

Thanks for your comments. This does not appear to be a bug report and we are closing it. We appreciate the difficulties you are facing, but it would make more sense to raise your question in the support tracker, http://www.asterisk.org/support