Re: [sipx-users] Bug fix release update: sipXecs 4.4.0 update #10
On Thu, Sep 8, 2011 at 3:38 PM, Tony Graziano wrote: > I have had no issues with it since installing it as soon as it was > published. thanks tony. I'm going to add one more fix to update #10 http://track.sipfoundry.org/browse/XX-9848 I should still get this out tonight. ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
[sipx-users] CentOS 6 binaries for sipxecs 0.0.4.5.2 available
I uploaded builds for CentOS 6, but only for development binaries : 0.0.4.5.2. If all tests out ok and I can backport FS fixes to sipxecs 4.4 to support CentOS 6, then sipxecs 4.4 binaries can be built. I have no idea about CentOS 6 as an ISO at this point. ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
Re: [sipx-users] SNOM 870
2011/9/4 Tony Graziano : > how polished is the plugin? does it have support for the open on config? > would you consider contributing it to the codebase? alberto, *bump* ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
[sipx-users] sipxecs 4.4 update #10 in staging area for review
http://download.sipfoundry.org/pub/sipXecs-stage - includes following fixes. === commit 5b3a195e85c65e3b51f676481180202178588d9f Author: Mircea Carasel Date: Fri Sep 2 14:30:32 2011 +0300 XX-9836: sipXrest and sipXivr should use the same keystore file: ssl-web.keystore as sipXconfig -changed sipxivr, sipxrest scripts to point to the true web keystore: ssl-web.keystore commit 1b1aa729aa212ec557a9926172edee110cb378d5 Author: George Niculae Date: Mon Aug 29 14:58:48 2011 +0300 XX-9760 - t.38 faxes are saying carrier lost in sofia.log but sender has successful confirmation This makes the fax send whatever it receives instead of silently deleting any fax that has any error whatsoever Based on a patch from Tony Graziano , Thanks commit f1a9eb9f58799c434927ae72cc7ff793c43f242c Author: George Niculae Date: Tue Aug 30 14:43:01 2011 +0300 XX-9749: Nullpointer exception in sipxbridge Patch from Seshu Kumar Velagapudi - Thanks! commit f99adcd77d0aa353d8e9de1fe246e656eea516f0 Author: ciuc Date: Fri Jul 8 10:20:59 2011 +0300 XX-9655 - gateway can be saved without any details - added check for invalid input ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
Re: [sipx-users] Feature Question
On Thu, Sep 1, 2011 at 12:29 AM, Tony Graziano wrote: > Users can have personal speeddials. What I am seeing is there is not > import/export utility for the user. contact manager for end user that doesn't allow import/export does seem inflexible. Feature makes sense to me. So Jason would export his contacts and send them to Mandy so she can import them. Modification can happen on both sides first. seems like a good simple solution to me. ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
Re: [sipx-users] Default IM-id Generation
On Wed, Aug 31, 2011 at 3:05 AM, Kumaran T wrote: > IMO I though that it will take the non-numeric value will be the > preferences but always the user-id will the default IM-id On the surface, this looks like a neat idea, but it would create all sorts of inconsistencies in the data that an admin wouldn't realize. I think the only proper way to implement this would be to change the "create new user" screen to A.) include the IM user name (does it already? not sure) B.) auto-populate the IM name thru javascript but give the admin a chance to change it before save. ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
Re: [sipx-users] Fax failure(s) and one method to avoid them.
On Tue, Aug 30, 2011 at 9:19 AM, George Niculae wrote: > Please give it a try in next build and let me know how it works Thanks Tony and George. I'll publish a URL to build when it's available. ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
Re: [sipx-users] Compiling sipx works fine but menu options are missing
sipxconfig.log show any useful errors? I assume you're compiling 0.0.4.5.2, if not what branch are you on? ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
[sipx-users] Bug fix release update: sipXecs 4.4.0 update #10
Update #9 : Thu, 18 Aug 2011 == - ** No security updates in this update ** - ISO has *not* been rebuilt as decided in release policy. Yum update after installation is recommended for getting these updates. - Thanks goes Douglas for fix and Roman Gelfand and Cyril Constantin for your bug reports! Build Log === commit 97ba58d4d427dc6a5113a1c18d63caa808f1592e Author: Douglas Hubler Date: Thu Aug 18 08:34:49 2011 -0400 XX-9811 - add support for custom permissions replication back in Change log for past releases can be found here http://download.sipfoundry.org/pub/sipXecs/ChangeLog-4.4.0 ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
Re: [sipx-users] sipXecs 4.4.0 update #9
>From what i can tell, custom permissions are not getting into /var/sipxdata/sipdb/permission.xml. I'm looking into it, not obvious from the commits. ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
Re: [sipx-users] Individual CLI not possible
On Tue, Aug 16, 2011 at 5:15 PM, Sven Evensen wrote: > ** ** ** ** > > Hi, the itsp is very flexible and expects CLI in from field within the DID > range. So therefore using “transform extension”** > > should be straight forward, but it just doesn’t work. > sipXbridge config is very confusing here so check each setting on the page, and report them back here. Even the advanced settings. ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
[sipx-users] Bug fix release update: sipXecs 4.4.0 update #9
Update #9 : Mon, 15 Aug 2011 == - ** No security updates in this update ** - There is a new ISO because of fix affected ISO setup script. - Thank goes to many people for this update and for continued testing. Build Log === commit 94b409b7ca5b51c6eb598f4333b4d31205852f56 Author: Douglas Hubler Date: Tue Aug 2 19:54:30 2011 -0400 XX-9791 - typo causing "out of order" errors commit 3a23f51572e0f2fccd19215de0a6468f0c92c84d Author: George Niculae Date: Tue Aug 2 18:47:34 2011 +0300 Add possibility to mark locations as not registered from config UI so replication does not occur commit d9e580defc6eb60358e7371555257d90e2c9125f Author: Joegen Baclor Date: Tue Aug 2 19:12:32 2011 +0800 XX-9791 - Registrar deadlocks when applyUpdatesToDirectory and applyRegisterToDirectory tries the grab the same mutex commit 33385491628eca2517db33f0f51aa316773c1e77 Author: Douglas Hubler Date: Wed Jun 1 01:03:29 2011 -0400 build : allow to pull missing rpms from download.sipfoundry.org by default commit 05675cc5485b31c95c83b33c1e008fb5068d1b36 Author: Mircea Carasel Date: Fri Jul 8 17:53:22 2011 +0300 XX-9756: SipXOpenfire plugin: bookmark IM conference -created BookmarkManager responsible with creating, deleting, updating bookmarks it verifies if clientcontrol plugin is installed if clientcontrol is installed, it uses Java Reflection API to instantiate objects, call methods from this plugin clientcontrol classes gets referenced in sipxopenfire plugin through the generic openfire java classLoader for plugins -changed sipxopenfire plugin to support bookmark creation when IM Chat Room/Moderated checkbox is checked commit 2a72f5c0393ae1be9c4b336969c95e6944c9dd82 Author: George Niculae Date: Mon Aug 1 13:57:05 2011 +0300 XX-9792: XML Error while reloading the Media services when distributed server is down Reload FS should be issued only on servers with FS installed on commit f858206bb104c2e00f80ddb64d5359ee08925189 Author: George Niculae Date: Mon Aug 1 13:57:05 2011 +0300 XX-9792: XML Error while reloading the Media services when distributed server is down Reload FS should be issued only on servers with FS installed on commit 8695a8a51025cb0fb500f158c1c495513231 Author: George Niculae Date: Mon Aug 1 14:53:08 2011 +0300 Allow more than 2 SIP redundant servers (that is 5 which we're going to) commit c4c62d263b98e288b1bfac793cd7887da83fe162 Author: George Date: Fri Jul 29 18:51:53 2011 +0300 XX-9790: Send profiles triggers profile generation on all locations without accounting selections - send profiles only on selected locations - mark services to restart only on selected locations commit f41e96553403d18647f52950c8d960403dc99705 Author: Douglas Hubler Date: Thu Jul 28 11:32:35 2011 -0400 XX-9737 - make a max of 10 attempts to connect from imbot to xmpp server, waiting 2^i * 10 seconds each time. This is instead of infinite attempts every 10 seconds which will kill your machine Conflicts: sipXimbot/bin/sipximbot.sh.in sipXimbot/src/org/sipfoundry/sipximbot/IMBot.java commit 8ca3aa6fcdc5f7635502514921b67e39fb3bbef5 Author: Douglas Hubler Date: Thu Jul 28 11:18:50 2011 -0400 XX-9788 - increase http connection limit from 5 to 20 for registrar xmlrpc server for reasonable results when using more than 3 nodes in the clusters commit 433350f9c2794a54498593e2afb41c189033af3c Author: George Niculae Date: Thu Jul 28 14:58:15 2011 +0300 XX-9787: SOAP API: add branch in user creation call - new branchName element added to AddUser request: use Test to add new user in Test branch - manageuser request modified to accept branch: use Test to add an existing user in Test branch commit 26f53e426e8455adc61ec496e5b966991024828d Author: George Niculae Date: Thu Jul 28 14:58:15 2011 +0300 XX-9787: SOAP API: add branch in user creation call - new branchName element added to AddUser request: use Test to add new user in Test branch - manageuser request modified to accept branch: use Test to add an existing user in Test branch commit 52e551ff21981f2a24f4c281610508743c9c6685 Author: laurentiu Date: Tue Jul 26 17:37:17 2011 +0300 XX-9597 - User Phonebook loading problem under Firefox 4.x - updated gwt and smartgwt libraries - tested with Chrome 8/12, FF 3.6/5, IE8/9, Safari 3.2.3 for Win commit b92960a5f5f79c394b96654b6ad79255e82e1870 Author: laurentiu Date: Tue Jul 26 14:21:13 2011 +0300 XX-9597 - User Phonebook loading problem under Firefox 4.x - updated gwt and smartgwt libraries - tested with Chrome 8/12, FF 3.6/5, IE8/9, Safari 3.2.3 for Win commit 747f486bbb2e4705e0346bd0bbf2062cf26a3dba Author: George Niculae Date: Sat Jul 23 03:19:49 2011 +0300 XX-9758: MyBuddy find function returns incorrect information for users w
Re: [sipx-users] Individual CLI not possible
2011/8/15 Sven Evensen > ** ** ** ** ** ** ** > > This is an issue I have seen now and then and I also saw mentioned earlier > here, but was never resolved. > > ** ** > > On outbound calls through SIP trunk to ITSP, we want every user to emit own > CLI. Normally that will be > > done in the GW setting with transform extension feature. That works most of > the time, NOT here. Alternatively > > we can set the full CLI in the users’s callerID section. That also does NOT > work. The only way the outgoing INVITE > > has anything but the ext number is when I set default caller ID in the GW. > But that is not what I want. > Unless I missed it, what specific header the SIP message are you expecting to be the user's caller id. Each ITSP can be different on what is uses for caller id to PSTN. sipXbridge config is very confusing here so check each setting on the page, and report them back here. Even the advanced settings. Inspect the SIP message in and out of sipXbridge to identify if the header is goes in wrong or comes out wrong. ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
Re: [sipx-users] Outbound calls through unmanaged gateway Asterisk
On Fri, Aug 12, 2011 at 8:01 AM, cyril constantin < cyril.constan...@gmail.com> wrote: > Call from sip peers on Asterisk to PSTN Avaya works without issue. > Call from Sipxecs sip peers through Asterisk then using H323 connection to > Avaya extension works > Call from Sipxecs sip peers through Asterisk then using H323 connection to > Avaya PSTN doesn't works, I can ring my mobile phone but when I answer the > call I don't have the voice in both way. > > Codec used is G.711 Alaw. > - check that's the final codec selected in all paths by analyzing the SDP in SIP. check working and not working paths to ensure they are the same - check specified RTP ip addresses and port numbers in the SDP of the SIP messages. ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
Re: [sipx-users] Memory and java
Unless i missed it, we want to identify the process that's consuming the memory. Given the thread dump, i *think* it's openfire. if it is when it's trying to unify presence. its possible it cannot connect to the registrar pluggin that feeds it presence change. possible logs on either side might help the problem. of course, even if there is connection issues, memory shouldn't leak. i recently found an issue w/imbot that had a similar issue. ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
Re: [sipx-users] sipxecs 4.4.0 update #9 this week or next
On Mon, Aug 8, 2011 at 12:58 PM, Douglas Hubler wrote: > eZuce team has discovered and fixed a number of bugs in sipxecs 4.4.0 when > testing sipxecs up to 30K users over 5 servers. Previously 10K was > difficult and more than 3 servers was not possible. We'll be merging the > fixes into 4.4.0 code base in next week or so. I wanted to give a heads up > because the update will include more fixes than the usual one or two > commits. There are about a dozen commits. > Actually, we took what we learned working on 4.6 and made some strategic improvements to 4.4. 4.6 will should scale even more than 4.4 does. Note: even if you have hundred or so users, you should see better stability and few resources consumed including network traffic. Out of this, we developed a fairly robust testing framework that is able to analyze individual processes memory footprint and cpu resources. Initial charts were like looking thru hubble telescope. ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
[sipx-users] sipxecs 4.4.0 update #9 this week or next
eZuce team has discovered and fixed a number of bugs in sipxecs 4.4.0 when testing sipxecs up to 30K users over 5 servers. Previously 10K was difficult and more than 3 servers was not possible. We'll be merging the fixes into 4.4.0 code base in next week or so. I wanted to give a heads up because the update will include more fixes than the usual one or two commits. There are about a dozen commits. Commit change history - NOTE: It was incorrectly labeled 4.4.1 https://github.com/dhubler/sipxecs/commits/release-4.4.1 Staged binaries are here if you'd like to test to make sure all is ok however keep in mind we will need to rebuild them once the commits get back into the right branch. http://download.sipfoundry.org/pub/sipXecs-stage/ I will make a backup or current 4.4.0 for a while in case anyone need to rollback for some reason. I may be being somewhat overly cautious sending out this email, we've tested this build fairly extensively and are pretty confident in our fixes. There were no changes to database schema or configuration files. Douglas ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
Re: [sipx-users] Clue Con?
On Wed, Aug 3, 2011 at 5:28 PM, Nathaniel Watkins wrote: > There was talk of some people doing Clue Con this year. Trying to decide if > I should be making some last minute travel plans? i should be there and looking forward to it. ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
Re: [sipx-users] FATAL Postgres Error
On Tue, Aug 2, 2011 at 9:56 AM, jnolen wrote: > I have the following error on a version 4.2.1-18890.6.1 system: > > Alarm: SPX00030 > Severity: CRIT > Alarm Text: Process 'CallResolver' failed its configuration test. > psql: FATAL: database is not accepting commands to avoid wraparound > data loss in database "postgres" > HINT: Stop the postmaster and use a standalone backend to vacuum > database "postgres". > ls: /etc/postgresql/*.*/main > : No such file or directory > Suggested Resolution: Check recent configuration changes. Do not > hand-edit configuration files. Check logs for more details. > > The suggested remedial procedure to vacuum the database, however, cannot > be carried out. The db is refusing connections. I cannot drop it, back > it up, or otherwise connect. > > I found several procedures to bypass this Catch-22 but am hesitant to do > this without a specific procedure for sipxecs. > > Can someone provide a specific procedure for sipxecs? > > Also, what would be the procedure to enable auto-vacuum for sipxecs? There's postgres config I appended to http://track.sipfoundry.org/browse/XX-9688 but I'm not sure this will help you start postgres, but it might help to avoid the problem in the future. So my question is : what does the message means? "stop the postmaster and use a standalone backend to vacuum database "postgres"." ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
Re: [sipx-users] SipXecs 4.4.0 Bug? Device files with Polycoms
On Mon, Aug 1, 2011 at 5:28 PM, Aaron Pursell wrote: > How? By creating a new set of device files using the EXACT SAME files and > deactivating the current ones and activating the "new" ones. I seriously > downloaded the files from the SipX GUI and then created a new device files > set using the downloaded files and all the problems we thought were Polycom > issues were resolved. there's a script installed in sipxecs that flatten out the polycom config files so you can diff them polycom-config 0004f23213121.* > before Can you compare before/after and see what's different in the config files? ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
Re: [sipx-users] Instant Messaging sipxecs to sipxecs federation
On Fri, Jul 29, 2011 at 11:00 AM, Aaron Pursell wrote: > I did test all that dns is working. It finally started > working as you replied I have to restart the services 2-3 > times to finally get it to work. I've been there too. There's a caching DNS server on machines that often bites me too. If you restarted downstream DNS before upstream DNS, you can get into situation where you have to restart downstream again. I'm not sure all parts of sipxecs handle changes that require DNS restarts properly. ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
Re: [sipx-users] Poor Call Quality and Issues Transferring Calls On SipXecs 4.0.1-015823
On Fri, Jul 29, 2011 at 10:54 AM, Tony Graziano wrote: > #4 and parts of #5 really point to no qos or shaping on the internet > connection. if ntp cant sync in a reasonable period, clocks wont sync. > sounds like an isp/shaping issue. re:ntp If time on devices starts to drift off from servers time, "strangeness" will follow especially at the cusp of the window. i would say a minute would be dangerous territory, but it's been awhile since i was in the situation.hard to describe "strangeness" because various messages of a SIP dialog fail authentication because of expired nonce and depending on what you're doing at the time call can abort. SIP - "Stepped In Poop" ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
Re: [sipx-users] IM - MyBuddy
On Mon, Jul 18, 2011 at 12:44 PM, Henry Dogger wrote: > When my status is set to DoNotDisturb (I have checked the setting, send to > voicemail on DND) I can’t use the function pickup or listen on the mybuddy. > In fact every function concerning the MyBuddy calling my phone is not > possible, I would understand this not working when my phone is on DND, is > this normal behavior? Did you expect calls w/mybuddy to go to voicemail when in DND? Can you explain terms "I can't use" and "this is not working" in more detail? Are you getting errors? silent ignores to your request... > The second thing I noticed was, (still with the setting go to voicemail on > DND) the DND is not working in a huntgroup, my phone will just ring for the > amount of seconds I configured, I would suspect the phone not to be ringing, > but moving on to the next in line… Is this also normal behavior? Doesn't sound like desired behavior. Question is: is this what other's get too, in which case i would say it's a bug. ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
Re: [sipx-users] Staging for pending 4.4.0 update #9
On Thu, Jul 14, 2011 at 11:48 AM, Douglas Hubler wrote: > On Thu, Jul 14, 2011 at 11:30 AM, Michael Picher wrote: >> XX-9672 effects initial system configuration. This really is useful mostly >> if installing from ISO. Do you think it would be appropriate to build a new >> ISO? > > you have a good point here. Folks won't yum update until after > running sipxecs-setup obviously. I will build/stage the ISOs as well. > Worst case we can not use them. This will add a little time to test > ISO. done http://download.sipfoundry.org/pub/sipXecs-stage2/ISO/ ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
Re: [sipx-users] Staging for pending 4.4.0 update #9
On Thu, Jul 14, 2011 at 11:30 AM, Michael Picher wrote: > XX-9672 effects initial system configuration. This really is useful mostly > if installing from ISO. Do you think it would be appropriate to build a new > ISO? you have a good point here. Folks won't yum update until after running sipxecs-setup obviously. I will build/stage the ISOs as well. Worst case we can not use them. This will add a little time to test ISO. ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
[sipx-users] Staging for pending 4.4.0 update #9
I decided i needed a staging area where i can publish build before actually moving them into production so they can be tested first. So I've built and published the next 4.4 build candidate here http://download.sipfoundry.org/pub/sipXecs-stage2/ You would have to be a bit comfortable swapping yum repos to use this build results (e.g. edit baseurl in /etc/yum.repos/sipxecs-4.4.0.repo) If you are affected by any of these issues and can verify any of these issues, it would be much appreciated. This build does have to go out today or early tomorrow so I won't be waiting too long. If for some reason we do need a new build and you've installed this build, you won't have to reinstall, just update again when the next fix is published. Build Log === commit 2667fd457c967c5f3208274b3d08a6a0fbdbe29b Author: Mircea Carasel Date: Fri Jul 8 17:53:22 2011 +0300 XX-9756: SipXOpenfire plugin: bookmark IM conference -created BookmarkManager responsible with creating, deleting, updating bookmarks it verifies if clientcontrol plugin is installed if clientcontrol is installed, it uses Java Reflection API to instantiate objects, call methods from this plugin clientcontrol classes gets referenced in sipxopenfire plugin through the generic openfire java classLoader for plugins -changed sipxopenfire plugin to support bookmark creation when IM Chat Room/Moderated checkbox is checked commit 631f587340e7db64cb7a58b7fbac6e3a76319445 Author: George Niculae Date: Thu Jul 7 09:36:49 2011 +0300 XX-9757: Lowered priority if XML-RPC request content from INFO to debug to unclutter mid process XML-RPC logging commit bc49a46e365b95b9104270e09dcb3da91a4cfd77 Author: Joegen Baclor Date: Thu Jul 7 14:24:22 2011 +0800 XX-9757 - Leak in Sip Unified presence redirector. When inserting new presence monitor information, the old value being overwritten is not de commit c69500f60045d6bd7e6ec056d098d7e9c3b80ec8 Author: Mircea Carasel Date: Thu Jun 30 16:00:24 2011 +0300 XX-9743: Call Forwarding REST service: expiration time for initial ring is missing --added expiration in XML file for first ring --exposed loadSettings method in TestUtil.java to enhance the ability to load neoconf settings in web tests --introduced new Representable class in ForwardResource that wrapps CallSequence for XStream binding offers the ability to add new fields to hold info from wrapped callSequence instance (expiration for instance) -changed test to autmatically load settings using TestUtil commit 14e8c27f3cd72c6d81dfb7567ae7d195ebbad5d3 Author: Mircea Carasel Date: Wed Jun 29 15:08:18 2011 +0300 XX-9717: call forwarding REST service, set withWoicemail with voicemail permission value REST PUT doesn't have to contain withVoicemail flag as this cannot be configurable in 4.4 call forwarding REST GET: will return content with withVoicemail flag set with the value established by the administrator for voicemail permission if set to true, the user will always receive voicemail if set to false, the user will never receive voicemail in 4.6 the user will be able to configure whether wants to receive voicemail or not in call forwarding scenario (see XX-9736) when voicemail commit 8437cd327bbd561cb3641e541302036764c08ef1 Author: George Niculae Date: Mon Jun 27 11:07:18 2011 +0300 XX-9337 - Lowered log priority of warning messages to debug commit ba21902e685becb92a63c238fcab79e8b58fde14 Author: Douglas Hubler Date: Thu Jun 23 06:09:34 2011 -0400 ISO reorganization for missing freeswitch dependencies commit 1e79a10fe4fc3ec4def9134a070579f8ba5381bf Author: Kemal Eroglu Date: Thu Jun 9 17:31:47 2011 +0300 XX-9672 - DNS configuration for second and third servers in HA configuration fix masterSystemName is changed with masterSystemAddr when const ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
Re: [sipx-users] CDR Issues
On Wed, Jul 13, 2011 at 2:10 AM, Yuri Kurkarewicz wrote: > When I make calls with the softphone BRIA 3.1 to another extension and > so no attendant, CDR says that the connection is completed (when the > connection was interrupted intentionally by Bria softphone 3.1), connecting > phone Polycom to Polycom and the Polycom to the softphone defect does not > occur! The error in cdr only occur the Softfone to everyone! CDRs can be imperfect when media is not relayed thru PBX as is the case with sipxecs. CDR logic inspects SIP messages thru proxy for what looks like a successful call. If you can capture a SIP trace and points out a particular SIP message or header that hits the proxy that shows the call was indeed torn down, perhaps that detection can be added to the CDR logic. ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
Re: [sipx-users] How can I make media go through my sipX server?
I think gor actually wants to relay to media thru sipxecs to "control" it. gor, what end user feature are you looking to achieve? On Tue, Jul 12, 2011 at 11:12 AM, Tony Graziano wrote: > If your ua is properly configured and your ua is local to sipx it will setup > the rtp peer to peer in the invite (sip). > > On Jul 12, 2011 9:53 AM, wrote: > > ___ > sipx-users mailing list > sipx-users@list.sipfoundry.org > List Archive: http://list.sipfoundry.org/archive/sipx-users/ > ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
Re: [sipx-users] General Centos Support Questions re: Centos version
On Mon, Jul 11, 2011 at 2:16 PM, Philippe Laurent wrote: > 6 has some hardware requirements that may not be met by some 5 > installations. > Would the CentOS 6 efforts negatively impact resource allocation towards the > improvement of the sipX base product? a bit, but many developers use fedora so we've generally found going to the next rhel/centos straightforward as we are already compatible w/the newer versions for each deps. I'd try to support anyone who wanted to make an attempt at it on their own. ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
Re: [sipx-users] General Centos Support Questions re: Centos version
On Mon, Jul 11, 2011 at 1:50 PM, Tony Graziano wrote: > Are there any plans to test or supply a working repo for centos 6.0? If anyone has any points to bump up this as a priority, please post. ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
Re: [sipx-users] Using FreeSwitch Modules
On Sun, Jul 10, 2011 at 5:42 PM, Roman Gelfand wrote: > I am looking to put together voice recognition system using mod_unimrcp.so > and mod_pocketsphinx.so modules on sipx server. Is there any issues doing > that as it is used by sipx server? When developing voice recognition google for previous testing results before you get too far. folks were disappointed w/quality of recognition of pocketsphinx. > application, is there anything different I need to do in sipx's freeswitch > as compared to straight freeswitch? not really, just know that all the configuration is read from /etc/sipxpbx/freeswitch/conf ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
Re: [sipx-users] sipxecs Fax with PDF rather than TIFF file attachments
On Wed, Jun 29, 2011 at 1:44 PM, Todd Hodgen wrote: > But to integrate, test and release falls > well within the goals of the project, and I believe how it should be done. ... standard FOSS response, I'm not sure if this addresses your point * Goal of project: I would say yes * Immediate goal of ezuce: not at this moment AFAIK * If you or someone you hire can get it to production quality and submit it to sipxecs, then yes, it will save you the burden of maintaining it yourself. ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
Re: [sipx-users] gmail issues, anyone else?
On Mon, Jun 27, 2011 at 12:21 PM, Philippe Laurent wrote: > I've not observed any issues... thanks everyone. I actually meant to send this internally ;) but your input was helpful. ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
[sipx-users] gmail issues, anyone else?
1.) I lose random emails from dave deutchmen. They do not wind up in spam. 2.) after sending an email, i randomly lose my copy of the email in my sent folder. anyone else have these issues or am i going nuts? ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
Re: [sipx-users] VM access problem
On Fri, Jun 24, 2011 at 5:32 PM, Norman Branitsky wrote: > There are lots of brand new messages in his mailbox - XX-9461 talks about > messages with bad date stamps. > I emptied out his INBOX at one point to no avail. that may not address the improper xml. Look at the xml w/text editor, you'll be able to see it with easy inspection. ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
Re: [sipx-users] TLS and SRTP
On Fri, Jun 24, 2011 at 4:22 PM, Tony Graziano wrote: > srtp was just added yesterday. you might consider waiting g for someone to > do test and create the wiki pages. it was confirmed that media relay doesn't properly proxy srtp. That means SRTP won't work with NAT and SIP Trunking (did i get that right?) so it's of very limited use ATM. ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
Re: [sipx-users] Bug fix release update: sipXecs 4.4.0 update #8
resending On Wed, Jun 22, 2011 at 1:14 PM, Douglas Hubler wrote: > Update #8 : Wed, 22 June 2011 > == > - ** No security updates in this update ** > - ISO has *not* been rebuilt as decided in release policy. Yum update > after installation is recommended for getting these updates > - Thank you George for your fixes and Tony G. and everyone > for your bug reports! > > Build Log > === > commit b158feaa0aaf9864f5317ba87736115ef9e619fa > Author: George Niculae > Date: Wed Jun 22 16:51:27 2011 +0300 > > XX-9713: SRTP should be disabled by default > > Change log for past releases can be found here > http://download.sipfoundry.org/pub/sipXecs/ChangeLog-4.4.0 > ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
[sipx-users] Bug fix release update: sipXecs 4.4.0 update #8
Update #8 : Wed, 22 June 2011 == - ** No security updates in this update ** - ISO has *not* been rebuilt as decided in release policy. Yum update after installation is recommended for getting these updates - Thank you George for your fixes and Tony G. and everyone for your bug reports! Build Log === commit b158feaa0aaf9864f5317ba87736115ef9e619fa Author: George Niculae Date: Wed Jun 22 16:51:27 2011 +0300 XX-9713: SRTP should be disabled by default Change log for past releases can be found here http://download.sipfoundry.org/pub/sipXecs/ChangeLog-4.4.0 ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
Re: [sipx-users] [SFtrack] Created: (XX-9724) Polycom phone rebots after 10-14 minutes on a call
Tony, I'm not sure if this is the same, but... There was a customer that had an issue where 50 percent of about 100 polycoms would randomly lockup. They were not on calls at the time, just out of the blue lock-ups. I never tracked down the ultimate problem, but did come up with a workaround. I removed all SRV records and used just a single A record avoided the lockups. In this case, customer didn't need HA so we could do this. I discovered this because the last log message in polycom phone log was a SRV record lookup. On Thu, Jun 23, 2011 at 5:56 AM, Tony Graziano (JIRA) wrote: > Polycom phone rebots after 10-14 minutes on a call > -- > > Key: XX-9724 > URL: http://track.sipfoundry.org/browse/XX-9724 > Project: sipXecs > Issue Type: Bug > Components: Polycom, sipXbridge, sipXproxy > Affects Versions: 4.4 > Environment: 4.4 installed from ISO all patched up, polycom firmware > 3.1.3, 3.2.4, 3.2.5 > Reporter: Tony Graziano > > > I am finding my polycom 650 reboots if i am on a call "more than" ten > minutes. I have gone back to CDR data and looked at the failed calls (which > only show COMPLETED) and find they are 10, 12 or 14 minutes long thus far. > The phone is not remote in this case either. It is using a sip trunk, but > have tried several POPS. Calls through analog ATA's stay up and do not reboot. > > The phone does have several "external lines on it". > > I will grab sip traces and log files and post after I verify it happens > without external lines on it or not. > > If you are also having the same type of issue details would also be > appreciated. > > -- > This message is automatically generated by JIRA. > - > If you think it was sent incorrectly contact one of the administrators: > http://track.sipfoundry.org/secure/Administrators.jspa > - > For more information on JIRA, see: http://www.atlassian.com/software/jira > > > ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
Re: [sipx-users] VM access problem
On Thu, Jun 23, 2011 at 5:08 PM, Norman Branitsky wrote: > I don't see much difference. > Suggestions, please. Did you upgrade from 4.0.4? It's possible you hit this http://track.sipfoundry.org/browse/XX-9461 there is a workaround posted ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
Re: [sipx-users] SipXez Phone outgoing call
On Thu, Jun 23, 2011 at 3:20 AM, Nihar wrote: > When I tried to make an outgoing call from SipXezPhone > found that call failed with CAUSE_NO_RESPONSE event and call > is disconnected with remote phone.I can see that there is > nothing wrong with remote x-lite phone.It's responding with > 200ok with codes as expected. > Does anyone has any idea why this can happen?? wrong project. Only contact i have for sipxtapi project is found here http://sipez.com/contact.html ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
Re: [sipx-users] OpenMeetings with sipx
On Thu, Jun 23, 2011 at 10:29 AM, m...@grounded.net wrote: > Tony, you're heavy into development. Have you heard of any RTMP (like red5) > apps that would work with sipx in terms of being able to have a browser based > phone? I know of a few apps but none that look very usable to the average > person. Andrew Thompson who wrote OpenACD worked on such a mod for freeswitch HEAD http://groups.google.com/group/openacd/browse_thread/thread/ed7b3ae6be391ef7 Anyone should be able to drop in freeswitch rpms built by yourself or anyone into a sipx box and it should just work, if anyone wanted to try this ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
Re: [sipx-users] Bug fix release update: sipXecs 4.4.0 update #8
resending... On Wed, Jun 22, 2011 at 1:14 PM, Douglas Hubler wrote: > Update #8 : Wed, 22 June 2011 > == > - ** No security updates in this update ** > - ISO has *not* been rebuilt as decided in release policy. Yum update > after installation is recommended for getting these updates > - Thank you George for your fixes and Tony G. and everyone > for your bug reports! > > Build Log > === > commit b158feaa0aaf9864f5317ba87736115ef9e619fa > Author: George Niculae > Date: Wed Jun 22 16:51:27 2011 +0300 > > XX-9713: SRTP should be disabled by default > > Change log for past releases can be found here > http://download.sipfoundry.org/pub/sipXecs/ChangeLog-4.4.0 > ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
[sipx-users] test
is list working? ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
[sipx-users] Bug fix release update: sipXecs 4.4.0 update #7
Update #7 : Tue, 21 June 2011 == - ** No security updates in this update ** - ISO has *not* been rebuilt as decided in release policy. Yum update after installation is recommended for getting these updates - Thank you Baris, Kemal, Joegen and George for your fixes and everyone for your bug reports! Build Log === commit 353d718c0c303064f7d61e0aec68758944c51f31 Author: Baris Yanar Date: Fri Jun 17 17:22:06 2011 +0300 XX-9694 _sips._tcp record is needed for TLS registrations commit 8ebbe64304f512aef067e412311725b363105b85 Author: Joegen Baclor Date: Tue Jun 21 15:10:04 2011 +0800 XX-9699 - TLS seems to affect recurseDNSChildren and making the transaction layer falsely recursing even if it is not required. Still needs further confirmation but this pat\ c commit bc4e20b0b67691187bba07807d9efe8eb7573e62 Author: Kemal Eroglu Date: Tue Jun 7 13:23:38 2011 +0300 UC-1011 - Fix for Phone reregistration problem in 20 sec on NAT setup (For Master Branch) XX-9692: Empty Via Header in OPTIONS messages commit 745f028de61e0f795142e925e6cf23e2d2d0e2b4 Author: George Niculae Date: Wed Jun 15 16:23:31 2011 +0300 XX-9675: SRTP is not working - included polycom srtp options as in http://supportdocs.polycom.com/PolycomService/support/global/documents/support/setup_maintenance/products/voice/spip_ssip_vvx_Admin_Guide\ _ Change log for past releases can be found here http://download.sipfoundry.org/pub/sipXecs/ChangeLog-4.4.0 ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
Re: [sipx-users] Increase Timeout to Enter Authorization Code
On Tue, Jun 21, 2011 at 12:26 PM, Alex Brown wrote: > Is it possible to increase the amount of time users have to enter their > authorization codes and numbers they wish to dial? The current time > limit is a little too short for several of our users. i don't think so. i looked at code, looks like this was never finished, the timeout values are defined, but are not hooked up to config files. you'd have to edit/recompile src ATM. ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
Re: [sipx-users] Problem with internal calls Polycom to Polycom - PRACK missing
On Tue, Jun 21, 2011 at 8:49 AM, Douglas Hubler wrote: > On Tue, Jun 21, 2011 at 8:19 AM, George Niculae wrote: >> There is a fix committed by Joegen and Douglas triggered RPMs build, >> we'd really appreciate if you could update and give it a try later >> today when available > > I will post link to build when available http://ec2-50-17-110-224.compute-1.amazonaws.com:40100/ I'll only keep it up for few hours or until someone tells me it's good, then i'll push to download.sipfoundry.org. if for some reason there is still a problem with this build, don't worry, you will still be able to update from this build to the final build. ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
Re: [sipx-users] Problem with internal calls Polycom to Polycom - PRACK missing
On Tue, Jun 21, 2011 at 8:19 AM, George Niculae wrote: > There is a fix committed by Joegen and Douglas triggered RPMs build, > we'd really appreciate if you could update and give it a try later > today when available I will post link to build when available Summary of issue http://track.sipfoundry.org/browse/XX-9699 ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
Re: [sipx-users] Problem with internal calls Polycom to Polycom - PRACK missing
On Mon, Jun 20, 2011 at 8:07 AM, George Niculae wrote: > Tony, could you take snapshot and raise a critical in JIRA? Yes, please. Even if it's related to a polycom bug Paul Curtis points out, if it doesn't happen in sipxecs 4.2.1, then we should at a minimum learn what the issue is and possibly provide a workaround. ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
Re: [sipx-users] Problem with internal calls Polycom to Polycom -PRACK missing
On Sun, Jun 19, 2011 at 11:44 PM, Paul Curtis wrote: > This is a known issue with Polycom, I worked with them to resolve the > missing PRACK. This also had to do with the on-hold issue I had posted a > while back. That was when Polycom noticed the missing PRACK. They do > have a software release fix coming 3.2.5B, surprised it hasn't posted yet. > It's been well over 6 weeks. Perhaps they found other issues to add > prior to releasing it. > > This only occurred in 4.4 (all releases). 4.2.1 worked just fine. > Polycom phones that are affected in my environment were 331,335,560,670. > At least that is what I have to test with. The error occurred with calls > from inbound / outbound gateways of any type, even other sipx systems. If someone can reproduce this on 4.4, can you disable this distinct ringtones http://wiki.sipfoundry.org/display/sipXecs/Distinct+ringtones+for+internal+and+external+calls and see if problem persists ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
Re: [sipx-users] IM 'on the phone' status on non provisioned phones
On Fri, Jun 17, 2011 at 6:06 AM, Tjardick van der Kraan wrote: > First of all compliments to the developers on the project as it seems to > have come a long way with loads of great new features, so keep up the good > work guys. Welcome back and thanks for kind words. > But when i login a soft phone or use a non-provisioned phone, with the sip > password i can nicely make and receive calls, but the IM status is not > updating when using this (soft) phone. > Is there something i am not doing right? Or is the "on the phone" status > only supported on Polycom phones ? Isn't there a strange restriction where both users have to be logged into IM. ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
Re: [sipx-users] ACD problem with 4.4.0
2011/6/17 Kumaran : > I tried OpenACD in Fresh ISO 4.4.0 but it didn't work for me...I > don't know whats wrong in my configuration.For me calls are not going to > queue only.Hope I had done some mistake in setting.Again when I have > time I will retest it and let you know the update. > I hope old ACD is working fine for you in 4.4.0.Please feel free to > ask query if I know I will update you.. Laurentiu, do you think you could try to see what's wrong with OpenACD in 4.4.0 specifically? ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
Re: [sipx-users] Bug fix release update: sipXecs 4.4.0 update #6
On Fri, Jun 17, 2011 at 5:55 AM, Tony Graziano wrote: > Thanks for the fixes! Thanks for testing, i should have given you credit. It really helps out a lot. > still all phones are rebooting when applying a patch... I just increased the rank for this and left a comment we should consider backporting it to 4.4. http://track.sipfoundry.org/browse/XX-9609 As i have to imagine this distruptive ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
[sipx-users] Bug fix release update: sipXecs 4.4.0 update #6
Update #6 : Fri, 17 June 2011 == - ** No security updates in this update ** - ISO has *not* been rebuilt as decided in release policy. Yum update after installation is recommended for getting these updates - Thank you Joegen and George for your fixes and everyone for your bug reports! Build Log commit 319cf9404bb02d7ad8aa3f29d927eb93b382537e Author: George Niculae Date: Tue Jun 14 23:40:09 2011 +0300 XX-9861: LDAP improvements - do not try to authenticate or verify LDAP connection in ConfigurableLdapAuthenticationProvider when LDAP configured checkbox is not selected - ldap settings retrieved every time from ldapManager - check in DaoAuthenticationProvider if LDAP is configured in addition to ldap only setting before throwing authentication exception - change LDAP configure label in LDAP authentication - changed Settings tab name in Authentication Settings - added Apply button in LDAP configuration tab (in addition to Continue button) - allows applying connection config and remaining on the same page - added Cancel buttons in object classes and attr map configuration tabs - allows navigating back to initial step (connection) - hide Authentication Settings tab (former Settings tab used for selecting auth scheme for user portal and openfire) if LDAP authentication checkbox is not \ s - changed LDAP connection step to save settings first and then to verify connection params (so the data entered by the user to be persisted even not valid) commit 1d1bd6a180099cbc990cfcf7e1cdca7b433147c1 Author: George Niculae Date: Fri May 27 01:47:54 2011 +0300 XX-9639: missing TLS SRV commit 11c2907155d827c9ee194b855a0463ca264cf0e3 Author: Joegen Baclor Date: Mon Jun 13 19:58:36 2011 +0800 recourseDnsChildren do not take into account TLS resulting to a NULL return value when only TLS is the sole protocol configured commit 2276adf5663e74b9cbee8d2b8672fa1337b43b04 Author: Joegen Baclor Date: Tue Jun 14 13:21:47 2011 +0800 Appearance Agent uses the TCP port for TLS causing port conflicts during initialization of the SipUserAgent Change log for past releases can be found here http://download.sipfoundry.org/pub/sipXecs/ChangeLog-4.4.0 ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
Re: [sipx-users] Codec setup
I think you want the sipxtapi project. There is no email list active,
but if you go to http://sipez.com/contact.html maybe you can find an
email address to ask your questions.
2011/6/15 Rajan, Nihar :
> < h t m l > < h e a d > < m e t a h t t p - e q u i v = " C o n t e n t - T
> y p e " c o n t e n t = " t e x t / h t m l ; c h a r s e t = u t f - 1 6 "
>> < / h e a d > < b o d y >
>
> Hi,
> Can anyone please suggest me what is the way to set codec for the line I
> added. I tried to set it as follows:
>
> sipxConfigSetAudioCodecPreferences(m_hInst, AUDIO_CODEC_BW_NORMAL) but found
> when I called that line it failed with 488 not acceptable here as my
> sipxtapi application is not at all replying with any SDP so codec
> negotiation failed. I also tried with in following way:
>
> mSelectedAudioCodecs =
>
> "PCMU" ;
>
> if (sipxConfigSetAudioCodecByName(m_hInst, mSelectedAudioCodecs.data()) !=
> SIPX_RESULT_SUCCESS)
>
> {
>
> printf(
>
> "\n Cannot set preferred audio codecs");
>
> return false;
>
> }
>
> It failed with following exception:
>
> Assertion failed: !"Could not find codec of given type!", file c:\documents
> and settings\administrator\desktop\resiprocate\resiprocate-1.6\
> y.cpp, line 315
>
> This application has requested the Runtime to terminate it in an unusual
> way.
>
> Can anyone please suggest me what is the way to do this.
>
>
>
> Regards,
>
> ND
>
> < h r > < f o n t f a c e = " A r i a l " c o l o r = " G r a y " s i z e =
> " 1 " > T h i s c o m m u n i c a t i o n m a y c o n t a i n p r i v i l e
> g e d o r o t h e r c o n f i d e n t i a l i n f o r m a t i o n . I f y o
> u h a v e r e c e i v e d i t i n e r r o r , p l e a s e a d v i s e t h e
> s e n d e r b y r e p l y i n g t h i s e - m a i l a n d i m m e d i a t e
> l y d e l e t i n g t h i s m e s s a g e a n d a n y a t t a c h m e n t w
> i t h o u t c o p y i n g o r d i s c l o s i n g t h e c o n t e n t s . A
> l t h o u g h t h i s e m a i l a n d a n y a t t a c h m e n t a r e b e l
> i e v e d t o b e f r e e o f a n y v i r u s , T r o j a n h o r s e p r o
> g r a m s , w o r m s , f a u l t o r o t h e r d e f e c t s w h i c h m i
> g h t a f f e c t a n y c o m p u t e r o r s y s t e m i n t o w h i c h i
> t i s r e c e i v e d a n d o p e n e d , i t i s t h e r e s p o n s i b i
> l i t y o f t h e r e c i p i e n t t o e n s u r e t h a t t h i s e m a i
> l a n d i t s a t t a c h m e n t s a r e f r e e f r o m s u c h v i r u s
> e s , f a u l t o r d e f e c t s a n d n o r e s p o n s i b i l i t y i s
> a c c e p t e d b y P l a n e t O n e a n d i t s g r o u p s o f c o m p a
> n i e s . < b r > < / f o n t > < / b o d y > < / h t m l >
> ___
> sipx-users mailing list
> sipx-users@list.sipfoundry.org
> List Archive: http://list.sipfoundry.org/archive/sipx-users/
>
___
sipx-users mailing list
sipx-users@list.sipfoundry.org
List Archive: http://list.sipfoundry.org/archive/sipx-users/
Re: [sipx-users] sipXecs and IPV6 - Again
On Tue, Jun 14, 2011 at 3:26 PM, Adrien Guillon wrote: > Anyways, I just wanted to voice that "I'm here and ready for ipv6". I > have noticed that in many projects (I'm looking at you ClearOS) there > is this mentality that "nobody is using ipv6, so we won't do it until > one day years from now". Thanks for the articulate email. Things pop on/off on ezuce's TODO list based on what paying customers need it so it could very well be shortly or could be awhile off. I would look at it as a great opportunity to replace some legacy components w/modern IPV6 ready ones (yeah, i'm looking at you proxy;) ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
Re: [sipx-users] Linksys AP Stopped Registering After Upgrade to 4.4
On Tue, Jun 14, 2011 at 12:27 PM, Roman Gelfand wrote: > I have Linksys SPA-3102 which successfully registered with sipx 4.2.1. > After the upgrade, it is failing to register. > > Are there settings changes? I don't recall many changes, but you can download the source and see. I would investigate the reason for the failed registration as the first step use the wiki for help. ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
Re: [sipx-users] Using SIP Viewer on older files
2011/6/14 Sven Evensen : > How can I use SIP viewer (i.e. sip-trace …) to look at old files, either the > likes of sipxBridge.log.1 etc, or even > > sipxbridge.log.2.gz etc… review the shell script and if it doesn't support it, consider submitting a patch that will allow a suffix to filter on ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
[sipx-users] Bug fix release update: sipXecs 4.4.0 update #5
Update #5 : Mon, 13 June 2011 == - ** No security updates in this update ** - ISO has *not* been rebuilt as decided in release policy. Yum update after installation is recommended for getting these updates - Thank you Mircea and George for your fixes and everyone for your bug reports! Build Log commit 0bc6cff813b3b70698432fb8546c2570ae8d9ea3 Author: Mircea Carasel Date: Tue Jun 7 02:32:37 2011 +0300 XX-9572: No Openfire admin user when using LDAP authentication. -remove im admin permission. existing superadmin permission will be used also for of console admin access -default of admins are admin and superadmin -if you create in ldap a user called admin it automatically will be of admin when of is configured with ldap -superadmin becomes of admin when is set as IM ID also -any other user that is made sipxecs admin becomes of admin as well commit 9eee605ddaabcfd98627d6d179cb29b20c733756 Author: George Niculae Date: Mon Jun 6 21:50:56 2011 +0300 XX-9659: AD: searching in subtrees with referrals fails patched acegi jar, includes fix for searchForSingleEntry to handle PartialResultException (as in latest Spring Security) commit 5b5179a118bbb82a86476cbbf07abe85b738aaa5 Author: George Niculae Date: Mon Jun 6 02:45:49 2011 +0300 XX-9660: LDAP: user portal authentication binds first with admin and password entered in login page remove admin bind from BindAuthenticator commit 084e84429fb5d74b727186ffc3252c41996dd615 Author: George Niculae Date: Mon Jun 6 03:33:00 2011 +0300 XX-9661: MyBuddy: password containing \ in sipximbot.properties interrupts string and breaks MyBuddy commit 19b8759976db017bab63bf86d9476dfa7344e316 Author: George Niculae Date: Mon Jun 6 14:07:30 2011 +0300 XX-9389: Authetication of MyBuddy fails with IM ID contaning capital letters - ignore case in jids map Change log for past releases can be found here http://download.sipfoundry.org/pub/sipXecs/ChangeLog-4.4.0 ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
Re: [sipx-users] HA Setup Problem
2011/6/9 Kemal Eroğlu : > Here is the patch. The setup script constructs the Configuration URL with > masterSystemName. Now it is changed with masterSystemAddr. We had tried it > manually before and it was working. > Kemal One more request, can you create a jira describing the problem and attach the file as a patch. That way it has a issue number for the commit message and we can coordinate the review and acceptable process. Thanks Kemal! ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
Re: [sipx-users] HA Setup Problem
On Thu, Jun 9, 2011 at 9:10 AM, Levend Sayar wrote: > Of course there is another solution, you can change the url in the > script with the ip number of master instead of master fqdn. Because > you already have this info. i like it. maybe you can come up with a simple patch for this. ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
Re: [sipx-users] LDAP and MyBuddy Bug fixes for 4.4 in staging area
i had to take web site down, but let me know if you were planning to test it. On Tue, Jun 7, 2011 at 8:38 AM, Douglas Hubler wrote: > On Tue, Jun 7, 2011 at 7:52 AM, Douglas Hubler wrote: >> These will push out to release shortly. If anyone would like to >> validate these changes before they go live, please do so shortly or >> let me know you would like some time. >> >> CentOS 5 >> URL: >> baseurl=http://ec2-50-17-110-224.compute-1.amazonaws.com:40100/CentOS_$releasever/$basearch >> Fedora 14 >> URL: >> baseurl=http://ec2-50-17-110-224.compute-1.amazonaws.com:40100/Fedora_$releasever/$basearch >> >> commit 0bc6cff813b3b70698432fb8546c2570ae8d9ea3 >> Author: Mircea Carasel >> Date: Tue Jun 7 02:32:37 2011 +0300 >> >> XX-9572: No Openfire admin user when using LDAP authentication. >> >> -remove im admin permission. existing superadmin permission will >> be used also for of console admin access >> -default of admins are admin and superadmin >> -if you create in ldap a user called admin it automatically will >> be of admin when of is configured with ldap >> -superadmin becomes of admin when is set as IM ID also >> -any other user that is made sipxecs admin becomes of admin as well >> >> >> commit 5b5179a118bbb82a86476cbbf07abe85b738aaa5 >> Author: George Niculae >> Date: Mon Jun 6 02:45:49 2011 +0300 >> >> XX-9660: LDAP: user portal authentication binds first with admin >> and password entered in login page >> >> remove admin bind from BindAuthenticator >> >> commit 084e84429fb5d74b727186ffc3252c41996dd615 >> Author: George Niculae >> Date: Mon Jun 6 03:33:00 2011 +0300 >> >> XX-9661: MyBuddy: password containing \ in sipximbot.properties >> interrupts string and breaks MyBuddy >> >> commit 19b8759976db017bab63bf86d9476dfa7344e316 >> Author: George Niculae >> Date: Mon Jun 6 14:07:30 2011 +0300 >> >> XX-9389: Authetication of MyBuddy fails with IM ID contaning capital >> letters >> >> - ignore case in jids map >> > > And... > > commit 9eee605ddaabcfd98627d6d179cb29b20c733756 > Author: George Niculae > Date: Mon Jun 6 21:50:56 2011 +0300 > > XX-9659: AD: searching in subtrees with referrals fails > > patched acegi jar, includes fix for searchForSingleEntry to handle > PartialResultException (as in latest Spring Security) > ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
Re: [sipx-users] LDAP and MyBuddy Bug fixes for 4.4 in staging area
On Tue, Jun 7, 2011 at 7:52 AM, Douglas Hubler wrote: > These will push out to release shortly. If anyone would like to > validate these changes before they go live, please do so shortly or > let me know you would like some time. > > CentOS 5 > URL: > baseurl=http://ec2-50-17-110-224.compute-1.amazonaws.com:40100/CentOS_$releasever/$basearch > Fedora 14 > URL: > baseurl=http://ec2-50-17-110-224.compute-1.amazonaws.com:40100/Fedora_$releasever/$basearch > > commit 0bc6cff813b3b70698432fb8546c2570ae8d9ea3 > Author: Mircea Carasel > Date: Tue Jun 7 02:32:37 2011 +0300 > > XX-9572: No Openfire admin user when using LDAP authentication. > > -remove im admin permission. existing superadmin permission will > be used also for of console admin access > -default of admins are admin and superadmin > -if you create in ldap a user called admin it automatically will > be of admin when of is configured with ldap > -superadmin becomes of admin when is set as IM ID also > -any other user that is made sipxecs admin becomes of admin as well > > > commit 5b5179a118bbb82a86476cbbf07abe85b738aaa5 > Author: George Niculae > Date: Mon Jun 6 02:45:49 2011 +0300 > > XX-9660: LDAP: user portal authentication binds first with admin > and password entered in login page > > remove admin bind from BindAuthenticator > > commit 084e84429fb5d74b727186ffc3252c41996dd615 > Author: George Niculae > Date: Mon Jun 6 03:33:00 2011 +0300 > > XX-9661: MyBuddy: password containing \ in sipximbot.properties > interrupts string and breaks MyBuddy > > commit 19b8759976db017bab63bf86d9476dfa7344e316 > Author: George Niculae > Date: Mon Jun 6 14:07:30 2011 +0300 > > XX-9389: Authetication of MyBuddy fails with IM ID contaning capital > letters > > - ignore case in jids map > And... commit 9eee605ddaabcfd98627d6d179cb29b20c733756 Author: George Niculae Date: Mon Jun 6 21:50:56 2011 +0300 XX-9659: AD: searching in subtrees with referrals fails patched acegi jar, includes fix for searchForSingleEntry to handle PartialResultException (as in latest Spring Security) ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
[sipx-users] LDAP and MyBuddy Bug fixes for 4.4 in staging area
These will push out to release shortly. If anyone would like to validate these changes before they go live, please do so shortly or let me know you would like some time. CentOS 5 URL: baseurl=http://ec2-50-17-110-224.compute-1.amazonaws.com:40100/CentOS_$releasever/$basearch Fedora 14 URL: baseurl=http://ec2-50-17-110-224.compute-1.amazonaws.com:40100/Fedora_$releasever/$basearch commit 0bc6cff813b3b70698432fb8546c2570ae8d9ea3 Author: Mircea Carasel Date: Tue Jun 7 02:32:37 2011 +0300 XX-9572: No Openfire admin user when using LDAP authentication. -remove im admin permission. existing superadmin permission will be used also for of console admin access -default of admins are admin and superadmin -if you create in ldap a user called admin it automatically will be of admin when of is configured with ldap -superadmin becomes of admin when is set as IM ID also -any other user that is made sipxecs admin becomes of admin as well commit 5b5179a118bbb82a86476cbbf07abe85b738aaa5 Author: George Niculae Date: Mon Jun 6 02:45:49 2011 +0300 XX-9660: LDAP: user portal authentication binds first with admin and password entered in login page remove admin bind from BindAuthenticator commit 084e84429fb5d74b727186ffc3252c41996dd615 Author: George Niculae Date: Mon Jun 6 03:33:00 2011 +0300 XX-9661: MyBuddy: password containing \ in sipximbot.properties interrupts string and breaks MyBuddy commit 19b8759976db017bab63bf86d9476dfa7344e316 Author: George Niculae Date: Mon Jun 6 14:07:30 2011 +0300 XX-9389: Authetication of MyBuddy fails with IM ID contaning capital letters - ignore case in jids map ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
[sipx-users] Bug fix release update: sipXecs 4.4.0 update #4
Update #4 : Fri, 3 June 2011 == - ** No security updates in this update ** - ISO has *not* been rebuilt as decided in release policy. Yum update after installation is recommended for getting these updates - Thank you Operations, Mike Picher and Mircea Carasel for your fixes and everyone for your bug reports! Build Log commit e0ec89136a02a53d4876db35bfaae2d4c9e5e718 Author: Douglas Hubler Date: Fri Jun 3 13:06:05 2011 -0400 Revert "XX-9639: missing TLS SRV" This reverts commit ad1a9f80f5832c1d9f76df894578d87af927cedd. The fix is correct but it exposes another bug in TLS XX-9656 Past updates log can be read here http://download.sipfoundry.org/pub/sipXecs/ChangeLog-4.4.0 ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
[sipx-users] Bug fix release update: sipXecs 4.4.0 update #3
Update #3 : Thu, 2 June 2011 == - ** No security updates in this update ** - ISO has *not* been rebuilt as decided in release policy. Yum update after installation is recommended for getting these updates - Thank you Hoa Nguyen and George for your fixes and everyone for your bug reports! Build Log commit 0a9ffa2c226d72a5b7e82341bb579e2d83933a44 Author: sipxchange Date: Wed May 25 09:00:59 2011 -0500 XX-9634 In a large scale phone system, the RLS crashes during startup Updated - in sipXrls/src/ResourceListFileReader.cpp added the delay in ResourceListUpdater::compare, which is a better place to delay and actually let the ResourceTaskList process it's queue. Removed - in sipXrls/src/ResourceListSet.cpp a delay was commented out, I have commented on why I commented that line out commit ad1a9f80f5832c1d9f76df894578d87af927cedd Author: George Niculae Date: Fri May 27 01:47:54 2011 +0300 XX-9639: missing TLS SRV * List of previous updates can be found here http://download.sipfoundry.org/pub/sipXecs/4.4.0/ChangeLog ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
[sipx-users] Cluecon 2011, Aug 9-11th in Chicago
I just purchased my tickets so I should be attending. I would encourage anyone with an inclination to tinker with FreeSWITCH to go, you do learn some good stuff. If anyone is going, let me know, maybe we can try to get together, I met a few of you last year. http://www.cluecon.com/ ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
Re: [sipx-users] New eZuce Hire...
On Thu, Jun 2, 2011 at 12:56 PM, Michael Picher wrote: > eZuce would like to welcome Josh Patten to the eZuce team as a Solutions > Architect. As of the 13th of this month he'll be working with our partners > and customers to plan, implement and maintain openUC / sipxecs systems > around the world. > > He has worked hard over the years on the sipXecs project, helped with > testing and development, built wiki documentation and assisted many of us > here as well. > > We're looking forward to working more closely with Josh and we're excited > about the expertise he'll bring to our team! > Welcome to the eZuce team Josh! Remember, I still owe you that punch in the arm, yeah, you know why. ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
Re: [sipx-users] Regarding: http://track.sipfoundry.org/browse/XX-8779
On Wed, Jun 1, 2011 at 9:41 AM, Mircea Carasel wrote: > > > On Thu, May 19, 2011 at 7:29 PM, Douglas Hubler wrote: > >> On Thu, May 19, 2011 at 10:27 AM, Mircea Carasel >> wrote: >> > With regard to XX-8779 the thing is that sipXconfig certificate >> authority >> > page for uploading certificates rejects non trusted certificates >> > (certificates signed by a trusted authority) >> > Therefore, self signed certificates does not pass validation and cannot >> be >> > uploaded >> >> Is the problem that we have also should be managing authorities too? >> > That's hard to say. One thing is that the root certificate that is > generated at system setup is not signed by a trusted authority, > and therefore it is not trusted. As an example, browsers detect the > certificate exposed at https://:8443/ and they report that it is not > trusted, meaning that is not signed by a trusted authority > > I think that's fine, I don't think that sipxecs should deal with trusted > authorities, and I think that is also fine that sipx to require a trusted > certificate if someone wants to upload a new certificate. > Hope this answers the question :) > I do know how the certs and CAs work, but my question more along the lines of what we need to do to support users w/real certs or certs they've generated elsewhere. > >> > So my question is that will it be desirable to remove that additional >> > verification (openssl -verify)? >> >> We want to disallow certs uploads that will cause the system to not >> work. As far as I know, uploading a self-signed cert w/o also >> installing the self-generated cert authority will break the system. >> Right? >> > I agree, IMO we should keep certificate verification as is in sipXconfig. > The most important thing is to define clear steps that should be followed by > every user admin to generate certificate and upload through UI > right, 2 cases: 1.) certs/CAs admins have generated elsewhere 2.) certs and/or CAs from real authorities ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
Re: [sipx-users] stable repo (4.4.0) memory questions
On Wed, Jun 1, 2011 at 8:07 AM, Douglas Hubler wrote: > On Wed, Jun 1, 2011 at 8:01 AM, Tony Graziano < > tgrazi...@myitdepartment.net> wrote: > >> I've disabled it for now in lieu of another method which should yield >> more results tomorrow on whether or not it can be backed up without >> consuming 5gb more of ram. >> >> Is there a limit to the memory the sipx backup can consume? >> > you can force a limit in the startup script but i'm not sure the impact given it's unclear why it needs that much memory to begin with. if it's required then you'll wind up with sipxconfig getting into a bad state. > Is sipxconfig consuming the memory? If not what is? > It would be good if you can verify this. George and to a degree I spent a lot of time trying to duplicate this. George, did you ever get Michael K's actually sipxconfig database and see if that made a difference? ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
Re: [sipx-users] stable repo (4.4.0) memory questions
On Wed, Jun 1, 2011 at 8:01 AM, Tony Graziano wrote: > I have a recent 4.4.0 upgrade that at boot consumes just under 2GB of > ram at bootup. I rebooted the system at 5pm, and with very few actual > call flows, consumes the rest of the memory overnight (8GB). The only > thing happening at night is a backup. It has just over 100 lines > registered. It's on its own vlan, etc. > > I have seen the system on its first day of use then eat into swap and > start exhibiting "stuck" (like no prack) calls. > > I've disabled it for now in lieu of another method which should yield > more results tomorrow on whether or not it can be backed up without > consuming 5gb more of ram. > > Is there a limit to the memory the sipx backup can consume? > Is sipxconfig consuming the memory? If not what is? Did this system exist as a 4.2.1 and not exhibit this behavior? If it was 4.2.1, did you fresh install or in-place upgrade the system? How many users? Anything unusual about this system? ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
Re: [sipx-users] Need to revert to slightly older version, dying here....
if you want to go backwards and you didn't save the original rpms, best bet is to download ISO and pull them off there. There were 2 updates to 4.4 so this may take you back to before 5/10. some repo file editing and a yum downgrade sipx* will get you thru until you're able to report what the issue is so we can get this fixed. i will say the fixes applied to 4.4.0 since 5/10 really don't look like they'd cause "Transfers are dead now" issues. On Tue, May 31, 2011 at 10:47 PM, Matthew Kitchin (public/usenet) < mkitchin.pub...@gmail.com> wrote: > Not working system > sipXecs (4.4.0- 2011-05-20EDT17:17:45 domU-12-31-39-15-3C-B1) > Working system > sipXecs (4.4.0- 2011-05-10EDT22:57:56 ip-10-110-26-134) > > I just installed the top system. It worked perfectly in my lab. I'm > thinking I may have run an update before I shut it down. Transfers are > dead now. > I have an entire site down right now since I just converted them off > their old system. The only thing I can find different is the patch > version above. > Can someone tell me how to get the top system on the exact same version > as the bottom system? > > Thanks, > Matthew > > ___ > sipx-users mailing list > sipx-users@list.sipfoundry.org > List Archive: http://list.sipfoundry.org/archive/sipx-users/ > ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
Re: [sipx-users] MyBuddy and PCMU problem
On Tue, May 31, 2011 at 10:53 AM, Irena Dolovčak wrote: > Thanks Tony, > you were right, myBuddy offeres only PCMU. > we opened a jira.. > Is there perhaps a way to "hack" the codec and force myBuddy to use the PCMA > codec? > > did anybody tried something like this? grep/modify the source and build the sipXimbot rpm. http://wiki.sipfoundry.org/display/sipXecs/Building+RPMS+on+CentOS+or+Fedora then, you can submit a patch w/configurable codec ability. ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
Re: [sipx-users] phone registrations expired
On Tue, May 31, 2011 at 12:09 PM, Tony Graziano < tgrazi...@myitdepartment.net> wrote: > what I have seen is that the busier the environnment the more frequent the > stops occur. That made me think it was related to the RLS patch. I tried > taking the RLS patch and related components separately from the build repo, > but it became moreso problematic after doing so. > > (sample cron entry for daily at 3 hour intervals) > * 0,3,6,9,12,15,18,21 * * * sipxproc -r SIPRegistrar > * 0,3,6,9,12,15,18,21 * * * sipxproc -r SIPXProxy > > I think it stems from a needed patch to RLS, but I might be wrong. I have > querid this already on the sipx-dev list and am hoping to see some activity > on it. If you are also having this issue on 4.4.0 (anyone) it would help to > know. I am not sure whether it is related to XX-9634 or not. > Patch for RLS can't possibly effect this in a negative way, fix was isolated to these 2 files. M sipXrls/src/ResourceListFileReader.cpp M sipXrls/src/ResourceListSet.cpp It could affect it in a positive way in that devices won't be blasting SUBSCRIBEs to RLS because they are not getting a response. I do think Mark should take Tony's advice on looking into sipvicious attacks, they seem to be more common then uncommon. ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
Re: [sipx-users] ACD problem with 4.4.0
We're switching you back and forth from new ACD (Call Center/OpenACD based) and old ACD (ACD/sipXacd). Laurentiu was talking about new one. Two systems are implemented completely separately. FYI: You can use both at the same time, but no good reason to that i know of unless you want to slowly migrate. On Fri, May 27, 2011 at 11:56 AM, Irena Dolovčak wrote: > I have tried your sugestion and I got the Ring Test to work. But I can't > make the Agent to ring when the call is in queue. I logged in in the Agent do you hear the hold music? > UI and when I open the supervisor tab, I can't see the call in the queue.. > as if the call is somewhere else.. the queue shows 0 active calls. > Here are new merge logs and full.log check the skills. i know at one point, the default skill was no skills and that meant agent's wouldn't get calls. An agent needs all the skills in order to be eligible including the queue. ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
Re: [sipx-users] weird log problem on snapshots
On Fri, May 27, 2011 at 5:28 AM, Henry Dogger wrote: > I installed patch as you proposed, but sipXecs crashed overnight > I put new snapshots on the FTP from before installing patch -> reboot -> > and then ran test again. did it resolve the cdr unique id errors? do you still have a lot of stunnel processes running? ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
Re: [sipx-users] Polycom station delay ring issue
On Thu, May 26, 2011 at 3:33 PM, Tony Graziano wrote: > Disabling the plugin resolves the issue. Jim or Tony, can you please file a bug in the external project http://track.sipfoundry.org/browse/XTRN We need to get to the bottom of the issue, but whether the feature works or not, i think this feature should be disabled by default. ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
Re: [sipx-users] Polycom station delay ring issue
On Thu, May 26, 2011 at 1:18 PM, Tony Graziano wrote: > So the difference is between internal and external calls. So i have to ask, > that there are two possibilities: > (I can duplicate this with bootrom 4.2.3 and 4.3.0 and firmware 3.1.3revc, > 3.2.4b and 3.2.5) > sipxconfig changes to differentiate between internal and external calls via > the "sound effects" (but still a polycom setting). > Does anyone have an opinion on this? Would the new settings being generated > in the polycom config file, even if untouched, provide a "logical delay" on > external calls rings that would manifest itself like this? Logically, I fall > into the "what is the reason polycom wants to audibly delay the external > ring using the yes, if i understand your theory correctly. The external/internal ring feature was implemented as a proxy plugin because it actually modify's the incoming SIP message. So it's possible the polycom phone can treat them differently. Jim, if you can disable this feature, we can prove/disprove this and at least My previous pleads for documentation went unanswered so i created this basic page. http://wiki.sipfoundry.org/display/sipXecs/Distinct+ringtones+for+internal+and+external+calls This should get you going, but please elaborate on the page to help others. ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
Re: [sipx-users] Polycom station delay ring issue
On Thu, May 26, 2011 at 12:32 PM, Jim Canfield wrote: > We've been fighting a strange issue where gateway calls (patton 4960 pri) > are taking 2-5 seconds before they begin to ring. Display shows the > incoming call and it can even be picked up. Internal calls work fine. > Oddly, the second call placed will work fine as long as it is shortly after > the first call. > > Right now I'm looking for direction. Could this be a sipproxy issue? We > have tried the various polycom firmware and the issue persists. Using HA? Both proxies working properly? is dns lookup times from that gateway and from the sip proxy itself less than 100ms? ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
Re: [sipx-users] weird log problem on snapshots
ok, i took a quick look for stack traces in logs in case stunnel is not the prob. i saw none. On Thu, May 26, 2011 at 12:29 PM, Henry Dogger wrote: > The problem seems related to the stunnel problems but I posted a > snapshot at: > ftp://ftp.telecats.nl > user: SipX > pass: SipXLogg1nG > It is in de folder dhubler :) > They contain a snapshot from 3 hours, around the time I restarted the > secondary server after the time-zone was changed. And when I clicked > send profiles on master server. > > Henry > > -Original Message- > From: sipx-users-boun...@list.sipfoundry.org > [mailto:sipx-users-boun...@list.sipfoundry.org] On Behalf Of Douglas > Hubler > Sent: donderdag 26 mei 2011 18:20 > To: Discussion list for users of sipXecs software > Subject: Re: [sipx-users] weird log problem on snapshots > > On Thu, May 26, 2011 at 10:55 AM, Henry Dogger > wrote: >> I changed the time zone, and restarted the secondary machine, but > still a crash on sending profiles... > > can you make a snapshot available somewhere? > ___ > sipx-users mailing list > sipx-users@list.sipfoundry.org > List Archive: http://list.sipfoundry.org/archive/sipx-users/ > ___ > sipx-users mailing list > sipx-users@list.sipfoundry.org > List Archive: http://list.sipfoundry.org/archive/sipx-users/ > ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
Re: [sipx-users] weird log problem on snapshots
On Thu, May 26, 2011 at 10:55 AM, Henry Dogger wrote: > I changed the time zone, and restarted the secondary machine, but still a > crash on sending profiles... can you make a snapshot available somewhere? ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
Re: [sipx-users] stunnel problems
Back in december I recommended you apply this patch http://forum.sipfoundry.org/index.php?t=msg&goto=55127&S=ad60d822e4f20cdb6a33400e600ecaa8 i can see you're still getting the same unique id errors in logs so i'm wondering if you ever applied the patch. The theory is the cdr script aborts abnormally and leaves the stunnel proc hanging. Please reply back w/you're results, good or bad, George and I are very curious. as FYI: in 4.6, I'm addressing this properly where stunnel is a self running process and can start/stop independently of other processes so we shouldn't have this fragility going forward. On Thu, May 26, 2011 at 10:54 AM, Henry Dogger wrote: > I don’t see any weird issues, before this problem in sipxcallresolver, but I > see this: > > http://pastebin.com/qi5Hr0Wn > > This was when I tried to see the registrations I guess…. > > After this nothing seemed to be working anymore (sipxproc no response etc) > > > > Henry > > > > From: sipx-users-boun...@list.sipfoundry.org > [mailto:sipx-users-boun...@list.sipfoundry.org] On Behalf Of Josh M. Patten > Sent: donderdag 26 mei 2011 15:30 > > To: Discussion list for users of sipXecs software > Subject: Re: [sipx-users] stunnel problems > > > > I think in your case stunnel is working properly but there is definitely > something deeper going on here. On the surface this appears to be an SSL > issue or possibly a database corruption issue. It would probably help if you > posted a snip of /var/log/sipxpbx/sipxconfig.log where the actual error is > occurring. > > > > Josh Patten > > Brazos County Network Engineer > > 979.361.4676 > > > > From: sipx-users-boun...@list.sipfoundry.org > [mailto:sipx-users-boun...@list.sipfoundry.org] On Behalf Of Henry Dogger > Sent: Thursday, May 26, 2011 5:32 AM > To: Discussion list for users of sipXecs software > Subject: [sipx-users] stunnel problems > > > > Hi all, > > > > I found a problem on the list a year ago concerning stunnel. > > I found a post of Josh Patten: > > http://list.sipfoundry.org/archive/sipx-users/msg25011.html > > And currently I see the following errors: > > http://pastebin.com/Tn4XT36z > > I think I encounter a similar problem since I see on my primary server that > stunnel is failing: > > > > [telecats@sipxecs1 tmp]$ ps aux | grep stunnel > > telecats 8433 0.0 0.0 61172 756 pts/1 S+ 12:25 0:00 grep > stunnel > > 500 8678 0.0 0.0 47216 3352 ? Sl May17 0:13 > /usr/sbin/stunnel /tmp/stunnel-config.8574.0 > > 500 8679 0.0 0.0 46380 432 ? S May17 0:00 > /usr/sbin/stunnel /tmp/stunnel-config.8574.0 > > 500 8680 0.0 0.0 46380 128 ? S May17 0:00 > /usr/sbin/stunnel /tmp/stunnel-config.8574.0 > > 500 8681 0.0 0.0 46380 128 ? S May17 0:00 > /usr/sbin/stunnel /tmp/stunnel-config.8574.0 > > 500 8682 0.0 0.0 46380 128 ? S May17 0:00 > /usr/sbin/stunnel /tmp/stunnel-config.8574.0 > > 500 8683 0.0 0.0 46380 128 ? S May17 0:00 > /usr/sbin/stunnel /tmp/stunnel-config.8574.0 > > 500 12648 0.0 0.0 0 0 ? Z May25 0:00 [stunnel] > > > > > Secondary seems running fine: > > [telecats@sipxecs2 ~]$ ps aux | grep stunnel > > 500 4762 0.0 0.0 43080 3356 ? Sl May25 0:01 > /usr/sbin/stunnel /etc/sipxpbx/sipxcallresolver-agent-config > > 500 4777 0.0 0.0 42220 876 ? S May25 0:00 > /usr/sbin/stunnel /etc/sipxpbx/sipxcallresolver-agent-config > > 500 4778 0.0 0.0 42220 628 ? S May25 0:00 > /usr/sbin/stunnel /etc/sipxpbx/sipxcallresolver-agent-config > > 500 4779 0.0 0.0 42220 628 ? S May25 0:00 > /usr/sbin/stunnel /etc/sipxpbx/sipxcallresolver-agent-config > > 500 4780 0.0 0.0 42220 628 ? S May25 0:00 > /usr/sbin/stunnel /etc/sipxpbx/sipxcallresolver-agent-config > > 500 4781 0.0 0.0 42220 628 ? S May25 0:00 > /usr/sbin/stunnel /etc/sipxpbx/sipxcallresolver-agent-config > > telecats 19952 0.0 0.0 61200 772 pts/0 S+ 12:25 0:00 grep > stunnel > > > > The primary server seems to choke on “sending profiles” sipxproc won’t > respond afterwards, I don’t see any services status information in web ui > and also no registrations… > > Any idea how to fix? > > I installed on CentOS 5.6 sipXecs 4.2.1 from RPM, so am using stunnel: > 4.28-5.2 > > I noticed the fips = no was in the stunnel config file…. > > > > Kind regards, > > > > Henry Dogger > > Telecats BV > > > > ___ > sipx-users mailing list > sipx-users@list.sipfoundry.org > List Archive: http://list.sipfoundry.org/archive/sipx-users/ > ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
Re: [sipx-users] Enhancement request:feedback
On Wed, May 25, 2011 at 12:14 PM, Tony Graziano wrote: > I am now seeing phone lockup issues when the sipx hostname is the same as > the sip domain name. mike p. and i saw a similar thing and strangely for this customer, removing the SRV records from DNS actually stopped the lockups! Of course that means you cannot do HA but this didn't impact this particular customer. > I know this has been discussed before, but I am wondering if it is time to > officially look for a feature request to separate the PIN from the DOMAIN. it's been time for a while, just keeps slipping down the list for ezuce anyway. ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
Re: [sipx-users] error after update: sipx-freeswitch
On Wed, May 25, 2011 at 12:34 PM, m...@grounded.net wrote: > Well, interesting then because my system didn't get updated to 4.4.0 when I > ran the update, it only updated 4.2.1. This is also a departure how sipxecs release eng ran in the past I think. You have to explicitly install a new sipxecs repository file in order to jump to the new X.X release. This is so you can actually apply bug fixes to your stable system when they come out and not accidentally upgrade the entire system one day just because a new major release came out. Messing w/repo files is probably not the most user friendly so maybe we should start installing a script that when run will repoint your local yum repository file to the next release. This is a lot how OS upgrades work. ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
Re: [sipx-users] error after update: sipx-freeswitch
On Wed, May 25, 2011 at 11:28 AM, m...@grounded.net wrote: > Bit nervous about doing that because it removes others at the same time and > I'm not sure if I should use nodeps or not. > Too easy to break the system when things get into dep problems. CAVEAT: I haven't tried this, just giving you an idea of an option that might work If you're nervous, you can do this rpm -ql sipx-freeswitch-1.0.5-17188.16739.2.i386 > file-list to get a list of the files installed first. then do rpm -e --justdb sipx-freeswitch-1.0.5-17188.16739.2.i386 to just trick the rpm database to think it's gone. It will orphan all the files on your disk. Then move or remove any/all files from the file-list by hand that you think are safe to remove. 32bit .so files for example. I wouldn't do --nodeps, but instead allow the command to fail and start at each of the packages that depend on sipx-freeswitch-1.0.5-17188.16739.2.i386 first and work your way up until you've removed all 32 bit sipxecs related rpms. NOTE: I think 64 systems come w/some 32 bit rpms installed, like openssl for some unported apps and such, leave those alone obviously. ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
Re: [sipx-users] error after update: sipx-freeswitch
On Wed, May 25, 2011 at 11:11 AM, m...@grounded.net wrote: > I haven't updated my 4.2.1 in a while so when doing it I get the following > error. > Thought I would check with the list before rebooting, just in case. > > > Transaction Check Error: > file /usr/local/freeswitch/bin/fsxs from install of > sipx-freeswitch-1.0.5-17188.16739.2.i386 conflicts with file from package > sipx-freeswitch-1.0.5-17188.16739.2.x86_64 unfortunately sipxecs 4.2.1 yum repo mixes 32 and 64 bit archs and although the OS is supposed to do the right thing, often folks get into situations were system has 32 and 64 bit rpms installed. i'm not sure how it gets into this situation. 4.4.0 and beyond the 32/64 bit rpms are keep the separate. so to fix your system, yes, tony is right, you have to uninstall the 32 bit packages. i always force reinstall of the 64 bit ones again in case the 32 bit uninstalls take any config files with them. > > ___ > sipx-users mailing list > sipx-users@list.sipfoundry.org > List Archive: http://list.sipfoundry.org/archive/sipx-users/ > ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
[sipx-users] anyone using preflight download for windows?
there is a link to download a tool to run on a windows machine to test the network the windows laptop is on. It tests the same thing that the web page in sipxecs does. The windows installer adds a lot of complexity to the build process, anyone care if i stop building it? ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
[sipx-users] Bug fix release update: sipXecs 4.2.1 update #1
Notes == - ** No security updates in this update ** - ISO has *not* been rebuilt as decided in release policy. Yum update after installation is recommended for getting these updates - Thank you George and Joegen for your fixes and everyone for your bug reports! Build Log == commit 83f662810ddfa7b8f3f320f002e22faf1d103cb8 Author: Douglas Hubler Date: Tue May 24 11:40:22 2011 -0400 (On behalf of joegen) HttpConnection recyles HttpMessage. However, the request object is declared outside of the read iteration which hinders its destructor to be called. Even though HttpMessage::read() commit 8fb8248a22207606abd43f948887d991dda58894 Author: Douglas Hubler Date: Mon Oct 18 18:19:41 2010 -0400 (On behalf of George) XX-8931 - allow more memory for sipxconfig to support 15k users commit 02de87fa7b972542c0406fa4a80a2b469c36bf42 Author: Douglas Hubler Date: Mon Oct 18 18:17:31 2010 -0400 (On behalf of George) XX-8931 - increase xmlrpc timeout from 5s to 1m for supporting 15K users commit f9f25a0c19a4802a6415331dac66b9ae14ce53d9 Author: joegen Date: Wed Oct 6 08:28:44 2010 -0400 added null sanity check to res_free commit 6fd66005e036c4296a7eee8ef681c2478250232f Author: George Niculae Date: Fri May 6 02:35:07 2011 +0300 XX-9565: record and send message also after 1 is pressed and menu timeouts after 1 is pressed and wrong option provided For a list of the change log http://download.sipfoundry.org/pub/sipXecs/4.2.1/ChangeLog ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
[sipx-users] anyone developing sipp tests?
ezuce has started developing a few internally and was curious if there were other efforts out there. ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
Re: [sipx-users] Configuration for Global or Group call pickup
On Tue, May 24, 2011 at 12:25 PM, Josh M. Patten wrote: > It’s *78 where is the extension you wish to pick up. Again, > there is no global call pickup. If you want you can create hunt groups and > use the pickup code on that hunt group. Also, if this doesn’t work, try > using the pickup code doing an extension to extension call. If you can do a > call pickup on extension to extension calls, but not on gateway to extension > calls then there is something wrong with the SIP stack on your gateway. > Could you possibly give this a try and post back the results? > Also, it you're picking up calls from huntgroups in 4.2.1, keep this issue in mind as it has a workaround http://track.sipfoundry.org/browse/XX-8438 ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
Re: [sipx-users] 4.2.1 -> 4.4 more depsolving issues
On Mon, May 23, 2011 at 1:48 PM, Joe Micciche wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > I am trying to upgrade 2 servers to 4.4, from sipXconfig > 4.2.1-018971.dhubler 2010-08-21T04:59:18 build34. Both experience the > same problem, sipx-freeswitch and sipxacd-devel dependency problems. Yet > the dependencies are installed, see below. I see the problem. I missed some packages that are installed when someone installs the *-devel which is not common but should be supported. Question: Did you intend to install the -devel rpms at one time? If so why? I'll have a fix but there should be a workaround, try removing these packages rpm -evh \ sipx-freeswitch-spidermonkey \ sipx-freeswitch-lang-en \ sipx-freeswitch-lua \ sipx-freeswitch-perl \ sipx-freeswitch-devel \ sipxecs-devel If you wanted the newer versions of these, then after updating run yum install freeswitch-spidermonkey \ freeswitch-lang-en \ freeswitch-lua \ freeswitch-perl \ freeswitch-devel sipxecs-devel is not installable at the moment, but you shouldn't need it. It does nothing except pull in other sipx -devel packages which are only needed for compiling. ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
Re: [sipx-users] Unidata Phone plug-in not working in 4.4.0 2011-04-19
On Sun, May 22, 2011 at 4:30 PM, Peter van der Salm wrote: > The current phone plug in for the Unidata WPU-7700 phone does not work in > 4.4.0 of 2011-04-19. > The .jar file is not the correct version. Can you put together a patch so we can get it fixed in future versions? ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
[sipx-users] Bug fix release update: sipXecs 4.4.0 update #2
Notes = - ** No security updates in this update ** - ISO has *not* been rebuilt as decided in release policy. Yum update after installation is recommended for getting these updates - Thank you Mircea and George for your fixes and everyone for your bug reports! For past update change logs, see http://download.sipfoundry.org/pub/sipXecs/4.4.0/ChangeLog Build Log commit 8fa7a1ce3732330de6d4adfdbd2d7819ac38d956 Author: Mircea Carasel Date: Thu May 19 20:39:30 2011 +0300 XX-9570: Missing ability to change MyBuddy / imbot pw from GUI (for LDAP auth) -exposed mybuddy password field since imbot cannot connect to openfire when openfire is configured with LDAP. in this scenario a ldap user has to be designed for imbot commit 942dd4a38a43f68020d593c6614385119e8513d6 Author: Mircea Carasel Date: Wed May 18 16:28:31 2011 +0300 XX-9626: LDAP: Additional search filter should not be accounted for authentication Any additional LDAP filters (RFC 2254) are removed from authentication search because here the filter is used to specify what LDAP attribute represents the username and it does not respect RFC2254 guidelines ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
[sipx-users] Anyone using sipXecs 4.2.1 on Fedora 12?
I think not, but I have to update the RPMs and I lost the ability to build on Fedora 12 so I'd rather take down the rpms if no one is using them, then keep out of date ones. ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
Re: [sipx-users] weird log problem on snapshots
On Fri, May 20, 2011 at 8:32 AM, Henry Dogger wrote: > No one knows what this could mean? > > I’m still experiencing this problem… Joegen might be the only one that knows. Are you experiencing any other problems that you know of beside the log file entries? ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
Re: [sipx-users] Possible to indicate inbound/outbound in dial plan rules?
On Thu, May 19, 2011 at 3:17 PM, Douglas Hubler wrote: > and do some custom freeswitch programming which will allow you to do anything. and by "freeswitch programming" i mean messing w/FS dial-plans, not C/C++ coding. ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
Re: [sipx-users] Possible to indicate inbound/outbound in dial plan rules?
On Thu, May 19, 2011 at 12:36 PM, Anders Mydland wrote: > Is there any way to indicate the direction of calls to be processed in the > dial plan rules? > > E.g. "for inbound calls from gateway XXX, strip first 3 digits" and "for > outbound calls to gateway YYY, add prefix 123" > > I can't see anything in the GUI, but maybe it can be done via configuration > files / direct database editing...? An idea if you get desperate is to route calls into freeswitch by setting up a unmanaged gateway http://wiki.sipfoundry.org/display/sipXecs/OpenACD+Setup+for+sipXecs+4.2 and do some custom freeswitch programming which will allow you to do anything. ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
Re: [sipx-users] Regarding: http://track.sipfoundry.org/browse/XX-8779
On Thu, May 19, 2011 at 10:27 AM, Mircea Carasel wrote: > With regard to XX-8779 the thing is that sipXconfig certificate authority > page for uploading certificates rejects non trusted certificates > (certificates signed by a trusted authority) > Therefore, self signed certificates does not pass validation and cannot be > uploaded Is the problem that we have also should be managing authorities too? > So my question is that will it be desirable to remove that additional > verification (openssl -verify)? We want to disallow certs uploads that will cause the system to not work. As far as I know, uploading a self-signed cert w/o also installing the self-generated cert authority will break the system. Right? ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
Re: [sipx-users] Paging server performance
there were no changes to paging for 4.4 so i'd bet it's the same On Wed, May 18, 2011 at 5:55 PM, Matthew Kitchin (public/usenet) wrote: > Old thread, but still relevant to me at least. > Does anyone have any updated info on paging limits within 4.4? Does the > info below still seem accurate? I'm chasing down some issues and I'm not > sure if I've run into this as well. My group had 17 in it, but I've got > it down to 14 by removing some phones that are near each other. Since > the pager doesn't get the page, there are 13 actual destinations on most > pages. > > On 11/24/2009 5:10 PM, Josh Patten wrote: >> Searching from April 2009 to present in the sipx-users list didn't >> reveal any paging server information. I was trying to avoid the expense >> of installing overhead paging equipment, but if it's necessary I will. >> As far as bandwidth goes, generously assuming 100 kbps x 200 extensions, >> that's approximately 20 megabits per second, FAR below the gigabit fiber >> I will be using. If anything it will be a limitation of the sipX paging >> module which as far as I know is limited by CPU speed and RAM, which I >> have plenty of. >> >> I gleaned most of my information from this page: >> http://sipx-wiki.calivia.com/index.php/Functional_Specification_for_a_Paging_Server >> which is a bit old so may be disconnected from reality. >> >> If anyone has actually tested this I'd be glad to know. >> >> Josh Patten >> Assistant Network Administrator >> Brazos County IT Dept. >> >> >> >> >> Todd Hodgen wrote: >>> There was discussion around this on the list a few months ago, and the >>> technical details were provided by one of the developers. There is a limit, >>> I don't recall what it is, but it wasn't as high as you are wanting to go >>> from what I do recall, but it was higher than 12. I'd check in the old >>> archives from the May/June timeframe or there about. >>> >>> -Original Message- >>> From: sipx-users-boun...@list.sipfoundry.org >>> [mailto:sipx-users-boun...@list.sipfoundry.org] On Behalf Of Josh Patten >>> Sent: Tuesday, November 24, 2009 2:02 PM >>> To: sipx-users@list.sipfoundry.org >>> Subject: [sipx-users] Paging server performance >>> >>> Has anyone documented or tested the performance of the paging server? >>> The reason I ask is because I am about to do a 200 phone rollout where, >>> occasionally, 100 phones will need to be paged at a time. On rare >>> occasions all 200 will need to be paged I have a pretty beefy server (8 >>> xeon 5500 series cores @ 2.33 GHz each, 16 GB RAM for primary proxy, >>> quad-core xeon 5500 2.33 GHz with 2 GB RAM for auxiliary redundant >>> proxy) and gigabit fiber to the location. Should I be concerned about >>> the performance of the paging server? >>> >>> >> ___ >> sipx-users mailing list sipx-users@list.sipfoundry.org >> List Archive: http://list.sipfoundry.org/archive/sipx-users >> Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users >> sipXecs IP PBX -- http://www.sipfoundry.org/ > > ___ > sipx-users mailing list > sipx-users@list.sipfoundry.org > List Archive: http://list.sipfoundry.org/archive/sipx-users/ > ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
Re: [sipx-users] how to monitor call status & codec used on sipXbridge call ?
On Wed, May 18, 2011 at 7:23 AM, Carl Farrington wrote: > Hi. I now have a trunk set up, and can make outgoing calls. > I am using the sipXbridge (Use built-in SIP Trunk SBC = yes). > I'm still a little confused by all the multitude of SIP > servers/proxies/clients running together. > I entered fs_cli and could not see any active calls. > I just want to see if g.729 pass-through is being used. > Any tips ? Additional tips beyond Dale's 1.) for phone to phone calls thru sipXbridge, sipXbridge does not need support g729 explicitly because sipXbridge is not decoding it, only passing the media thru. (Technically, sipXbridge isn't even passing it thru, it delegates that to sipXrelay, but you get the idea.) 2.) Only calls that handle media such as AA, VM or Conferences would show up in fs_cli. Even then, to see g729 processing, you have to have installed g729 support in Freeswitch which can be very tricky. Have you done this? There are instructions on the wiki. ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
