Hello, Everyone.
We have a PRI line with several DIDs. We do not want only a single outgoing caller id (OCID). We want to be able to set the OCID per call
to one of our DID numbers. This is what we did.
We created Zap trunks, all Zap/g0, but each having its unique OCID. "Duplicating" a single Zap trunk didn't seem to be a problem,
as trixbox created various OUT_1, OUT_2, etc. in extensions_additional.conf. Then, we routed outgoing calls to the trunk with
the desired OCID (via Outbound Routes) based on prefixes (e.g. 044) that we dial before the number. OUT_1 was left as the default
trunk to catch cases in which a prefix was not dialed.
The Outgoing Route pointing to the default trunk of OUT_1 contains a long list in Dial Patterns, things like "NXXXXXX", "NXXNXXXXXX", etc.
Things didn't go well when we added corresponding Dial Patterns into the other Outbound Routes. For example, for the Outbound Route
corresponding to the prefix "044" we had Dial Patterns that looks like this: "044|NXXXXXX", "044|NXXNXXXXXX", etc. When we did that, we
had dropped calls on those trunks, even though those calls did signal the correct OCID. Calls on the default trunk were all good.
We seem to have solved the problem by simplifying the Dial Patterns on the Outgoing Routes corresponding to the non-default trunks,
using a single pattern such as "044|." for each one. So far, no calls have dropped.
So, it seems to us that the cause of the dropped calls was our having long lists for Dial Patterns in the various Outbound Routes. Can anyone
comment on this?
Member Since:
2008-05-05