cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
281
Views
0
Helpful
1
Replies

CMS Cluster - remote SIP teardown with reason 21 (forbidden)

zentata04
Level 1
Level 1

Hi,

I made a CMS cluster, CMS-A and CMS-B (CMS-C is only DB). The video endpoints registered to CUCM.

If I call from a video endpoint(9206) to a virtual meeting room (address: 2005) and the call is replaced from CMS-A to CMS B, the call is ringing but it can not connect to the room. In the syslog looks like:

CMS - A
Info call 17: incoming SIP call from "sip:9206@[MY SIP DOMAIN]" to local URI "sip:2005@[IP-CMS-A]:5060" / "sip:2005@[IP-CMS-A]"
Info replace query for conference a3653261-b59b-4cbd-b4f0-8eb6b41255ad: response from '[IP-CMS-A]' (priority: 1, load level: 0, conference is running: 0)
Info replace query for conference a3653261-b59b-4cbd-b4f0-8eb6b41255ad: response from '[[FQDN-CMS-A]]' (priority: 0, load level: 0, conference is running: 1)
Info replace query for conference a3653261-b59b-4cbd-b4f0-8eb6b41255ad: using remote server '[[FQDN-CMS-A]]' (priority: 0, load level: 0, conference is running: 1)
Info replacing call '2802b680-1ee1c66f-371fd-bfc16ac@[IP-CUCM-SUB]' to conference a3653261-b59b-4cbd-b4f0-8eb6b41255ad on server '[[FQDN-CMS-A]]'
Info call 17: ending; local teardown, timed out - not connected after 0:10
Info call 17: destroying API call leg 00000000-0000-0000-0000-000000000000

CMS - B
Info API call leg 8937636a-b77e-4c8e-99a4-955f982b7c80 in call 0021076f-e7ab-4fe6-8520-be83e302ac91 (API call 9542d15f-4102-4bdf-a4b9-435ed17b4879)
Info replacing call '2802b680-1ee1c66f-371fd-bfc16ac@[IP-CUCM-SUB]' from server '[IP-CMS-A]' into conference a3653261-b59b-4cbd-b4f0-8eb6b41255ad
Info call 282: outgoing SIP call to "9206@[MY SIP DOMAIN]" from space "[space name]"
Info call 282: configured - API call leg 8937636a-b77e-4c8e-99a4-955f982b7c80 with SIP call ID "83e96718-aebf-4c95-97ad-e452d8f2d04f"
Info call 282: ending; remote SIP teardown with reason 21 (forbidden) - not connected after 0:00
Info call 282: destroying API call leg 8937636a-b77e-4c8e-99a4-955f982b7c80

 

What could be the problem? I could not find discussion with problem: remote SIP teardown with reason 21 (forbidden).

 

Thanks

1 Reply 1

zentata04
Level 1
Level 1

I found the solution:

I need to set two parameters in CUCM.

1. "Accept Replaces Header" in sip trunk security profile

2. Need configure "Rerouting Calling Search Space" on the SIP trunk