It is interesting that this is not specifically documented anywhere, as an
unsupported feature. My suspicion is that because, it does work, some to most
of the time.
The typical symptom I've seen from shared mgcp fxs is a, "ghost ring". Pretty
sure it has to do with the notify event in the MGC
No unfortunately, just gotta play the cards dealt on this one.
Actually, I'm not interested in changing anything, I'm looking for
documentation that supports what these two Cisco employee have publicly
stated. I personally will only cite sources from official documentation,
and not from web forum
Sounds good.
Also, I must say, that I have not seen this Tomcat issue the folks in this
thread seem to be reporting as normal Tomcat behavior. I can't think of
the last time I had Tomcat hang, and I had to restart it. Not saying it
doesn't happen, just not in my world.
I have no concerns using
In IM&Presence under Presence->Domains, do you have multiple domains
listed? Do you have something other than default under Presence Advanced
configuration for setting domain names? Setting the voice services domain
is one of the few reasons you need to login internally first.
If you are using U
What’s the flexible Jabber ID? Also I have local users created on CUCM with no
LDAP integration.
For the domain portion it’s not removed if the first login is through MRA and
the login failed but as mentioned if I logged in thought inside network before
the login through MRA goes smooth and log
I think Brian has it FJID (Flexible Jabber ID) is not supported over MRA.
Sent from my iPhone
On Dec 18, 2017, at 4:02 PM, Ahmed Abd EL-Rahman
mailto:ahmed.rah...@bmbgroup.com>> wrote:
No Ryan, I have no WebEx service.
Best Regards
Ahmed Abd EL-Rahman
Senior Network Engineer
From: R
No Ryan, I have no WebEx service.
Best Regards
Ahmed Abd EL-Rahman
Senior Network Engineer
From: Ryan Huff [mailto:ryanh...@outlook.com]
Sent: Monday, December 18, 2017 11:48 PM
To: Ahmed Abd EL-Rahman
Cc: Brian Meade ; cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] Jabber IM service
Are you using flexible Jabber ID?
One thing to make sure is that first time MRA login gets rid of the domain
portion in the username on the username/password form after entering
username@domain in the service discovery window.
On Mon, Dec 18, 2017 at 3:43 PM, Ahmed Abd EL-Rahman <
ahmed.rah...@bm
Is your domain provisioned with the WebEx connect service?
On Dec 18, 2017, at 3:43 PM, Ahmed Abd EL-Rahman
mailto:ahmed.rah...@bmbgroup.com>> wrote:
Hi Brian,
Will try what you suggested, but other than this issue I have another symptom,
the user must use Jabber for first time from inside the
Hi Brian,
Will try what you suggested, but other than this issue I have another symptom,
the user must use Jabber for first time from inside the network then afterwards
he can use it from outside but if he tries the first time from outside the
network it won’t register as all, even the login st
Try removing "inspect sip" from the global policy. You don't want that in
there with Expressway. Not sure if XMPP traffic hits that as well or not.
You can also try refreshing the IM&P Servers on the Expressway-C Unified
Communications configuration.
Enabling diagnostic logging on the Expresswa
Hi Brian,
Currently I’m opening all IP traffic to Expressway public IP on our Cisco ASA FW
Regarding the inspection configured here it is :
policy-map global_policy
class inspection_default
inspect dns maximum-length 512
inspect ftp
inspect h323 h225
inspect h323 ras
inspect rsh
inspe
Looks like possible XMPP/TCP 5222 connection issues from the logs. It just
keeps reconnecting over and over again but the port is open on the
Expressway and through the firewall.
What model firewall are you using? You may need to disable some XMPP
inspection/application filtering.
On Mon, Dec
Hello,
Does anyone have any insight into why UCCE 11.6 does not support using the
8845/8865 for Whisper or Silent Monitor even though the other 88XX models
are supported?
Thanks,
James
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck
Not taking this personally at all. ☺
Tomcat was running for approximately 25 days as we had just upgraded from 11.5
SU2 to SU3 for O365 support and had rebooted all of the UCM pub and subs as
well as the IMP pub and sub. I am hoping this is not indicative of what may
become a routine to res
We have 10.5.x running with the same issue as well. frequently the tomcat
hang on the publisher.
Finding is there's excessive AXL request from poorly programmed application
which sort of DoS the server.
By right they should reuse AXL connection, instead the software keep on
establishing around 5 c
16 matches
Mail list logo