04-11-2017 12:08 PM - edited 03-18-2019 12:59 PM
Hi all,
I need to configure a direkt h.323 call to an Lifsize Room.
With that guide I was able to call IPs with Jabber or MX Devices:
But I need to call somethink like this, otherwise the user need to type the RoomID and Password:
<IP Address>##<RoomID>**<Password> like 123.123.123.123##123456**1234
Paul
Solved! Go to Solution.
04-12-2017 04:55 PM
You shouldn't transform it on the Expressway, as you found out, that won't work.
The Polycom/Lifesize devices should be able to accept the conference@ipaddress format (this H.323 Annex O format has been around since July 2003), so if your Expressway just passes that across to the other infrastructure, it should be able to accept it and connect the call at the other manufacturer's end.
Wayne
--
Please remember to rate responses and to mark your question as answered if appropriate.
Please remember to mark helpful responses and to set your question as answered if appropriate.
04-12-2017 08:34 PM
Exactly what kind of device is the 'Lifesize Room' are you dialing to: mfr, model and software version?
From the dialing string it appears you're dialing an IP address of a device with a conference number with a password. If it is a Lifesize MCU this dialing document might help: https://www.lifesize.com/~/media/Documents/Product%20Documentation/Bridge/Guides%20and%20Reference/Dialing%20Patterns%20for%20LifeSize%20MCUs.ashx
It shows a Cisco MXP H.323 dialing format of <conference id>**<pw>@<mcu ip> along with other endpoint formats.
04-11-2017 01:13 PM
That address format is used by Polycom and Lifesize endpoints, which isn't compatible with Cisco products. You'll need to use URI dialing, for example: alias@ip_address. For the conference PIN, this will need to be entered by the user manually once connected as it's not possible to input this into the dial string.
04-12-2017 12:46 AM
Hi [@patrick.sparkman] ,
thanks for your fast reply.
With the cisco guide I already use URI dialing which will be transformed by Expressway-E to a h323 call to an IP.
But if it is not possible to input the parameter it is not possible...
I transformed strings like that: 123.123.123.123/101013@ip to 123.123.123.123##101013 but as expected expressway was not able to handle it (416 Unsupported URI Scheme).
04-12-2017 04:55 PM
You shouldn't transform it on the Expressway, as you found out, that won't work.
The Polycom/Lifesize devices should be able to accept the conference@ipaddress format (this H.323 Annex O format has been around since July 2003), so if your Expressway just passes that across to the other infrastructure, it should be able to accept it and connect the call at the other manufacturer's end.
Wayne
--
Please remember to rate responses and to mark your question as answered if appropriate.
Please remember to mark helpful responses and to set your question as answered if appropriate.
04-12-2017 08:34 PM
Exactly what kind of device is the 'Lifesize Room' are you dialing to: mfr, model and software version?
From the dialing string it appears you're dialing an IP address of a device with a conference number with a password. If it is a Lifesize MCU this dialing document might help: https://www.lifesize.com/~/media/Documents/Product%20Documentation/Bridge/Guides%20and%20Reference/Dialing%20Patterns%20for%20LifeSize%20MCUs.ashx
It shows a Cisco MXP H.323 dialing format of <conference id>**<pw>@<mcu ip> along with other endpoint formats.
04-13-2017 12:44 AM
Thanks for your answers.
Now I use <conference id>/<mcu ip>@ip and transfor it to <conference id>@<mcu ip>.
And it works fine. Thanks a lot
I do not know how I should configure a SIP Route Pattern for IPs on UCM.
*.*.*.* does not work.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide