There's a mobile version of our website.
I have the following setup
VCSc (ver X5.2) connected to (SIP<->SIP) Codian MCU 4505
The zone on VCSc has the following setup
On the MCU the sip trunk has the following setup
when i dial the MCU on the VCS i get the following error
In the logs of the MCU i can see the call coming across. I also see the error:
|SIP||Error||Registration lost - server error code 403|
over and over again...
Any help would be great!
Is there a reason why you want to run the MCU with SIP only. Did you try with h323 only+interworking on the VCS?
What version do you run on the MCU? I would also look into upgrading to a later VCS version.
What is the encryption policy on the EX90? Do you force encryption?
Can you try to call from the EX90 with disabled encryption?
Btw, you should see that you get/install the encryption key for the MCU and use SIP-TLS.
All the video endpoints are configured with SIP so the reason for using SIP on the MCU is just to save on transcoding from H323 to SIP but i will try and use H323.
The MCU version is 4.1(1.59). I can’t really do anything about the versions running on the hardware. This kit is on loan from Cisco so we can “try out” the product before the decision is made to purchase.
Encryption is set to best effort. I switch it to off but get the same issue
If using a VCS control you get 100 traversal calls with the box so transcoding calls (MCU: H323 and Endpoints: SIP) is a great if you have limited Non-traversal licenses.
The only disadvantage is that when transcoding calls all signalling and media is routed through the VCS. So if you only have one central VCS and endpoints in different regions bandwidth across links can become a concern if running a lot of calls.
could you post the full search history? The screenshot you attached seems to be cut off at the bottom.
Have you checked that your MCU has available video ports? I believe that the MCU would return 480 if it doesn't have any available video ports.
I cut the bottom off as i didnt think it was needed below is the full search history
Sorry how do i check for the Video ports? This is my first installation of VCS and MCU
you can see the amount of available video ports from the status page on the MCU web interface.
Why do you have a neighbor zone towards the MCU? If you have H323 registered the MCU to the VCS, could you post a screenshot of the H323 settings on the MCU? Is the alias '701122' expected to match an existing conference on the MCU?
The video ports seem ok
I created a neighbour zone so that I will be able to control the amount of bandwidth that can be directed to the MCU... But i think this is a mistake i should have created a subzone to do this....
Here are the H323 settings on the MCU:
Here is the conference settings:
the serach rule
on the MCU i have the following confrence setup and would dial 701122
but also has this setting
if you look at the bottom of the H323 settings on the MCU, you will see that the MCU has not successfully registered to the VCS. Can you try disabling H323 gatekeeper usage on the MCU, click save and then enable it again and save again to see if this helps with getting the MCU registered on H323?
I also think that you might be mixing Multiway with regular conference registrations, what exactly are you trying to achieve? Do you want to get Multiway/Conference Factory working, or static conferences?
I have disable and re-enable the Gatekeeper on MCU (both under H323 and Gatekeeper tab) but still the same result. I also tried a reboot but no change. On the VSC it seem to be ok
Your right I do have the 2 confused I didn't know there was a difference between the 2. At the moment i would like to integrate the MCU with the VCS and have static conference.
I have also removed the "MCU zone"
what do you see in the 'Current status' section of the H323 gatekeeper settings page on your MCU now? Does it still say <not registered>?
It is not neccessary to create a separte zone for MCU. When you create a Neighbor zone to MCU.
MCU will not register to VCS, instead VCS will send LRQ's to MCU. Also you don't need SIP trunk.
You can directly register MCU to VCS using local zone using service prefix.
please try to do the following on the H323 settings page on the MCU:
- Untick 'Port B' under Ethernet port associations (I assume only Port A is connected to the network?)
- Set H323 gatekeeper usage to 'Disabled' and click 'Save'
- Set H323 gatekeeper usage to 'Enabled' and click 'Save'
- Wait for 15 seconds, go to another page on the MCU's web interface and then go back to the H323 settings page and see if the 'Current status' has updated to show that the MCU is now registered.
On a side note, you mention running X5.2 on your VCS, and although the MCU should happily register to the VCS on X5.2, I would recommend on a general note that you get your VCS upgraded to a newer software.
If this procedure doesn't help, I would recommend you raise a TAC case since further troubleshooting would require taking logs from the MCU and VCS (And we normally don't want those posted on this forum, for your best interest) .
Only port A is connected to the network. I did as you suggested but unfortunately still the same result (Registered address <not registered>)
Unfortunately an upgrade or raising a TAC case is not an option. This kit/hardware is on loan from Cisco. Management here wanted to try before they purchase the solution. I will contact the Cisco representative and see if there is anything he can do.
Andreas, Just to say thanks for all your time and effort on this. If i do manage to resolve this I will update.
All the best,
HI Alexis. I'm a bit curious about this one. Odd that it can't register to VCS so maybe something is conflicting somewhere?
1) If you can, disable the onboard Gatekeeper. MCU has its own gatekeeper function, but you have VCS, so this shouldn't be enabled. Disable this for us if possible.
2) Verify all Network>Services are enabled?
3) Anything in the event log worth noting?
4) If you can, disable H323 on MCU. Go to H323 Log on MCU and enable. Re-enable h323 log on MCU. MCU should send TX RRQ and hopefully get a response back from VCS. Either RX - RCF or RRJ. If RRJ, should provide a reason why RRJ'ed to MCU. You don't have to post the entire log, but the reason why for the RRJ, if it sends it, would be nice to know.
5) The search you posted says LRJ from MCU neighbor zone. This *could* be, because the onboard GK is enabled and VCS trying to send LRQ to and it of course it rejects it. Only a theory though.
If you pursue, would like to know the outcome.
I have disable the MCU gatekeeper as suggested.
Here is a snap shot of the MCU services
Only thing in the log at the moment is the following message
|SYSTEM||Warning||Product activation key required|
As I mention this kit/hardware is on loan from Cisco. I did mention this error message to the Cisco representative and he said this shouldn’t be a problem and that other customers have used the MCU without this causing any issues.
I increased the log details for H323 here is the output of the event logs:
|252||12:33:18.433||GATEKEEPER||Info||tearing down all registrations - deactivating gatekeeper|
|253||12:33:18.434||GATEKEEPER||Info||settings changed - deregistering all|
|254||12:34:17.859||SYSTEM||Warning||Product activation key required|
|255||12:35:06.664||GATEKEEPER||Info||settings changed - registering all|
|256||12:35:06.665||H.323||Trace||New registration request|
|257||12:35:06.665||H.323||Trace||Allocated registraton handle 013b0000|
|258||12:35:06.665||H.323||Trace||registration request with 10.21.60.30|
|259||12:35:06.716||H.323||Trace||Main thread received message|
|261||12:35:06.717||H.323||Trace||Main thread waiting for message|
|262||12:35:06.717||H.323||Trace||Main thread received message|
|263||12:35:06.717||H.323||Trace||Main thread waiting for message|
|264||12:35:06.717||H.323||Trace||Main thread received message|
|266||12:35:06.718||H.323||Trace||Incoming interface association: 0|
|267||12:35:06.718||H.323||Trace||Main thread waiting for message|
|268||12:35:06.718||H.323||Trace||Main thread received message|
|270||12:35:06.718||H.323||Trace||Incoming interface association: 1|
|271||12:35:06.719||H.323||Trace||Main thread waiting for message|
|272||12:35:06.719||H.323||Trace||Main thread received message|
|274||12:35:06.719||H.323||Trace||Main thread waiting for message|
|275||12:35:06.719||H.323||Trace||Main thread received message|
|276||12:35:06.720||H.323||Trace||Main thread waiting for message|
|277||12:35:06.720||H.323||Trace||Main thread received message|
|279||12:35:06.720||H.323||Trace||Incoming interface association: 0|
|280||12:35:06.720||H.323||Trace||Main thread waiting for message|
|281||12:35:06.721||H.323||Trace||Main thread received message|
|283||12:35:06.721||H.323||Trace||Incoming interface association: 1|
|284||12:35:06.721||H.323||Trace||Main thread waiting for message|
|285||12:35:06.721||H.323||Trace||Main thread received message|
|286||12:35:06.722||H.323||Trace||Main thread waiting for message|
|287||12:35:06.722||H.323||Trace||Main thread received message|
|288||12:35:06.722||H.323||Trace||Message for registration 13b0000|
|290||12:35:06.723||H.323||Trace||Registering with 10.21.60.30|
|291||12:35:06.723||H.323||Trace||Main thread waiting for message|
|292||12:35:06.723||H.323||Trace||Main thread received message|
|293||12:35:06.723||H.323||Trace||Message for registration 13b0000|
|294||12:35:06.724||H.323||Trace||THREAD_STARTED: Registration rx thread|
|295||12:35:06.736||H.323||Trace||Sending RRQ message|
|296||12:35:06.738||H.323||Trace||Logged Message 1|
|297||12:35:06.738||H.323||Trace||Main thread waiting for message|
|298||12:35:06.754||H.323||Trace||Main thread received message|
|299||12:35:06.755||H.323||Trace||Message for registration 13b0000|
|301||12:35:06.756||H.323||Trace||Logged Message 2|
|302||12:35:06.756||H.323||Trace||Got RAS RRJ|
|303||12:35:06.757||H.323||Trace||Destroying registration 13b0000|
|304||12:35:06.757||H.323||Trace||Main thread has shut down reg socket|
|305||12:35:06.757||H.323||Trace||RAS thread terminating|
|306||12:35:06.758||H.323||Trace||Main thread waiting for message|
|307||12:35:18.097||SYSTEM||Warning||Product activation key required|
|308||12:35:36.757||H.323||Trace||New registration request|
|309||12:35:36.757||H.323||Trace||Allocated registraton handle 013c0000|
|310||12:35:36.757||H.323||Trace||registration request with 10.21.60.30|
|311||12:35:36.758||H.323||Trace||THREAD_STARTED: Registration rx thread|
|312||12:35:36.758||H.323||Trace||Main thread received message|
|313||12:35:36.759||H.323||Trace||Message for registration 13c0000|
|315||12:35:36.759||H.323||Trace||Registering with 10.21.60.30|
|316||12:35:36.759||H.323||Trace||Main thread waiting for message|
|317||12:35:36.759||H.323||Trace||Main thread received message|
|318||12:35:36.760||H.323||Trace||Message for registration 13c0000|
|319||12:35:36.763||H.323||Trace||Sending RRQ message|
|320||12:35:36.764||H.323||Trace||Logged Message 3|
|321||12:35:36.764||H.323||Trace||Main thread waiting for message|
|322||12:35:36.776||H.323||Trace||Main thread received message|
|323||12:35:36.776||H.323||Trace||Message for registration 13c0000|
|325||12:35:36.777||H.323||Trace||Logged Message 4|
|326||12:35:36.778||H.323||Trace||Got RAS RRJ|
|327||12:35:36.778||H.323||Trace||Destroying registration 13c0000|
|328||12:35:36.778||H.323||Trace||Main thread has shut down reg socket|
|329||12:35:36.779||H.323||Trace||RAS thread terminating|
|330||12:35:36.780||H.323||Trace||Main thread waiting for message|
Not much in the H323/SIP log tab
it seems the VCS is rejecting the registration attempt. Can you check the VCS event log for corresponding entries and post screenshots, so that we can see why the VCS rejects the registrations?
Can you also go to your VCS and check what 'VCS Configuration > Protocols > H323 > Registration conflict mode' is set to? If set to 'Reject', can you try switching this to 'Overwrite' and try to register the MCU again?
It was set to "Reject" and i change it to "overwrite" but the issue still remains.
On the VCS the H323 settings are as follows:
and here is the log file on the VCS
|Apr 20 11:52:39||tvcs: Event="Registration Rejected" Reason="Received from unauthenticated source" Service="H323" Src-ip="10.21.60.31" Src-port="2222" Dst-alias-type="H323" Dst-alias="MCU4505" Dst-alias-type="E164" Dst-alias="701122" Protocol="UDP" Level="1" UTCTime="2012-04-20 10:52:39,691"|
|Apr 20 11:52:39||tvcs: Event="Registration Requested" Service="H323" Src-ip="10.21.60.31" Src-port="2222" Src-alias-type="H323" Src-alias="MCU4505" Src-alias-type="E164" Src-alias="701122" Protocol="UDP" Level="1" UTCTime="2012-04-20 10:52:39,691"|
so your default subzone (Or possibly another subzone which this MCU will be a member of) is set to 'Check credentials', yet you have not configured a password on the H323 settings page on the MCU.
To resolve this, either add credentials for the MCU in the VCS local database (Or LDAP if you use that for authentication) or configure your Default Subzone with an authentication setting of 'Treat as authenticated'. Please note that this will disable authentication for registrations on your VCS-C, allowing any user to register without credentials.
Thats it !!!! All up and working!
Added the MCU to the local VCS database and it register
p.s Haydn also a big thank you for the offer to remote in and have a look
Login to share your discussion activity with your friends on Facebook. You can control what you share and turn off sharing anytime.
Your Facebook friends can now see that you have started this discussion
Your Facebook friends can now see that you have commented on this discussion
Your Facebook friends can now see that you have read this discussion