CallTo URL Syntax
The CallTo URL syntax, introduced in NetMeeting 3, allows you to specify an extensible address for placing all forms of NetMeeting calls from your Web page. CallTo URLs are not case sensitive and can be up to 512 bytes long.
Examples of complete CallTo syntax are shown following in the context of each calling mode. Calls can be placed in these ways:
- Directly by host name or IP address.
- Through a directory server.
- Through a gateway.
- Through a gatekeeper.
The following table gives examples of these modes as they would be specified in a Web page using the CallTo method on the NetMeeting object.
| Mode | Description | Example |
|---|---|---|
| Direct call | Type in a host name. | Not available |
| Direct call | Type in an IP address. | callto:192.168.103.77+type=ip |
| Direct call using directory service | Enter account name, use default directory service and default port. See note following this table. | callto:someone@example.com+type=directory |
| Direct call using directory service | Enter account name, specify directory service and default port. See note following this table. | callto:msils/someone@example.com+type=directory |
| Direct call using directory service | Enter account name, specify directory service and specify port. See note following this table. | callto:msils:1002/someone@example.com+type=directory |
| Using a gateway | Type in phone number, default gateway name. | callto:12345+type=phone |
| Using a gateway | Type in phone number, specify gateway name. | callto:12345+gateway=fusion+type=phone |
| Using a gatekeeper | Type in account name. This is the value found in Tools/Options/General/Advanced Calling/Gatekeeper/Account name. | callto:someone@example.com |
| Using a gatekeeper | Enter phone number. This is the value found in Tools/Options/General/Advanced Calling/Gatekeeper/Phone number. | callto:12345+type=phone |
Note Account names are customizable. By convention, NetMeeting uses the e-mail name in the Tools/Options/General tab.
NetMeeting User Interface Syntax
End users that enter call addresses through the NetMeeting address bar or through the CallToAddress text box (shown in Including a CallTo URL in Your Web Page) can enter only the address components of the CallTo syntax. The "callto:" string at the beginning of a CallTo address and the parameter list at the end of the CallTo address will not be recognized by the parser. Web developers would take the string entered by the end user and append the appropriate parameter and value pairs before passing the address to the NetMeeting object CallTo method.
Optional Parameter and Value Pairs
The parameter and optional value pairs component allows you to include additional information about the call to be placed. The NetMeeting run time parses and handles parameters locally so they are not sent to the remote computer as part of a CallTo URL address. Parameters that are not recognized are ignored without error. If any parameter is specified more than once, the first value is used.
Use a "+" to separate multiple parameters. Currently recognized parameters are listed in the following table.
| Parameter | Syntax | Description |
|---|---|---|
| type | phone ip host directory |
Address is a phone number. Address is an IP address. Address is a computer name. Address is an ILS directory server. |
| gateway | string | Name of the gateway, for example, +gateway=myfavoritegateway. |
| secure | true false |
Whether the requested call should be secure. A secure call requires that members that join have a certificate and that the call communications are encrypted. The default value uses the underlying NetMeeting default value set through Tools\Options\Security or during installation. |
| password | string | T.120 password to use for the call, for example, +password=redcar. Not available in H.323 calls. Defaults to no password.
Note This password is not encrypted. |
| conference | string | The name of the conference to join. Default behavior when calling a NetMeeting node is to join any existing NetMeeting conference. Default behavior when calling a multipoint control unit (MCU is to query the user to choose the conference to join. |
| data | true false |
Whether a T.120 data conference needs to be set up with a call recipient and data conferencing features made available. The default value is TRUE. |
| av | true false |
Whether the call has audio/video capabilities. The default value is TRUE. |
| H323 | true false |
Whether to use H.323 call model for all calls including data conferencing calls. The default value is TRUE. |