This use case will show you hoe to extend the capabilities of your legacy PBX with DECT phones using your tsandar FXS or BRI ports in the PBX one Vega 50 and a third party DECT IP base station
This is a very cost effectuve effective way to enable, for example, in a factory envronmentenvironment, or in an hospital to take advantage of DECT technology for wireless phones assigned to in move personnel (around the building or in a plant or large warehouse) and integrate them as plain extensions of a legacy PBX that has no DECT support and is far away from the location where the etensions extensions are needed
...
PBX<-- (BRI/FXS)-->VEGA50<--(SIP)-->BASE-STATION<--(DECT)-->Hand Sets
...
You will need to define on the Base Extension the identities to register in the vega ENP.
...
...
Just to illustrate what is needed in the Base extension here is an example of the configuration screen of a KWS6000 Server. The highlighted fields must be populated with the identities and credentials defined in the previous point.
...
Realm for ENP will be the Vega IP address (i.e. 192.168.200.20):
...
To keep consistency, keep ITSP Proxy pointing and enabled to Vega IP address:
...
Make sure Trunk Gateway on ENP is properly enabled as this:
...
Make sure ENP has enabled and configured the Trunk Gateway, so any (TEL:*) outbound call will always be sent to Trunk gateway ID 1 (defined in previous point)
...
You need to create a SIP Profile pointing from the Media Gateway side of the Vega to the ENP Proxy side (Vega IP is 192.168.200.20 in this example):
...
And
...
...
Also, disable SIP registrar on this profile:
...
Now, on the Dial Plan, you will need (TO PSTN: meaning to the PBX, and to SIP: menaing meaning to DECT Phone via DEC Server like this:
...
...
So, To_PBX_via_BRI should containg contain this rule, asuming assuming extensions are 101, 102, 103, …. Etc)
...