Jump to content


< Back to Forum


 

Dnis


  • Please log in to reply

#1 ahmed.muneer 03 December 2017 - 05:23 PM

Dear VG team,

Greetings.

 

i was looking for a result variable to determine the call to which route to go, then i found $RV_DNIS, but i were facing a problem that once i sued it's showing me an old IP address, please find the attached VG engine and config.xml.



#2 SupportTeam 03 December 2017 - 07:32 PM

There are over 100 calls in that vgEngine trace and the DNIS for all of them is the same: 192.168.5.204

 

Can you explain in more detail what do you mean by: "it's showing me an old IP address" ? What is the DNIS that you were expecting?



#3 ahmed.muneer 03 December 2017 - 09:15 PM

in the config.xml i used to register the <RegClient> with this IP 192.168.5.204 ,and it's still showing the same.

note : all my calls coming from Avaya IPO V2 thru a SIP trunk

Avaya IP address is : 192.168.5.1

<VoIP_Registration>
<Display>Geidea</Display>
<Protocol>SIP</Protocol>
<RegServer>192.168.5.1</RegServer>
<RegClient>192.168.1.143</RegClient>
<LocalAlias></LocalAlias>
<Expires></Expires>
</VoIP_Registration>


#4 ahmed.muneer 03 December 2017 - 09:17 PM

what am looking for is i want to show my IVR IP address



#5 SupportTeam 04 December 2017 - 09:47 AM

Can you describe in more detail your network setup?

 

It looks like you have a SIP trunk pointing to the VoiceGuide IVR, and looks like you are registering it at restart time (but not Authenticating?).

 

It looks like the IP address of VoiceGuide system is 192.168.1.143, and IP address of the Avaya IPOffice which is providing the SIP trunk is 192.168.5.1

 

What is the 192.168.5.204 address of?

 

Is 192.168.5.204 maybe the address to which the calls are routed it initially?, and then 192.168.5.204 routes call to 192.168.5.1 which then routes call to 192.168.1.143 ?

 

It looks like the system at 192.168.5.204 and the system that is sending call to 192.168.5.204 is not passing on the number dialed, but is placing the 192.168.5.204 in the DNIS field.

 

Looking at WireShark trace will let you better see what information is supplied with the call, and sounds like you may want to run WireShark traces on traffic between 192.168.5.204 and the Avaya IPOffice, and probably on traffic arriving into the 192.168.5.204 as well.



#6 ahmed.muneer 04 December 2017 - 04:52 PM

Dear VG team,

 

VoiceGuide system was configured with this IP earlier 192.168.5.204  then we have changed it to 192.168.1.143 and in my network there is no more 192.168.5.204

that's why am wondering that 192.168.5.204  it's appearing in Vgengine logs as DNIS.



#7 ahmed.muneer 04 December 2017 - 05:48 PM

Dear VG team, 

 

You are correct i have found in the wire shark and on IPO that's 192.168.5.204 still there i have chagned it and am getting the bew DNIS , but i apprecaite your support to how to determine based on whch DNIS i can route the call by using the evaluate expression.

Thank you very much 



#8 SupportTeam 04 December 2017 - 07:08 PM

If DNIS information reaches VoiceGuide then VoiceGuide can use it to route calls etc.

 

Right now it looks like this information is lost by one of the switches in the path of the call route. You will need to ensure that those other switches pass on the DNIS information.