Hi Jeff,
Jeff Kronlage wrote:
We'd like to implement the ability to organize CDRs by account code,
and/or to restrict calling to certain areas based on code.
These are different things:
- how you organize CDRs is something not opensips related - you
simply get account data (you can
Hi Brett,
Brett Nemeroff wrote:
Bogdan,
I presently record the 200 OK ACK in my ACC, but I don't seem to
actually utilize it for anything at present. If I did the fix jeff
mentioned, will I no longer get that ACK in ACC?
yes, it that case you will not get the ACK in the acc (at least not
Hi Jeff,
Some time, simply experiment with some configurations may provide a
quicker solution rather than start digging to the bottom to see what's
happening - of course, this is a good approach only for quick fixes - as
you said, at a point, you really need to understand how it's working.
Hello Adam,
There are 2 ways to get this working:
- use opensips 1.6, where via the callcontrol module you can send
custom data (including the source IP)
- in 1.5, you can try to mask the src IP in some of the fields that
are already sent out - maybe RURI ...
Regards,
Bogdan
Adam
Hi Sanjeev,
what is the account you created? I can check the state of your pending
account.
Regards,
Bogdan
Sanjeev BA wrote:
Hi,
I have been trying to login to OpenSIPS website using the Login option.
However, everytime I click on the confirmation email link, I see a
webpage with
Hi,
I am trying to get OpenSIPS working with OpenXCAP. Has anyone in the group,
tried this before?
OpenXCAP best practices mentions the following.
The rpc management interface exposed by OpenSER needs to be protected by
iptables or other methods otherwise is reachable from the network.
Most of the software you mentioned had been designed to run with SIP
URI in the form of u...@domain.
The short answer is that it will not work with only IP addresses
without a major re-engineering.
--
Adrian
On Oct 7, 2009, at 4:59 AM, Adam Botbyl wrote:
I am trying to setup a
The problem you mentioned has been fixed in OpenSIPS xml_rpc module. I
have just updated the wiki page to reflect this.
--
Adrian
On Oct 7, 2009, at 9:33 AM, Sanjeev BA wrote:
Hi,
I am trying to get OpenSIPS working with OpenXCAP. Has anyone in the
group, tried this before?
The only advantage that remains is the configurable access list for
who mis allows to connect over xml_rpc. This ACL is not available in
OpenSIPS module.
--
Adrian
On Oct 7, 2009, at 11:00 AM, Iñaki Baz Castillo wrote:
2009/10/7 Adrian Georgescu a...@ag-projects.com:
The problem you
2009/10/7 Adrian Georgescu a...@ag-projects.com:
The only advantage that remains is the configurable access list for
who mis allows to connect over xml_rpc. This ACL is not available in
OpenSIPS module.
ok, so basically with iptables the same feature can be achieved.
Thanks a lot.
--
Iñaki
Hi all,
I am using call controller-2.0.3 .
Problem 1: If i place the *call_control( )* function after setting
diverter_avp the call controller *takes all the accounts as postpaid*. what
is the reason for this behavior
Problem 2: Same kind of code behave differently on 2 different opensips
Hi,
I am new to openxcap, have installed Version 1.1.2 on redhat linux box,
but having problem while starting the server.
looks like it is failing at process.daemonize(pidFile)
1.first of all is this supported on redhat linux?
2. Is it mandatory to have Mysql installed to start xcap
2009/10/7 Susheela sushee...@alcatel-lucent.com:
Hi,
I am new to openxcap, have installed Version 1.1.2 on redhat linux box,
but having problem while starting the server.
looks like it is failing at process.daemonize(pidFile)
There are various possible reasons (perhaps, you'll need
Try executing with the --no-fork option. It may give you some clue.
Regards
Sanjeev
-Original Message-
From: users-boun...@lists.opensips.org
[mailto:users-boun...@lists.opensips.org] On Behalf Of Peter Lemenkov
Sent: Wednesday, October 07, 2009 8:58 PM
To: OpenSIPS users mailling list
Hi,
I'd like to know what exactly does this note mean: (from the documentation)
NOTE that the changes on the request that are made after this
function call will not be saved into transaction!!!
What is the limitation in practice / what is saved into transaction.
In details - if I have an INVITE
Hi Stan,
Just to explain you want actually happens when you do t_newtran() :
This function forces the creation of the transaction (which otherwise is
automatically done by functions like t_relay() and t_reply() ). Part of
creating the transaction is cloning of the current request into shared
Bogdan,This kind of explanation is really helpful. If you don't mind, I'd
like to ask a little more detail.
Can you please explain when it would be necessary to force creation of a
transaction where t_relay wouldn't suffice?
Thanks,
Brett
On Wed, Oct 7, 2009 at 9:50 AM, Bogdan-Andrei Iancu
2009/10/7 Susheela sushee...@alcatel-lucent.com:
2. Is it mandatory to have Mysql installed to start xcap server.
Please read the full documentation as it clearly says that MySQL is required.
--
Iñaki Baz Castillo
i...@aliax.net
___
Users mailing
2009/10/7 Brett Nemeroff br...@nemeroff.com:
Can you please explain when it would be necessary to force creation of a
transaction where t_relay wouldn't suffice?
It's really not that t_relay() doesn't suffice, but rather that
t_relay() is at the end of the script and if one process starts
Hi Brett,
if you create sooner the transaction, you have bigger chances to catch a
retransmission asap - detecting retransmission asap helps you because
you avoid any processing (in script) for a retransmission.
Regards,
Bogdan
Brett Nemeroff wrote:
Bogdan,
This kind of explanation is
On 7 Oct 2009, at 14:22, ASHWINI NAIDU wrote:
Hi all,
I am using call controller-2.0.3 .
Problem 1: If i place the call_control( ) function after setting
diverter_avp the call controller takes all the accounts as postpaid.
what is the reason for this behavior
The diverter_avp if
Hi,
Trying to get sip trace functionality on opensips-cp working also.
Toggling the trace on and off from the web interface appears to be working
fine.
Oct 7 13:08:59 [2332] DBG:mi_xmlrpc:default_method: starting up.
Oct 7 13:08:59 [2332] DBG:mi_xmlrpc:default_method: done looking the
Hi Marc,
loading the siptrace module is not enough. You need to use the
sip_trace() function and set the trace_flag (for transaction tracing). See:
http://www.opensips.org/html/docs/modules/1.5.x/siptrace.html#id228291
Best regards,
Bogdan
marcher wrote:
Hi,
Trying to get sip trace
I am trying to setup OpenSIPs to run behind a firewall, and not
finding much information regarding how to get OpenSIPs to be aware of
the public IP for it's signaling. The firewall is setup with a 1 to 1
NAT for the public and private IPs, and right now all udp and tcp
traffic is being passed
Hi Daniel,
try using the advertise_address and advertise_port to force opensips in
using the public IPs of the NAT:
http://www.opensips.org/Resources/DocsCoreFcn#toc24
Regards,
Bogdan
Daniel Goepp wrote:
I am trying to setup OpenSIPs to run behind a firewall, and not
finding much
Thanks for the information, that seems to at least change the Via, but
RTPproxy is still not handling this well. It will only give it's
private IP back to OpenSIPS, so I end up wtih:
Connection Information (c): IN IP4 10.250.7.164
I will try and see if I can work around this on the RTPproxy
After further investigation, this only updating the Via header, but
the RR is remaining untouched:
Record-Route: sip:10.250.7.164;lr=on
Ideas about how I might get this field updated correctly?
Thanks
-dg
On Wed, Oct 7, 2009 at 2:10 PM, Bogdan-Andrei Iancu
bog...@voice-system.ro wrote:
Hi
Hi Bogdan,
I appreciate you taking the time to answer my basic questions in getting
opensips-cp functional with my opensips implementation.
I had read the link you included, but its still not clear to me where the
sip_trace function should be called within the opensips config file.
My opensips
Hi,
My mediaproxy is just stop working for no reason, after my testing
server (opensips+dispatcher+relay) changed IP address. I modified
/etc/mediaproxy/config.ini with new IP as below.
[Relay]
dispactchers = public IP
relay_ip = public IP
log_level = DEBUG
[Dispatcher]
socket_path =
Forget to add, the error when making a call is as below.
Oct 8 15:53:18 debian /sbin/opensips[2906]: Media Session starts
Oct 8 15:53:18 debian media-dispatcher[2780]: error: Error processing
request: No suitable relay found
Oct 8 15:53:18 debian /sbin/opensips[2906]:
30 matches
Mail list logo
