[Spce-user] [EXTERNAL] Re: Number Alias not work in 13.2.1 and 13.3.1

[Marco Capetta]

Hi Cesar,

The "is device ID" flag could in fact change the routing of the call, but
this preference is mainly intended to be used in PBX environment (that
requires a PRO system with CloudPBX module).
Can you please describe more in details your problem?

Regarding the preference "e164_to_ruri" you are correct. From the doc:
"Enable preference Number Manipulations > e164_to_ruri for routing inbound
calls to SIP-PBX. This ensures that the Request-URI will comprise a SIP-URI
containing the dialed alias-number as user-part, instead of the user-part
of the registered AOR (which is normally a static value)."

Thank you
Marco



On Sat, Sep 20, 2025 at 10:41 PM Cesar Mora <cesarluis89 at gmail.com> wrote:

> I am also encountering a problem with Aliases on 13.2.1. Aliases don’t
> route correctly on inbound when set to “is device ID”. As for aliases on a
> trunk, it is usually routed correctly by enabling "e164_to_ruri"
>
> On Aug 23, 2025, at 7:45 AM, Danny Cappellari via Spce-user <
> spce-user at lists.sipwise.com> wrote:
>
> Good morning, I found a bug in the mr.13.2.1 and 13.3.1 versions. Number
> aliases set on the Subscribers account no longer work. All calls go out
> only with the Master Number. By rolling back to 13.1.1, the number aliases
> work correctly again.
> --
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> http://lists.sipwise.com/mailman/listinfo/spce-user_lists.sipwise.com
>
>
> --
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> http://lists.sipwise.com/mailman/listinfo/spce-user_lists.sipwise.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20250922/80339cb2/attachment.htm>