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

Server Edition calls not anti-tromboning 1

Status
Not open for further replies.

Qzwsa

Technical User
Sep 26, 2011
309
CA
Hey guys. First things first, this is my companies first server edition install so I'm sure there are things I've done wrong and/or inefficiently.

The set up is thus:

500v2 @ r9.1 with a PRI. Call comes into the system and is directed via ICR to a voicemail module, obviously hosted on the server, also @ r9.1.
User selects an option and is transferred using a standard transfer block to a huntgroup set up as a call centre, with users on digital phones connected to the original 500v2.

My question is why, in system status under active calls, it has one entry for the call coming in on the trunk for the PRI (9) terminating on the trunk for the Server (17)
plus a call from the server trunk (17) to the digital endpoint. I understand that the call is obviously directed out to the VM on the server, but should it not drop the two channels linking in the server and just have the PRI connected to the digital station?

ICR is - VM:myAA
Group is - Longest waiting with 14 users (only about 3 logged in at this point as it is the end of the day, but doubt that matters!)
Trunk 17 to server has direct media path enabled (should it be?)

 
I am not familiar with the way it is programmed but within a SCN each line must have unique Line IDs, both incoming and outgoing.
Interconnect lines(SCN lines) only have outgoing IDs to set.
Only then anti tromboning will work.
 
Is Allow Direct Media Path selected on the SCN trunks? I don't know if you will ever see what you are looking for in SSA. I think the call will show even though audio is not following the path.
 
Intrigrant, when programming server edition the systems throw errors if you have any line IDs that are duplicated within the entirety of the network. All my line IDs are based off the 3rd IP address octet so there's a plan in place that prevents duplicates.

Bluebells, yes. I stated in my OP "[highlight #00ff00]Trunk 17 to server has direct media path enabled[/highlight]
 
I know about the errors but some ignores them and I only wanted to be helpfull but you did not gave enough info to start with.
Direct media path has nothing to do with anti-tromboning...
Maybe server edition doesn't support or use anti-tromboning
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top