VSCc with Codian-MCU

Answered Question
Apr 13th, 2012

Hi there,

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:

SIPErrorRegistration lost - server error code 403

over and over again...

Any help would be great!

thanks

alexis

I have this problem too.
0 votes
Correct Answer by awinter2 about 1 year 12 months ago

Alexis,

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.

- Andreas

Correct Answer by Martin Koch about 2 years 2 days ago

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.

  • 1
  • 2
  • 3
  • 4
  • 5
Average Rating: 5 (4 ratings)
darren.goulden Fri, 04/13/2012 - 07:27

Hi Alexis,

On the VSC you have the SIP transport set to TCP, on the MCU it's set to UDP, maybe this is your issue?

Rgds

alexis.katsavras Fri, 04/13/2012 - 07:34

Hi Darren,

I change the setting to TCP but no change in the error messages on the MCU or the VCS...

alexis

Correct Answer
Martin Koch Fri, 04/13/2012 - 15:07

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.

alexis.katsavras Mon, 04/16/2012 - 02:03

Hi Martin,

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

Thanks

Alexis

haydnv@omegadig... Mon, 04/16/2012 - 12:00

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.

alexis.katsavras Thu, 04/19/2012 - 07:32

hi there,

I change the MCU to be H323. I now get the following error:

the serach log show the following

Any suggestions?

cheers

alexis

awinter2 Thu, 04/19/2012 - 07:49

Alexis,

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.

-Andreas

alexis.katsavras Thu, 04/19/2012 - 07:56

Hi Andreas,

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

Thanks

Alexis

awinter2 Thu, 04/19/2012 - 08:07

Hi,

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?

- Andreas

alexis.katsavras Thu, 04/19/2012 - 08:49

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

awinter2 Thu, 04/19/2012 - 09:05

Alexis,

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?

- Andreas

alexis.katsavras Fri, 04/20/2012 - 01:35

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"

thanks

Alexis

awinter2 Fri, 04/20/2012 - 01:45

Alexis,

what do you see in the 'Current status' section of the H323 gatekeeper settings page on your MCU now? Does it still say ?

- Andreas

alexis.katsavras Fri, 04/20/2012 - 01:50

Under the gatekeep tab there is no status info:

Under the H323 gatekeeper its still the same:

Alexis

sagsheth Thu, 04/19/2012 - 13:03

Alexis,

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.

-Sagar

awinter2 Fri, 04/20/2012 - 01:57

Alexis,

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) .

- Andreas

alexis.katsavras Fri, 04/20/2012 - 02:16

Only port A is connected to the network. I did as you suggested but unfortunately still the same result (Registered address )

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,

Alexis

papettit Fri, 04/20/2012 - 03:12

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. 

VR

Patrick

alexis.katsavras Fri, 04/20/2012 - 03:41

Hi Patrick,

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

SYSTEMWarningProduct 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:

25212:33:18.433 GATEKEEPERInfotearing down all registrations - deactivating gatekeeper
25312:33:18.434 GATEKEEPERInfosettings changed - deregistering all
25412:34:17.859 SYSTEMWarningProduct activation key required
25512:35:06.664 GATEKEEPERInfosettings changed - registering all
25612:35:06.665 H.323TraceNew registration request
25712:35:06.665 H.323TraceAllocated registraton handle 013b0000
25812:35:06.665 H.323Traceregistration request with 10.21.60.30
25912:35:06.716 H.323TraceMain thread received message
26012:35:06.716 H.323TraceQUEUE_RX: MSG_GATEKEEPER_INSIST
26112:35:06.717 H.323TraceMain thread waiting for message
26212:35:06.717 H.323TraceMain thread received message
26312:35:06.717 H.323TraceMain thread waiting for message
26412:35:06.717 H.323TraceMain thread received message
26512:35:06.718 H.323TraceQUEUE_RX: MSG_GATEKEEPER_INCOMING_INTERFACE_ASSOCIATION
26612:35:06.718 H.323TraceIncoming interface association: 0
26712:35:06.718 H.323TraceMain thread waiting for message
26812:35:06.718 H.323TraceMain thread received message
26912:35:06.718 H.323TraceQUEUE_RX: MSG_GATEKEEPER_INCOMING_INTERFACE_ASSOCIATION
27012:35:06.718 H.323TraceIncoming interface association: 1
27112:35:06.719 H.323TraceMain thread waiting for message
27212:35:06.719 H.323TraceMain thread received message
27312:35:06.719 H.323TraceQUEUE_RX: MSG_GATEKEEPER_INSIST
27412:35:06.719 H.323TraceMain thread waiting for message
27512:35:06.719 H.323TraceMain thread received message
27612:35:06.720 H.323TraceMain thread waiting for message
27712:35:06.720 H.323TraceMain thread received message
27812:35:06.720 H.323TraceQUEUE_RX: MSG_GATEKEEPER_INCOMING_INTERFACE_ASSOCIATION
27912:35:06.720 H.323TraceIncoming interface association: 0
28012:35:06.720 H.323TraceMain thread waiting for message
28112:35:06.721 H.323TraceMain thread received message
28212:35:06.721 H.323TraceQUEUE_RX: MSG_GATEKEEPER_INCOMING_INTERFACE_ASSOCIATION
28312:35:06.721 H.323TraceIncoming interface association: 1
28412:35:06.721 H.323TraceMain thread waiting for message
28512:35:06.721 H.323TraceMain thread received message
28612:35:06.722 H.323TraceMain thread waiting for message
28712:35:06.722 H.323TraceMain thread received message
28812:35:06.722 H.323TraceMessage for registration 13b0000
28912:35:06.722 H.323TraceQUEUE_RX: MSG_REGISTER_WITH_GATEKEEPER
29012:35:06.723 H.323TraceRegistering with 10.21.60.30
29112:35:06.723 H.323TraceMain thread waiting for message
29212:35:06.723 H.323TraceMain thread received message
29312:35:06.723 H.323TraceMessage for registration 13b0000
29412:35:06.724 H.323TraceTHREAD_STARTED: Registration rx thread
29512:35:06.736 H.323TraceSending RRQ message
29612:35:06.738 H.323TraceLogged Message 1
29712:35:06.738 H.323TraceMain thread waiting for message
29812:35:06.754 H.323TraceMain thread received message
29912:35:06.755 H.323TraceMessage for registration 13b0000
30012:35:06.755 H.323TraceQUEUE_RX: MSG_H225_RAS_PDU
30112:35:06.756 H.323TraceLogged Message 2
30212:35:06.756 H.323TraceGot RAS RRJ
30312:35:06.757 H.323TraceDestroying registration 13b0000
30412:35:06.757 H.323TraceMain thread has shut down reg socket
30512:35:06.757 H.323TraceRAS thread terminating
30612:35:06.758 H.323TraceMain thread waiting for message
30712:35:18.097 SYSTEMWarningProduct activation key required
30812:35:36.757 H.323TraceNew registration request
30912:35:36.757 H.323TraceAllocated registraton handle 013c0000
31012:35:36.757 H.323Traceregistration request with 10.21.60.30
31112:35:36.758 H.323TraceTHREAD_STARTED: Registration rx thread
31212:35:36.758 H.323TraceMain thread received message
31312:35:36.759 H.323TraceMessage for registration 13c0000
31412:35:36.759 H.323TraceQUEUE_RX: MSG_REGISTER_WITH_GATEKEEPER
31512:35:36.759 H.323TraceRegistering with 10.21.60.30
31612:35:36.759 H.323TraceMain thread waiting for message
31712:35:36.759 H.323TraceMain thread received message
31812:35:36.760 H.323TraceMessage for registration 13c0000
31912:35:36.763 H.323TraceSending RRQ message
32012:35:36.764 H.323TraceLogged Message 3
32112:35:36.764 H.323TraceMain thread waiting for message
32212:35:36.776 H.323TraceMain thread received message
32312:35:36.776 H.323TraceMessage for registration 13c0000
32412:35:36.776 H.323TraceQUEUE_RX: MSG_H225_RAS_PDU
32512:35:36.777 H.323TraceLogged Message 4
32612:35:36.778 H.323TraceGot RAS RRJ
32712:35:36.778 H.323TraceDestroying registration 13c0000
32812:35:36.778 H.323TraceMain thread has shut down reg socket
32912:35:36.779 H.323TraceRAS thread terminating
33012:35:36.780 H.323TraceMain thread waiting for message

Not much in the H323/SIP log tab

112:35:06.737
013B000010.21.60.31:222210.21.60.30:1719RASTXRRQ
212:35:06.756
013B000010.21.60.30:171910.21.60.31:2222RASRXRRJ
312:35:36.764
013C000010.21.60.31:222210.21.60.30:1719RASTXRRQ
412:35:36.777
013C000010.21.60.30:171910.21.60.31:2222RASRXRRJ
512:36:06.783
013D000010.21.60.31:222210.21.60.30:1719RASTXRRQ
612:36:06.804
013D000010.21.60.30:171910.21.60.31:2222RASRXRRJ
712:36:36.809
013E000010.21.60.31:222210.21.60.30:1719RASTXRRQ
812:36:36.826
013E000010.21.60.30:171910.21.60.31:2222RASRXRRJ
912:37:06.826
013F000010.21.60.31:222210.21.60.30:1719RASTXRRQ
1012:37:06.840
013F000010.21.60.30:171910.21.60.31:2222RASRXRRJ
1112:37:36.844
0140000010.21.60.31:222210.21.60.30:1719RASTXRRQ
1212:37:36.862
0140000010.21.60.30:171910.21.60.31:2222RASRXRRJ
1312:38:06.868
0141000010.21.60.31:222210.21.60.30:1719RASTXRRQ
1412:38:06.886
0141000010.21.60.30:171910.21.60.31:2222RASRXRRJ
1512:38:36.890
0142000010.21.60.31:222210.21.60.30:1719RASTXRRQ
1612:38:36.907
0142000010.21.60.30:171910.21.60.31:2222RASRXRRJ
1712:39:06.912
0143000010.21.60.31:222210.21.60.30:1719RASTXRRQ
1812:39:06.931
0143000010.21.60.30:171910.21.60.31:2222RASRXRRJ
1912:39:36.936
0144000010.21.60.31:222210.21.60.30:1719RASTXRRQ
2012:39:36.956
0144000010.21.60.30:171910.21.60.31:2222RASRXRRJ

Thanks

Alexis

awinter2 Fri, 04/20/2012 - 03:46

Alexis,

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?

- Andreas

alexis.katsavras Fri, 04/20/2012 - 03:55

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:39tvcs: 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:39tvcs: 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"

thanks

Alexis

Correct Answer
awinter2 Fri, 04/20/2012 - 04:02

Alexis,

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.

- Andreas

alexis.katsavras Fri, 04/20/2012 - 04:12

Thats it !!!! All up and working!

Added the MCU to the local VCS database and it register

Thanks again

Alexis

p.s Haydn also a big thank you for the offer to remote in and have a look

Actions

Login or Register to take actions

This Discussion

Posted April 13, 2012 at 7:13 AM
Stats:
Replies:24 Avg. Rating:5
Views:1819 Votes:0
Shares:0

Related Content

Discussions Leaderboard