BRIA CLOUD extension use case problems using SIP_CHAN stack

I have a FreePBX 12 system with BRIA CLOUD mobile user accounts and plan to use BRIA PC clients as well. At this moment it looks as they both are considered as “backup” devices for an IPphone as main device, but not to replace IPhones.

As long as a “main” device (IP phone) is configured and has been registered once (using the main extension number e.g. 45) then they can both be reached (forked call between both extensions 45 and 9945).

However when there is a “main” extension configured, but never registered, then the BRIA user can’t be called (status : unavailable), neither on 45 or on 9945, while on the other hand this moble user can make outgoing calls (as it is registered with a 99945 extension).

Strange remark: for extensions with both devices 45 and 99945 configured, and when the main device is deregistered or unplugged, the mobile device remains reachable…???.

I have 3 use cases of which only 1 is working as wanted:

  1. user with IPphone and BRIA mobile device : no problem as explained above

  2. user with BRIA PC client and BRIA mobile device : not possible as they both would need the same 999XX extension. See PJSIP remark below.

  3. user who only has a mobile device : he can make calls, but is not reachable

I tried using PJSIP in stead, which in theory should offer a solution for all above use cases because multiple devices can register with the same SIP account, but due to the fact that BULK extension input (CSV) does not work, and the fact that BRIA module is based on SIP_CHAN + AGI script for forking (using the 999 prefix method), this is not a valid way either.

Please advise howto make above 3 use cases working, but also howto setup mass deployement for them.

Please open a ticket at

Ok, I will do so. I thought first to put it on the forum to see if someone has maybe an alternative solution.