This was something new to me:
If an original call arrives and 3cx uses the default settings, The called number is guessed from the to:user part. Correct.
However if a diverted call arrives, this header contains the number which was originally called. This is nice, but will identify the called number incorrect. If you want to route the call to the correct destination the header: Request Line URI: User part has to be selected.
But if you want to make a special extension for forwarded calls you can. Leave the CallerID identification default, and add the number which diverts the call to the ddi of the trunk. Then add a new extension with this DDI or add this DDI to the matching extension to route the call to the default extension matching the called number.
If an original call arrives and 3cx uses the default settings, The called number is guessed from the to:user part. Correct.
However if a diverted call arrives, this header contains the number which was originally called. This is nice, but will identify the called number incorrect. If you want to route the call to the correct destination the header: Request Line URI: User part has to be selected.
But if you want to make a special extension for forwarded calls you can. Leave the CallerID identification default, and add the number which diverts the call to the ddi of the trunk. Then add a new extension with this DDI or add this DDI to the matching extension to route the call to the default extension matching the called number.
