Trunk Number in Meridian

[Vic]

Can someone please tell me how I can retrieve a trunk number in a strategy?

It seems like in case of inbound call, OrigAdress contains the trunk number. It also looks like OrigAddress is contained inside ExtensionData. How can I retrieve it from there?

Thanks,
Vic

[Richard]

Vic,

Under the IRD miscellaneous icon "traffic light" you will find an icon for functions. If you use this in your strategy you can select CallInfo and under that select different information. Trunk number may not be accessible so you may have to associate that to a particular DN which you can retrieve. Please explain further and I will see what I can do?

[Vic]

Richard,

I was hoping about retrieving trunk number using ERS so that we could have a simple way to correlate ConnIDs with trunks. In a multisite environment, the trunk that calls arrives and the trunk that is being used on a satellite site are different. I was hoping to be able to record the original trunk that the call arrived on...

Is there a simple way to do it in ERS? With CallInfo, would ERS retrieve this information given that it is connected to the first TServer?

[Richard]

Since you are referring to a Meridian switch are both switches Meridian? If so you can add the NACD package that way you will be able to get a Universal CallID passed from switch to switch and track the call from one switch to the other. This is the best solution in regards to tracking the call across the switches.

Otherwise it is difficult to track the same call unless through external router you associate the 2 connIDs. Please send me email and give me more details.

[Josee]

I Victor, I'm curious. In which case do you need this information ?

[Vic]

I am trying to tie together a logger with Genesys so that we would be able to easily find the conversation of a particular agent in the logger files. The voice logger we are using does not have this functionality, so we need to develop a thirdparty app that would tie together trunk info and connection id.