TMS & Conductor Error

[Justin Ferello]

All,

When scheduling a conference with Conductor on TMS, I try to add an external dial out participant via H323 and I get the following error:

"No route possible from conductor to 1.1.1.1"

If we change the dial out protocol to SIP, and use the same IP it works fine.

What and where is Conductor/TMS checking when trying to add this participant?

Thank you,

Justin Ferello
Technical Support Specialist
KBZ, a Cisco Authorized Distributor
http://www.kbz.com
e/v: justin.ferello@kbz.com       

[Martin Koch]

What is set as:

TMS > Admin Tools > Conf > General Settigns >

Route Phone Book Entries

Possibly: Yes

Does it change the behavior if you toggle it to no?

[Justin Ferello]

Martin,

I believe it is set to 'no' but will double check.

Thank you,

Justin Ferello
Technical Support Specialist
KBZ, a Cisco Authorized Distributor
http://www.kbz.com
e/v: justin.ferello@kbz.com

[Martin Koch]

btw, what do you try to dial, just 

1.1.1.1 (which I guess is your replacement for a real ip?)

does it behave different if you try to dial 

ip@1.1.1.1

and if it works for you you could have a search rule stripping the ip@

(or something like 1.1.1.1@domain.com and stripping the domain.com)

Not sure how well ip dialing works :-)

Do other h323 addresses work for you?

Which conductor, vcs and mcu versions do you run?

[Paulo Souza]

Hi Justin,

I may be missing some point here, but I think that TMS cannot schedule Conductor using H323, I think you can only choose SIP participants.

I am not sure. =/

Regards

Paulo Souza

Please rate replies and mark question as "answered" if applicable.

[Magnus Ohm]

Hi

H323 should work just fine.

In TMS, go into the Conductor, edit settings. At the bottom there is a set of permission checkboxes. Have you allowed your conductor to perform H323 calls inbound and outbound? If not, check the boxes and try again.

This is the only thing I can think of at the moment since an external dialout might as well fail even if the routing logic is passed. TMS should at least attempt to engage, but if you have the h323 allowed not checked then you will see this issue when trying to make a h323 call.

/Magnus

[Kjetil Ree · Accepted solution]

Hi Justin,

TMS deliberately disallows scheduling H.323 direct mode dial-outs from a Conductor, as we cannot guarantee that the Conductor is able to call them. There are no plans for changing the behavior, but you can as always file a feture request through your account manager.

Regards,

Kjetil

[Justin Ferello]

Kjetil,

Works fine in xc2.2 and tms 14.3, so maybe the answer should be it will be resolved in the next release? :)

Thanks,
Justin

Sent from Cisco Technical Support iPhone App

[Kjetil Ree · Accepted solution]

Justin Ferello wrote:
Works fine in xc2.2 and tms 14.3 [...]

Not as far as I can see:

There have been no deliberate changes in 14.3 when it comes to this.

-Kjetil

[Justin Ferello]

Kjetil,

Sorry, you were correct.  Apparently the IP I was testing with was in TMS as a managed system, thats why it was working.

Followup question, is there anyway to remove H323/IP from the external participant window and or make SIP the default choice instead of H323/IP?

Thank you,

Justin Ferello
Technical Support Specialist
KBZ, a Cisco Authorized Distributor
http://www.kbz.com
e/v: justin.ferello@kbz.com

[Kjetil Ree]

Justin Ferello wrote:
Followup question, is there anyway to remove H323/IP from the external participant window and or make SIP the default choice instead of H323/IP?

No and no, unfortunately.

-Kjetil