* You are viewing Posts Tagged ‘incoming number’

CDR Question

Hi,

We have an asterisk box with Digium 4xE1 card running libss7. All is well, except for a CDR issue about incoming calls whose DNID (local numbers) are not valid.

In the dialplan, we do a check if the incoming call has a particular prefix for DNID. If it does not, then we hangup the call with 403 or 404, as applicable. For these calls, no “lastdata” is recorded. What we understand is, this is perhaps the desired behaviour, as the “lastapp” was
“Hangup” and not “Dial”.

What would be the strategy to correctly store the incoming number for these calls?

Regards

HASSAN

Using MixMonitor()

Hello Folks;

I appreciate all of the help so far – thanks.

Another question: I am using MixMonitor() to record calls and I would
like to include the called number/extension in the filename:

In my dialplan, I am able to save the file with the caller id in the
filename. However, what I am a little unsure about is the incoming
number/called number/extension – passing that information on to part of
the filename.

Does anyone follow me?

Glen

Linux RDNIS

RDNIS is Redirected Dialed Number Information Service. RDNIS contains Type of Number (TON), Presentation, and Redirecting Number (RGN), and Reason (busy, no answer, etc.). When redirecting calls, the Originally Called Number (OCN) contains, as its name suggests, the number that was originally called.

The RGN identifies the telephone number redirecting a call. For example, if one forwards a call on busy from home to another number, RGN contains the home number. This is useful if, for example, one is running a voice mail system and wants one incoming number to which everyone can forward calls. The RGN can then be used to determine the appropriate mailbox. This usually only works on a PRI.

Q.931 supports RDNIS Type of Number (TON), Presentation, and Redirecting Number (RGN). It is (IE) 115 on a DMS-100 switch, IE 116 on National-ISDN-2.

A note about wireless phones: the ‘forward all calls’ feature does not necessarily send RDNIS, but ‘forward when busy’, ‘forward when unavailable’, and ‘forward when unreachable’ are supposed to send RDNIS. Functionality may depend on wireless provider more than PRI provider.

Groupe Telecom and Bell Canada both support this on their PRIs.