Buy or Renew
Buy or Renew
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
4986
Views
20
Helpful
39
Replies

Conductor XC2.2 and TMS 14.3 Automatic Connect

Go to solution
Paul Woelfel
Level 4
Level 4

‎08-07-2013 06:12 AM - last edited on ‎03-25-2019 09:09 PM by Community Manager

Hi,

I also saw a topic about the current beta versions Conductor XC2.2 and TMS 14.3, so I'll post my question here.

I'm using conductor with VCS, CUCM, MCU 4505 and TS. I'm able to create AdHoc conferences via CUCM and VCS and scheduled calls via TMS.

If I create a conference with automatic connect and the conductor in the call I can see that the MCU or TS tries to reach a participant, but not with the correct URI. It should use my email address (findme ID) to call me, but instead it uses some strange URI: 009a8bb3-ac2c-4bc1-8b02-4e4b52c171e2@1.1.1.1:5073

1.1.1.1 is the IP of the conductor. About the part before @ I do not know where it comes from, but it looks like an internal ID.

This are the logs from the MCU for an test conference with one participant to be connected automatically:


13:38:05          API          admin          /HTTP/TCP/1.1.1.1:38141          Info          Konferenzen: "Videokonferenz 101" erstellt

13307          13:38:05          API          admin          /HTTP/TCP/1.1.1.1:38141          Info          Konferenzen: Konferenz [Videokonferenz 101], numerische ID gesetzt auf "88800010"

13308          13:38:05          API          admin          /HTTP/TCP/1.1.1.1:38141          Info          Konferenzen: Konferenz [Videokonferenz 101], PIN gesetzt auf "114"

13309          13:38:05          API          admin          /HTTP/TCP/1.1.1.1:38141          Info          Konferenzen: Konferenz [Videokonferenz 101], Gast-PIN gesetzt auf "114"

13310          13:38:05          API          admin          /HTTP/TCP/1.1.1.1:38141          Info          Konferenzen: Konferenz [Videokonferenz 101], Sichtbarkeit "öffentlich"

13311          13:38:05          API          admin          /HTTP/TCP/1.1.1.1:38141          Info          Conferences: conference [Videokonferenz 101] content mode set to "Transcoded"

13312          13:38:05          API          admin          /HTTP/TCP/1.1.1.1:38141          Info          Konferenzen: Konferenz [Videokonferenz 101] Stummschaltung bei Teilnahme [Audio=deaktiviert]

13313          13:38:05          API          admin          /HTTP/TCP/1.1.1.1:38141          Info          Konferenzen: Konferenz [Videokonferenz 101] Stummschaltung bei Teilnahme [Video=deaktiviert]

13314          13:38:05          API          admin          /HTTP/TCP/1.1.1.1:38141          Info          Konferenzen: Konferenz [Videokonferenz 101], Layoutsteuerung über FECC/DTMF "Use FECC and fallback to DTMF"

13315          13:38:05          API          admin          /HTTP/TCP/1.1.1.1:38141          Info          Konferenzen: Konferenz [Videokonferenz 101], Maximale Dauer gesetzt auf "permanent"

13316          13:38:05          API          admin          /HTTP/TCP/1.1.1.1:38141          Info          Konferenzen: Konferenz [Videokonferenz 101], Ende gesetzt auf "kein Enddatum"

13317          13:38:05          API          admin          /HTTP/TCP/1.1.1.1:38141          Info          Conferences: conference [Videokonferenz 101] auto delete timeout set to "600 seconds"

13318          13:38:06          API          admin          /HTTP/TCP/1.1.1.1:38141          Info          API-Endpunkt-Einstellungen: Endpunkt [e922d880ee1854c242ba94e69b113af :: 00e98127-6564-4136-b0d7-bcca3c5076a4@1.1.1.1:5073] via API zu Konferenz "Videokonferenz 101" hinzugefügt

13319          13:38:06          API          admin          /HTTP/TCP/1.1.1.1:38141          Info          API-Endpunkt-Einstellungen: Endpunkt [3805 :: 009a8bb3-ac2c-4bc1-8b02-4e4b52c171e2@1.1.1.1:5073] via API zu Konferenz "Videokonferenz 101" hinzugefügt

13320          13:38:36          API          admin          /HTTP/TCP/1.1.1.1:38149          Info          API-Endpunkt-Einstellungen: Endpunkt [3806 :: 77e51d22-2239-483a-9e6d-2c8baa1ee1ae@1.1.1.1:5073] via API zu Konferenz "Videokonferenz 101" hinzugefügt

Unfortunatetly the logs are in german, but I think you can see that there is some strange URI added.

If I create a conference without conductor the log shows the correct URI:

13386           14:07:14           API           admin           /HTTP/TCP/172.21.10.12:52001           Info           API-Endpunkt-Einstellungen: Endpunkt [Paul Woelfel :: paul.woelfel@nts.eu] via API zu Konferenz "1234 - Videokonferenz 8/7/2013 " hinzugefügt

1.1.1.1 is the conductor IP (of course not the real IP ;-))

Has anyone testing the latest versions also expirenced that issue?

Regards, Paul
Labels:
0 Helpful
39 Replies 39

Go to solution
rasimyigit
Level 1
Level 1
In response to Alok Jaiswal

‎09-13-2013 01:57 AM

Hi Alok,

we tried only the internal endpoints with the TMS Auto connect but without success

0 Helpful

Go to solution
Paul Woelfel
Level 4
Level 4
In response to rasimyigit

‎09-13-2013 02:24 AM

What does the Conductor and TMS logs state? Do you see a try on conductor ? Also do you see something on the MCU, does the MCU try to call out?

Regards, Paul
0 Helpful

Go to solution
Paul Woelfel
Level 4
Level 4
In response to rasimyigit

‎09-13-2013 03:57 AM

1.1.1.1 is the Conductor IP address, right?

Is the MCU configured with a sip proxy? It should not have a sip proxy configured and use direct calling. The id@conductor will be translated to an endpoint for conductor and conductor should then forward the call to the correct participant. Did you configure a VCS location on conductor?

Regards, Paul
0 Helpful

Go to solution
rasimyigit
Level 1
Level 1
In response to Paul Woelfel

‎09-13-2013 04:19 AM

The 1.1.1.1 os the Conductor IP !!

On The MCU's the H323 settings and SIP is diabled but in the SIP proxy settings,there is the VCS -C clustername included.  I configure also the VCS Location on the Conductor with the additional IP. And on the VCS-C Zone to the Conductor , i put the additional IP from the Conductor. The translation do not work correctly at the Auto connect

0 Helpful

Go to solution
Paul Woelfel
Level 4
Level 4
In response to rasimyigit

‎09-13-2013 04:29 AM

remove the SIP Proxy from the MCU config and it should work fine. The MCU will then call the conductor, which will forward the call to VCS.

Regards, Paul
0 Helpful

Go to solution
rasimyigit
Level 1
Level 1
In response to Paul Woelfel

‎09-13-2013 05:32 AM

Hi,

so also remove the sip proxy even though the sip is disabled on the MCU. Not it does not work, that is strange. No Movi , no Endpoint, no external dial out nothing wit auto connect

0 Helpful

Go to solution
Paulo Souza
VIP Alumni
VIP Alumni
In response to rasimyigit

‎09-13-2013 05:34 AM

Hi,

Conductor B2BUA deployment model is based upon SIP, so you cannot disable SIP on your MCU. You must to keep SIP turn on and make sure that MCU is not registered to any SIP registrar or H323 gatekeeper.

Regards

Paulo Souza

Was my response helpful? Please rate useful replies and remember to mark any solved questions as "answered".

Paulo Souza Was my response helpful? Please rate useful replies and remember to mark any solved questions as "answered".
0 Helpful

Go to solution
rasimyigit
Level 1
Level 1
In response to Paulo Souza

‎09-13-2013 05:43 AM

That are the sSIP settings on both MCU's:

SIP registrar usage Select Disabled.

SIP proxy address Leave blank.

Outgoing transport Select TLS.

Use local certificate for outgoing connections and registrations Check this box.

SIP registrar usage Select Disabled.

SIP proxy address Leave blank.

Outgoing transport Select TLS.

Use local certificate for outgoing connections and registrations Check this box.

0 Helpful

Go to solution
Paulo Souza
VIP Alumni
VIP Alumni
In response to rasimyigit

‎09-13-2013 05:50 AM

That is right.

Tell me something, when MCU tries to call "72efwe-23bf-43erg3-ber6-e8wef5g4c1@1.1.1.1:5073", are you able to see that call attempt reaching Conductor? What do you see in Conductor's logs?

Regards

Paulo Souza

Was my response helpful? Please rate useful replies and remember to mark any solved questions as "answered".

Paulo Souza Was my response helpful? Please rate useful replies and remember to mark any solved questions as "answered".
0 Helpful
Customers Also Viewed These Support Documents