Can we limit the time on a meet me conf. vdn/vector?
We have had instances where a user didn't disconnect and got billed for a 15 day call as the bridge kept the call active, the call originated thru our 800# number.
We have problems with this when users on analog phones accidentally switch-hoo-flash and conference two ports onto the same conf call.
We have not found a solution for this other than to manually look for active meet-me conference bridges (like in the middle of the night).
Fortunately this doesn't cost us TF or LD charges since it's only used locally but it does cause the users a problem because then they are placed directly into the conference without being asked for the pin.
I thought I might be able to use CDR data but the data feed is only sent upon the call completion and so I don't get the alert until the call disconnects. y that time it may have been connected for hours/days.
I have an exception rule created in CMS for all trunk groups to send out an exception if a trunk has been in use for more than 5400 seconds (90 minutes). Then I can chase down any thing that might come up and find out the reason why.
Not an answer to yoru question, but something that might help out.
Susan “Before you criticize someone, you should walk a mile in their shoes.
Then, when you criticize them, you are a mile away ...
and you have their shoes.”
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.