[Phone.Systems provisioner] trunks provisioning

[dmitry-sinina]

During service provisioning to phone.systems we have to configure trunks on phone.systems side:

• Incoming trunk https://doc.telecom.center/reference/incoming-trunks.html
• Termination gateway https://doc.telecom.center/reference/gateways.html
• Termination route https://doc.telecom.center/reference/routes.html

On yeti side we have to create customer Gateway.

Service type configuration variables:

"yeti_gw": {
  "codec_group_id": 112
}

"ps_incoming_trunk": {
  "transport_protocol": "UDP",
  "codecs": ["g729", "G722", "PCMU", "OPUS", "telephone-event"],
  "destination_field": "RURI_USERPART"
}

"ps_trm_gw": {
  "host": sip.yeti-switch.org, 
  "port": 5060, -- optional
  "codecs": ["g729", "G722", "PCMU", "OPUS", "telephone-event"],
}

After creation of incoming trunk on pbx side, domain from response should be used as yeti gateway Host. During creation of gateway on pbx side, we have to generate random 20 symbols username/password and use it as incoming_auth_username/password in yeti gateway. PBX termination routes should be created with default values(linked to previously created gw)

Naming:

• Yeti gateway name should be generated as ps-<ID> where ID is service.id
• PBX gateway name should be generated as gw-<uuid> where uuid is service.uuid on yeti side
• PBX route name should be generated as gw-<uuid> where uuid is service.uuid on yeti side
• PBX incoming trunk name should be generated as gw-<uuid> where uuid is service.uuid on yeti side

in case when PBX objects with same name already present we have to patch them to update attributes with our values.