I have already set up my FreePBX (PIAF-Ast11-FS-Skype) in Oracle VM VirtualBox.
I've also installed X-Lite 4.0 (a voip phone system).
Now, I am about to create trunk for it but where do I get this information. Please attached link.
https://monosnap.com/image/qnV2oREpK1mbFcpWNjb4l0iygHSW9y
You have get contract with any provider
http://www.voip-info.org/wiki/view/VOIP+Service+Providers
After that you can request needed info at provider's support /check provider's help center.
Related
I have access to our corporate PCF, though both the Apps Manager webpage and the "cf" CLI (and thus the API).
How can I detect what version of PCF they're running? There's nothing in the website that lists it, and the best I can find is using cf api which returns:
api version: 2.98.0
How can I map that to the PCF version, or is there another way to detect it?
Usually via Ops Manager however another quick way is to click on the 'Docs' in Apps Manager it should take you to the documentation of relevant PCF version. For ex: https://docs.pivotal.io/pivotalcf/2-6/pas/intro.html means PCF 2.6
Please be advised that documentation link requires to be updated during upgrades so if someone doesn't do - it will be pointing out to older version..
I don't believe Apps Manager or the API (i.e. Cloud Controller) will report that information. Both are just single parts of the entire system, so I think you could really only expect them to publish their own version information.
If you want to see versions of what is installed, you need to look at Ops Manager. That will show you the tiles that are installed and each version.
If you don't have access to Ops Manager, you'd need to ask your platform operators.
Hope that helps!
Since I already know APIM 1.9.0 is default support BAM, that UI is for deploy the BAM analytics artifacts called toolbox. When you work with DAS, you should leave Data Analyzer Configurations as blank. And need to deploy artifacts(CaPP) manually on DAS .
I seached and found below link which might be helpful:
http://blog.rukspot.com/2015/09/publishing-apim-runtime-statistics-to.html
But the bad thing is for unknown reason I tried times to access this link ,,all failed.
Can anybody help to paste the content of above link here or just send a private mail to me via my mail : menglong567#aliyun.com
That would be very appreaciated !
Please find the official documentation for WSO2 API-M 1.9.0 statistics configurations in here.
All the necessary information is covered in the official doc.
I'm looking for some guidance about two specific WSO2 products, API Manager and Identity Server and for the best solution to solve the problem I'm going to explain below.
In my company, we are using ADFS 3.0 for Single Sign On support in our applications. However we are now building applications that will require OpenID Connect Specification (SPA's+Rest API's) and ADFS does not support this out of the box so we've decided to use WSO2 products for that purpose.
I already managed to install WSO2 Identity Server 5.0.0 SP1 and configured ADFS as a federated Identity Provider (the new applications will still have to authenticate users using ADFS). I also installed WSO2 API Manager 1.9.1 and configured it to use WSO2 Identity Server as the Key Manager (Configuration tutorial).
Now the problem:
Using WSO2 Identity Server 5.0.0 SP1 I couldn't get the Logout feature to work due to the issue reported here. It seems that this issue has been solved in version 5.1.0M4 so I tried to install version 5.1.0-alpha and managed to make the logout to work with ADFS (I tested it by enabling SSO for the carbon administration). However, now I'm not able to install the Key Manager feature through the carbon repositories due to incompatibilities.
As a result, with the first combination (wso2is 5.0.0 SP1/wso2am 1.9.1) I had the logout issue with ADFS and with the second combination (wso2is 5.1.0-alpha/wso2am 1.9.1), I'm not able to install the Key Manager feature in Identity Server.
Is there any way to apply a patch to solve the logout issue in the first combination? Is there a way to install the key manager feature on WSO2IS 5.1.0-alpha? Or can someone point me to another solution to solve this issue?
The issue you pointed above, marked as it type as "Patch". Usually that means WSO2 have fixed this issue for a earlier version and provided a patch to its customer. Easiest thing would be, if you are already a customer of WSO2 ask for the patch directly from their support.
If you are not a paid customer of WSO2 you are in bit of a trouble. As per this question, the source of the Service Pack also not available in public.
But luckily in your case, the component which need to have this fix not a core component. So you wouldn't be in trouble if you change the authenticator code bit. But the warning is, it would lose any fixes done for org.wso2.carbon.identity.application.authenticator.samlsso_4.2.1.jar in the service pack.
Anyway, these are the steps you should follow.
Checkout the source. Lazy path would be checkout the whole source from here. That is the most easy way which you will face less troubles when you try to build the source but the downside of that is, it would take bit of time to checkout. If you know how to build specific component from WSO2 source, you can directly checkout component it needed to changed.
Try to build the component without doing any change just to make sure there are not any issues upto this point.
Goto the class DefaultSAML2SSOManager and do the same change done in the PR.
Build the component again.
Create folder named like "patch9000" inside the <IS_HOME>/repository/components/patches/ folder.
Copy build jar (org.wso2.carbon.identity.application.authenticator.samlsso-4.2.1.jar ) in step 4 from the target folder to the <IS_HOME>/repository/components/patches/patch9000 folder.
Restart the server. If you have done everything to the point, in the server startup it would print a log like, org.wso2.carbon.server.extensions.PatchInstaller - Patch changes detected
Now retry the your flow and it would work as expected.
If you too lazy to do all above, you can wait until Identity Server Service Pack 2, which will have your fix.
The WSO2IS sample app instructions are less than accurate and there are some key details to the instructions are missing. Does anyone have a complete set of instructions that will actually produce a working example?
Also, it seems like localhost is coded everywhere, some guidance on how to add and update the service provider and identity provider that are on different hosts is important.
also, is the patch or service pack needed for this to run correctly? That info is not in the documentation or blogs I've been reading from WSO2
I've written a post on configuring the sample for a tenant scenario1. You should be able to configure using this. Change the hostname of SAML.IdPUrl in WEB-INF/classes/travelocity.property to that of IS. Change Assertion Consumer URL at SP registration and on WEB-INF/classes/travelocity.property to that of SP(travelocit app).
1 - how-to-configure-identity-server-sso
I am new to vtiger. I would like to know is there any modules available for Asterisk and multitenant. If so can you please give me the link. I saw some post saying it will be in future release.
as per developers, setting PBX Manager back in action is planned in version 6.1
Meantime, you'll need to wait or create your custom module.
check out http://www.vtigerexperts.com/vtiger-crm-6-1-demo/
PBX manager is available in 6.1. For multi-tenancy you have to customize.