Get Called Number (dnis) Using Isdn Bri

[Guest Brian]

Hi,

 

I use Fritz Card USB v2.1 on ISDN line, VG v. 5.2.5000, located in Europe

 

When I call from cellphone to VG IVR system, the $RV_DNIS variable contains the called number (my ISDN number where the IVR runs)

 

But when I call via VoIP using computer, this variable is empty (because the caller (VoIP company) is outside my country and has "hidden number" AND/OR my Telecom provider does not supply me with DNIS info in this case)

 

The interesting thing is that application supplied with the modem "Protocol ISDNWatch" logs every inbound/outbound call and recognizes Called number EVERY time even if VoIP call. Therefore I guess that this application doesn't use DNIS info. It somehow must get the called number in another way. I really need these Called numbers every time :-/

 

If I understand this correctly, the system Works this way

 

VoiceGuide <-> ComISDN <-> Modem Software.

 

So where should I look for the called number ?

Well I can access the "Protocol ISDNWatch" call log file (it is located somewhere at HDD) and eventually try to pair off these "Called numbers" using Time of call supplied by Voice Guide and time of call in this log file AND using estimate call length in VG and in this log.

 

But this isn't the best solution because

a) Call date/time differs a bit between VG and that log

What if two calls started at the same time, both from hidden number, both the same length :-)

c) I need Called Number almost in real-time. I am not sure how much time the ISDNWatch needs to update the log after finishing a call and when it updates the log.

 

I can play with this a couple of hours and it may work...

 

But isn't there any magic solution ? :-)

 

----

more info:

I use both B-channels. Each has it's own number assigned.

I know about variable $Rv_LineId... but thats not solution in this case.

----

[SupportTeam]

Sounds like this question should be directed to the ComISDN driver supplier.

 

VoiceGuide will just use the DNIS as provided by the hardware driver (in this case ComISDN).

 

Please contact ComISDN about it, and provide them all the log files etc.

 

(if you can post the Protocol ISDNWatch log file here as well we can look at it and maybe come up with some advice as well)