Call Recording and "Dynamic Trunks" (PRI)

[DJensen99]

This is a question I think I already know the answer to, yet I need to relate this information to a vendor.

We have just installed a call recording system with our Legend (CKE4 upgraded to Magix 3.0). 3 PRIs, all one pool, trunks 809 to 880 (including D channels), the PRIs are being tapped and sent in parallel to the call recorder.

The calls appear to be recording correctly, but the call recorder is associating random trunk numbers that in NO way coincide with the SMDR output. The vendor is stating that we will never be able to use the SMDR detail to match extension to calls because "your PBX is outputting dynamic trunks instead of fixed trunks." Having done the factory reset and all programming on this Legend/Magix based on the guide on this site, I am pretty sure that the correlation is 1:1 for trunks to PRI channels, and everything I have viewed on the call detail recorder that we have used for the last 2 years syncs up to the trunk info shown on the MLX phones, the best that I can tell. My gut feeling is that the vendor doesn't know what's going on here and is throwing up their hands.

Any suggestions? Anyone familiar with PRI-level call recording solutions for the Magix/Legend?


Thanks!

 

[memphisribs]

Your vendor is correct, B channels do not match trunks on the Merlin, PRI protocol negotiates the B channel to use on a dynamic basis. Found this to be true when working on trying to split a PRI for different pools. Had to assign B channels to separate b channel groups so calls would ride on the B channels that were desired, just creating the pools would not dictate the B channels used.
Hope this helps

43 years in the business and counting.

 

[DJensen99]

Ah ha - I was wondering if that would work. Time to create 69 b-channel groups. And then I can tweak the trunk usage order as well...

Thanks! Valuable information!