Summary:ASTERISK-01214: [patch] Incoming H.323 calls via E164 or E164 Prefixes get sent to configured context
Reporter:slepp (slepp)Labels:
Date Opened:2004-03-15 05:33:00.000-0600Date Closed:2011-06-07 14:04:42
Versions:Frequency of
Environment:Attachments:( 0) h323-1.35-revised-2.diff
( 1) h323-1.35-revised-3.diff
Description:With this patch, incoming H.323 calls with chan_h323 are checked against the list of e164 numbers and prefixes that have been registered with a gatekeeper. If a matching e164 is found in any alias, it will send it to the context= specification of that specific alias.

If no exact match on the e164 dialed digits is made, it will attempt to find a matching prefix. It compares the first strlen(our prefix) characters of the incoming e164 number against each prefix (iff the incoming number is longer than the alias' prefix).

If a match is found there, it will send it to the related context for that alias.

If no matches are found, it is sent to default_context as defined in the [general] section and logs a warning.

With the current chan_h323 driver, it sends all e164 calls to the default_context, no matter which alias the prefix/e164 number belongs to. This changes that.

It also adds a 'h.323 show aliases' command to the CLI to allow for viewing of the configured aliases and their related contexts.
Comments:By: () 2004-03-15 06:01:43.000-0600

Updated the patch to revision 2. Fixed up so the formatting is consistent with the code it's patching. Also added an h323.conf.sample update to explain more of what goes on with e164/prefixes.

By: () 2004-03-17 04:57:19.000-0600

With revision 3, fixed a typo in a function name (needed e164, not prefix).

By: jerjer (jerjer) 2004-03-18 15:45:50.000-0600

Applied to cvs -HEAD

By: slepp (slepp) 2004-03-21 20:13:36.000-0600

It was rolled back. Further testing/development is needed.