11-21-2017 08:53 AM - edited 03-18-2019 01:38 PM
Dear Colleagues,
I need a guidance regarding remote registration / registration proxy on Expressway Edge to Core.
Currently the remote registration has been enabled by the followings:
- Traversal zone between Core and Edge
- Search rule on Edge
Protocol: SIP (All variants)
Source: Default zone
Mode: Any alias
Target: Traversal zone
By these settings, all external requests are forwarded to the Core, including inappropriate calls.
I was thinking that is there any way to filter/enable the registration requests (like in MRA) and the targeted calls only?
When I modified the search rule above to use .*@domain.com.* regex pattern, all external registrations were dropped.
Unfortunately the MRA scenario can be used for UCM registration only, as far as I know.
Thanks,
Laszlo
03-16-2018 02:18 AM
I have the same problem.
Did you find any solution?
03-17-2018 10:29 AM - edited 03-17-2018 10:30 AM
Hi,
You should try the suffix option with the appropriate domain, instead of regex pattern.
Regards,
Laszlo
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide