![]() |
All numbers must be in E.164 format (for example, +13629812002)
No phone number is stored in the directory for [username]
The E164 dialstring [E.164 number] was not converted. Reason = NO MATCH. Verify dialplan rules.
All numbers must be in E.164 format (for example +13629812002): Indicates that a phone number either in LDAP or provided by a Sametime user (either the phone number they have set in their Sametime Connect Location Profile or a number they typed in the Type a name or number field when they tried to call an external number) is not in E.164 format.
No phone number is stored in the directory for [username]: Indicates that the entry of the given user in the LDAP server does not have a telephone number. If the user's entry in the LDAP server does have a telephone number, verify that the value of the avaya.aes.sametime.ldap.telephone_number_attr property is correct for the environment by comparing it to the name of the telephone number attribute on the LDAP server.
The dial plan is correct but the converted external number is the same as the E.164 number. Identification: You will see the message FINE: Resolved switch name = [some switch name] in dmcc-trace.log.0. Resolution: if the customer is using Communication Manager's Extended Dial Plan so that internal extensions are the same length as their corresponding E.164 numbers, they must install the AE Services patch from the Sametime download page. This patch only applies to AE Services 4.2.
The dial plan is correct, but the E.164 number does not fit the dial plan.
The dial plan is incorrect. Identification: Examine dmcc-trace.log.0 on the AE Services Server Look for FINE: Resolved switch name = in dmcc-trace.log.0. Resolution: correct the dial plan.
AE Services is not getting a response (from Communication Manager) to the SnapshotDevice request that AE Services sends while trying convert the E.164 number to a dial string. The purpose of the SnapshotDevice request is to discover which switch owns the device, so we know where to route requests. Identification: Look for the message FINE: Resolved switch name = in dmcc-trace.log.0; the message will not include a switch name. (This could indicate that the problem is that the dial plan is incorrect, as well, particularly if the existing rules do not convert the E.164 number to an extension that the switch recognizes as an extension it owns.)
Investigate further. The primary issue is: what is causing DMCC not to receive a response to the SnapshotDevice request.