Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
UDP info 1
- Thread starter Scott99
- Start date
-
1
- #2
Basically, if you enable UDP in your dialplan, you just assign extension-ranges (cha udp xxxx) a UDPCode xyz. This xyz must be administered in the AAR Analysis and given a route-pattern and/or a partioning number. In the AAR/ARS you can convert and (re)route calls to route-patterns and send them over particular trunk-groups or keep 'em in your Definity etc. etc.
That's for (really really) short how it works basically. Not enough time, room and interaction methods here to explain the whole of it. Right now I'm developing a training on the subject...so if you have more specific questions: just sound the alarm.
Good luck. (It's all pretty hard to understand if you're not into it...so I've learned the hard way
)
Kind Regards,
Maarten Copini
-Please let fellow members know if their post was of any help-
That's for (really really) short how it works basically. Not enough time, room and interaction methods here to explain the whole of it. Right now I'm developing a training on the subject...so if you have more specific questions: just sound the alarm.
Good luck. (It's all pretty hard to understand if you're not into it...so I've learned the hard way
)Kind Regards,
Maarten Copini
-Please let fellow members know if their post was of any help-
- Thread starter
- #3
Thanks Maarten.
The reason I'll be needing UDP is that I will be routing incoming faxes over an TN556 board to the fax server. At the moment I using data modules but they don't allow different caller ids to be sent over to the fax despite various suggestions from programmers. Seems the only way to go is to program the TN556 into a BRI trunk board rather than a WCBRI board. I'm then going to set up VDNs with VDn overide set to Y - route to extensions in the UDP which will then route over the BRI trunks hopefully carrying the extension of the VDN. When routing via Data modules the origintaing extension seen by the fax server is always the data module extension rather than the VDN extension - this means that only one profile can be used on each ISDN-2 line. What I need to know is how to convert this TN556 board into a BRI trunk board. I think to remove the admin of this board from the switch but I'm not sure of how do to this and how to introduce it as a trunk board. Any ideas?
The reason I'll be needing UDP is that I will be routing incoming faxes over an TN556 board to the fax server. At the moment I using data modules but they don't allow different caller ids to be sent over to the fax despite various suggestions from programmers. Seems the only way to go is to program the TN556 into a BRI trunk board rather than a WCBRI board. I'm then going to set up VDNs with VDn overide set to Y - route to extensions in the UDP which will then route over the BRI trunks hopefully carrying the extension of the VDN. When routing via Data modules the origintaing extension seen by the fax server is always the data module extension rather than the VDN extension - this means that only one profile can be used on each ISDN-2 line. What I need to know is how to convert this TN556 board into a BRI trunk board. I think to remove the admin of this board from the switch but I'm not sure of how do to this and how to introduce it as a trunk board. Any ideas?
Sorry, not familiar with the TN556...
anyone else?
Kind Regards,
Maarten Copini
-Please let fellow members know if their post was of any help-
anyone else?
Kind Regards,
Maarten Copini
-Please let fellow members know if their post was of any help-
scottyjohn
Technical User
Sorry if this sounds stupid Scott, but if the vdns have the "allow VDN Override" set to y, will they not then present the extension of the data modules and not the originating VDNs?
John
John
- Thread starter
- #6
no it's the other way round Scottyjohn.
Heres what's in the Avaya manual:
"Allow VDN Override? — Valid entries are y and n (default). This entry affects the operation of an agent’s display and certain options or data assigned to the VDN
when a call is routed through several VDNs. If the
field is set to y, the name of the VDN that appears on the terminating displaydepends on the administration and chaining of the subsequent VDNs and the AUDIX mail for the last VDN that is accessed. The default is n. "
Basically if the originating VDn was called 'Sales' and was routed to another VDN or data module the display and number of the originating VDN will be seen.
Heres what's in the Avaya manual:
"Allow VDN Override? — Valid entries are y and n (default). This entry affects the operation of an agent’s display and certain options or data assigned to the VDN
when a call is routed through several VDNs. If the
field is set to y, the name of the VDN that appears on the terminating displaydepends on the administration and chaining of the subsequent VDNs and the AUDIX mail for the last VDN that is accessed. The default is n. "
Basically if the originating VDn was called 'Sales' and was routed to another VDN or data module the display and number of the originating VDN will be seen.
- Status
Similar threads