I have recently installed Yeti in our lab for the purpose of testing and checking if it fits our business purpose.
After setting up vendors and customers, I unable to find any straight forward way to allocate a range of DID numbers to an account.
For eg. Customer Account A has Phone number starting from 610 000 0001 to 610 0000 0100
How or where can we create a pool of DID or phone numbers
How can we assign all DID to the customer (or vendor) and establish a route plan to route incoming calls to the customer account A
How can we set up to allow only outbound caller id of the customer account A to be within the DID number range?
How can we generate report/list of number of phone number allocated to Customer Account A for the purpose of billing using other external billing systems
So far, Yeti seems to be a good product and well done is building a class 4 switch.
Contractor A should have Vendor* flag enabled.(In yeti terms customer is call originator but vendor is termination side, so vendor should be enabled to send calls from external DID provider to your customer).
How or where can we create a pool of DID or phone numbers.
How can we assign all DID to the customer (or vendor) and establish a route plan to route incoming calls to the customer account A
Just create dialpeer for customer’s numbers and assing routing plan includes these dialpeers to customer auth recors used for incoming calls from your DID provider
How can we set up to allow only outbound caller id of the customer account A to be within the DID number range?
Create numberlist and use it as src number list at customer auth record.
Yes, the inbound call is working as per your instructions by creating a dialpeer.
Is there a way to make it work if we enable allow termination on the gateway and enable registered aor without having to add dialpeer? More like one to one mapping between DID range to a SIP Gateway?
For Eg:
Customer A DID numbers
+12123456700 —> SIP Registered gw: 1.2.3.4 username +12123456700
+12123456701 —> SIP Registered gw: 1.2.3.4 username +12123456700
+12123456702 —> SIP Registered gw: 1.2.3.4 username +12123456700
Customer B DID numbers
+12123456703 —> SIP Registered gw_ip: 6.7.8.9 username +12123456705
+12123456704 —> SIP Registered gw_ip: 6.7.8.9 username +12123456705
Customer A +12123456701 calling Customer B +12123456704 or vice versa without a dialpeer since they both are registered to the same node.
why not to add 3 dialpeers pointed to same GW:
+12123456700 —> GW1
+12123456701 —> GW1
+12123456702 —> GW1
where GW1 is Registered gw: 1.2.3.4 username +12123456700" ?
Customer A +12123456701 calling Customer B +12123456704 or vice versa without a dialpeer since they both are registered to the same node.
YETI is not working in this way. Every call originated by remote gateway(any gw) will pass full routing procedure(customer auth lookup-> destinations lookup-> dialpeers lookup). But you can create separate routing group Internal routing that will includes dialpeers(that will point to customer’s gateways) for your customers numbers. Including this routing group to customer’s routing plan will allow you route calls “Internally”
Thanks Dmitry. Makes sense from C4 point of view. Will give it a try with the dp and rg
btw, I wanted to mention another issue that I have faced yesterday not sure if this the right topic place to discuss. I was getthing the error below and it was responding back with 500 Internal server error. I restarted server, flushed redis and restarted services for it to be back to normal. Is there any particular reason for this error?
sems[1176]: [1202/yeti:yeti.cpp:541] ERROR: error/unexpected reply from redis: 'Too many registrations
