This shows you the differences between two versions of the page.
how_it_works [2014/07/01 19:32] admin created |
how_it_works [2014/07/02 15:59] admin |
||
---|---|---|---|
Line 21: | Line 21: | ||
- If the Service is disabled or not | - If the Service is disabled or not | ||
- IP address which should be assigned to customer (if enabled) | - IP address which should be assigned to customer (if enabled) | ||
- | - If any surcharges should apply \\ Note: If the VoIP switch in config file is enabled, "Called-Station-Id" attribute will be used as the destination phone number | + | - If any surcharges should apply \\ \\ Note: If the VoIP switch in config file is enabled, "Called-Station-Id" attribute will be used as the destination phone number \\ \\ |
- If there is no LoginID in the database that matches the User-Name, request will be rejected, with "Invalid User" message. | - If there is no LoginID in the database that matches the User-Name, request will be rejected, with "Invalid User" message. | ||
- If there is no Service assigned to this customer, request will be rejected, with "No Service Assigned" message. | - If there is no Service assigned to this customer, request will be rejected, with "No Service Assigned" message. | ||
- | - Password coming from Access Request is compared with password stored in the database. If they don't match, request will be rejected, with "Invalid xxxx Password" message, which xxxx shows the authentication method. If a client try to authenticate using an authentication protocol which is disabled in config file, request will be rejected, with "xxxx protocol is not allowed." message. \\ Note: If the VoIP switch in config file is enabled, Evolynx will skip the password check process described above. | + | - Password coming from Access Request is compared with password stored in the database. If they don't match, request will be rejected, with "Invalid xxxx Password" message, which xxxx shows the authentication method. If a client try to authenticate using an authentication protocol which is disabled in config file, request will be rejected, with "xxxx protocol is not allowed." message. \\ \\ Note: If the VoIP switch in config file is enabled, Evolynx will skip the password check process described above. \\ \\ |
- If the Customer is disabled (using Admin program / Customer Edit page / Service Info tab) then request will be rejected, with "Account Disabled" message. | - If the Customer is disabled (using Admin program / Customer Edit page / Service Info tab) then request will be rejected, with "Account Disabled" message. | ||
- If today's date is greater than the "End Date" (same location) then request will be rejected, with "Account Expired" message. | - If today's date is greater than the "End Date" (same location) then request will be rejected, with "Account Expired" message. | ||
Line 47: | Line 47: | ||
RADIUS Accounting packets are used to specify when a customer is connected to (Accounting-Start) and disconnected from (Accounting-Stop) the system. When RADIUS server receives the "Accounting-Start" packet, it stores some information in "Connected" table. When "Accounting-Stop" packet is received, RADIUS server will store the call information in "Usage" table and updates balance if required. Extra fees like "Connection Fee" and "Maintenance Fee" are logged in a table called "FeeLog". | RADIUS Accounting packets are used to specify when a customer is connected to (Accounting-Start) and disconnected from (Accounting-Stop) the system. When RADIUS server receives the "Accounting-Start" packet, it stores some information in "Connected" table. When "Accounting-Stop" packet is received, RADIUS server will store the call information in "Usage" table and updates balance if required. Extra fees like "Connection Fee" and "Maintenance Fee" are logged in a table called "FeeLog". | ||
**VoIP Note:** Accounting packets which contain attribute "h323-call-origin=answer" will be ignored. | **VoIP Note:** Accounting packets which contain attribute "h323-call-origin=answer" will be ignored. | ||
- |