Page tree
Skip to end of metadata
Go to start of metadata

Our full list of extensions can be found here Updated list of H323 clients on the REMC#1 WAN 

All references to the Codian H323 Ip Gateway should use the IP Address: 208.68.24.64   

SIP:  

On SIP phones to dial a combination of IP address/domain name and E.164 number or extension, you will use the following syntax:    

<xxx>@<IP address/domain name of IP gateway>    

For example, to dial 101 on a IP gateway with an IP address of 208.68.24.64, you will dial: 101@208.68.24.64   

Tandberg endpoints (H.323 and SIP):  

Tandberg endpoints allow you to use the SIP format to dial a combination of IP address/domain name and E.164 number. You will use the following syntax:    

<xxx>@<IP address/domain name of IP gateway>    

For example, to dial 101 on a IP gateway with an IP address of 208.68.24.64, you will dial: 101@208.68.24.64   

Other H.323 (like Polycoms):   

How to dial a combination of E.164 number and IP address/domain name. On some endpoints, you can use the following  syntax:    

<IP address/domain name >##<number>    

For example, to dial 101 on a IP gateway with a domain name/IP of 208.68.24.64, you will dial:   

208.68.24.64##101   

 

To have an MCU dial direct ip plus extension dialing

  

Now it gets really fun!!  

 

 Calling Other MCU Conference Rooms
 Posted on August 21, 2009 by Janine Lim
 
 One of the conundrums of my videoconferencing life is how to make calls work with weird dialing. Since 60%
 of my calls are with schools across the country (off my network with various dialing policies of their own),
 I run into these a lot.  Please, please, please vendors, when will it work like a phone?!
 
 Yesterday I received additional training on TMS from SKC. We spent pretty much two hours trying to figure
 out how to make TMS in conjunction with my Tandberg MPS 800 dial conferences on other MCUs that are off my
 network. Since the results are obscure and undocumented, I thought it would be helpful to share. This was
 tested with TMS J12.2 and the MPS J4.5.
 
 Codian:
 
 Create a Participant Template. Enter the MCU IP as normal. In the DTMF box, enter the extension this way:
 ,,,numbers#
 Polycom MGC:
 
 Create a Participant Template. Enter the MCU IP as normal. In the DTMF box, enter the extension this way:
 
 ,,,,,number,,number,,number,,#
 
 (Apparently the numbers come too fast for the MGC. The commas slow it down.)
 Polycom RMX
 
 Create a Participant Template. Enter the MCU IP as normal. In the DTMF box, enter the extension this way:
 
 ,,,numbers#
 Tandberg MPS
 
 This needs the alias@IP format, however you can’t enter this in the participant template. If you put the alias@IP in the IP field, it strips out the @IP.
 
 So, instead, use the phone book to enter alias@IP.
 
 This solution works for a Tandberg endpoint behind a Border Controller as well.
 
 Your Turn: If you have additional tips for making MCUs dial conferences and extensions on other equipment outside your network, please comment!!
  • No labels