[OpenSIPS-Users] Audio problem because of "to-tag" changes during the call
Hi, I'm new to the community. I search to solve some audio problem (one way) with my provider. I suspect it is related to the changement of the "to-tag" between the SIP 183 session progress and the SIP 200 OK. I think the "to-tag" change make the rtpengine use a new RTP src port, this make my provider drop this flow :'( -->the source port is different than what has been announce in the SDP invite I send to him. Here an extract of what I suspect to be my problem : janv. 20 23:20:39 rtpengine[8465]: INFO: [3ea6d1f855781fb501382118222db638@X.Y.Z.A ]: Final packet stats: janv. 20 23:20:39 rtpengine[8465]: INFO: [3ea6d1f855781fb501382118222db638@X.Y.Z.A ]: --- Tag 'as32bd80f6', created 0:46 ago for branch '', in dialogue with 'SDr6vf398-MVIsCA' janv. 20 23:20:39 rtpengine[8465]: INFO: [3ea6d1f855781fb501382118222db638@X.Y.Z.A ]: -- Media #1 (audio over RTP/AVP) using PCMA/8000 janv. 20 23:20:39 rtpengine[8465]: INFO: [3ea6d1f855781fb501382118222db638@X.Y.Z.A ]: - PortX.Y.Z.B:5000 <> X.Y.Z.A :11636, SSRC 143ba6ae, 142 p, 24424 b, 0 e, 30 ts janv. 20 23:20:39 rtpengine[8465]: INFO: [3ea6d1f855781fb501382118222db638@X.Y.Z.A ]: - PortX.Y.Z.B:5001 <> X.Y.Z.A :11637 (RTCP), SSRC 143ba6ae, 3 p, 152 b, 0 e, 30 ts janv. 20 23:20:39 rtpengine[8465]: INFO: [3ea6d1f855781fb501382118222db638@X.Y.Z.A ]: --- Tag 'SDr6vf398-B7CIvQ', created 0:46 ago for branch '', in dialogue with 'as32bd80f6' janv. 20 23:20:39 rtpengine[8465]: INFO: [3ea6d1f855781fb501382118222db638@X.Y.Z.A ]: -- Media #1 (audio over RTP/AVP) using PCMA/8000 janv. 20 23:20:39 rtpengine[8465]: INFO: [3ea6d1f855781fb501382118222db638@X.Y.Z.A ]: - PortX.Y.Z.C:5000 <> X.Y.Z.D:33800, SSRC 326b3c5a, 778 p, 133816 b, 0 e, 30 ts janv. 20 23:20:39 rtpengine[8465]: INFO: [3ea6d1f855781fb501382118222db638@X.Y.Z.A ]: - PortX.Y.Z.C:5001 <> X.Y.Z.D:33801 (RTCP), SSRC 326b3c5a, 1 p, 52 b, 0 e, 30 ts janv. 20 23:20:39 rtpengine[8465]: INFO: [3ea6d1f855781fb501382118222db638@X.Y.Z.A ]: --- Tag 'SDr6vf398-MVIsCA', created 0:33 ago for branch '', in dialogue with 'as32bd80f6' janv. 20 23:20:39 rtpengine[8465]: INFO: [3ea6d1f855781fb501382118222db638@X.Y.Z.A ]: -- Media #1 (audio over RTP/AVP) using unknown codec janv. 20 23:20:39 rtpengine[8465]: INFO: [3ea6d1f855781fb501382118222db638@X.Y.Z.A ]: - PortX.Y.Z.C:5014 <> X.Y.Z.D:33800, SSRC 0, 0 p, 0 b, 0 e, 33 ts janv. 20 23:20:39 rtpengine[8465]: INFO: [3ea6d1f855781fb501382118222db638@X.Y.Z.A ]: - PortX.Y.Z.C:5015 <> X.Y.Z.D:33801 (RTCP), SSRC 0, 0 p, 0 b, 0 e, 33 ts Does the option 'via-branch=auto' for the rtpengine_offer can help me to solve this issue ? What are the impact to do so ? Regards, Florent ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] OpenSIPS Bootcamp - Early Birds closing
* 22nd-26th of October 2018, Cluj-Napoca, Romania **DoubleTree by Hilton Hotel** * *Early Birds get to an end* The /*1st of September*/ deadline for the Early Bird 10% discount is almost there, so do not mis the opportunity and secure your seat for a good price. Register now <http://opensips.org/training/OpenSIPS_Bootcamp_2018/#mu-pricing> *Our Audience* ** Service Providers, Mobile Operators or Carriers seeking Open Source platforms to enhance their businesses: * Anyone seeking proficiency in OpenSIPS * Network Consultants and VARs who need a jump start in the technology * Developers who want to use OpenSIPS to create new telephony applications and appliances Check the Schedule now <http://opensips.org/training/OpenSIPS_Bootcamp_2018/#mu-schedule> Any questions? do not hesitate to contact us <mailto:bootc...@opensips.org>! You received this email as part of your relationship with the OpenSIPS Project. If you do not want to receive any more news, please email to unsubscribe <mailto:news-le...@lists.opensips.org?Subject=Unsubscribe>. ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] A New OpenSIPS Bootcamp training session
* 22nd-26th of October 2018, Cluj-Napoca, Romania* *OpenSIPS Bootcamp!* Join the core developers and founder of the OpenSIPS project for a new *OpenSIPS Bootcamp* <http://opensips.org/training/OpenSIPS_Bootcamp_2018/> session in Europe - a five days (40 hours) intensive and practical training, covering installation, configuration and administration of *OpenSIPS.* This year's curriculum has been aligned to OpenSIPS 2.4, but also enhanced to cover some of the latest introduced features like OpenSIPS clustering. Join us in Cluj-Napoca, the Silicon Valley of Romania and one of the most beautiful and touristy places in Transylvania! Check the Schedule now <http://opensips.org/training/OpenSIPS_Bootcamp_2018/#mu-schedule> *Early Birds open * The Early Bird 10% discount is available for registrations before /*1st of September*/, so do not mis the opportunity. The number of seats is limited, so be sure and book a seat now. Keep in mind that a 10% group discount is also available - grab your work mate and start learning more OpenSIPS together . Register Now! <http://opensips.org/training/OpenSIPS_Bootcamp_2018/#mu-pricing> * * *Certified training saves time and money* OpenSIPS mistakes are easily avoided if you get proper training! Companies that use OpenSIPS waste time and money when they don't have a trained engineer on staff. Searching on Google, waiting on IRC, even the latency in mailing list replies takes it's toll over time. Take this rare opportunity to train your employees with the project members themselves. Get training! <http://opensips.org/training/OpenSIPS_Bootcamp_2018/#mu-pricing> Any questions? do not hesitate to contact us <mailto:bootc...@opensips.org>! You received this email as part of your relationship with the OpenSIPS Project. If you do not want to receive any more news, please email to unsubscribe <mailto:news-le...@lists.opensips.org?Subject=Unsubscribe>. ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] [BLOG] Deep Dive into the OpenSIPS Statistics Support
Interested in learning about concepts such as architecture and advanced uses for the OpenSIPS statistics? Then make sure to check out our latest blog post: https://blog.opensips.org/2017/11/20/deep-dive-into-the-opensips-statistics-support/ -- OpenSIPS Team https://opensips.org ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] Wrong Contact in location table
OK, I managed to figure out why you get the private IP in the location
table - that's because you are saving the registration in the onreply
route, where you no longer have access to the fix_nated_contact() value.
To fix your issue, you need to do the following:
a. specify a mcontact_avp[1] in your script:
modparam("registrar", "mcontact_avp", "$avp(register)")
b. just after fix_nated_contact() on your REGISTER request, store the
changed contact in that AVP:
fix_nated_contact();
$avp(register) = $ct.fields(uri);
Doing these two changes to your script should store the real IP in the
location table.
[1]
http://www.opensips.org/html/docs/modules/2.4.x/registrar.html#idp5598160
Best regards,
On 11/01/2017 10:24 AM, Răzvan Crainea wrote:
Can you print $ct.fields(uri) instead of $ct?
Also, please post the output on pastebin.com.
Best regards,
Răzvan Crainea
OpenSIPS Developer
www.opensips-solutions.com
On 10/31/2017 03:47 PM, Răzvan Crainea wrote:
Hi, Dragomir!
Please post the logs I asked you to.
Best regards,
Răzvan Crainea
OpenSIPS Developer
www.opensips-solutions.com
On 10/31/2017 03:45 PM, Sumit Birla wrote:
X-Lite figures out its public IP and uses that in Via: and Contact:
headers unless you set ‘Firewall traversal method’ to ‘None’ in the
account settings.
On Oct 31, 2017, at 9:14 AM, Dragomir Haralambiev
mailto:goup2...@gmail.com>> wrote:
When REGISTER received from X-lite all is OK. Here part from
REGISTER message:
REGISTER sip:OpenSip_IP:Opensips_port;transport=UDP SIP/2.0
Via: SIP/2.0/UDP
219.101.241.150:64726;branch=z9hG4bK-524287-1---39ee8718032a1a5a;rport
Contact:
Here "Via" contains real IP (this is Route IP).
When REGISTER received from Yealink VoIP phone I have problem. Here
part from REGISTER message:
REGISTER sip:OpenSip_IP:Opensips_port SIP/2.0
Via: SIP/2.0/UDP 192.168.2.207:5062;branch=z9hG4bK77238423
Contact: <http://sip:55896207@192.168.2.207:5062/>>
Here "Via" contains not real IP (this is Yealink IP).
What I do ?
2017-10-31 14:18 GMT+02:00 Răzvan Crainea <mailto:raz...@opensips.org>>:
So you did manage to fix your problem?
Răzvan Crainea
OpenSIPS Developer
www.opensips-solutions.com <http://www.opensips-solutions.com/>
On 10/31/2017 02:17 PM, Dragomir Haralambiev wrote:
Hi,
Thanks for your replay.
I execute fix_nated_contact() after fix_nated_register().
Here part of my script:
if (isflagset(NAT)) {
if (is_method("REGISTER")) {
fix_nated_register();
setbflag(NAT_BFLAG); # nat register
}
fix_nated_contact();
}
In this case fix_nated_contact() will be fix contact records
in location table.
2017-10-31 14:02 GMT+02:00 Răzvan Crainea mailto:raz...@opensips.org>>:
Hi, Dragomir!
fix_nated_register() does not change the contact of the
message, fix_nated_contact() does that.
Please print the Contact header as I instructed earlier
and send back the script trace. Also, please post the logs
on pastebin.com <http://pastebin.com/> or something, don't
do it directly in the email.
Best regards,
Răzvan Crainea
OpenSIPS Developer
www.opensips-solutions.com
<http://www.opensips-solutions.com/>
On 10/31/2017 12:40 AM, Dragomir Haralambiev wrote:
What will I do to solve this problem?
2017-10-27 11:50 GMT+03:00 Dragomir Haralambiev
mailto:goup2...@gmail.com>>:
Oct 27 11:47:32 web /usr/local/sbin/opensips[30490]:
57995010: REGISTER before fix_nated_register
http://192.168.2.196:5060/>>[1]
Oct 27 11:47:32 web /usr/local/sbin/opensips[30490]:
57995010: REGISTER after fix_nated_register
http://192.168.2.196:5060/>>[1]
2017-10-27 10:41 GMT+03:00 Răzvan Crainea
mailto:raz...@opensips.org>>:
Hi, Dragomir!
Can you also print the Contact header ($ct[1]).
[1]
http://www.opensips.org/Documentation/Script-CoreVar-2-4#toc26
<http://www.opensips.org/Documentation/Script-CoreVar-2-4#toc26>
Best regards,
Răzvan Crainea
OpenSIPS Developer
www.opensips-solutions.com
<http://www.opensips-solutions.com/>
___
Users mailing list
Users@lists.opensips.org <mailto:Users@lists.opensips.org>
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
<http://lists.opensips.org/cgi-bin/mailman/listinfo/users>
___
Users mailing list
Users@lists.ope
[OpenSIPS-Users] [NEWS] Special event: OpenSIPS and FreeSWITCH integration demo!
Hi, all! Join us today at 19:00 GMT+3 for a live demo and Q/A [1] regarding the OpenSIPS and FreeSWITCH integration added to the latest OpenSIPS release! The conference will be hosted and moderated by the FreeSWITCH team in a similar format to Wednesday's ClueCon Weekly. Just visit https://cantina.freeswitch.org/vc, dial 888, set up your devices and you're good to go! As an alternative to the conference, you can follow along a YouTube livestream [2] [1]: https://goo.gl/vQVMDj(Facebook event page) [2]: https://www.youtube.com/watch?v=gDpe1fyRaZw See you there, -- OpenSIPS Team https://opensips.org ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] Need help defining a stackexchange (i.e. stackoverflow) for telephony
For those of that are fans of stackoverflow.com, and stackexchange.com, there's an effort to define a telephony stackexchange site. It's still in the definition phase -- what it needs to move forwards is more votes on on/off topic questions, and perhaps some better questions to vote for or against. If you're interested in helping out, or following the progress, visit: http://area51.stackexchange.com/proposals/12932/telephony/ Cheers, spd ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] Disabling TCP or UDP (RFC forbidden)
Hello list, Somewhere I read that OpenSIPS 1.6.0 allows to disable TCP but not UDP because UDP is required by the SIP RFC, so I looked at the RFCs. RFC 2543 states that 'UDP and TCP should be implemented.' RFC 3261 states that 'UDP and TCP must be implemented.' It would seem intuitive that OpenSIPS developers force the OpenSIPS runtime to conform to the most recent RFC, meaning that neither UDP nor TCP listening is possibly disabled. ...or the developers allow the admin (config file editor) to disable either UDP or TCP. This could be because the developers want to support the oldest RFC for backwards compatibility for example, or because they want to allow the admin to make the decision themselves. But the current release of OpenSIPS does not allow UDP to be disabled, while allowing TCP to be disabled. Can somebody explain why this policy was chosen or what is wrong with my logic? Regards, Brian ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] number of opensips children
Hello Bogdan, An ven., déc 18, 2009, Bogdan-Andrei Iancu schrieb: >there are modules creating separate processes for handling >additional events (like the mi_ modules). > >To see what processes you have and what they are doing, do: > >opensipsctl fifo ps > You were right about that, what a surprise ;) # opensipsctl fifo ps Process:: ID=0 PID=24975 Type=attendant Process:: ID=1 PID=24977 Type=SIP receiver udp:123.234.210.1:5060 Process:: ID=2 PID=24978 Type=time_keeper Process:: ID=3 PID=24979 Type=timer Process:: ID=4 PID=24980 Type=MI FIFO That's what I see when turning TLS and TCP off and children=1. I'm guessing that having five processes is the minimum possible when using the mi_fifo module. I don't know if the 'time_keeper' and 'timer' processes are needed however, and how to remove them in the configuration if they are unneeded. I assume that the 'attendant' does no real work other than coordinating the other processes, right? My gut feeling is that having four UDP listening processes and four TCP listening processes is about right for us, because we only have a handful of UACs participating infrequently (5 calls per day.) Regards, Brian ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] TREX error letter expected
Thank you very much for the reply Brett.
I haven't used it on my configuration. The only thing I did relevant for it is
the dial plan configuration below on opensips.cfg.
#dialplanloadmodule "dialplan.so"modparam("dialplan",
"db_url","mysql://opensips:xxx...@localhost/opensips")modparam("dialplan",
"attrs_pvar", "$avp(s:dest)")
Regards,
al
--- On Fri, 6/26/09, Brett Nemeroff wrote:
From: Brett Nemeroff
Subject: Re: [OpenSIPS-Users] TREX error letter expected
To: "Opensips Philippines"
Cc: users@lists.opensips.org
Date: Friday, June 26, 2009, 8:37 PM
This is likely a result of a failed regex. What's the regex you are using?
On Fri, Jun 26, 2009 at 1:39 PM, Opensips Philippines
wrote:
I am trying to activate the dial plan module but I am having this error.
Initially, I tried version 1.5.1 then removed it. I tried it with 1.5.0 but
still the same result.
Jun 27 10:36:31 [22004] INFO:core:init_tcp: using epoll_lt as the TCP io watch
method (auto detected)
Jun 27 10:36:31 [22006] NOTICE:core:main: version: opensips 1.5.1-notls
(i386/linux)Jun 27 10:36:31 [22006] INFO:core:main: using 32 Mb shared
memoryJun 27 10:36:31 [22006] INFO:core:main: using 1 Mb private memory per
process
Jun 27 10:36:31 [22006] NOTICE:signaling:mod_init: initializing module ...Jun
27 10:36:31 [22006] INFO:sl:mod_init: Initializing StateLess engineJun 27
10:36:31 [22006]
INFO:tm:mod_init: TM - initializing...Jun 27 10:36:31 [22006]
INFO:maxfwd:mod_init: initializing...Jun 27 10:36:31 [22006]
INFO:usrloc:ul_init_locks: locks array size 512Jun 27 10:36:31 [22006]
INFO:registrar:mod_init: initializing...
Jun 27 10:36:31 [22006] INFO:textops:mod_init: initializing...Jun 27 10:36:31
[22006] INFO:xlog:mod_init: initializing...Jun 27 10:36:31 [22006]
INFO:acc:mod_init: initializing...Jun 27 10:36:31 [22006] INFO:dialog:mod_init:
Dialog module - initializing
Jun 27 10:36:31 [22006] INFO:siptrace:mod_init: initializing...Jun 27 10:36:31
[22006] INFO:auth:mod_init: initializing...Jun 27 10:36:31 [22006]
INFO:auth_db:mod_init: initializing...
Jun 27 10:36:31 [22006] INFO:dialplan:mod_init: initializing module...Jun 27
10:36:31 [22006] ERROR:dialplan:trex_charnode: TREX error letter
expected Jun 27 10:36:31 [22006] ERROR:dialplan:trex_compile: compilation
error [letter expected]!Jun 27 10:36:31 [22006] ERROR:dialplan:build_rule:
failed to compile match expression *Jun 27 10:36:31 [22006]
ERROR:dialplan:init_db_data: failed to load database data
Jun 27 10:36:31 [22006] ERROR:dialplan:mod_init: could not initialize dataJun
27 10:36:31 [22006] ERROR:core:init_mod: failed to initialize module
dialplanJun 27 10:36:31 [22006] ERROR:core:main: error while initializing
modules
Please advise
Regards,
al
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] TREX error letter expected
I am trying to activate the dial plan module but I am having this error. Initially, I tried version 1.5.1 then removed it. I tried it with 1.5.0 but still the same result. Jun 27 10:36:31 [22004] INFO:core:init_tcp: using epoll_lt as the TCP io watch method (auto detected)Jun 27 10:36:31 [22006] NOTICE:core:main: version: opensips 1.5.1-notls (i386/linux)Jun 27 10:36:31 [22006] INFO:core:main: using 32 Mb shared memoryJun 27 10:36:31 [22006] INFO:core:main: using 1 Mb private memory per processJun 27 10:36:31 [22006] NOTICE:signaling:mod_init: initializing module ...Jun 27 10:36:31 [22006] INFO:sl:mod_init: Initializing StateLess engineJun 27 10:36:31 [22006] INFO:tm:mod_init: TM - initializing...Jun 27 10:36:31 [22006] INFO:maxfwd:mod_init: initializing...Jun 27 10:36:31 [22006] INFO:usrloc:ul_init_locks: locks array size 512Jun 27 10:36:31 [22006] INFO:registrar:mod_init: initializing...Jun 27 10:36:31 [22006] INFO:textops:mod_init: initializing...Jun 27 10:36:31 [22006] INFO:xlog:mod_init: initializing...Jun 27 10:36:31 [22006] INFO:acc:mod_init: initializing...Jun 27 10:36:31 [22006] INFO:dialog:mod_init: Dialog module - initializingJun 27 10:36:31 [22006] INFO:siptrace:mod_init: initializing...Jun 27 10:36:31 [22006] INFO:auth:mod_init: initializing...Jun 27 10:36:31 [22006] INFO:auth_db:mod_init: initializing...Jun 27 10:36:31 [22006] INFO:dialplan:mod_init: initializing module...Jun 27 10:36:31 [22006] ERROR:dialplan:trex_charnode: TREX error letter expected Jun 27 10:36:31 [22006] ERROR:dialplan:trex_compile: compilation error [letter expected]!Jun 27 10:36:31 [22006] ERROR:dialplan:build_rule: failed to compile match expression *Jun 27 10:36:31 [22006] ERROR:dialplan:init_db_data: failed to load database dataJun 27 10:36:31 [22006] ERROR:dialplan:mod_init: could not initialize dataJun 27 10:36:31 [22006] ERROR:core:init_mod: failed to initialize module dialplanJun 27 10:36:31 [22006] ERROR:core:main: error while initializing modules Please advise Regards, al ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] opensips_debug.pdf
Hi Anca Here is the opensips debug out when communicating to jabberd2 server. I can see opensips sending all info to jabberd2, but not the other way . Could you please tell from the debug out if jabberd2 is sending state updates to opensips. I would greatly appreciate your help. opensips_debug.pdf http://docs.google.com/fileview?id=F.32408c3d-c402-4708-9da4-f51563a59ae2 ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] failed to connect to the diameter client
Good day. I'm having a hard time looking for a solution for this, nothing much on google either. Opensips wouldn't start. I turned on the debug mode and it would give me this error. Jun 24 06:45:52 [18568] NOTICE:core:main: version: opensips 1.5.1-notls (i386/linux) Jun 24 06:45:52 [18568] INFO:core:main: using 32 Mb shared memory Jun 24 06:45:52 [18568] INFO:core:main: using 1 Mb private memory per process Jun 24 06:45:52 [18568] NOTICE:signaling:mod_init: initializing module ... Jun 24 06:45:52 [18568] INFO:sl:mod_init: Initializing StateLess engine Jun 24 06:45:52 [18568] INFO:tm:mod_init: TM - initializing... Jun 24 06:45:52 [18568] INFO:maxfwd:mod_init: initializing... Jun 24 06:45:52 [18568] INFO:usrloc:ul_init_locks: locks array size 512 Jun 24 06:45:52 [18568] INFO:registrar:mod_init: initializing... Jun 24 06:45:52 [18568] INFO:textops:mod_init: initializing... Jun 24 06:45:52 [18568] INFO:xlog:mod_init: initializing... Jun 24 06:45:52 [18568] INFO:acc:mod_init: initializing... Jun 24 06:45:52 [18568] INFO:dialog:mod_init: Dialog module - initializing Jun 24 06:45:52 [18568] INFO:siptrace:mod_init: initializing... Jun 24 06:45:52 [18568] INFO:auth:mod_init: initializing... Jun 24 06:45:52 [18568] INFO:auth_db:mod_init: initializing... Jun 24 06:45:52 [18568] INFO:core:probe_max_receive_buffer: using a UDP receive buffer of 255 kb Jun 24 06:45:52 [18568] INFO:core:probe_max_receive_buffer: using a UDP receive buffer of 255 kb Jun 24 06:45:52 [18568] INFO:core:probe_max_receive_buffer: using a UDP receive buffer of 255 kb Jun 24 06:45:52 [18570] ERROR:acc:init_mytcp: failed to connec to the DIAMETER client Jun 24 06:45:52 [18570] ERROR:acc:child_init: TCP connection not established Jun 24 06:45:52 [18570] ERROR:core:init_mod_child: failed to initializing module acc, rank 2 Jun 24 06:45:52 [18570] ERROR:core:main_loop: init_child failed for UDP listener Jun 24 06:45:52 [18569] ERROR:acc:init_mytcp: failed to connec to the DIAMETER client Jun 24 06:45:52 [18569] ERROR:acc:child_init: TCP connection not established Jun 24 06:45:52 [18569] ERROR:core:init_mod_child: failed to initializing module acc, rank 1 Jun 24 06:45:52 [18569] ERROR:core:main_loop: init_child failed for UDP listener Jun 24 06:45:52 [18572] ERROR:acc:init_mytcp: failed to connec to the DIAMETER client Jun 24 06:45:52 [18571] ERROR:acc:init_mytcp: failed to connec to the DIAMETER client Jun 24 06:45:52 [18571] ERROR:acc:child_init: TCP connection not established Jun 24 06:45:52 [18571] ERROR:core:init_mod_child: failed to initializing module acc, rank 3 Jun 24 06:45:52 [18571] ERROR:core:main_loop: init_child failed for UDP listener Jun 24 06:45:52 [18572] ERROR:acc:child_init: TCP connection not established Jun 24 06:45:52 [18572] ERROR:core:init_mod_child: failed to initializing module acc, rank 4 Jun 24 06:45:52 [18572] ERROR:core:main_loop: init_child failed for UDP listener Jun 24 06:45:52 [18574] ERROR:acc:init_mytcp: failed to connec to the DIAMETER client Jun 24 06:45:52 [18574] ERROR:acc:child_init: TCP connection not established Jun 24 06:45:52 [18574] ERROR:core:init_mod_child: failed to initializing module acc, rank 5 Jun 24 06:45:52 [18575] ERROR:acc:init_mytcp: failed to connec to the DIAMETER client Jun 24 06:45:52 [18574] ERROR:core:main_loop: init_child failed for UDP listener Jun 24 06:45:52 [18575] ERROR:acc:child_init: TCP connection not established Jun 24 06:45:52 [18575] ERROR:core:init_mod_child: failed to initializing module acc, rank 6 Jun 24 06:45:52 [18575] ERROR:core:main_loop: init_child failed for UDP listener Jun 24 06:45:52 [18576] ERROR:acc:init_mytcp: failed to connec to the DIAMETER client Jun 24 06:45:52 [18577] ERROR:acc:init_mytcp: failed to connec to the DIAMETER client Jun 24 06:45:52 [18576] ERROR:acc:child_init: TCP connection not established Jun 24 06:45:52 [18577] ERROR:acc:child_init: TCP connection not established Jun 24 06:45:52 [18576] ERROR:core:init_mod_child: failed to initializing module acc, rank 7 Jun 24 06:45:52 [18577] ERROR:core:init_mod_child: failed to initializing module acc, rank 8 Jun 24 06:45:52 [18576] ERROR:core:main_loop: init_child failed for UDP listener Jun 24 06:45:52 [18577] ERROR:core:main_loop: init_child failed for UDP listener Jun 24 06:45:52 [18578] ERROR:acc:init_mytcp: failed to connec to the DIAMETER client Jun 24 06:45:52 [18578] ERROR:acc:child_init: TCP connection not established Jun 24 06:45:52 [18578] ERROR:core:init_mod_child: failed to initializing module acc, rank 9 Jun 24 06:45:52 [18578] ERROR:core:main_loop: init_child failed for UDP listener Jun 24 06:45:52 [18579] ERROR:acc:init_mytcp: failed to connec to the DIAMETER client Jun 24 06:45:52 [18579] ERROR:acc:child_init: TCP connection not established Jun 24 06:45:52 [18579] ERROR:core:init_mod_child: failed to initializing module acc, rank 10 Jun 24 06:45:52 [18579] ERROR:core:main_loop: init_child failed for UDP listener Jun 24 06:45
Re: [OpenSIPS-Users] Fwd: OpenXCAP
oh fine... thanks... it is the picture :) can you sent me the picture a little bit larger? Regards Michael Original-Nachricht > Datum: Thu, 28 May 2009 11:55:51 +0200 > Von: Adrian Georgescu > An: "Michael Ciupka" > CC: users@lists.opensips.org > Betreff: Re: [OpenSIPS-Users] Fwd: OpenXCAP > Is this one what you mean? > > > > > On May 28, 2009, at 11:07 AM, Michael Ciupka wrote: > > > nobody have the old picture from the openxcap homepage? > > or somebody know where i can download the "old" png file? > > > > > > Original-Nachricht > > Datum: Wed, 27 May 2009 22:39:43 +0200 > > Von: "Michael Ciupka" > > An: users@lists.opensips.org > > Betreff: [OpenSIPS-Users] OpenXCAP > > > > Hello, > > > > i need absolute the "old" picture from the openxcap homepage. > > it has been changed, i think in the last week. > > have somebody store the old picture local? > > the old picture have a modul under the OpenXCAP modul, it was the > > soap-simple modul. > > > > Regards > > Michael > > > > ___ > > Users mailing list > > Users@lists.opensips.org > > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > > ___ > > Users mailing list > > Users@lists.opensips.org > > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] OpenSips and RLS
Hello, someone has a functioning main routing logic from Opensips where RLS is configure. opensips work well and the modparam from RLS too, but i dont know what code i need i the main routing logic to make RLS 100% functional. it would be great if someone could help me Regards Michael ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] OpenXcap
Hello,
IMSCore and opensips run on my local machine, now i install openxcap, it run
also but the communication with the opensips and openxcap dont work.
you see a small tutorial on the button of this page:
http://openxcap.org/wiki/Installation
can my someone explain how to configure the opensips.cfg with the files from
the page.
when i read the page right i think i must include the main but then i get
errors when i start opensips (etc/init.d/opensips start)
my opensips.cfg:
### Global Parameters #
debug=3
log_stderror=yes
log_facility=LOG_LOCAL0
fork=yes
children=4
/* uncomment the following lines to enable debugging */
#debug=6
#fork=no
#log_stderror=yes
/* uncomment the next line to disable TCP (default on) */
#disable_tcp=yes
/* uncomment the next line to enable the auto temporary blacklisting of
not available destinations (default disabled) */
#disable_dns_blacklist=no
/* uncomment the next line to enable IPv6 lookup after IPv4 dns
lookup failures (default disabled) */
#dns_try_ipv6=yes
/* uncomment the next line to disable the auto discovery of local aliases
based on revers DNS on IPs (default on) */
#auto_aliases=no
/* uncomment the following lines to enable TLS support (default off) */
#disable_tls = no
#listen = tls:your_IP:5061
#tls_verify_server = 1
#tls_verify_client = 1
#tls_require_client_certificate = 0
#tls_method = TLSv1
#tls_certificate = "/etc/opensips/tls/user/user-cert.pem"
#tls_private_key = "/etc/opensips/tls/user/user-privkey.pem"
#tls_ca_list = "/etc/opensips/tls/user/user-calist.pem"
port=5065
/* uncomment and configure the following line if you want opensips to
bind on a specific interface/port/proto (default bind on all available) */
#listen=udp:192.168.2.5:5065
alias=presence.open-ims.test:5065
#alias=open-ims.test:5065
#alias=scscf.open-ims.test:5065
#alias=presence-server.open-ims.test:5065
### Modules Section
#set module path
mpath="/usr/lib/opensips/modules/"
/* uncomment next line for MySQL DB support */
loadmodule "db_mysql.so"
loadmodule "signaling.so"
loadmodule "sl.so"
loadmodule "tm.so"
loadmodule "rr.so"
loadmodule "maxfwd.so"
loadmodule "usrloc.so"
loadmodule "registrar.so"
loadmodule "textops.so"
loadmodule "mi_fifo.so"
loadmodule "uri_db.so"
loadmodule "uri.so"
loadmodule "xlog.so"
loadmodule "acc.so"
#loadmodule "mi_datagram.so"
#loadmodule "mysql.so"
#loadmodule "presence_mwi.so"
#loadmodule "presence_xcapdiff.so"
#loadmodule "pua.so"
#loadmodule "pua_mi.so"
#loadmodule "rls.so"
/* uncomment next lines for MySQL based authentication support
NOTE: a DB (like db_mysql) module must be also loaded */
loadmodule "auth.so"
loadmodule "auth_db.so"
/* uncomment next line for aliases support
NOTE: a DB (like db_mysql) module must be also loaded */
loadmodule "alias_db.so"
/* uncomment next line for multi-domain support
NOTE: a DB (like db_mysql) module must be also loaded
NOTE: be sure and enable multi-domain support in all used modules
(see "multi-module params" section ) */
loadmodule "domain.so"
/* uncomment the next two lines for presence server support
NOTE: a DB (like db_mysql) module must be also loaded */
loadmodule "presence.so"
loadmodule "presence_xml.so"
# - setting module-specific parameters ---
# - mi_fifo params -
modparam("mi_fifo", "fifo_name", "/tmp/opensips_fifo")
# - rr params -
# add value to ;lr param to cope with most of the UAs
modparam("rr", "enable_full_lr", 1)
# do not append from tag to the RR (no need for this script)
modparam("rr", "append_fromtag", 0)
# - registrar params -
modparam("registrar", "method_filtering", 1)
/* uncomment the next line to disable parallel forking via location */
# modparam("registrar", "append_branches", 0)
/* uncomment the next line not to allow more than 10 contacts per AOR */
#modparam("registrar", "max_contacts", 10)
# - usrloc params -
#modparam("usrloc", "db_mode", 0)
/* uncomment the following lines if you want to enable DB persistency
for location entries */
modparam("usrloc", "db_mode", 2)
modparam("usrloc", "db_url",
"mysql://opensips:opensip...@localhost/opensips")
# - uri_db params -
/* by default we disable the DB support in the module as we do not need it
in this configuration */
modparam("uri_db", "use_uri_table", 0)
modparam("uri_db", "db_url", "")
[OpenSIPS-Users] (no subject)
hi all,
i have some problems with the configuration from opensips for the openxcap.
the route from the file opensips.cfg must be configure
my problem is with the "main request routing logic"
I paste my main from the opensips.cfg
now i must configure it
with this help "http://openxcap.org/wiki/Installation";
when i copy and paste the main from the homepage and adjust the IP i get errors
when i compile the file (/etc/init.d/ opensips start).
can somewhere help me to configure the main or can somewhere paste his/her main
which works with opensips and opnexcap?
regards
michael
#
# $Id: opensips.cfg 5503 2009-03-22 16:22:32Z bogdan_iancu $
#
# OpenSIPS basic configuration script
# by Anca Vamanu
#
# Please refer to the Core CookBook at:
# http://www.opensips.org/index.php?n=Resources.DocsCookbooks
# for a explanation of possible statements, functions and parameters.
#
### Global Parameters #
debug=6
log_stderror=yes
log_facility=LOG_LOCAL0
fork=yes
children=4
/* uncomment the following lines to enable debugging */
#debug=6
#fork=no
#log_stderror=yes
/* uncomment the next line to disable TCP (default on) */
#disable_tcp=yes
/* uncomment the next line to enable the auto temporary blacklisting of
not available destinations (default disabled) */
#disable_dns_blacklist=no
/* uncomment the next line to enable IPv6 lookup after IPv4 dns
lookup failures (default disabled) */
#dns_try_ipv6=yes
/* uncomment the next line to disable the auto discovery of local aliases
based on revers DNS on IPs (default on) */
#auto_aliases=no
/* uncomment the following lines to enable TLS support (default off) */
#disable_tls = no
#listen = tls:your_IP:5061
#tls_verify_server = 1
#tls_verify_client = 1
#tls_require_client_certificate = 0
#tls_method = TLSv1
#tls_certificate = "/etc/opensips/tls/user/user-cert.pem"
#tls_private_key = "/etc/opensips/tls/user/user-privkey.pem"
#tls_ca_list = "/etc/opensips/tls/user/user-calist.pem"
port=5065
/* uncomment and configure the following line if you want opensips to
bind on a specific interface/port/proto (default bind on all available) */
#listen=udp:192.168.2.5:5065
alias=presence.open-ims.test:5065
#alias=open-ims.test:5065
#alias=scscf.open-ims.test:5065
#alias=presence-server.open-ims.test:5065
### Modules Section ####
#set module path
mpath="/usr/lib/opensips/modules/"
/* uncomment next line for MySQL DB support */
loadmodule "db_mysql.so"
loadmodule "signaling.so"
loadmodule "sl.so"
loadmodule "tm.so"
loadmodule "rr.so"
loadmodule "maxfwd.so"
loadmodule "usrloc.so"
loadmodule "registrar.so"
loadmodule "textops.so"
loadmodule "mi_fifo.so"
loadmodule "uri_db.so"
loadmodule "uri.so"
loadmodule "xlog.so"
loadmodule "acc.so"
#loadmodule "mi_datagram.so"
#loadmodule "mysql.so"
#loadmodule "presence_mwi.so"
#loadmodule "presence_xcapdiff.so"
#loadmodule "pua.so"
#loadmodule "pua_mi.so"
#loadmodule "rls.so"
/* uncomment next lines for MySQL based authentication support
NOTE: a DB (like db_mysql) module must be also loaded */
loadmodule "auth.so"
loadmodule "auth_db.so"
/* uncomment next line for aliases support
NOTE: a DB (like db_mysql) module must be also loaded */
loadmodule "alias_db.so"
/* uncomment next line for multi-domain support
NOTE: a DB (like db_mysql) module must be also loaded
NOTE: be sure and enable multi-domain support in all used modules
(see "multi-module params" section ) */
loadmodule "domain.so"
/* uncomment the next two lines for presence server support
NOTE: a DB (like db_mysql) module must be also loaded */
loadmodule "presence.so"
loadmodule "presence_xml.so"
# - setting module-specific parameters ---
# - mi_fifo params -
modparam("mi_fifo", "fifo_name", "/tmp/opensips_fifo")
# - rr params -
# add value to ;lr param to cope with most of the UAs
modparam("rr", "enable_full_lr", 1)
# do not append from tag to the RR (no need for this script)
modparam("rr", "append_fromtag", 0)
# - registrar params -
modparam("registrar", "method_filtering", 1)
/* uncomment the next line to disable parallel forking via location */
# modparam("registrar", "append_branches", 0)
/* uncomment the next line not to allow more than 10 contacts per AOR */
#modparam("registrar", "max_contacts", 10)
# - usrloc params -
#modparam("usrloc", "db_mode", 0)
/* uncomment the following lines if you want to enable DB persistency
for location entries */
modpar
