cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1442
Views
0
Helpful
2
Replies

Cisco meeting server Conference bridge problem

m.soleimani
Level 1
Level 1

i installed CUCM 12.5 and Cisco meeting server 2.9.1 and i configured new Conference bridge with cms,

  • Call from EndpointA registered to CUCM (MRGL added) to another EndpointB 
  • On EndpointA, Click conference, dial EndpointC
  • EndpointB call disconnected  
  • EndpointA, Click Join For EndpointC
  • just EndpointA and EndpointC in Conference
  • Select the SIP Trunk that points to CMS is in Full Service state
  • CMS conference bridge is Registered with CUCM

cisco meeting server event logs:

 

127.0.0.1:58164: API user "admin" created new space 0268291a-de1d-49c1-82d4-7080d4ed22d3 (001229090007)
2020-06-1315:55:24.364Infocall create failed to find coSpace -- attempting to retrieve from database
2020-06-1315:55:24.369Infoconference 36bc1610-e24a-46e1-b0ab-be0cd17b61bf: locked due to lack of lock consensus
2020-06-1315:55:24.369Infoconference 36bc1610-e24a-46e1-b0ab-be0cd17b61bf: lock state has changed to locked
2020-06-1315:55:24.369InfoAPI "001229090007" Space GUID: 0268291a-de1d-49c1-82d4-7080d4ed22d3 <--> Call Correlator GUID: c10bd35c-6835-4129-820a-06416313443f <--> Internal GUID: 36bc1610-e24a-46e1-b0ab-be0cd17b61bf
2020-06-1315:55:24.369Infoconference 36bc1610-e24a-46e1-b0ab-be0cd17b61bf: lock state has changed to unlocked
2020-06-1315:55:24.369Info127.0.0.1:58166: API user "admin" created new call 8af2e4b2-c941-4d88-acf2-f737cf47992a
2020-06-1315:55:24.382Infocall 14: incoming SIP call from "sip:2001@172.17.54.33" to local URI "sip:001229090007@mci-lan-cms.mcci.local:5060" / "sip:001229090007@mci-lan-cms.mcci.local"
2020-06-1315:55:24.394Infocall 14: ending; local teardown, destination URI not matched - not connected after 0:00
2020-06-1315:55:24.394Infocall 14: destroying API call leg 00000000-0000-0000-0000-000000000000
2020-06-1315:55:24.467Info127.0.0.1:58170: API user "admin" deleted space 0268291a-de1d-49c1-82d4-7080d4ed22d3 (001229090007)
2 Replies 2

Patrick Pettit
Cisco Employee
Cisco Employee

Hi. Can you try adding the domain portion to the incoming dial plan rules to see if the calls connect?  If the dial plan is already there, can you make sure it targets cospaces?  Does this solve your issue? The server is saying the URI doesn't match and sometimes this is caused that the inbound dial plan rule isn't there to accept that domain.  Hope this helps?

 

VR

P2

Hi m.soleimani;

 

Did u find an answer to that problem, I have the same issue

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: