Ovidiu,
haven't yet migrated, but I do not foresee issues with that - I will
adapt :)
Regards,
Bogdan
Ovidiu Sas wrote:
Should I understand that all rtpproxy users have switched to
rtpproxy_offer/rtpproxy_answer?
If there are no objections, sometimes next week I will remove the old
Hi Paul,
you need a substitution, replacement or simply matching ?
Regards,
Bogdan
Paul Smith wrote:
Hi Bogdan,
Thanks for the reply. I am using dialplan module for mangling the
dialled number to local valid service codes and e164 destinations.
I was hoping to use a simple field in the
Hello Thomas,
at the moment I am refactoring the SEAS module to work with current
sip-router, still haven't poked into current OpenSIPS to see how
difficult the port will be, but expect to update it in the following
months (after rework for sip-router is done).
well, SEAS is mainly composed of 2
Hi,
I am newbie for Opensips,
I installed Opensips 1.6.3 notls.i386 and begin to testing.
Unfourtunately, My softphone(Eyebeam) did not register Opensips.
Please help.
Opensips Ngrep log;
192.168.126.1:6109 - 192.168.126.144:5060
REGISTER sip:192.168.126.144 SIP/2.0.
To:
Use digest authentication in your sip client.
From: users-boun...@lists.opensips.org
[mailto:users-boun...@lists.opensips.org] On Behalf Of Mustafa Aykut
Sent: Thursday, September 23, 2010 1:02 PM
To: users@lists.opensips.org
Subject: [Spam ***] [OpenSIPS-Users] eyebeam softphone
Hi,
Hi Bodgan,
Mainly matching, to allow me to verify that a customer owns the CLI he
is presenting.
Ideally I was thinking substitution as I can then add as well in one
operation.. but I can do that as 2 separate operations.
So... how can I do a dynamic match using an account specific pattern?
Excellent. We are making progress here. Later on, we will need to
break the nathelper module in two:
- nathelper: dealing with NAT related issues
- rtpproxy - connector to the rtpproxy server
Regards,
Ovidiu Sas
On Thu, Sep 23, 2010 at 3:30 AM, Bogdan-Andrei Iancu
bog...@voice-system.ro
Hi,
I've got a server running OpenSIPS with MediaProxy 2.4.2 and it seems that the
duration
in the returned statistics includes early media (e.g. ringing) and therefore
isn't ideal for
billing purposes.
This seems to be different from my MediaProxy 1.x installation on an older
OpenSER
SIP Scenario has been out for a while. does it right from pcaps... it's
fantastic:
http://www.iptel.org/~sipsc/
On Wed, Sep 22, 2010 at 7:12 AM, Andrew Pogrebennyk
andrew.pogreben...@portaone.com wrote:
Iñaki,
You may want to check the siplogview (http://siplogview.sourceforge.net)
tool
