Thinking Workshop”. Cisco Small Business is excited to invite its
Silicon Valley customers to an exclusive interactive one-day session
customers and product Managers. If you are interested in this
workshop, please fill out the Registration
For more information, please check out our FAQ
Get the latest new and information the November issue of the Cisco Small Business Monthly Newsletter
I'd like to confirm a few settings.
1. Internet Calling
Do you want to confirm the above settings for my Jabber client? That's exactly how it's setup currently.
Are you saying I should be able to log into CUE gui at 10.1.10.1 using 123456 / 123456?
I would like for you to just confirm those settings.
I would like for you to run an additional debug when you are trying to register the Jabber client:
debug ccsip messages
Please post or attach that debug out here. This should also us to see the SIP registration and why the UC is not accepting it.
Thanks for providing that debug.
Comparing this to my lab debug, I do see the registration in both cases initially rejected. Then the 2nd registration in my lab works, but fails in your debug with the following error:
Aug 1 19:49:46.752: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
SIP/2.0 500 Internal Server Error
Via: SIP/2.0/TCP 10.1.1.40:56312;branch=z9hG4bK41b6d8ba
Date: Wed, 01 Aug 2012 19:49:46 GMT
CSeq: 106 REGISTER
Is there anymore configuration under the voice service voip than what was listed above? If I recall correctly, did we remove the bind statements for the MWI issue? If so, I think we need to add those back in for Jabber.
This is what I have currently -
voice service voip
ip address trusted list
ipv4 0.0.0.0 0.0.0.0
allow-connections h323 to h323
allow-connections h323 to sip
allow-connections sip to h323
allow-connections sip to sip
registrar server expires max 600 min 60
I removed the bind statements to get my MWI working again. Does Jabber require these bind statements? I believe CCA added the bind statements in when I added a Jabber client.
Yes, it does seem like Jabber requires those bind statements. Please add the following back to the configuration:
voice service voip
bind control source-interface Vlan100
bind media source-interface Vlan100
We might have to change the CUE MWI notification to unsolicited to resolve the MWI issue. Please see your other post regarding MWI for the unsolicted configuraiton.