1. Descriptions
In this article, we provide a workaround for this particular case.
In headquarter there is a P-Cloud pbx.
In branch there is a hardware pbx S100 or P550.
In P550 it is connected to a dedicated sip trunk or register a general sip trunk, we call it local trunk.
P550 interconnects with Cloud PBX by account/register trunk.
Customers have to configure local trunk's DOD numbers on Cloud pbx assotiated with Cloud extensions.
2. Goals
Make free calls between Cloud pbx and hardware pbx.
Cloud users could make outbound calls through hardware pbx's local trunk.
Cloud users could receive inbound calls from hardware pbx's local trunk.
3. Steps
3.1 Create an account trunk on Cloud PBX.
3.2 Register sip trunk on hardware pbx, e.g Yeastar S100 IPPBX, do not set caller id number and name.
3.3 Check register status in both systems.
3.4 Create outbound route on cloud pbx, set dialpattern to XXXX that equals extension length of appliance pbx.
3.5 Create outbound route in hardware pbx and set dial pattern with X., Do not miss the dot.
3.6 On Cloud pbx – SIP Settings - SIP headers – Outbound Parameters, select ‘From User Part’ to ‘Extension Caller ID’ in drop-down box.
After above settings, internal calls between cloud and hardware pbx should be working now, do not have to set up inbound routes in both system, if you only want to achieve call between cloud pbx and appliance pbx, you can only configure above settings.
Continue next steps will achieve external calls, including inbound calls to cloud pbx from hardware pbx's local trunk and outbound call from cloud pbx through hardware pbx's local trunk, considering sps113 is the sip trunk in appliance pbx for external calls and you want to configure DOD numbers on cloud pbx instead on appliance pbx for some particular case.
3.7 Create outbound route in appliance pbx for general outbound calls, change patterns and strip accordingly.
3.8 Create two inbound routes on cloud pbx, one for internal calls between cloud and appliance pbx, the other for inbound calls from appliance pbx's local trunk, change destinations accordingly.
3.9 Create there inbound routes on appliance pbx, one for internal calls between cloud and appliance pbx, one for inbound calls from cloud to outside through appliance pbx's local trunk, change DID numbers accordingly to own extension range, one for inbound call from local sip trunk to cloud pbx.
3.10 On appliance pbx, in the trunk settings which registers to cloud, select Transfer Parameters – From to 'The Originator Caller ID', this will forward original external caller id to cloud pbx by appliance pbx.
3.11 On pcloud sip trunk settings – sip headers – outbound parameters – from user part, select [Default] again.
3.12 IMPORTANT! Create each outbound route for each user on cloud pbx, configure each DOD number on outbound route – Outbound caller id, thus it will work as user’s DOD number and sent out.
3.13 Last thing, set up outbound caller id in cloud sip trunk settings, set outbound caller id range to same as extension range, this will make cloud pbx send user's number to appliance pbx when trying to dial appliance’s user, a slight issue is cannot send each extension name to appliance, but this could be fixed by company contact feature on appliance pbx, you can add cloud users to company contact and configure proper view permission, so the phone on appliance pbx will be able see the name.
0 Comments