[cisco-voip] RDNIS delivery

[Andrew Dignan]

I have not used this tcl script but in areas where we could not get RDNIS
we used POTS lines and the vm-integration commands:

dial-peer voice 92499 pots
 destination-pattern 17775551212T
 port 2/0/8
 prefix 17775551212,,,,,,
!
dial-peer voice 924991 pots
 preference 1
 destination-pattern 17775551212T
 port 2/0/9
 prefix 17775551212,,,,,,
!
dial-peer voice 924992 pots
 preference 2
 destination-pattern 17775551212T
 port 2/0/10
 prefix 17775551212,,,,,,
!
dial-peer voice 924993 pots
 preference 3
 destination-pattern 17775551212T
 port 2/0/11
 prefix 17775551212,,,,,,
!
dial-peer voice 924994 pots
 preference 4
 destination-pattern 17775551212T
 port 2/0/12
 prefix 17775551212,,,,,,
!
dial-peer voice 924995 pots
 preference 5
 destination-pattern 17775551212T
 port 2/0/13
 prefix 17775551212,,,,,,
!
!
call-manager-fallback
 voicemail 17775551212
!
!
vm-integration
 pattern direct * CGN
 pattern ext-to-ext no-answer # FDN #2
 pattern ext-to-ext busy $ FDN #2
 pattern trunk-to-ext no-answer # FDN #2
 pattern trunk-to-ext busy # FDN #2

Regards,

Andy

> Hi
>
> I have a number of sites that cannot get RDNIS end to end to our central
> Unity system.  I'm wondering if anyone is familiar with the
> rdnis_restore.tcl script and used it with any success to work around this
> problem.  I've tried it and the script seems to be modifying the call
> correctly because I see it when I debug the h225 from the central site
> gateway to call manager.  However, the call arrives to Unity looking like
> a direct call still.
>
> thanks
>
> Kris Seraphine
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>