# MMC Controller - General

Here you can define the interface to the AMC Controller.

Table 1. AMC Controller General settings
Parameter | Explanation
ID | Controller ID in the communication server’s configuration
IP address | IP address of the Controller
MMC hostname |
MAC address |
SIP port | SIP port of the Controller (default is port 11000)
Enable keep alive | The communication server periodically updates the NAT table on its own firewall using notification messages to the proxy server. This means that the system remains in constant contact with the Controller.
External IP (for NAT) |
Transport protocol | Here you can select the transport protocol you want
Bandwidth control area | The assigned bandwidth area determines the codecs used on the WAN link to the Controller.
Relay RTP data via communication server | Indirect switching: During connection set-up to another IP endpoint, the voice data is forwarded via the communication server and not directly. This can help in solving NAT and firewall problems. Direct switching: During connection set-up to another IP endpoint, the voice data is forwarded directly. Note: Indirect switching requires two additional VoIP channels on the communication server.
Active line supervision (using session refresh) | Checks, with the session refresh method at regular intervals, whether connection to the remote station is still active. If the remote station does not react within the defined session refresh period, the connection is cut.
Number of mobile phone digits to match |
User name |
Password |
Redirect server PIN |

Table 2. MMCC Direct dialling number
Parameter | Explanation
DDI plan | The following dialling-in numbers must be created in a direct dialling plan. Here you can specify in which plan you opened them.
DDI | Dialling-in number for the MMC-Clients.
Callback | The MMC client uses this dialling-in number to trigger a callback on the Controller. Once the MMC user has answered the callback, he can dial the call number of the call party he wants using DTMF.
Call reverse | If the call reverse feature is activated, incoming calls are signalled to the MMC client, but not offered. Instead the Controller takes the call. As soon as the MMC user wants to answer the call, the MMC client sets up a connection to the Controller and the Controller connects the two calls.
SIM switch | In the Controller several SIM cards with different call numbers may be registered for one and the same MMC client. After a change of SIM card the MMC user can then inform the Controller which of the cards is now active.
IMS handover |

Table 3. MMC client dial in numbers
Parameter | Explanation
DDI |
Callback |
Call reverse |
SIM switch |
MTC number | Enter as MTC number (MTC = Mobile Terminated Call), for instance, the main call number of the communication system.

Table 4. Extended settings
Parameter | Explanation
Disable inband DTMF detection |
Registration timeout interval(s) |
Listening SIP port |
Listening TLS port |
RTP start port |
RTP end port |
HTTP server port |
Route for outgoing calls |
Ignore CLIP of the caller | The MTC number is sent to the mobile phone instead of the caller CLIP. This makes the mobile phone to display the caller information transmitted via the MMCC data channel to the mobile phone. Note: This setting is only necessary if “Special Arrangement” (CLIP not screening) is not available at your network provider's. This is the case in Australia, for instance.

See also....

"Firewall configuration"

Parent topic: Mitel Mobile Client
↑