-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.Windows 11 Support Center.
-
-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.Windows 11 Support Center.
-
- HP Community
- Poly Video Conferencing
- Collaboration & Conferencing Platforms
- Re: DMA dial rule issue

Create an account on the HP Community to personalize your profile and ask a question

03-17-2015 06:25 AM
Hello,
I have problem with one of the dial rules at DMA server. When I try to dial IP_address##e.164, for example 75.76.77.78##456789, everything works very well. When I try to dial e.164@IP_address, for example 456789@75.76.77.78, my DMA server passes through the rule responsible for this type of the connection and say "Domain is controlled by DMA: 75.76.77.78 (or any IP address used to call). Then goes to the next rules and at the end block this of connection. There are no any scripts in all rules
Regards
Solved! Go to Solution.
Accepted Solutions
03-17-2015 09:29 PM
Pablo,
The screenshots were very helpful. If you want the DMA to be able to route calls using the email address type dial strings, 1234@140.242.22.1, for example, you have to specify a local domain. Under Admin, call server, Domains, please add the DNS domain name or IP address whiich should be local to the DMA.
Domain names must be valid and full domains, but you can replace a single host label within a domain with the wildcard character to match multiple subdomains. For instance:, *.mycompany.com matches:
eng.mycompany.com
fin.mycompany.com
And eng.*.mycompany.com matches:
eng.sanjose.mycompany.com
eng.austin.mycompany.com
Subdomains are not local if the domain is listed without a wildcard character.
For example, if the domain mycompany.com is entered without any other mycompany domains, this would NOT match eng.mycompany.com.
The Resolve to external address dial rule action doesn’t match against domains that are considered local. If the list of domains is empty then all domains are considered local, this dial rule action won’t match any dial string and can’t be used.
In some circumstances (depending on network topology and configuration), dialing loops can develop if you don't restrict the RealPresence DMA system to specific domains.
S.
03-17-2015 07:10 AM
Hello PabloPL,
welcome to the Polycom Community.
It is always useful to include the currently used software version as issues experienced may already be addressed in a newer release.
This also allows yourself and others to check against current software release notes.
Is there any other Polycom infrastructure involved ?
Please ensure to provide some feedback if this reply has helped you so other users can profit from your experience.
Best Regards
Steffen Baier
Polycom Global Services
Notice: This community forum is not an official HP Poly support resource, thus responses from HP Poly employees, partners, and customers alike are best-effort in attempts to share learned knowledge. If you need immediate and/or official assistance please open a service ticket through your support channels.
Please also ensure you always check the General VoIP , Video Endpoint , UC Platform (Microsoft) , PSTN

03-17-2015 09:04 PM
Domain always work in string userid\domain and SIP work in string user@domain.com
It seems you are point worong string which causing a error, alias@ip is supported and resorved string for Cisco EP so the given string could not resolved or recognized by DMA.
I think you don't need to put rule IP##ID as this always suuport in case you do not have call server in your enviorment
BR
Yash
03-17-2015 09:29 PM
Pablo,
The screenshots were very helpful. If you want the DMA to be able to route calls using the email address type dial strings, 1234@140.242.22.1, for example, you have to specify a local domain. Under Admin, call server, Domains, please add the DNS domain name or IP address whiich should be local to the DMA.
Domain names must be valid and full domains, but you can replace a single host label within a domain with the wildcard character to match multiple subdomains. For instance:, *.mycompany.com matches:
eng.mycompany.com
fin.mycompany.com
And eng.*.mycompany.com matches:
eng.sanjose.mycompany.com
eng.austin.mycompany.com
Subdomains are not local if the domain is listed without a wildcard character.
For example, if the domain mycompany.com is entered without any other mycompany domains, this would NOT match eng.mycompany.com.
The Resolve to external address dial rule action doesn’t match against domains that are considered local. If the list of domains is empty then all domains are considered local, this dial rule action won’t match any dial string and can’t be used.
In some circumstances (depending on network topology and configuration), dialing loops can develop if you don't restrict the RealPresence DMA system to specific domains.
S.

Didn't find what you were looking for? Ask the community