|
From: Henri H. <he...@or...> - 2011-02-04 00:13:38
|
1. and 3. are related, you need to fix 3. and it will also fix 1. Oreka should automatically pick up the SIP packets and report the phone numbers, if not the case it might be a variety of reasons but most likely your port mirroring is wrongly configured so the SIP does not even hit the recording server. 2. I have no idea. What exactly do you see? _____ From: Petr Gola [mailto:go...@ef...] Sent: 29 January 2011 16:30 To: ore...@li... Subject: [Oreka-user] Oreka - connection between call and recorded file (joined sessions, extracting telephone numbers) Hi, we're using Oreka recording in production environment for last year. We're recording about 10-20 calls simultaneously. It is great - we haven't found another working solution for this. But there are some issues. All we need is doing reliable connections between calls and recorded files... but 1) Some wav records contain more than one conversation (calls) in one file. For example three "joined" calls in the wav file. We have set up timeouts (<RtpSessionTimeoutSec> and <RtpSessionWithSignallingTimeoutSec> to "1") and it is better now - but not 100% - there are still same joined sessions. Can we debug RTP recording at Oreka? I think there should be some information like "call start" and "call end" in SIP protocol - does Oreka listen to this events? 2) There is also some problem with startTime of recording in the Oreka database - does Oreka make some buffering before writing timestampts for recorded files? 3) How to store called numbers to database? Is there any possibility to extract this information from SIP by Oreka? Thanks, Petr |