Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Community Member

Calls from MCU API are treated as unauthenticated?

Hi all,

I have a problem that I can not make a call using MCU API through VCS-C and VCS-E.

Calls from MCU API are treated as unauthenticated on VCS-E, even thghough MCU is treated as authenticated.

When I make a call to "71.14.2.158(Global test site)", using "Add participant" button on MCU, it succeeds.

But when I make a call to the same destination using MCU API "participant.add" from same MCU, it fails.

In the seach history of VCS-C, I see the status of the failed call is "Invalid permission - Insufficient privilege".

But ofcourse I can find the status of succeeded call call is "Found", both "H323 (ARQ)" and "H323 (Setup)".

I thought this was caused by VCS-E Call policy rules, so I changed the rule as follows.

Before)

Source:Unauthenticated User

Dest:(.*)

Action:Reject

After)

Source:Unauthenticated User

Dest:(.*)

Action:Allow

Then I can make a call using MCU API without problem.

Why are calls from MCU API treated as unauthenticated even though the MCU belongs to VCS-C's subzone where "Authentication policy" is set as "Treat as authenticated"?

MCU 4501

SW Ver.:4.3(2.32)

VCS-C

SW Ver.:X7.2.1

VCS-E

SW Ver.:X7.2.1

Best Regards,

Kotaro Hashimoto

Everyone's tags (4)
1 ACCEPTED SOLUTION

Accepted Solutions
Community Member

Re: Calls from MCU API are treated as unauthenticated?

Hi all,

I found the reason why calls from MCU API are treated as unauthenticated.

I designated H323 gateway address in API command as follows.

         

            gatewayAddress

           

              IP address of H323 gateway(=VCS-C)

           

         

This caused the issue.

When I dial ( using "participant.add" parameter )  from MCU which is registered with VCS-C, designating H323 gateway, this call is treated as unauthenticated on VCS.

But in the same way without H323 gateway, it is treated as authenticated on VCS.

Thus the same issue can happen also when I call from MCU WebGUI ( "Add participant") if I designate H323 gateway.

Why calls designating H323 gateway are treated as unauthenticated?

Best Regards,

Kotaro Hashimoto

1 REPLY
Community Member

Re: Calls from MCU API are treated as unauthenticated?

Hi all,

I found the reason why calls from MCU API are treated as unauthenticated.

I designated H323 gateway address in API command as follows.

         

            gatewayAddress

           

              IP address of H323 gateway(=VCS-C)

           

         

This caused the issue.

When I dial ( using "participant.add" parameter )  from MCU which is registered with VCS-C, designating H323 gateway, this call is treated as unauthenticated on VCS.

But in the same way without H323 gateway, it is treated as authenticated on VCS.

Thus the same issue can happen also when I call from MCU WebGUI ( "Add participant") if I designate H323 gateway.

Why calls designating H323 gateway are treated as unauthenticated?

Best Regards,

Kotaro Hashimoto

334
Views
0
Helpful
1
Replies
CreatePlease to create content