Hello,
Just installed opensips control panel and some things are not working:
I noticed that selecting the SIP Trace feature was initially giving me
on-screen error:
Array ( [0] = sorry -- cannot open write fifo )
So I then uncommented the sections in
Hi,
I want to know how can I check the peers of source and destination phones?
Like if both phones are located (registered) on one UAS(OpenSIPS) can call
SIP-SIP, if any one phone is registered on UAS and other is on PSTN, call
will be re-routed to SIP-PSTN. In case of SIP-SIP, lookup(location)
Hi,
On 16/3/10 11:47 AM, Paris Stamatopoulos wrote:
Hello everyone,
I’ve been struggling for a few days with OpenSIPS and OpenXCAP and I’ve
reached a certain point where I think I could really use some help on
the matter. I’ve configured a dedicated OpenSIPS instance with pretty
much the
Hi,
Use the uac_replace_from() to change the URI only and build a new URI
based on the old one:
$var(new_uri) = sip:+$fU+@10.200.0.5 ;
uac_replace_from($var(new_uri))
or, much simpler:
uac_replace_from(sip:$...@10.200.0.5)
see: http://www.opensips.org/Resources/DocsCoreVar16#toc39
Hi Ahmed,
if the destination number (called number) is not a local subscriber (a
SIP user), you simply route the call to a PSTN GW (you do this re-route
from the script)
To check if a user is a local subscriber, you can either check a pattern
(like all my local users are alphanumeric, or all
Hi Christian,
does your opensips load the mi_fifo module and create a fifo file with
the same name as the fifo you configured in the opensips-cp boxes? (note
that the fifo is created automatically by opensips at startup).
also take care and check the permissions of the fifo file - if you run
Hi Jeff,
as opensips will act as b2b, your call will be actually split in 2 calls
(from SIP point of view) - a call C1 from GW to opensips and another one
C2 from opensips to UAC. So at re-INVITE time, opensips b2b will hung up
C2 and replace it with a C3 to a new destination, bridging it with
Thanks Bogdan,
I've checked that mi_fifo is loaded, and that /tmp/opensips.fifo is created by
user/group opensips:opensips
Based on what I could find via google, I made the apache user part of opensips
group.. Buy now I get a new error on the SIP Trace main screen:
sorry -- reply fifo opening
Hi Christian,
The OpenSIPS CP 4.0 tar ball had a bug that was causing the error that
you are encountering. This bug was fixed two days ago. Please download
the latest tar ball and give it a try - it should work fine now.
Regards,
Alex
On 3/18/2010 10:38, Christian Vo wrote:
like MI tool:
Hello Saúl,
Thank you for your reply!
Thanks for your report! Unfortunately I've been unable to continue
fixing the existing bugs in OpenXCAP, but I can tell you that shortly
we'll have a new release with the existing bugs fixed. If you find any
other bug just open a new bug report :)
Hi Bogdan,
Thanks for reply. I forgot to mention earlier that for I'm using OpenSIPS +
FreeRadius, where radius is doing accounting and authentication. I used
aaa_does_uri_exist() function as well, but seems not working or making
mistake while implementing it. On other hand using
HI Alex
did you find new issue on opensips cp
Thank youHa`
--- On Sat, 3/13/10, Alex Ionescu a...@opensips.org wrote:
From: Alex Ionescu a...@opensips.org
Subject: Re: [OpenSIPS-Users] Problem with OpenSIPS Control Panel 4.0
To: OpenSIPS users mailling list users@lists.opensips.org
Date:
Hi,
Actually there were a few issues that were found and solved the last few
days. I hope you won't have anymore problems if you download the new 4.0
tarball.
So, give it a try and let me know.
Regards,
Alex
On 3/18/2010 13:35, ha do wrote:
HI Alex
did you find new issue on opensips cp
2010/3/17 Patrice Dalle patda...@gmail.com:
Hi,
Can opensips put the optional display-name of a watcher within the XML
payload of a NOTIFY related to presence.winfo?
I could not get such display-name? Is it supported?
OpenSIPS doesn't modify the presentity, it must be done by the watcher.
Hey;
I've been upgrading all of our older OpenSER 1.3 proxies to OpenSIPS 1.6.0
(we have several dozen) and I found a problem child in our inbound Verizon
proxy. After completely destroying the configs, grasping at straws and all
sorts of crazy theories I discovered that apparently OpenSIPS
Hi Ahmed,
Ahmed Munir wrote:
Hi Bogdan,
Thanks for reply. I forgot to mention earlier that for I'm using
OpenSIPS + FreeRadius, where radius is doing accounting and
authentication. I used aaa_does_uri_exist() function as well, but
seems not working or making mistake while implementing
Hi Jock,
The problem is tha maddr header - 1.6 has some new maddr processing and
it seams there is a bug there. According to RFC 3261, 16.4:
If the Request-URI contains a maddr parameter, the proxy MUST check
to see if its value is in the set of addresses or domains the proxy
is
Thx for the notice, I've just downloaded and re-installed the lastest 4.0
tarball (moved the old dir to backup, and replaced it with the new,
re-adjusting config parameters along the way...)
Not sure if I missed something, but I'm getting this error on-screen now:
Under the System-- Monit
Bogdan
I have good new
This is the history
1- Install the patch
cd /var/www
tar -xvzf /path/to/opensips-cp.tgz
cd opensips-cp
patch -p1 /path/to/opensips-cp_4.0.patch
2- Re-configure the Control-Panel File
3- Access the control panel http://192.168.50.10/cp/
- Access is ok
4- Check
2010/3/10 Bogdan-Andrei Iancu bog...@voice-system.ro:
I just added flag 0x08 for Reason hdr propagation - both in trunk and
1.6 branch. It will part of the 1.6.2 release.
Already shown the commit, great ;)
--
Iñaki Baz Castillo
i...@aliax.net
___
Hi,
I got the following error when trying to insert a new user.
Fatal error: Call to undefined method MDB2_Error::execute() in
/var/www/opensips-cp/web/tools/users/user_management/user_management.php
on line 223
Any help would be welcome.
Thanks,
Flavio E. Goncalves
New problem:
So under opensips-cp/config/boxes.global.inc.php
I changed the following:
$boxes[$box_id]['mi']['conn']=127.0.0.1:8080;
(previously was $boxes[$box_id]['mi']['conn']=/tmp/opensips_fifo;
This seemed to resolve my issue with System-- Monit
However,
System -- Statistics Monitor ,
I noticed that the latest documentation on:
http://www.opensips.org/Resources/DocsTutorials
regarding TLS only goes up to v1.4. Is that because nothing has changed, or
am I missing something? In fact the 1.5.x link on the site really points to
the 1.4.x page.
-dg
Also seeing the same problem
PHP Fatal error: Call to undefined method MDB2_Error::execute() in
/srv/www/htdocs/opensips-cp/web/tools/users/user_management/user_management.php
on line 223...
-Original Message-
From: users-boun...@lists.opensips.org
Hi,
Have you installed the mdb2 php pear? Also have you properly configure the db
access?
Regards,
Bogdan
-original message-
Subject: Re: [OpenSIPS-Users] Error message on opensips-cp 4.0
From: Christian Vo c...@nvidia.com
Date: 19/03/2010 03:58
Also seeing the same problem
PHP Fatal error:
Hi,
The tls tutorial did not change since v1.4, so it's the same for all the
following versions. You can safely use it.
Regards,
Bogdan
-original message-
Subject: [OpenSIPS-Users] TLS support
From: Daniel Goepp d...@goepp.net
Date: 19/03/2010 03:51
I noticed that the latest documentation on:
26 matches
Mail list logo
