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 Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

difference between.... 1

Status
Not open for further replies.

mikeyb123

Programmer
Jul 1, 2003
1,801
GB
Voice Networking and Voice Transport??

We have a couple of passports doing voice and data over a atm link

Network ring again (a telecom feature) will work on voice transport but not on voice networking.

any clues?

If it's nortel then they'll be a patch involved........

It's not getting any smarter out there. You have to come to terms with stupidity, and make it work for you.
 
Voice Transport is basically just 'nailed-up' voice (with a limited ability to switch). Voice networking is more flexible, using ingress call routing based on dialled numbers to automatically select the optimal path. Both require PORS (Path Oriented Routing System) an NetSynch - the two Nortel proprietary systems used to create fixed-path, jitter-controlled and packet-ordered paths, and ene-to-end synchronisation, respectively. If an intermediate passport in a network has these two things but no "voice" configured (Vroute/SVS, VS, VNCS etc), then it is still capable of "voice transport" - a term that Nortel uses confusingly to apply to the nailed up 'VS' type of voice configuration, rather than the 'Vroute SVS' type which is generally called Voice Networking.

As to your "Network Ring Again" problem, it's probably a signalling channel problem - what sort of signalling are you seeing from your carrier? Voice transport is probably using something like a Common Channel Signalling (CCS) connection which is just being shipped uninterpreted by a Bit Transparent Data Service (BTDS) to the next PABX/PBX. Using Voice Networking, however, you may be trying to decode a proprietary (or at least unsupported by Nortel) feature/signalling. Can you look at debug output from your signalling channel (don't forget to enable debug datastreams to your telnet etc session as well)?

Oh and as a matter of course, ask your local Nortel folks about relevant patches anyway! Good luck...
 
Thanks NTPeave,

We've sent traces to Nortel to see what's going on here.

BAsically we have a nortel meridian one end, passports in the middle and another nortel meridian at the other. both meridians are using the same sl1 interface/mcdn proprietry nortel.

nortel all the way and the poxy thing doesn't work....

It's gonna need a patch!!



It's not getting any smarter out there. You have to come to terms with stupidity, and make it work for you.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top