Alternative of Cisco PGW2200 for SS7 Signaling termination

Hi
I want to know which alternative of Cisco PGW 2200 that I can use to terminate SS7 Signaling on my Voice gateway. And I can continue further. Actually I want to some low and high cost alternative of Cisco PGW2200 solution.
BR//
Sultan Al Arif

Cisco BTS 10200 may be the one you want.
Here are the documents for BTS.
http://www.cisco.com/en/US/partner/products/hw/vcallcon/ps531/tsd_products_support_series_home.html

Similar Messages

Hi Team, I wuold like to know if you have any app to make Firefox OS working with cisco Call Manager 10.5. Something like Cisco Jabber for Android or iOS.

I'm interesting on buying a Firefox Smart Phone, but
I would like to know if are any app to install on Firefox OS smart phone in order to work with cisco call manager 10.5.
Something like Cisco Jabber for Android o iOS.
Thanks,

Hi Itech,
If Cisco Jabber has a webapp, or mobile version of their website available, you should technically be able to access it through Firefox OS.
You may also search Firefox Marketplace for an alternative solution:
* [https://marketplace.firefox.com/]
- Ralph

Cisco Jabber for Mac - Directory Lookup and Contact Fields

Hello,
After having issues myself with Cisco Jabber for Mac 9.2 specifically with Active Directory lookups not working, or contact information not populating (and therefore not being able to call users from the contact list as no telephone information exists) I am including a sample jabber-config.xml file that works for me.
Please note: there are many different ways to configure this. What I will be showing is the method that works for me and my deployment, which is pretty standard.
As always and as a disclaimer, once again, this is what has worked for my deployment scenario. Always keep backups of your configuration files, and always be mindful of anything you have configured already, especially in the jabber-config.xml file.
Background
My deployment is based on CUCM 9, with 1 publisher and 2 subscribers. I also have a CUCM IM & Presence 9.0 server. This assumes that you have already configured your deployment and Jabber is functioning already, albeit with the aforementioned issues.
As for Active Directory, my deployment will be based on Windows 2008 R2 Domain Controllers running in native 2008 mode. For this example, we will be searching directly against one of the DCs with a Global Catalogue role. Please be aware that in large deployments you will have to plan accordingly with regards to lookup traffic from Jabber clients to the DCs.
Also, as of Cisco Jabber for Mac 9, the client no longer can search via the CUCM internal directory (which may be made of local end users, Active Directory synced users, or a mix of both) and this must be done via a LDAP mechanism.
Scenario
In this deployment scenario, Cisco Jabber for Windows is working properly - you can search and add people from Active Directory, and contacts in your contact list have all the appropriate fields populated from Active Directory. However, when trying the same with Jabber for Mac, Jabber for iPhone or Jabber for iPad you notice that you cannot perform a directory lookup, and if you add people directly (for example, [email protected]) the user only has the IM field populated. No telephone, email or additional information is displayed.
Solution
Whereas Cisco Jabber for Windows uses the EDI mechanism (native Windows), whereby when running from a computer that is on the domain (or in the event that you are search for contacts in another Active Directory domain where a domain trust exists) , Jabber for Mac / iPhone / iPad uses the BDI mechanism.
In this case, you will need to provision a jabber-config.xml file that you will upload to your TFTP server (or Publisher) that will be "downloaded" by your Jabber for Mac client and also used by the iPhone and iPad client. You can configure many options in the jabber-config.xml file, but for this example we will place just the information that we need to order for these clients to request and display Active Directory information.
Please note that the configuration may vary depending on your deployment, but at the very least we will be:
- Configuring a DC where we will perform the lookup.
- Configure credentials that will be used to perform the lookup. This will be an Active Directory account that has read rights on the Active Directory domain. Please note that these credentials are saved in plain text in the file, so ensure that the account that you will be using is not privileged.
- Configure the server port that we will be using to perform the lookup.
- Configure the Search Base. This is basically where we want the directory lookup to happen. You can either choose for this lookup to start at the "base" of the domain (and therefore the search will iterate through all the user accounts and and OUs below the root base) or define a specific OU where you want to search.
Caution!
- There is a current limitation with Cisco Jabber for Mac whereby you can only have 1 search base configured. Please keep this in mind if, like me, you have multiple OUs (like an OU for each company in your organization) and under these OUs you have sub OUs as a user account container.
- If using the top level search base, unless you specify a filter, you will potentially be able to search for all user accounts in the domain. You will need to configure the <BDIBaseFilter> parameter if you want to fine tune your search ability.
Steps
These are the steps I have followed. Other steps or considerations may vary.
- Log in to your TFTP server and download the jabber-config.xml file and keep it as a backup. If you are already using the jabber-config.xml file for other purposes, do not worry - you can add your BDI information parameters inside.
- Remove the jabber-config.xml file
- Edit the jabber-config.xml file and configure thus:
<?xml version="1.0" encoding="UTF-8"?>
<config version="1.0">
 <Directory>
 <DirectoryServerType>BDI</DirectoryServerType>
 <BDILDAPServerType>AD</BDILDAPServerType>
 <BDIPrimaryServerName>DOMAIN CONTROLLER IP ADDRESS</BDIPrimaryServerName>
 <BDIPresenceDomain>YOUR PRESENCE DOMAIN</BDIPresenceDomain>
 <BDIServerPort1>3268</BDIServerPort1>
 <BDISearchBase1>YOUR SEARCH BASE</BDISearchBase1>
 <BDIConnectionUsername>[email protected]</BDIConnectionUsername>
 <BDIConnectionPassword>PASSWORD</BDIConnectionPassword>
 <BDIEnableTLS>0</BDIEnableTLS>
 </Directory>
</config>
For example, let´s assume the following:
- Domain controller IP address is 10.1.1.2 .
- Your presence domain is test.local .
- Your search base will be test.local using the top level of the domain.
- Your username with which you will be doing your searches is called walt . Usually you can either identify walt as test.local\walt or [email protected] . It is always best, in these sort of scenarios, to use the UPN convention so we will be configuring a [email protected] .
- The password is the Active Directory password for the account walt .
- I have disabled TLS in my case. There are issues with the Jabber for Mac client when using other security methods.
<?xml version="1.0" encoding="UTF-8"?>
<config version="1.0">
 <Directory>
 <DirectoryServerType>BDI</DirectoryServerType>
 <BDILDAPServerType>AD</BDILDAPServerType>
 <BDIPrimaryServerName>10.1.1.2</BDIPrimaryServerName>
 <BDIPresenceDomain>test.local</BDIPresenceDomain>
 <BDIServerPort1>3268</BDIServerPort1>
 <BDISearchBase1>DC=test,DC=local</BDISearchBase1>
 <BDIConnectionUsername>[email protected]</BDIConnectionUsername>
 <BDIConnectionPassword>walt01!</BDIConnectionPassword>
 <BDIEnableTLS>0</BDIEnableTLS>
 </Directory>
</config>
One you have configured the jabber-config.xml file, you will now need to upload it to you TFTP server. Once uploaded, you will need to restart the Cisco TFTP service. Again, my TFTP server is on my CUCM publisher, so:
- I go to Cisco Unified OS Administration on my Publisher server, TFTP File Management and I upload jabber-config.xml to / directory
- I then go to Cisco Unified Serviceability on my Publisher server, I locate the Cisco TFTP service and I restart the service
Once this is done, you can figure up your Jabber for Mac client. As a test, on your Mac (using Terminal) go to:
/Users/username/Library/Application Support/Cisco/Unified Communications/Jabber/Config
In here you will see several files, but what we want to see is jabber-config.xml . As soon as you start the Jabber for Mac client and log in, the jabber-config.xml file will download from your TFTP server and get saved here. When you see it appear, just type in your terminal window more jabber-config.xml and make sure that the output is the same as the xml file you created.
From there, try doing directory search. If you have previously added contacts and they still lack attribute information, you will need to remove them (sometimes it will not refresh properly) and add them again from the directory.
I will be updating this guide and ammending anything that is incorrect, but this is meant to be a quick checklist and steps to get this, at least in the most very basic version, up and running for Jabber for Mac.

Hello,
Thanks for this post! It works, I can do lookup and also I can add found contact to contact list and get information about contact from LDAP.
One more question: - I can't get all information about contact. I don't get e.c mobile phone number and more others attributes. I have tried to expand your file as follows:
<?xml version="1.0" encoding="UTF-8"?>
<config version="1.0">
<Directory>
<DirectoryServerType>BDI</DirectoryServerType>
<BDILDAPServerType>AD</BDILDAPServerType>
<BDIPrimaryServerName>IP of AD</BDIPrimaryServerName>
<BDIPresenceDomain>Presence Domain</BDIPresenceDomain>
<BDIServerPort1>3268</BDIServerPort1>
<BDISearchBase1> Search Base</BDISearchBase1>
<BDIConnectionUsername>User</BDIConnectionUsername>
<BDIConnectionPassword>Password</BDIConnectionPassword>
<BDIEnableTLS>0</BDIEnableTLS>
 <BDISipUri>msRTCSIP-PrimaryUserAddress</BDISipUri>
 <BDIPhotoSource>thumbnailPhoto</BDIPhotoSource>
 <BDIBusinessPhone>telephoneNumber</BDIBusinessPhone>
 <BDIMobilePhone>mobile</BDIMobilePhone>
 <BDIHomePhone>homePhone</BDIHomePhone>
 <BDIOtherPhone>otherTelephone</BDIOtherPhone>
 <BDITitle>title</BDITitle>
 <BDICompanyName>company</BDICompanyName>
<BDILocation>co</BDILocation>
<BDIPostalCode>postalCode</BDIPostalCode>
 <BDICity>l</BDICity>
 <BDIState>st</BDIState>
 <BDIStreetAddress>streetAddress</BDIStreetAddress>
</Directory>
</config>
But it didn't help.
When I capture lookup via Wireshark, I can see that Jabbers sends search request with bunch of attributes, but from LDAP answer contains only 8 attributes. (see attached screenshots)

Cisco Jabber for Telepresence 4.6.3 Setting for "Webex Telepresence" Cloud Service

I am looking for the server setting that can be installed into the Cisco Jabber for Telepresence Client (MOVI) that will allow it to connect to the "Webex Telepresence" cloud service. I cannot find a download anywhere that has the infomation re-configured for the "Webex Telepresence" service.
Thanks for your help in advance
Tim
Well after a few hours of searching i have the Answer
The Client can be downloaded from: http://download.telepresence.webex.com/MCX/4.6.3.17194/WIN/JabberVideo_4.6.3GA.exe
This will come with the following setting pre-configured: Sign-in Setting > Internal Server: https://boot.telepresence.webex.com/tmsagent/api/rest/devices/movi/provisioning
If you have the JabberVideo Client installed and just want to change where it gets provisioned from VCS or Webex Telepresence then you should be able to use your current client and just change the internal server settings and clear the external setting.
Then you will need to use your Webex Telepresence Login ID and Password.
Hope this helps Someone.
Tim
Message was edited by: Timothy Shire

A1: Because it can use either (webex or CUPS), there are two deployment modes, all is on the documentation if you haven't gone thru it.
You type in what it's asking, nothing more. Choose one, and then use the CUPS hostname, DNS is basically mandatory, the PC needs name resolution for all you have configured (VM/CUCM/etc)
A2: No, it can be IM&P, full UC and phone mode. No, Full UC and phone mode use the PC for media termination, deskphone control uses the phone for media. Did you change the parameters during install for phone mode??? If not, it's not in phone mode.
A3: No, that can be many things, DNS, connectivity, credentials, etc
You mention DNS is not used, so, most likely that's the problem.
I'd strongly recommend you to review the whole deployment guide for Jabber for Windows.
HTH
java
if this helps, please rate
www.cisco.com/go/pdihelpdesk

Cisco Jabber for Windows in Extend and Connect mode and making outbound calls

Hi guys,
I've set up Cisco Jabber for Windows to use Extend and Connect to control a remote PBX endpoint. I've configured the required CTI-RD device, remote destinations, associated the users to the line and added the devices to end-user controlled device. The extend and connect part is working flawlessly without any issues. I'm able to receive inbound calls on the remote PBX endpoint and control the call (hold, resume, transfer etc.) using the Jabber call window that pops up.
However, I'm unable to make any outbound calls via the Jabber client when in extend and Connect mode. Reading the Extend and Connect guide, I need to configure Dial Via Office (DVO) Reverse. So when the user initiates a Dial-Via-Office reverse call, CUCM calls and connect to the Extend and Connect device (CTI-RD). CUCM then calls and connects to the number the user dialled and finally connects the two call legs.
After attempting to configure DVO-R for Jabber for Windows in Extend and Connect mode following the CUCM feature services guide, i'm unable to get any outbound calls working. From RTMT, i am receiving the following Termination Cause Code: (27) Destination out of order. What i also notice is that there is no calling number for that trace either. I would've thought that the calling party would've been the Enterprise Feature Access (EFA) number.
Has anyone got this working or can provide some guidance?
Thanks.

Hi guys,
I've set up Cisco Jabber for Windows to use Extend and Connect to control a remote PBX endpoint. I've configured the required CTI-RD device, remote destinations, associated the users to the line and added the devices to end-user controlled device. The extend and connect part is working flawlessly without any issues. I'm able to receive inbound calls on the remote PBX endpoint and control the call (hold, resume, transfer etc.) using the Jabber call window that pops up.
However, I'm unable to make any outbound calls via the Jabber client when in extend and Connect mode. Reading the Extend and Connect guide, I need to configure Dial Via Office (DVO) Reverse. So when the user initiates a Dial-Via-Office reverse call, CUCM calls and connect to the Extend and Connect device (CTI-RD). CUCM then calls and connects to the number the user dialled and finally connects the two call legs.
After attempting to configure DVO-R for Jabber for Windows in Extend and Connect mode following the CUCM feature services guide, i'm unable to get any outbound calls working. From RTMT, i am receiving the following Termination Cause Code: (27) Destination out of order. What i also notice is that there is no calling number for that trace either. I would've thought that the calling party would've been the Enterprise Feature Access (EFA) number.
Has anyone got this working or can provide some guidance?
Thanks.

Ask the Expert: Cisco TelePresence for the Enterprise

Welcome to the Cisco® Support Community Ask the Expert conversation. This is an opportunity to learn and ask questions about Cisco Telepresence® for the enterprise.
Cisco experts Jaret, Fernando, and Fred will be covering all Cisco TelePresence products. Topics include Cisco TelePresence endpoints and TelePresence infrastructure such as the Cisco TelePresence Video Communication Server (VCS), Cisco Expressway Series, Cisco Unified Communication Manager (CallManager), Cisco TelePresence Servers (MSE 8710, on Virtual Machine, etc.), MCU (MSE 8510, etc.), Cisco TelePresence Management Suite (TMS), and all other Cisco TelePresence related devices.
Jaret Osborne is an 8-year Cisco Advanced Services veteran. In his Advanced Services tour, Jaret has covered all aspects of Cisco Unified Communications and TelePresence products, including both enterprise and service provider verticals. Most recently Jaret has been working with global service providers supporting their Cisco TelePresence as a Service offerings while also incubating new cloud services at Cisco.
Fernando Rivas is a Cisco Advanced Services NCE, starting in the Cisco Technical Assistance Center (TAC), 2007, on the Collaboration Technology Team mastering the Cisco Unified Communication technologies and specialized in call control CUCM,VCS) and conferencing (MeetingPlace, Telepresence). In 2011, he joined Cisco Advanced Services as a member of the Cisco Collaboration team and participated in several Cisco TelePresence and video-related technologies deployments. Currently he is a member of the Video Cloud Technology Team, supporting video exchanges in several and architecting new private video cloud solutions for large enterprises. Fernando holds a routing and switching CCIE® certification (22975).
Fred Mollenkopf is a Cisco Advanced Services Network consulting engineer working at Cisco for the last 7 years. Fred has led some of the largest Cisco Unified Communication and Collaboration deployments done for Cisco customers and partners. Over 15 years’ experience in data networking with a specialization in Cisco Unified Communications in 2004. Currently he is a member of the SP Video Advanced Services Team, supporting SP video exchanges and the Cisco Telepresence solutions. Fred maintains an active CCIE® in Voice (17521).
Remember to use the rating system to let Jaret, Fernando, and Fred know if you have received an adequate response.
Because of the volume expected during this event, Jaret, Fred, and Fernando might not be able to answer every question. Remember that you can continue the conversation in the Collaboration, Voice and Video Community, under the sub-community TelePresence, shortly after the event. This event lasts through August 15, 2014. Visit this forum often to view responses to your questions and the questions of other Cisco Support Community members.

Tenaro,
Additionally here are the most common login issues. Unfortunately this includes items related to Presence implementation but I commented where we did not use these in our lab setup for CUCM Phone Capabilities only.
Login Issues
Problem:
Jabber Unable to Sign-in Through MRA
Solution
This can be caused by a number of things, a few of which are outlined below.
1. Collaboration Edge SRV record not created and/or port 8443 unreachable
For a jabber client to be able to login successfully using MRA, a specific collaboration edge SRV record must be created and accessible externally. When a jabber client is initially started it will make server DNS SRV queries:
_cisco-uds : this SRV record is used to determine if a CUCM server is available.
_cuplogin : this SRV record is used to determine if an IM&P server is available.
_collab-edge : this SRV record is used to determine if MRA is available.
If the jabber client is started and does not receive an SRV answer for _cisco-uds and _cuplogin, and does receive an answer for _collab-edge then it will use this answer to try to contact the Expressway-E listed in the SRV answer.
The _collab-edge SRV record should point to the FQDN of the Expressway-E using port 8443. If the _collab-edge SRV is not created, or is not externally available, or if it is available, but port 8443 is not reachable, then the jabber client will fail to login.
2. Unacceptable or No Available Certificate on VCS Expressway
After the jabber client has received an answer for _collab-edge, it will then contact the expressway using TLS over port 8443 to try to retrieve the certificate from the expressway to setup TLS for communication between the jabber client and the expressway.
If the Expressway does not have a valid signed certificate that contains either the FQDN or domain of the Expressway, then this will fail and the jabber client will fail to login.
If this is occurring, the you should use the CSR tool on the Expressway, which will automatically include the FQDN of the expressway as a Subject Alternative Name.
MRA requires secure communication between the Expressway-C and Expressway-E, and between the Expressway-E and external endpoints.
Expressway-C Server Certificate Requirements:
The Chat Node Aliases configured on the IM&P servers. This is required if you are doing XMPP federation. The Expressway-C should automatically include these in the CSR provided that an IM&P server has already been discovered on the Expressway-C.
The names in FQDN format of all Phone Security Profiles in CUCM configured for TLS and used on devices configured for MRA. This allows for secure communication between the CUCM and Expressway-C for the devices using those Phone Security Profiles.
Expressway-E Server Certificate Requirements:
All domains configured for Unified Communications. This includes the domain of the Expressway-E and C, e-mail address domain configured for Jabber, and any presence domains.
The Chat Node Aliases configured on the IM&P servers. This is required if you are doing XMPP federation.
The MRA Deployment guide describes this in greater detail on pages 17-18. (http://www.cisco.com/c/dam/en/us/td/docs/voice_ip_comm/expressway/config_guide/X8-1/Mobile-Remote-Ac...
Note: In our lab for testing Phone Capabilities only, we did not include the Chat Node Aliases in the certificate as we were not using IM&P.
3. No UDS Servers Found in Edge Config
After the Jabber client successfully establishes a secure connection with the Expressway-E, it will ask for its edge config. This edge config will contain the SRV records for _cuplogin and _cisco-uds. If these SRV records are not returned in the edge config, then the jabber client will not be able to proceed with trying to login.
To fix this, make sure that _cisco-uds and _cuplogin SRV records are created internally and resolvable by the Expressway-C
More information on the DNS SRV records can be found on page 10 of the MRA deployment guide for X8.1.1 (http://www.cisco.com/c/dam/en/us/td/docs/voice_ip_comm/expressway/config_guide/X8-1/Mobile-Remote-Access-via-Expressway-Deployment-Guide-X8-1-1.pdf)
Note: In our lab for testing Phone Capabilities only, we did not include the DNS SRV for _cuplogin.
4. The Expressway-C logs will indicate the following error: XCP_JABBERD Detail="Unable to connect to host '%IP%', port 7400:(111) Connection refused"
If Expressway-E NIC is incorrectly configured, this can cause the XCP server to not be updated. If the Expressway-E meets the following criteria, then you will likely have this issue:
Using a single NIC
Advanced Networking Option Key is installed
Use Dual Network Interfaces option is set to “Yes”
To correct this problem, change the “Use Dual Network Interfaces” option to “No”
The reason this is a problem is because the Expressway-E will be listening for the XCP session on the wrong network interface, which will cause the connection to fail/timeout. The Expressway-E listens on TCP port 7400 for the XCP session. You can verify this by using the netstat command from the VCS as root.
Note: We used a Dual Network Interface Expressway for testing but were not using XCP, so this was not applicable to us.
5. VCE-E Server hostname/domain name does not match what is configured in the _collab-edge SRV.
If the Expressway-E Server hostname/domain name does not match what was received in the _collab-edge SRV answer, the jabber client will not be able to communicate to the Expressway-E. The Jabber client uses the xmppEdgeServer/Address element in the get_edge_config response to establish the XMPP connection to the Expressway-E.
This is an example of what the xmppEdgeServer/Address would look like in the get_edge_config response from the Expressway-E to the Jabber client:
<xmppEdgeServer>
<server>
<address>ott-vcse1.vcx.cisco.com</address>
<tlsPort>5222</tlsPort>
</server>
</xmppEdgeServer>
To avoid this, make sure that the _collab-edge SRV record matches the Expressway-E hostname/domain name. Enhancement CSCuo83458 has been filed for this.
Note: This was one of our issues when we first setup. We adjusted our Expressway-E to insure the below:
System > Administration > System Name this was the FQDN
System > DNS > System Host Name was the host portion of the FQDN
System > DNS > Domain Name was the domain portion of the FQDN
System > Clustering > Cluster Name (FQDN for Provisioning) was the FQDN
6. Unable to log into certain IM&P servers. VCS logs say "No realm found for host cups-example.domain.com, check connect auth configuration"
From the Expressway-E, go to Configuration -> Unified Communications -> IM&P Servers. Open each server and click "Save" again. Not sure exactly why this happens.
Note: This was N/A to our test and can be ignored with Phone Capabilities only.
Thanks
Fred

Downloaded Cisco Connect for E1200 v2 disk image damaged. Now what? recent Mountain Lion upgrade

I had originally set up my E1200 Jan 2012 & had Cisco Connect setup. I didn't use it much but back in Oct after being away for 10 days I didn't have internet connection. Had to re-set both cable modem--then I at least had connection via ethernet, but still no wifi connection. Had to turn off for awhile to get it Router to properly reset & work. & then I think I had to do another reset maybe in Dec, can't remember exactly.
As I mention in another post, I have been having frequent intermittent not connected to internet messages for a long time. Usually if I just turn wifi off & then turn it back on it finds my network (although frequently I notice that it was on my guest network rather than main). I still don't know if it is cable modem, router or my ISP, altho they came out & checked & said signals ok, but modem could be going (Its old but about to move so don't want to buy new modem now).
I updated to Mountain Lion about 2-3 weeks ago.
After a Panic last night I was advised to make sure everything updated including router firmware.
When I opened Cisco Connect it said I had an unsupported Operating System. Trying to figure this all out, I finally found links to download Cisco Connect that are supposed to be compatible w Mountain Lion (at least the original link said that, but not where I went w the links so hoping it is right link for that). Anyway I downloaded it & was reading a bit & then clicket on the setup icon.
That said it was damaged & to eject it. I downloaded it via wifi just like I download other software. Maybe it is hyper sensitive so I need to take it over to plug directly into my cable modem? But then that will mess up the router, although I guess it will need to be reset any way.
So I think i need to get Cisco Connect updated so it works w Mountain Lion. Mountain Lion told me about 1 software that wasn't compatible but didn't pick up on Cisco Connect.
So don't know if I need to do a hard wired download, unlike the way I download other things, or what to get an undamaged copy. I then hope that it will see the old version, even though it isn't didn't work & hopefully pick up all my settings & all.
& then I guess I still need to check for a firmware update. & I understand that a firmware update should be done w a good connection (although the user manual just says good signal, web says hard wired ethernet. & because of the intermittent issues I plan to to it manually by 1st downloading & then installing from the download so there won't be a risk of interruption during install--if its even needed.
I'm running on a mid April 2010 13" MacBookPro
Any suggestions? This all is rather confusing.
Kathi

Well I was trying to update Cisco Connect so it would work w Mountain Lion but after 3 tries at the download I kept getting this same error message that it is downloaded. I even shut down & restarted before the last time w same result.
I should not have to spend hours of my time to get this to work. That is ridiculous.
Right before starting this process I checked for Apple updates & found a firmware update for my MacBookPro. I quickly downloaded & installed it, no problem. It took a very few minutes & then I backed it up & started working on this many hours ago.
I am an end user--not an IT professional. I just want things to work. I should not be expected to have to spend hours trying to figure out how to get stuff to work & still it doesn't. So I guess Linksys doesn't care that much about making things easy for Mac users.
I recently had the cable co come out & check the levels & all. they all checked out ok & they did change the fittings in several places on the coax connecters for good measure.
My cable modem is set up just across my living room from me & it is not a large living room. The router is right next to it, but it is not at a desk or place that is very comfortable to set up my Mac.
I sure hope that those security settings have been set up by default when I orginally set this up about a year ago. & I don't reall know how to change those settings without Cisco Connect, which I have been unable to get reinstalled since i keep getting those warnings about it being damaged.
I just want my computer devices to work. I don't want to have to spend hours troubleshooting them w poorly written instructions that don't really tell how to update firmware & Cisco Connect for tnose of us who have already had it set up before upgrading to Mountain Lion.
Having a link to download Cisco Connect that supposedly works w Mountain Lion but doesn't since it keeps giving a warning is not very helpful. There was nothing I saw in all my searches to tell what the results of even being able to upgrade Cisco Connect. Would it be able to figure existing settings? Didn't see anything that explained how that would work.
I don't appreciate my time being stolen by making it so hard to just get this updated! I"m giving up on this. I may try taking it back to Best Buy to see if they can tell if the router itself was also defective but I think I will likely go get an airport Express so I have a reliable router that is easy to use!
Kathi

BOOLEAN expression for fluctuating signal

I want to create a BOOLEAN expression to return a TRUE for a signal that is increasing and FALSE for a signal that is decreasing. Any idea how this can be done?

Assuming you use a while loop, you just check the iteration terminal. Presumably you can calculate how many points are in your 20 periods worth of data.
You can also use a FOR loop and feed it an autoindexed array of 20 periods. Attached is a quick example (LAbVIEW 7.1).
LabVIEW Champion . Do more with less code and in less time .
Attachments:
ShowDirection.vi ‏36 KB

How should i do?when i use the sc2345 for analog signal acquired!

please help me！
I have to use the sc2345+NI6221 for analog signal acquired. but i don't have a analog input module such as SCC-AIXX.
So I want to pass the signal to the DAQ device. how should i do to connect the wire on the sc2345？
how can I use the sc2345 for a pass connector？
Thank you very much and look forward to your reply...
Solved!
Go to Solution.

What kind of signal do you want to acquire?
If it does not need any conditioning, then, you can connect the signal to 6221 with a terminal block such as SCB-68.
Best regards,
NISH AE Haiping.Fei

I am using the Order Analysis Toolkit and want to get more information about the compensation for "Reference Signal Processing", which is scarce in the manuals, the website and the examples installed with the toolkit.

I am using the Order Analysis Toolkit and want to get more information about the compensation for "Reference Signal Processing", which is scarce in the manuals, the website and the examples installed with the toolkit.
In particular, I am analyzing the example "Even Angle Reference Signal Processing (Digital Tacho, DAQmx).vi", whose documentation I am reproducing in the following:
DESCRIPTIONS:
This VI demonstrates how to extract even angle reference signals and remove the slow-roll errors. It uses DAQmx VIs to acquire sound or vibration signals and a digital tachometer signal. This VI includes a two-step process: acquire data at low rotational speed to extract even angle reference; use the even angle reference to remove the errors in the vibration signal acquired at normal operation.
INSTRUCTIONS:
1. Run the VI.
2. On the DAQ Configurations tab, specify the sample rate, samples per channel, device and channel configurations, and tachometer channel information.
NOTE: You need to use DSA PXI-447x/PXI-446x and PXI TIO device in a PXI chassis to run this example. The DSA device must be in slot 2 of the PXI chassis.
3. Switch to Extract Even Angle Reference tab. Specify the number of samples to acquire and the # of revs in reference which determines the number of samples in even angle reference. Click Start to take a one-shot data acquisition of the vibration and tachometer signals. After the acquisition, you can see the extracted even angle references in Even Angle Reference.
4. Switch to the Remove Slow-roll Errors tab. Click Start to acquire data continuously and view the compensate results. Click Stop in this tab to stop the acquisition.
ORDER ANALYSIS VIs USED IN THIS EXAMPLE:
1. SVL Scale Voltage to EU.vi
2. OAT Digital Tacho Process.vi
3. OAT Get Even Angle Reference.vi
4. OAT Convert to Even Angle Signal.vi
5. OAT Compensate Even Angle Signal.vi
My question is: How is the synchronization produced at the time of the compensation ? How is it possible to eliminate the errors in a synchronized fashion with respect to the surface of the shaft bearing in mind that I am acquired data at a low rotation speed in order to get the "even angle reference" and then I use it to remove the errors in the vibration signal acquired at normal operation. In this application both operations are made in different acquisitions, therefore the reference of the correction signal is lost. Is it simply compensated without synchronizing ?
Our application is based on FPGA and we need to clarity those aspects before implementing the procedure.
Solved!
Go to Solution.

Hi CracKatoA.
Take a look at the link bellow:
http://forums.ni.com/ni/board/message?board.id=170&message.id=255126&requireLogin=False
Regards,
Filipe Silva

Cisco Jabber for Windows Voicemail issue

At this I'm in processing of implementation Cisco Jabber UC solution for big Company.
I use CUCM 9.1.2, Cisco IM and Presence 9.1.2, CUC 9.1.2, Cisco Jabber for Windows 9.6.1.
I have issue in Cisco Jabber with VoiceMail Integration - when I leave voice message for any user,
than this message is arrived only him Cisco IP Phone, but not in him Cisco Jabber.
From Cisco Jabber Connectivity status in help menu I see that VoiceMail service is successfully connected
and I see VoiceMail button in Cisco Jabber.
How can I resolve this issue?

Have you configured the UC Service profile on CUCM with both Voicemail server and mailbox servers?

Call/video not working between Cisco jabber for Windows and VCS control C40s

Hello,
I've been struggling with no luck how to make a call using Cisco Jabber for Windows 9.6.0 registered to CM 8.6.2 with intercluster ICT to another CM 8.6.2 where we have a VCS Control 7.0.2 via GK H225, and all C40s are registered as H.323.
The VCS has interworking between H323 and SIP, however not sure if there is any problem with that. Assuming it is ok, not sure either if I'm facing any interoperability issue because in my remote site I have C40 (H323 registered at VCS and SIP listening mode) and cisco jabber for windows which is SIP based.
If is not possible, would I be able to change my C40 from H323 to SIP at VCS, or have both H323/SIP registered at VCS? If so, will I need to change as well instead of GK I'll have to establish a SIP Trunk between the CM and VCS?
Another thing I do not believe either I would be able to have one VCS connected with two clusters, right?
I'm just trying to find a solution in case my current topology is not compatible, but feel free if you have any better idea to make it work.
Anyway here is what is happening:
When I make a call from my cisco jabber windows to C40 using alias number. The call is being redirected just fine to the C40 and it rings, however when someoene or the auto answer picks it up, the call dropped right away.
However, if I enabled the MTP in my CSF device, the call gets longer before dropping. I was even able to see my jabber " start video" turns green, before was grayed out all the time and the call dropped faster. I hear a fast busy tone.
I'm able to provide SDI traces, logs, diagnostic sip/h323 calls from VCS in order to know for sure if this is an incompatible issue or something I can workaround.
Let me know if someone of you are interested in read these logs or could point me on the right direction.
Thanks!

Ok,
I have looked at both logs. I have to mentinon though that you didnt
provide the log that shows the h323 setup between cucm and the VCS. This
is most likely because the call originated from a different cucm than
the ones you provided the logs from.
The call would have orginated from the first cucm in the cucm group of
this trunk: Name=RL_TRUNK_VIDEO
The cucm ip will be : 10.252.53.10.
This is the VCS log that confirms where the h323 request originated
from:
pr 10 22:50:29 TWELDVCS01 tvcs: UTCTime="2014-04-11 01:50:29,187"
Module="network.h323" Level="DEBUG": Src-ip="10.252.53.10" Src-
port="54000"
Received RAS PDU:
Having said that here is my analysis of the logs that you sent..
Jabber sent an INVITE to CUCM and advertised all the codecs (audio and
video it can support)..
Observer that Jabber says it doesnt support G729 anexB
21:55:16.576 |//SIP/SIPTcp/wait_SdlReadRsp: Incoming SIP TCP message
from 10.223.20.73 on port 54677 index 90661 with 2220 bytes:
[862370,NET]
INVITE sip:[email protected];user=phone SIP/2.0
Via: SIP/2.0/TCP 10.223.20.73:54677;branch=z9hG4bK000029d3
From: "4122107" <sip:[email protected]>;tag=00059a3c78000011000070b0
-00000e65
To: <sip:[email protected]>
Call-ID: [email protected]
Max-Forwards: 70
Date: Fri, 11 Apr 2014 01:55:16 GMT
CSeq: 101 INVITE
User-Agent: Cisco-CSF/9.4.1
m=audio 19252 RTP/AVP 0 8 18 105 104 101
c=IN IP4 10.223.20.73
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:105 G7221/16000
a=fmtp:105 bitrate=24000
a=rtpmap:104 G7221/16000
a=fmtp:104 bitrate=32000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=sendrecv
m=video 28878 RTP/AVP 97
c=IN IP4 10.223.20.73
++++Now lets observer the capabilites exchange during h245 negotiation
between cucm and VCS++++
Here CUCM advertises its caps to VCS (afterreceiving caps from VCS)
Note that G729A, G729AB, G729 is all advertised..
Apr 10 22:50:31 TWELDVCS01 tvcs: UTCTime="2014-04-11 01:50:31,017"
Module="network.h323" Level="DEBUG": Src-ip="10.252.53.10" Src-
port="45660"
Received H.245 PDU:
value MultimediaSystemControlMessage
::= request : terminalCapabilitySet
capabilityTableEntryNumber 2,
 capability receiveAudioCapability :
g729wAnnexB : 6
 capabilityTableEntryNumber 3,
 capability receiveAudioCapability : g729AnnexAwAnnexB : 6
 capabilityTableEntryNumber 4,
 capability
receiveAudioCapability : g729 : 6
capabilityTableEntryNumber 5,
 capability receiveAudioCapability :
g729AnnexA : 6
++++++
After doing MSD (master slave determination, we move to the OLC phas e..
Here we see that the far end..c40 wants to use G729AB for media++++
Apr 10 22:50:31 TWELDVCS01 tvcs: UTCTime="2014-04-11 01:50:31,783"
Module="network.h323" Level="DEBUG": Src-ip="10.224.114.11" Src-
port="11163"
Received H.245 PDU:
value MultimediaSystemControlMessage
::= request : openLogicalChannel :
 forwardLogicalChannelNumber 1,
forwardLogicalChannelParameters
 dataType audioData :
g729AnnexAwAnnexB : 20,
 multiplexParameters
h2250LogicalChannelParameters :
+++Next VCS sends G729AB as the codec to use to CUCM+++
Apr 10 22:50:31 TWELDVCS01 tvcs: UTCTime="2014-04-11 01:50:31,784"
Module="network.h323" Level="DEBUG": Dst-ip="10.252.53.10" Dst-
port="45660"
Sending H.245 PDU:
value MultimediaSystemControlMessage
::= request : openLogicalChannel :
 forwardLogicalChannelNumber 1,
forwardLogicalChannelParameters
 dataType audioData :
g729AnnexAwAnnexB : 20,
 multiplexParameters
h2250LogicalChannelParameters :
++++The next thing we get is an OLC reject from CUCM and this is where
th call drops++
Apr 10 22:50:31 TWELDVCS01 tvcs: UTCTime="2014-04-11 01:50:31,790"
Module="network.h323" Level="DEBUG": Src-ip="10.252.53.10" Src-
port="45660"
Received H.245 PDU:
value MultimediaSystemControlMessage
::= response : openLogicalChannelReject :
forwardLogicalChannelNumber 1,
 cause dataTypeNotSupported : NULL
Apr 10 22:50:31 TWELDVCS01 tvcs: UTCTime="2014-04-11 01:50:31,790"
Module="network.h323" Level="INFO": Dst-ip="10.224.114.11" Dst-
port="11163"
Detail="Sending H.245 OpenLogicalChannelRejResponse
+++We then receive a call release from cucm with cause code of 47:
resource unavailable++++
Apr 10 22:50:32 TWELDVCS01 tvcs: UTCTime="2014-04-11 01:50:32,365"
Module="network.h323" Level="DEBUG": Src-ip="10.252.53.10" Src-
port="50913"
Received H.225 PDU:
Q931
 Message Type: Release
Complete
 Call reference flag: Message sent from originating side
Call reference value: 0x7b
 Info Element : Cause
 Location: Usr
 Cause Value: Resource unavailable
 Info Element : User User
 Length = 22
Suggestions:
Change the region setting between the ICT trunk to VCS and Jabber to use
G711 and test again.

Cisco Jabber for Blackberry

Hi Jabber Experts,
I was trying with Cisco Jabber IM for Blackberry(9700) , i had manually loaded the application on the device and chose the CUPS(On-Premise) mode installation. I was able succesfully login with my CUPC login credentials. I could see all my contacts, presence info and chat. But Iam not able to place a call. I tried to search one of the contact profile and see no information there, though my desktop(cupc) application all the contact profiles populated with required informations(work phone, cell,email)
We have a LDAP integration on CUPS.
Please advice how can i place a call from my Cisco Jabber Application?
Regards
John

Hi Binu,
Cisco Jabber for Blackberry probably has similar causes for failure to register as the Android version. You may wish to check out the "Cisco Jabber Registration Fails" section at the following URL for ideas:
http://www.cisco.com/en/US/docs/voice_ip_comm/cumc/cisco_jabber/Android/86/Cisco_Jabber_Android_8.6.x_Admin_Guide.html#wp170272
Kind regards,
Craig

Cisco jabber for mac over fortigate vpn problem

Hi all,
We have installed the cisco jabber for mac successfully.Jabber client able to register locally successfully.
Calling and other features working properly. Jabber IM also working fine.
But when we try over vpn its shows error."services are missing".All the ports are open on fortigate firewall.

If you have detailed diagnostics from the Jabber Mac client, this would provide some more context to why it's displaying those errors. (Help > Detailed Logging enabled) (Help > Report a problem)
Another thing to check for would be DNS resolution of the configured servers when the Mac is VPN'd in. If Jabber cannot resolve the DNS name, it will not know where to connect to.
If the diagnostics are pointing towards a connectivity problem, but the firewall says it's wide open, then taking a packet capture on the Mac where Jabber is trying to register may illustrate what's going on at the network layer.

Cisco Jabber for Windows 10.5 search Contact with two lastnames

Hey Guys,
I have a little problem with the contact search feature of the cisco jabber for windows (Version 10.5.37889)
In my environment I have some Users (secretary phones and users too) which have two lastnames.
Exampleuser1: Firstname: Thomas Lastname: Meier Cisco ....
If a user is searching for Exampleuser1 by lastname (Cisco) the correct contact won't be listed
If a user is searching for Exampleuser1 by firstname (Thomas) the correct contact will be listed
If a user is searching for Exampleuser1 by lastname (Meier) the correct contact will be listed
is there a workaround or something else for resolving my problem?
thanks for reading my question :)

Workaround: "Cisco Meier, Thomas"
Have you looked at enabling wild card searches in jabber-config.xml?

Alternative of Cisco PGW2200 for SS7 Signaling termination

Similar Messages

Maybe you are looking for