Kolmisoft Wiki - User contributions [en]

Product Feedback Policy

2021-11-15T17:08:14Z

Mindaugas: /* How to submit product feedback */

Kolmisoft is continuously aiming to improve your experience by rolling out new features and product enhancements.
On this page, you will learn about the way we collect product feedback from our customers in order to make our product
better and help your business succeed.

 
= Our approach to product feedback =

At Kolmisoft, your feedback is highly valued as it provides us with direction on the features we should implement to
make your experience with the product the best it can be.

We use your feedback to identify the most important features, ideas, pain points, and opportunities so that you can
get more value from the product as efficiently as possible.

Please note that submitting your idea doesn’t guarantee any changes. While every piece of feedback will be read as our
Product Team reviews and triages the submissions, it doesn’t necessarily ensure action.

 
= How to submit product feedback =

If you have a product suggestion or an idea about how a feature could be improved, we’d love to hear more!

To get started:

# Log into your Kolmisoft support system account and click on the Make a Suggestion button.
# You’ll be taken to the submission form, where you’ll need to type in your feedback.
# The more information you can provide the better.
# Click Submit request when you are finished.

If your submission is not a product feature or suggestion, it may be removed.

If you need to report a problem or have a question about the product that requires a more immediate or direct response, go to https://support.kolmisoft.com and create a Trouble Ticket to connect with our Support staff.

=== Avoid duplicate ideas ===
When suggesting a new idea, please check to see if someone else has already suggested a similar feature.

You can vote on feature requests that you want by clicking “I Want this” beside the title of the post.
Remember to vote for the features you want to see - it will bring them to our attention faster.

 

= What does an actionable product feedback submission look like? =

After posting your feedback request, it can be voted on by other users. An ideal post succinctly describes what it is you want to do, what your pain point is, how you currently workaround the issue, and the impact this problem has on your work.

The clearer your post is and the more detail you have, the easier it will be for other users to understand the value of your request, making it more likely to be upvoted.

To make your request more impactful, here are tips for good feedback:

* '''Make your title concise and descriptive.''' This will help others find and upvote your feedback. Also, please write in English.
* '''Clearly outline what your ultimate goal is.''' What problem are you trying to solve with your suggestion? Our Product Team members are experts at troubleshooting and problem-solving. We may be able to help you find a feature or a solution that already exists!
* '''Provide additional context.''' Feel free to add a comment with any additional information or context around why this change would be helpful for you (for ex. how this suggestion will improve your daily workflow). You can even attach some screenshots to help us see what you’re experiencing!
* '''Highlight any workarounds.''' How are you currently getting around or solving this problem?

We don’t expect you to know all the answers, but feel free to get creative with what you think would work!

On the practical side, we also recommend including one suggestion per post and refraining from posting personal information.

 
= What happens after I submit the request? =

All new requests are set to the "Awaiting Feedback" status so that more people can vote, prioritize and give us information. This allows us to gauge demand, gather use cases and automatically establish impact & value using our Reports.

Periodically, our Product team sits down for a feedback meeting. The product team reviews the requests that have the highest number of votes first. The team discusses the highest priorities for our customers, team members, and prospects and how the requests align with our own strategy.

When reading through feedback, we’re primarily evaluating the level of impact that an update could have on all of our users. The larger the impacted audience, the more likely it that feedback would be prioritized.

As the team goes through they'll update the status of each request so that you immediately know the outcome.
If we decide to build a request the status will change to "Planned" or "Building".

Please note that there is no assured timeline or commitment that the request will in fact end up in our product.

 
= Viewing and prioritising your requests =

If you’ve voted for some requests, you’ll see your requests under My Priorities.

You can adjust the sliding bars to reflect your priorities.

Be sure to prioritize your requests – that way, we will know if a particular request is important to you.

 
= Status of the requests =

We will always provide an explanation as to the nature of the status update.

Our feedback portal always has the most up-to-date information about our products and what we're building next.

Note: The Request System always has the most up-to-date information about the status of requests and what we're building next.

If you reach out directly to our support or sales team they'll be able to look up the request for you, but they won't have any additional information or provide an estimate for when your item will be reviewed/developed.

 
=== Definition of Kolmisoft request statuses ===

* '''Not reviewed''' - Our Product team has not reviewed this suggestion yet. Usually, they will provide a status within 1-2 weeks.
* '''Awaiting feedback''' -This suggestion is under consideration by the team for future development. Our Product team is gathering feedback and additional use cases regarding this suggestion. Please add your comments and support this suggestion so we can prioritize it accordingly.
* '''Planned''' -This suggestion is on our roadmap. We will post an update when we start working on it.
* '''Building''' - This suggestion is part of the current product roadmap theme.
* '''Released''' - This suggestion has been delivered and is generally available. Should we realize a feature that a customer has been requesting, we will notify everyone who has submitted related feedback.
* '''Declined''' - This suggestion is not under consideration for the current or for the next roadmap theme. It might also refer to an existing feature.

 
= FAQs =

=== How long will it be before the product team reviews my idea? ===

Items will be reviewed by Kolmisoft’s product team every other week; we take the new requests and update the status where appropriate.

=== My request hasn’t been reviewed yet and I submitted it 6+ months ago. What can I do? ===

If we haven’t reviewed your request and it is a high priority for you:
* Make sure it’s at the top of your priority list.
* Make sure your request is clear. Why do you need this? What is stopping you from doing? Please add these details as a comment on your idea.
* Create a Trouble Ticket in the https://support.kolmisoft.com with the link to your original request

===My idea has some votes. Why hasn't it been implemented yet? ===

While we would love to be able to implement more of the suggestions we receive, with finite resources and a big product roadmap, we have to decide what we work on based on a combination of factors.

This includes not just votes, but also technical complexity, time to delivery, value, and the number of users it would benefit.

Unfortunately, this means sometimes we have to make tough decisions that we know disappoint some users. Rest assured that we regularly review the ideas and suggestions posted here as part of our routine product
planning and popular requests do play a large part in prioritization considerations.

=== Can you provide an ETA for my idea or suggestion? ===

We try to keep users updated using the status indicators and comments in the tracker system as much as possible.
However, it is not possible for us to provide ETAs for individual ideas or suggestions at this time.

We have never found that sharing hard delivery dates is a positive experience for either the software vendor or the customer. It sets expectations that are near impossible to keep.

There are just too many factors that can change how long an improvement or new piece of functionality takes to develop. That’s why we choose to show “Features in Development” and “Features that are Planned”. It’s more than enough transparency to keep customers confident we have a plan and strategy behind our product.

=== Why would you implement new features free of charge? ===

The general approach is the following: if a feature makes our product better for all related parties, in the long run, it is a feature worth implementing at no cost.

=== Can I pay for the feature to be implemented faster? ===

In some cases, it is possible after careful consideration about how the feature impacts the product and other clients. How hard it is to implement and support in the future. How much value it brings to everybody related. And do we have spare resources to postpone all other planned features for this paid feature implementation?

If you really need some feature implemented as fast as possible - please contact us directly by creating Trouble Ticket in the Support System.

=== If I pay for the feature will it be available for all the product users? ===

Yes, it will. It's impossible for us to manage and support hundreds of different versions of the product.

 

<big><big>IMPORTANT: Our product roadmap is always subject to change. 
It is not a commitment, promise, or obligation to deliver any specific features. 
Customers should make any purchasing decisions on Kolmisoft's product features that are already available.</big></big>

 

Thank you for your feedback, understanding, and support.

Product Feedback Policy

2021-11-15T17:02:28Z

Mindaugas:

Kolmisoft is continuously aiming to improve your experience by rolling out new features and product enhancements.
On this page, you will learn about the way we collect product feedback from our customers in order to make our product
better and help your business succeed.

 
= Our approach to product feedback =

At Kolmisoft, your feedback is highly valued as it provides us with direction on the features we should implement to
make your experience with the product the best it can be.

We use your feedback to identify the most important features, ideas, pain points, and opportunities so that you can
get more value from the product as efficiently as possible.

Please note that submitting your idea doesn’t guarantee any changes. While every piece of feedback will be read as our
Product Team reviews and triages the submissions, it doesn’t necessarily ensure action.

 
= How to submit product feedback =

If you have a product suggestion or an idea about how a feature could be improved, we’d love to hear more!

To get started:

# Log into your Kolmisoft support system account and click on the Make a Suggestion button.
# You’ll be taken to the submission form, where you’ll need to type in your feedback.
# The more information you can provide the better.
# Click Submit request when you are finished.

=== Avoid duplicate ideas ===
When suggesting a new idea, please check to see if someone else has already suggested a similar feature.

You can vote on feature requests that you want by clicking “I Want this” beside the title of the post.
Remember to vote for the features you want to see - it will bring them to our attention faster.

If your submission is not a product feature or suggestion, it may be removed.

If you need to report a problem or have a question about the product that requires a more immediate or direct response, go to https://support.kolmisoft.com and create a Trouble Ticket to connect with our Support staff.

 
= What does an actionable product feedback submission look like? =

After posting your feedback request, it can be voted on by other users. An ideal post succinctly describes what it is you want to do, what your pain point is, how you currently workaround the issue, and the impact this problem has on your work.

The clearer your post is and the more detail you have, the easier it will be for other users to understand the value of your request, making it more likely to be upvoted.

To make your request more impactful, here are tips for good feedback:

* '''Make your title concise and descriptive.''' This will help others find and upvote your feedback. Also, please write in English.
* '''Clearly outline what your ultimate goal is.''' What problem are you trying to solve with your suggestion? Our Product Team members are experts at troubleshooting and problem-solving. We may be able to help you find a feature or a solution that already exists!
* '''Provide additional context.''' Feel free to add a comment with any additional information or context around why this change would be helpful for you (for ex. how this suggestion will improve your daily workflow). You can even attach some screenshots to help us see what you’re experiencing!
* '''Highlight any workarounds.''' How are you currently getting around or solving this problem?

We don’t expect you to know all the answers, but feel free to get creative with what you think would work!

On the practical side, we also recommend including one suggestion per post and refraining from posting personal information.

 
= What happens after I submit the request? =

All new requests are set to the "Awaiting Feedback" status so that more people can vote, prioritize and give us information. This allows us to gauge demand, gather use cases and automatically establish impact & value using our Reports.

Periodically, our Product team sits down for a feedback meeting. The product team reviews the requests that have the highest number of votes first. The team discusses the highest priorities for our customers, team members, and prospects and how the requests align with our own strategy.

When reading through feedback, we’re primarily evaluating the level of impact that an update could have on all of our users. The larger the impacted audience, the more likely it that feedback would be prioritized.

As the team goes through they'll update the status of each request so that you immediately know the outcome.
If we decide to build a request the status will change to "Planned" or "Building".

Please note that there is no assured timeline or commitment that the request will in fact end up in our product.

 
= Viewing and prioritising your requests =

If you’ve voted for some requests, you’ll see your requests under My Priorities.

You can adjust the sliding bars to reflect your priorities.

Be sure to prioritize your requests – that way, we will know if a particular request is important to you.

 
= Status of the requests =

We will always provide an explanation as to the nature of the status update.

Our feedback portal always has the most up-to-date information about our products and what we're building next.

Note: The Request System always has the most up-to-date information about the status of requests and what we're building next.

If you reach out directly to our support or sales team they'll be able to look up the request for you, but they won't have any additional information or provide an estimate for when your item will be reviewed/developed.

 
=== Definition of Kolmisoft request statuses ===

* '''Not reviewed''' - Our Product team has not reviewed this suggestion yet. Usually, they will provide a status within 1-2 weeks.
* '''Awaiting feedback''' -This suggestion is under consideration by the team for future development. Our Product team is gathering feedback and additional use cases regarding this suggestion. Please add your comments and support this suggestion so we can prioritize it accordingly.
* '''Planned''' -This suggestion is on our roadmap. We will post an update when we start working on it.
* '''Building''' - This suggestion is part of the current product roadmap theme.
* '''Released''' - This suggestion has been delivered and is generally available. Should we realize a feature that a customer has been requesting, we will notify everyone who has submitted related feedback.
* '''Declined''' - This suggestion is not under consideration for the current or for the next roadmap theme. It might also refer to an existing feature.

 
= FAQs =

=== How long will it be before the product team reviews my idea? ===

Items will be reviewed by Kolmisoft’s product team every other week; we take the new requests and update the status where appropriate.

=== My request hasn’t been reviewed yet and I submitted it 6+ months ago. What can I do? ===

If we haven’t reviewed your request and it is a high priority for you:
* Make sure it’s at the top of your priority list.
* Make sure your request is clear. Why do you need this? What is stopping you from doing? Please add these details as a comment on your idea.
* Create a Trouble Ticket in the https://support.kolmisoft.com with the link to your original request

===My idea has some votes. Why hasn't it been implemented yet? ===

While we would love to be able to implement more of the suggestions we receive, with finite resources and a big product roadmap, we have to decide what we work on based on a combination of factors.

This includes not just votes, but also technical complexity, time to delivery, value, and the number of users it would benefit.

Unfortunately, this means sometimes we have to make tough decisions that we know disappoint some users. Rest assured that we regularly review the ideas and suggestions posted here as part of our routine product
planning and popular requests do play a large part in prioritization considerations.

=== Can you provide an ETA for my idea or suggestion? ===

We try to keep users updated using the status indicators and comments in the tracker system as much as possible.
However, it is not possible for us to provide ETAs for individual ideas or suggestions at this time.

We have never found that sharing hard delivery dates is a positive experience for either the software vendor or the customer. It sets expectations that are near impossible to keep.

There are just too many factors that can change how long an improvement or new piece of functionality takes to develop. That’s why we choose to show “Features in Development” and “Features that are Planned”. It’s more than enough transparency to keep customers confident we have a plan and strategy behind our product.

=== Why would you implement new features free of charge? ===

The general approach is the following: if a feature makes our product better for all related parties, in the long run, it is a feature worth implementing at no cost.

=== Can I pay for the feature to be implemented faster? ===

In some cases, it is possible after careful consideration about how the feature impacts the product and other clients. How hard it is to implement and support in the future. How much value it brings to everybody related. And do we have spare resources to postpone all other planned features for this paid feature implementation?

If you really need some feature implemented as fast as possible - please contact us directly by creating Trouble Ticket in the Support System.

=== If I pay for the feature will it be available for all the product users? ===

Yes, it will. It's impossible for us to manage and support hundreds of different versions of the product.

 

<big><big>IMPORTANT: Our product roadmap is always subject to change. 
It is not a commitment, promise, or obligation to deliver any specific features. 
Customers should make any purchasing decisions on Kolmisoft's product features that are already available.</big></big>

 

Thank you for your feedback, understanding, and support.

CPS Calls Per Second

2021-10-27T11:33:58Z

Mindaugas: Created page with '.'

Product Feedback Policy

2021-10-25T09:09:24Z

Mindaugas: Created page with '.'

Various Guides

2021-10-25T09:09:02Z

Mindaugas: /* Documentation */

==Guides==

===Testing===

* [[Performance Testing with Sipp]]

===Installation===
* [[G723/G729 Codec installation]]
* [[MySQL Replication]]
* [[Sangoma Wanpipe installation]]
* [[Centos installation]]
* [[Setting up https secure connection | Setting up https secure connection (SSL)]]
* [[Install Eluna Stats]]
* [[Configure SSH connection between servers]]
* [[Fail2Ban installation]]
* [[OVH server installation]]
** [[OVH server Rescue Mode]]
** [[OVH NVME atop Reporting Problem]]

===MySQL===
* [[Live Backups]]
* [[How to access MySQL database via WEB]]
* [[Lost MySQL root password?]]
* [[Backup old Calls]]
* [[How to recover corrupted MySQL data]]
* [[How to restore system from Backup which are made from GUI]]

===Asterisk===

* [[Ports which should be opened]]
* [[Asterisk under NAT]]
* [[Asterisk CLI debug]]
* [[Which codecs should I choose for devices]]
* [[How to restart Asterisk server]]
* [[How to change RTP port range for Asterisk]]
* [[Two SIP listening ports for single Asterisk]]
* [[sip.conf]]
* [[RTPAUDIOQOS Demystified]]
* [[Explanation about stucked calls]]
* [[SIP Domains in Asterisk]]
* [[Additional Asterisk Server]]

===Troubleshooting===
* [[SIP Call Flow]]
* [[SIP analysis using sngrep]]
* [[SIP Capture with TCPDump]]
* [[How to capture packets using wireshark]]

===Other===

* [[Voice quality]]
** [[How to increase call volume]]
* [[Latency]]
* [[How to change server's IP]]
* [[Server working very slowly]]
* [[Timezone in RoR]]
* [[Sound files]]
** [[Convert WAV file to Asterisk playable format]]
** [[TTS Engines]]
* [[Fax over VoIP]]
** [[Send_Receive_Fax-T38 | Send Receive Fax over T38]]
* [[NTP: Server Time Sync]]
* [[Selinux]]
* [[Fail2Ban]]
* [[How to block someone's IP]]
* [[High availability (Heartbeat clustering)]]
* [[Migration to other server]]
* [[What is direct URL]]
* [[How to join Webex meeting]]
* [[Load-balancing using DNS SRV]]
* [[Kamailio kamcli installation on Centos 7]]
* [[sipp installation]]
* [[Enbloc or Overlap]]
* [[Session Description Protocol]]

=== Softphones ===

* [[Idefisk configuration| Idefisk 1.37 Configuration]]
* [[X-PRO Configuration]]
* [[Video call with CounterPath eyeBeam]]

=== Hardware ===

* [[Cisco Gateway Settings]]
* [[How to connect to Huawei devices]]
* [[TELES configuration]]
* [[VoiceBlue Ring problem ]]
* [[Linksys SPA942 Configuration]]
* [[Linksys PAP2]]
* [[How to get pause on mobile phone keyboard]]
* [[CDMA support]]
* [[Check RAID status]]

 

==Documentation==

* [[VoIP Business Glossary]]
* [[VoIP Advantages]]

* [[Why we do not suggest to use IAX2]]
* [[Various documentation| FAQ]]

* '''[[Ticket System | Support System]]'''
** [[Support System explanation]]
** [[Create new Ticket in Ticket System]]
** [[Write comment to the Ticket]]
** [[In what order tickets are solved in Support System]]
** [[Support]]
** [[Amazon S3 Backups]]
** Accounting
*** [[Where to find invoices]]

* '''[[Product Feedback Policy]]'''

* [[Forum|Forum]]
* [[Pricing structure]]
* [[Training]]

Various Guides

2021-10-25T09:08:52Z

Mindaugas: /* Documentation */

Client not receiving incoming calls

2021-10-19T12:07:51Z

Mindaugas:

Steps to troubleshoot:

1. Check if the device is registered to the system, fix if no

2. Open Call Info for the problematic call

Please check the hangup cause. It has code 20, which means that the device is unavailable (not registered).
Asterisk log usually shows: WARNING Unable to create channel of type 'SIP' (cause 20 - Subscriber absent)

3. Retrieve PCAP

4. Check if INVITE was sent to the correct IP:PORT

 
==See also==
* [[Cause No. 20 - subscriber absent]]
* [[I have a problem with Registration]]

Client not receiving incoming calls

2021-10-19T12:06:27Z

Mindaugas:

Steps to troubleshoot:

1. Check if the device is registered to the system, fix if no

2. Open Call Info for the problematic call

3. Retrieve PCAP

4. Check if INVITE was sent to the correct IP:PORT

 
==See also==
* [[I have a problem with Registration]]

Client not receiving incoming calls

2021-10-19T11:13:48Z

Mindaugas: Created page with 'Steps to troubleshoot: 1. Open Call Info for the problematic call 2. Retrieve PCAP 3. Check if INVITE was sent to the correct IP:PORT 4. ...'

Steps to troubleshoot:

1. Open Call Info for the problematic call

2. Retrieve PCAP

3. Check if INVITE was sent to the correct IP:PORT

4. ...

I have a problem with Calls

2021-10-19T11:12:45Z

Mindaugas:

What problem do you have?

* [[I cannot make a call]]
** [[Troubleshooting failed Call]]
* [[Cannot See Calls From Originator]]
** [[Call is not going through and not shown in Last Calls]]
* [[Client not receiving incoming calls]]
* [[Call was billed incorrectly]]
* [[Call is going but not visible in Active Calls]]
* [[I do not want to hear an error message at the end of the call]]
* [[Call hangs after 1 second]]
* [[Call hangs after 8 seconds]]
* [[Call hangs after 30 seconds]]
* [[Call hangs after 60 seconds]]
* [[Call hangs after 15 minutes]]
* [[Call hangs after 30 minutes]]
* [[Call hangs after 2 hours]]
* [[BYE is not forwarded]]
* [[I have a problem with Active Calls]]
* [[I have Unlimited Minutes when trying to dial out]]
* [[I hear wrong Time for the call]]
* [[Troubleshooting RINGING|I do not hear RINGING]]
* [[DID is not working]]
* [[Calls using ZAP/DAHDI are not working]]
* [[Why call was not routed through other provider/trunk?]]
* [[Very long delay before ring tone]]
* [[Provider is not working]]
* [[How to increase call volume | How to increase call volume?]]
* [[Timezone_in_RoR | Call time in GUI]]
* [[Reseller cannot make calls using his providers]]
* [[How_to_change_default_button_for_call_end | Call does not end when pressing ##]]
* [[Digits are skipped when entering destination or PIN]]
* I have bad [[Voice quality]]
* [[Reseller calls are not working]]
* [[Localization|Clients want to dial and use local area numbers]]
* [[Simultaneous_call_limitation#Device|"sip show peers" shows incorrect call limit]]
* [[H.323 incoming calls do not work]]
* [[H.323 outgoing calls delays]]
* [[Call with video support enabled fails]]
* [[Lots of calls made by System Admin user |Somebody is calling over my system!]]
* [[username mismatch error in Asterisk CLI]]
* [[Spy from Active Calls always connects same call]]
* [[Spy Device is registered on different server than this call. Spying on this call is not possible]]
* [[Call rejected, CallToken Support required.]]
* [[Cannot make calls from FreePBX]]
* [[Balance, Calls and Invoices are zero]]
* [[Lots of dropped calls]]
* [[Calls of NEC PBX are propped after few seconds]]
* [[User gets "403 Forbidden" from MOR]]
* [[Low ASR/ACD]]
* [[Device receiving strange calls]]
* [[PCAP file cannot be retrieved]]
* [[MOR server is sending a SIP response, but the originating server is not receiving it]]

 
* [[One-way audio or not audio at all]]
** [[One way audio problems]]

* [[Call connections are slow]]

 
* [[I want to setup a user to call for free]]
* [[I want to hide providers IP]]

= See also =
* [[Main_Page#Asterisk_2 | Asterisk problems]]
* [[I HAVE A PROBLEM]]
* http://kb.smartvox.co.uk/voip-sip/top-reasons-voip-calls-drop/

NO ANSWER/BUSY interpretation for providers

2021-10-14T14:10:02Z

Mindaugas:

This option is applied to the call LegB.

By default, the '''NO ANSWER''' or '''BUSY''' call end disposition is counted as the end of a call. After this, it is pointless to try to dial the same destination again, because the destination is not answering (NO ANSWER) or is currently busy (BUSY).

If we have several providers in our LCR, the call ends after we receive NO ANSWER or BUSY from a provider, and our routing ends.

This is okay for an ideal world in which all providers follow standards and send the correct call end codes, e.g.:

* NO ANSWER when calls are not answered after a certain period (timeout).
* BUSY when a recipient is busy (talking with somebody else).
* ANSWERED when a call has been answered and ends.
* FAILED when an error occurs.

However, providers sometimes cheat (or do not have the technical skills to make this correctly). For example, if they can't deliver a call to a destination because of some problem in their network or something similar, they may send the NO ANSWER or BUSY signal for a FAILED call. And then our routing breaks. If we have several more providers in our LCR, our LCR will not try to send calls over to the remaining providers and will end the call.

This often happens for GREY (illegal) routes.

To partly solve this problem, MOR provides a workaround: "NO ANSWER/BUSY interpretation for providers".

This makes it possible to set a NO ANSWER and/or BUSY interpretation as FAILED.

That means, if a provider reports NO ANSWER and/or BUSY, MOR treats this as FAILED and the next provider in LCR (if there are further providers) is tried to send the call.

These options can be set in Providers Settings:

[[Image:noanswer_busy_interpretation.png]]

'''It is advised to use these settings ONLY and ONLY on confirmed cheating/misconfigured providers. That is, these settings should usually be 'NO'.'''

 
=See also=

* [[Why call was not routed through other provider/trunk?|Why was a call not routed through another provider/trunk?]]
* [[* button does not work]]

M4 Origination Points

2021-10-11T10:02:13Z

Mindaugas:

Origination Point is connection from some initial entity (device/line/trunk/provider/supplier/etc) where call starts/originates.

Call comes from Origination Point and goes to [[M2 Termination Points | Termination Points]].

==Timeouts==

* '''Ringing Timeout''' - allows to limit ringing duration (in seconds). Leave 0 for unlimited. 
* '''Call Timeout''' - allows to limit Call duration (in seconds). Leave 0 for unlimited (global Call timeout (7200 seconds) is still applicable in this case). 

==Servers==

Origination Points (OP) can be assigned to one or more servers. If call comes from server where OP is not assigned, call will not go through. 

==Authentication==

* '''Tech. Prefix''' - Destination technical prefix that is used to authenticate OP. If this field is empty, calls will be accepted with any Destination number only based on IP:PORT. If this field is not empty, then only calls with specific prefix in Destination will be authenticated (for example if Tech. Prefix is 00, then OP accepts Destination numbers which start with 00xxxxxxx). 

* '''IP Address''' - IP Address of Origination Point (subnetting and IP range is allowed. For more information read Subnetting and IP range sections below). 
* '''Port''' - Port of Origination Point. 

==Origination Point==
[[File:OriginationPoint.png]]
* '''Act as Origination Point''' - if set to 'yes', this Connection Point will be handled as Origination Point. 
* '''Active''' - allows to activate or deactivate OP. If OP is deactivated, calls will not be accepted from this OP. 
* '''Destination Transformation''' - special [[M2 Destination Transformation | Destination Transformation]] rules used to modify outgoing number. Rules are applied before billing so it can be used to correct non E164 formats. 
* '''Source Transformation''' - special [[M2 Source Transformation | Source Transformation]] rules used to modify Source number. 
* '''Routing Algorithm''' - defines how Termination Points are ordered for this Origination Point. 
* '''Routing Group''' - Routing Group used for OP routing. 
* '''Use MNP''' - enable [[M2 Mobile Number Portability|MNP]] for this OP. 
* '''MNP Routing Group''' - name of Routing Group used for [[M2 Mobile Number Portability|MNP]].
* '''Capacity''' - limit the number of concurrent calls for this OP (both ringing and answered calls are included in this limit). 
* '''Source (CallerID) Allow''' - regular expression (regexp) that defines which CallerIDs are allowed to go through this OP. If you want to allow all CallerIDs, enter '''.*''' in this input field. 
* '''Source (CallerID) Deny''' - regular expression (regexp) that defines which CallerIDs are denied to go through this OP. 
* '''Custom Tariff''' - Custom Tarrif that can override regular OP Tariff. If rates are found in Custom Tariff then these rates will be applied in accounting. If rates are not found in Custom Tariff, then regular OP Tariff is used. 
* '''Conditional Tariff''' : XXXXX (description why and how to use it [[M2_EU_Roaming_Regulations | here]])
** If CallerID matches/not matches Rule-Set: [[M2 Number Pools | Number Pool Rule Set]] 
** Use CallerID Number from PAI Header if available: No / Yes 
** and if Destination: do not use/matches/not matces Rule-Set [[M2 Number Pools | Number Pool Rule Set]] 
** Using this option it is possible to Use other tariff if CallerID and Destination matched Rule-Set. It is possible to create a Rule-Set at Maintenance - Number Pools. Also, it offers possibility to use CallerID Number from PAI Header if available.
* '''Default Tariff''' - Tariff used for OP accounting if previous option is not used. 
* '''USA Jurisdictional Routing''' - Jurisdictional routing is telephone call routing logic based upon the locations of the calling and called number and regulatory considerations. '''Can be enabled by Kolmisoft only. Please contact support to enable.''' More information can be found here [https://transnexus.com/whitepapers/jurisdictional-routing Here]
[[File:USAJurisdictionalRouting.png]]
* Intra Tariff- Tariff for Intrastate routing. Calls between two points within the same state
* Inter Tariff - Tariff for Interstate routing. Calls made from one state to another
* Indeter Tariff - Tariff for Invalid ANI, or indeterminate routing. Calls where the calling number is any value other than a valid telephone number—these are usually rated at the intrastate rate

==CallerID==

* '''Name''' - set name part for CallerID. 
* '''Number''' - set number part for CallerID. 
* '''Random Number from Number Pool''' - set random number from Number Pool. Only number part for CallerID is set.
** '''Random''' - Send random CallerID from Number Pool.
** '''Pseudorandom with Deviation''' - Range can vary from 0 to 9999999. If 0 is chosen, then all numbers will be chosen same amount of times. If 9999999 is set, then numbers will be completely random.

==Codecs==

Set which codecs are allowed for OP. 

* '''Inherit leg B Codecs''' - if enabled, system will try to force leg B negotiated Codec to leg A. If leg A does not support that Codec, then system uses any other available Codec. This option is used to prevent transcoding in some cases. More information can be found [[M2 Codec Negotiation | here]].

==Advanced==

* '''Grace Time''' - if call duration is less than Grace Time, it will not be accounted (CDR will be generated, but OP balance will not be reduced). 
* '''Custom SIP Header''' - adds custom header to SIP request. Format is header: value (for example x-My-Custom-Header: my value). 
* '''Limit up to X Calls, during Y seconds''' - allows to control Calls per Second (CPS). 
* '''Disable Q.850 Reason''' - by default M2 returns Q.850 Reason header in SIP responses to Originator. This can be disabled by setting this option to "yes".
* '''Bypass Media''' - when set, the media (RTP) from the originating endpoint is sent directly to the destination endpoint and vice versa. The signaling (SIP) for both endpoints still goes through M2, but the media is point-to-point.

==Advanced Origination Point Settings==

* '''Accept calls from any port''' - if set to 'yes', then calls from any port are accepted. If set to 'no', then only calls from a specific port are accepted (see Port input field in authentication section). 
* '''Change RPID/PAI Host''' - allows overwriting original host address in RPID/PAI header with proxy server's IP address.
* '''Use Destination from INVITE request''' - by default M2 uses Destination number from SIP '''To''' header (To: <sip:123@sip.com>). If you set this option to "yes", M2 will use Destination number from SIP '''INVITE''' request line (INVITE sip:123@sip.com SIP/2.0).
* '''Ring instead Session Progress''' - if enabled, M2 translates SIP 183 Session Progress from terminator side to SIP 180 Ringing to originator side (M2 receives SIP 183 from terminator but sends SIP 180 to the originator).
* '''Send CallerID in Contact header''' - when this option is enabled, the Contact header will be set to CallerID number.
* '''Disconnect Code Changes''' - allows changing hangup code which is returned to OP. 
* '''Use PAI Number for Routing''' - uses PAI Number instead of FROM callerID for routing.
* '''Send PAI Number as CallerID to TP''' - uses PAI Number as CallerID.
* '''Forward RPID''' - by default forward RPID header from Originator to Terminator. This can be disabled by setting this option to "no". [[M4 RPID/PAI|More info]]
* '''Forward PAI''' - by default forward PAI header from Originator to Terminator. This can be disabled by setting this option to "no". [[M4 RPID/PAI|More info]]
* '''Ignore SIP 183 without SDP''' - by default disabled. Select '''Yes''' to enable the option.
* '''Ignore SIP 180 after 183''' - by default disabled. Select '''Yes''' to enable the option.
* '''Allow to use own User's TPs''' - by default, it is not allowed to route the call through TP which belongs to the same User. Such call results in HGC 339. By setting this option to Yes, you can disable this protection.

=Subnetting=

It is possible to set [http://en.wikipedia.org/wiki/Subnetwork subnetwork] (subnet) for Origination Point. Subnets allow you to have single Origination Point for multiple IP addresses. Instead of IP address, you can set subnet in '''IP Address''' input field. Subnet should be written in [http://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing CIDR notation] (for example 192.168.0.1/28). When subnet is used in Origination Point, all calls coming from that subnet will be authenticated.

M2 subnet value range is 4-30.
 
You can use online subnet [http://www.aboutmyip.com/AboutMyXApp/SubnetCalculator.jsp? calculator] to check IP addresses for given subnet. 

=IP range=

If you need to set multiple IP addresses for single Orignation Point and Subnetting does not meet your needs, then you can set IP ranges. Ranges are written in the following format:

xxx.xxx.xxx.xxx-yyy

When IP range is used in Origination Point, all calls coming from that IP range will be authenticated. For example, if we have IP range 192.168.0.101-150, then all IP addresses starting from 192.168.0.101 to 192.168.0.150 will be authenticated (50 different IP addresses are allowed to call to this Origination Point).

M4 Switch Manual

2021-10-11T09:59:45Z

Mindaugas: /* General Info */

<div align="center">
[[File:m2_logo.png|800px|link=|alt="M2 Class 4 Softswitch"]]
 
<center>M4 (former M2) is class 4 Softswitch with Billing and Routing with extended functionality, increased stability and professional support directly from the developers. It enables VoIP providers to offer wholesale/transit services.</center>
</div>
 

= General Info =

* [[M2 Switch | Introduction]]
* [[M2 Functionality | Functionality]]
* [[M2 Network Architecture]]
* [[M4 System Architecture]]
* Codecs
** [[M2 Supported Codecs]]
*** [[M2 Codec Negotiation | Codec Negotiation]]
** [[M4 Supported Codecs]]
* [[M2 API | API]]
* [[M2 Video Demonstrations]]
* [[M2 Changelog]]

 

= Configuration =

* [[M2-M4 Settings | Settings]]
* [[M2 Users | Users]]
* [[system.conf]]
* [[Performance Suggestions M2 | Performance Suggestions]]
* [[Destination Groups Policy]]
* [[Move MOR Database to M2]]
* [[M2 Caching]]
* [[M4 Media Bypass|Media Bypass]]
* [[M4 RPID/PAI | RPID/PAI]]

 

= Routing =

* [[M2 Routing Logic | Routing Logic]]
* [[M2 Regexp Examples|Regexp Examples]]
* [[M2_Connection_Points | Connection Points]]
** [[M2 Termination Points | Termination Points (TP) ]]
*** [[M2 TP Call Limit | TP Call Limit]]
** [[M2 Origination Points | Origination Points (OP) ]]
* [[M2 Source Transformation | Source Transformation]]
* [[M2 Destination Transformation | Destination Transformation]]
* [[M2 Routing Groups | Routing Groups (RG) ]]
* [[M2 Quality Routing | Quality Routing]]
* [[M2 Dial Peers | Dial Peers (DP) ]]
* [[M2_Directions_and_Destinations | Directions and Destinations]]
* [[M2_How_to_block_calls | How to block calls]]
* [[M2_Mobile_Number_Portability | Mobile Number Portability]]
* [[M4_Local_Number_Portability | Local Number Portability - US Jurisdictional Routing]]
 

= Billing =

* [[M2 Tariffs| Tariffs]]
* [[M2_Custom_Tariffs | Custom Tariffs]]
* [[M2_CDR_Disputes | CDR Disputes]]
* [[M2 EU Roaming Regulations | EU Roaming Regulations]]
* [[M2 Rates | Rates]]
** [[Rate Notifications | Rate Notifications]]
** [[M2 Blocked Rates | Blocked Rates]]
** [[M2 Work Days and Free Days | Work Days and Free Days]]
 

= Accounting =

* [[M2 Payments | Payments]]
* [[M2 Customer Invoices| Customer Invoices]]
* [[M2 Supplier Invoices| Supplier Invoices]]
* [[M2_CDR_Rerating | CDR Rerating]]
 

= Reporting =

* [[M2_Aggregates | Aggregates]]
* [[M2_Calls_by_Clients | Calls by Clients]]
* [[M2_Calls_List | Calls List]]
* [[M2_Quick_Stats | Quick Stats]]
* [[M2 Balance Report | Balance Report]]
* [[M2 Financial Status|Financial Status]]
* [[M2 CSV Export | CSV Export]]
* [[M2 Reports Examples | Reports Examples]]
* [[M2 Destination Groups Stats | Destination Groups Stats]]
* [[M2_Load_Stats | Load Stats]]
* [[M2_Calls_Dashboard | Calls Dashboard]]
* [[M2_Terminator_Active_Calls| Terminator Active Calls]]
 

= Maintenance/Troubleshooting =

* [[M2 Access Levels | Access Levels]]
* [[M2 CDR Management | CDR Management]]
* [[M2 Hangupcause Codes | Hangupcause Codes]]
** [[M2 Disconnect Code Changes | Disconnect Code Changes]]
* [[M4 Disconnect Codes]]
* [[M2 Warning Balance | Warning Balance]]
* [[M2 Alerts | Alerts]]
* [[Freeswitch]]
** [https://wiki.freeswitch.org/wiki/Codecs#Transcodable_codecs Freeswitch Codecs]
** [https://wiki.freeswitch.org/wiki/Codec_Negotiation Freeswitch Codec Negotiation]
** [[Freeswitch under NAT]]
** [[Freeswitch Port Range]]
** [[Freeswitch SNMP]]
* [[M2 Number Pools|Number Pools]]
* [[M2 Directions | Directions]]
* [[M2 Call Tracing | Call Tracing]]
* [[M2 Call Info | Call Info]]
* [[M2_disable_Q.850_Reason_header | Disable Q.850 Reason header]]
 

= Security =

* [[M2_Blocked_IPs | Block IPs]]
* [[M2_Blocked_Countries | Block Countries]]
* [[M2_Login_Failure_Report | Login_Failure_Report]]
* [[M2_Login_with_approved_IP%27s | Login with approved IP's]]
 

= I Have a Problem =

* [[M2_Ports_which_should_be_opened | Ports which should be opened]]
* [[Call Count Bigger That What We Can Process]]
* [[Sometimes Users Blocked Automatically]]
 

= User Portal =

* [[M2 User Dashboard | Dashboard]]
 

= Tutorials =

* [[M2 How to make first call | How to make first call]]
* [[M2 video demonstrations]]

M4 Video Demonstrations

2021-10-11T09:59:26Z

Mindaugas: moved M2 video demonstrations to M2 Video Demonstrations

= Prepaid Postpaid billing =

<html>
<iframe width="640" height="360" src="https://www.youtube.com/embed/ItB8-btLvwg" frameborder="0" allowfullscreen="1"></iframe>
</html>

= LCR =

<html>
<iframe width="640" height="360" src="https://www.youtube.com/embed/lZLXTeh-B4I" frameborder="0" allowfullscreen="1"></iframe>
</html>

= Quality base routing =

<html>
<iframe width="640" height="360" src="https://www.youtube.com/embed/Sy99-GWIUMk" frameborder="0" allowfullscreen="1"></iframe>
</html>

= Tariff management =

<html>
<iframe width="640" height="360" src="https://www.youtube.com/embed/c8jrYQ0j7-Q" frameborder="0" allowfullscreen="1"></iframe>
</html>

= Invoicing =

<html>
<iframe width="640" height="360" src="https://www.youtube.com/embed/LQD-BlGUZjA" frameborder="0" allowfullscreen="1"></iframe>
</html>

= CDR export =

<html>
<iframe width="640" height="360" src="https://www.youtube.com/embed/E8sphQMzVyk" frameborder="0" allowfullscreen="1"></iframe>
</html>

= Alerts and notifications =

<html>
<iframe width="640" height="360" src="https://www.youtube.com/embed/PobW9DT5tRw" frameborder="0" allowfullscreen="1"></iframe>
</html>

M4 Switch Manual

2021-10-11T09:58:41Z

Mindaugas: /* General Info */

<div align="center">
[[File:m2_logo.png|800px|link=|alt="M2 Class 4 Softswitch"]]
 
<center>M4 (former M2) is class 4 Softswitch with Billing and Routing with extended functionality, increased stability and professional support directly from the developers. It enables VoIP providers to offer wholesale/transit services.</center>
</div>
 

= General Info =

* [[M2 Switch | Introduction]]
* [[M2 Functionality | Functionality]]
* [[M2 Network Architecture]]
* [[M4 System Architecture]]
* Codecs
** [[M2 Supported Codecs]]
*** [[M2 Codec Negotiation | Codec Negotiation]]
** [[M4 Supported Codecs]]
* [[M2 API | API]]
* [[M2 video demonstrations]]
* [[M2 Changelog]]

 

= Configuration =

* [[M2-M4 Settings | Settings]]
* [[M2 Users | Users]]
* [[system.conf]]
* [[Performance Suggestions M2 | Performance Suggestions]]
* [[Destination Groups Policy]]
* [[Move MOR Database to M2]]
* [[M2 Caching]]
* [[M4 Media Bypass|Media Bypass]]
* [[M4 RPID/PAI | RPID/PAI]]

 

= Routing =

* [[M2 Routing Logic | Routing Logic]]
* [[M2 Regexp Examples|Regexp Examples]]
* [[M2_Connection_Points | Connection Points]]
** [[M2 Termination Points | Termination Points (TP) ]]
*** [[M2 TP Call Limit | TP Call Limit]]
** [[M2 Origination Points | Origination Points (OP) ]]
* [[M2 Source Transformation | Source Transformation]]
* [[M2 Destination Transformation | Destination Transformation]]
* [[M2 Routing Groups | Routing Groups (RG) ]]
* [[M2 Quality Routing | Quality Routing]]
* [[M2 Dial Peers | Dial Peers (DP) ]]
* [[M2_Directions_and_Destinations | Directions and Destinations]]
* [[M2_How_to_block_calls | How to block calls]]
* [[M2_Mobile_Number_Portability | Mobile Number Portability]]
* [[M4_Local_Number_Portability | Local Number Portability - US Jurisdictional Routing]]
 

= Billing =

* [[M2 Tariffs| Tariffs]]
* [[M2_Custom_Tariffs | Custom Tariffs]]
* [[M2_CDR_Disputes | CDR Disputes]]
* [[M2 EU Roaming Regulations | EU Roaming Regulations]]
* [[M2 Rates | Rates]]
** [[Rate Notifications | Rate Notifications]]
** [[M2 Blocked Rates | Blocked Rates]]
** [[M2 Work Days and Free Days | Work Days and Free Days]]
 

= Accounting =

* [[M2 Payments | Payments]]
* [[M2 Customer Invoices| Customer Invoices]]
* [[M2 Supplier Invoices| Supplier Invoices]]
* [[M2_CDR_Rerating | CDR Rerating]]
 

= Reporting =

* [[M2_Aggregates | Aggregates]]
* [[M2_Calls_by_Clients | Calls by Clients]]
* [[M2_Calls_List | Calls List]]
* [[M2_Quick_Stats | Quick Stats]]
* [[M2 Balance Report | Balance Report]]
* [[M2 Financial Status|Financial Status]]
* [[M2 CSV Export | CSV Export]]
* [[M2 Reports Examples | Reports Examples]]
* [[M2 Destination Groups Stats | Destination Groups Stats]]
* [[M2_Load_Stats | Load Stats]]
* [[M2_Calls_Dashboard | Calls Dashboard]]
* [[M2_Terminator_Active_Calls| Terminator Active Calls]]
 

= Maintenance/Troubleshooting =

* [[M2 Access Levels | Access Levels]]
* [[M2 CDR Management | CDR Management]]
* [[M2 Hangupcause Codes | Hangupcause Codes]]
** [[M2 Disconnect Code Changes | Disconnect Code Changes]]
* [[M4 Disconnect Codes]]
* [[M2 Warning Balance | Warning Balance]]
* [[M2 Alerts | Alerts]]
* [[Freeswitch]]
** [https://wiki.freeswitch.org/wiki/Codecs#Transcodable_codecs Freeswitch Codecs]
** [https://wiki.freeswitch.org/wiki/Codec_Negotiation Freeswitch Codec Negotiation]
** [[Freeswitch under NAT]]
** [[Freeswitch Port Range]]
** [[Freeswitch SNMP]]
* [[M2 Number Pools|Number Pools]]
* [[M2 Directions | Directions]]
* [[M2 Call Tracing | Call Tracing]]
* [[M2 Call Info | Call Info]]
* [[M2_disable_Q.850_Reason_header | Disable Q.850 Reason header]]
 

= Security =

* [[M2_Blocked_IPs | Block IPs]]
* [[M2_Blocked_Countries | Block Countries]]
* [[M2_Login_Failure_Report | Login_Failure_Report]]
* [[M2_Login_with_approved_IP%27s | Login with approved IP's]]
 

= I Have a Problem =

* [[M2_Ports_which_should_be_opened | Ports which should be opened]]
* [[Call Count Bigger That What We Can Process]]
* [[Sometimes Users Blocked Automatically]]
 

= User Portal =

* [[M2 User Dashboard | Dashboard]]
 

= Tutorials =

* [[M2 How to make first call | How to make first call]]
* [[M2 video demonstrations]]

M4 Switch Manual

2021-10-11T09:56:57Z

Mindaugas:

<div align="center">
[[File:m2_logo.png|800px|link=|alt="M2 Class 4 Softswitch"]]
 
<center>M4 (former M2) is class 4 Softswitch with Billing and Routing with extended functionality, increased stability and professional support directly from the developers. It enables VoIP providers to offer wholesale/transit services.</center>
</div>
 

= General Info =

* [[M2 Switch | Introduction]]
* [[M2 Functionality]]
* [[M2 Network Architecture]]
* [[M4 System Architecture]]
* Codecs
** [[M2 Supported Codecs]]
** [[M2 Codec Negotiation]]
** [[M4 Supported Codecs]]
* [[M2 API]]
* [[M2 video demonstrations]]
* [[M2 Changelog]]

 

= Configuration =

* [[M2-M4 Settings | Settings]]
* [[M2 Users | Users]]
* [[system.conf]]
* [[Performance Suggestions M2 | Performance Suggestions]]
* [[Destination Groups Policy]]
* [[Move MOR Database to M2]]
* [[M2 Caching]]
* [[M4 Media Bypass|Media Bypass]]
* [[M4 RPID/PAI | RPID/PAI]]

 

= Routing =

* [[M2 Routing Logic | Routing Logic]]
* [[M2 Regexp Examples|Regexp Examples]]
* [[M2_Connection_Points | Connection Points]]
** [[M2 Termination Points | Termination Points (TP) ]]
*** [[M2 TP Call Limit | TP Call Limit]]
** [[M2 Origination Points | Origination Points (OP) ]]
* [[M2 Source Transformation | Source Transformation]]
* [[M2 Destination Transformation | Destination Transformation]]
* [[M2 Routing Groups | Routing Groups (RG) ]]
* [[M2 Quality Routing | Quality Routing]]
* [[M2 Dial Peers | Dial Peers (DP) ]]
* [[M2_Directions_and_Destinations | Directions and Destinations]]
* [[M2_How_to_block_calls | How to block calls]]
* [[M2_Mobile_Number_Portability | Mobile Number Portability]]
* [[M4_Local_Number_Portability | Local Number Portability - US Jurisdictional Routing]]
 

= Billing =

* [[M2 Tariffs| Tariffs]]
* [[M2_Custom_Tariffs | Custom Tariffs]]
* [[M2_CDR_Disputes | CDR Disputes]]
* [[M2 EU Roaming Regulations | EU Roaming Regulations]]
* [[M2 Rates | Rates]]
** [[Rate Notifications | Rate Notifications]]
** [[M2 Blocked Rates | Blocked Rates]]
** [[M2 Work Days and Free Days | Work Days and Free Days]]
 

= Accounting =

* [[M2 Payments | Payments]]
* [[M2 Customer Invoices| Customer Invoices]]
* [[M2 Supplier Invoices| Supplier Invoices]]
* [[M2_CDR_Rerating | CDR Rerating]]
 

= Reporting =

* [[M2_Aggregates | Aggregates]]
* [[M2_Calls_by_Clients | Calls by Clients]]
* [[M2_Calls_List | Calls List]]
* [[M2_Quick_Stats | Quick Stats]]
* [[M2 Balance Report | Balance Report]]
* [[M2 Financial Status|Financial Status]]
* [[M2 CSV Export | CSV Export]]
* [[M2 Reports Examples | Reports Examples]]
* [[M2 Destination Groups Stats | Destination Groups Stats]]
* [[M2_Load_Stats | Load Stats]]
* [[M2_Calls_Dashboard | Calls Dashboard]]
* [[M2_Terminator_Active_Calls| Terminator Active Calls]]
 

= Maintenance/Troubleshooting =

* [[M2 Access Levels | Access Levels]]
* [[M2 CDR Management | CDR Management]]
* [[M2 Hangupcause Codes | Hangupcause Codes]]
** [[M2 Disconnect Code Changes | Disconnect Code Changes]]
* [[M4 Disconnect Codes]]
* [[M2 Warning Balance | Warning Balance]]
* [[M2 Alerts | Alerts]]
* [[Freeswitch]]
** [https://wiki.freeswitch.org/wiki/Codecs#Transcodable_codecs Freeswitch Codecs]
** [https://wiki.freeswitch.org/wiki/Codec_Negotiation Freeswitch Codec Negotiation]
** [[Freeswitch under NAT]]
** [[Freeswitch Port Range]]
** [[Freeswitch SNMP]]
* [[M2 Number Pools|Number Pools]]
* [[M2 Directions | Directions]]
* [[M2 Call Tracing | Call Tracing]]
* [[M2 Call Info | Call Info]]
* [[M2_disable_Q.850_Reason_header | Disable Q.850 Reason header]]
 

= Security =

* [[M2_Blocked_IPs | Block IPs]]
* [[M2_Blocked_Countries | Block Countries]]
* [[M2_Login_Failure_Report | Login_Failure_Report]]
* [[M2_Login_with_approved_IP%27s | Login with approved IP's]]
 

= I Have a Problem =

* [[M2_Ports_which_should_be_opened | Ports which should be opened]]
* [[Call Count Bigger That What We Can Process]]
* [[Sometimes Users Blocked Automatically]]
 

= User Portal =

* [[M2 User Dashboard | Dashboard]]
 

= Tutorials =

* [[M2 How to make first call | How to make first call]]
* [[M2 video demonstrations]]

M4 Switch Manual

2021-10-11T09:56:21Z

Mindaugas: moved M2 Switch Manual to M4 Switch Manual

<div align="center">
[[File:m2_logo.png|800px|link=|alt="M2 Class 4 Softswitch"]]
 
<center>M2 is class 4 softswitch with Billing and Routing with extended functionality, increased stability and professional support directly from the developers. It enables VoIP providers to offer wholesale/transit services.</center>
</div>
 

= General Info =

* [[M2 Switch | Introduction]]
* [[M2 Functionality]]
* [[M2 Network Architecture]]
* [[M4 System Architecture]]
* Codecs
** [[M2 Supported Codecs]]
** [[M2 Codec Negotiation]]
** [[M4 Supported Codecs]]
* [[M2 API]]
* [[M2 video demonstrations]]
* [[M2 Changelog]]

 

= Configuration =

* [[M2-M4 Settings | Settings]]
* [[M2 Users | Users]]
* [[system.conf]]
* [[Performance Suggestions M2 | Performance Suggestions]]
* [[Destination Groups Policy]]
* [[Move MOR Database to M2]]
* [[M2 Caching]]
* [[M4 Media Bypass|Media Bypass]]
* [[M4 RPID/PAI | RPID/PAI]]

 

= Routing =

* [[M2 Routing Logic | Routing Logic]]
* [[M2 Regexp Examples|Regexp Examples]]
* [[M2_Connection_Points | Connection Points]]
** [[M2 Termination Points | Termination Points (TP) ]]
*** [[M2 TP Call Limit | TP Call Limit]]
** [[M2 Origination Points | Origination Points (OP) ]]
* [[M2 Source Transformation | Source Transformation]]
* [[M2 Destination Transformation | Destination Transformation]]
* [[M2 Routing Groups | Routing Groups (RG) ]]
* [[M2 Quality Routing | Quality Routing]]
* [[M2 Dial Peers | Dial Peers (DP) ]]
* [[M2_Directions_and_Destinations | Directions and Destinations]]
* [[M2_How_to_block_calls | How to block calls]]
* [[M2_Mobile_Number_Portability | Mobile Number Portability]]
* [[M4_Local_Number_Portability | Local Number Portability - US Jurisdictional Routing]]
 

= Billing =

* [[M2 Tariffs| Tariffs]]
* [[M2_Custom_Tariffs | Custom Tariffs]]
* [[M2_CDR_Disputes | CDR Disputes]]
* [[M2 EU Roaming Regulations | EU Roaming Regulations]]
* [[M2 Rates | Rates]]
** [[Rate Notifications | Rate Notifications]]
** [[M2 Blocked Rates | Blocked Rates]]
** [[M2 Work Days and Free Days | Work Days and Free Days]]
 

= Accounting =

* [[M2 Payments | Payments]]
* [[M2 Customer Invoices| Customer Invoices]]
* [[M2 Supplier Invoices| Supplier Invoices]]
* [[M2_CDR_Rerating | CDR Rerating]]
 

= Reporting =

* [[M2_Aggregates | Aggregates]]
* [[M2_Calls_by_Clients | Calls by Clients]]
* [[M2_Calls_List | Calls List]]
* [[M2_Quick_Stats | Quick Stats]]
* [[M2 Balance Report | Balance Report]]
* [[M2 Financial Status|Financial Status]]
* [[M2 CSV Export | CSV Export]]
* [[M2 Reports Examples | Reports Examples]]
* [[M2 Destination Groups Stats | Destination Groups Stats]]
* [[M2_Load_Stats | Load Stats]]
* [[M2_Calls_Dashboard | Calls Dashboard]]
* [[M2_Terminator_Active_Calls| Terminator Active Calls]]
 

= Maintenance/Troubleshooting =

* [[M2 Access Levels | Access Levels]]
* [[M2 CDR Management | CDR Management]]
* [[M2 Hangupcause Codes | Hangupcause Codes]]
** [[M2 Disconnect Code Changes | Disconnect Code Changes]]
* [[M4 Disconnect Codes]]
* [[M2 Warning Balance | Warning Balance]]
* [[M2 Alerts | Alerts]]
* [[Freeswitch]]
** [https://wiki.freeswitch.org/wiki/Codecs#Transcodable_codecs Freeswitch Codecs]
** [https://wiki.freeswitch.org/wiki/Codec_Negotiation Freeswitch Codec Negotiation]
** [[Freeswitch under NAT]]
** [[Freeswitch Port Range]]
** [[Freeswitch SNMP]]
* [[M2 Number Pools|Number Pools]]
* [[M2 Directions | Directions]]
* [[M2 Call Tracing | Call Tracing]]
* [[M2 Call Info | Call Info]]
* [[M2_disable_Q.850_Reason_header | Disable Q.850 Reason header]]
 

= Security =

* [[M2_Blocked_IPs | Block IPs]]
* [[M2_Blocked_Countries | Block Countries]]
* [[M2_Login_Failure_Report | Login_Failure_Report]]
* [[M2_Login_with_approved_IP%27s | Login with approved IP's]]
 

= I Have a Problem =

* [[M2_Ports_which_should_be_opened | Ports which should be opened]]
* [[Call Count Bigger That What We Can Process]]
* [[Sometimes Users Blocked Automatically]]
 

= User Portal =

* [[M2 User Dashboard | Dashboard]]
 

= Tutorials =

* [[M2 How to make first call | How to make first call]]
* [[M2 video demonstrations]]

M4 Switch Manual

2021-10-11T09:53:36Z

Mindaugas: /* Configuration */

M4 Switch Manual

2021-10-11T09:53:25Z

Mindaugas: /* Configuration */

<div align="center">
[[File:m2_logo.png|800px|link=|alt="M2 Class 4 Softswitch"]]
 
<center>M2 is class 4 softswitch with Billing and Routing with extended functionality, increased stability and professional support directly from the developers. It enables VoIP providers to offer wholesale/transit services.</center>
</div>
 

= General Info =

* [[M2 Switch | Introduction]]
* [[M2 Functionality]]
* [[M2 Network Architecture]]
* [[M4 System Architecture]]
* Codecs
** [[M2 Supported Codecs]]
** [[M2 Codec Negotiation]]
** [[M4 Supported Codecs]]
* [[M2 API]]
* [[M2 video demonstrations]]
* [[M2 Changelog]]

 

= Configuration =

* [[M2-M4 Settings]]
* [[M2 Users | Users]]
* [[system.conf]]
* [[Performance Suggestions M2 | Performance Suggestions]]
* [[Destination Groups Policy]]
* [[Move MOR Database to M2]]
* [[M2 Caching]]
* [[M4 Media Bypass|Media Bypass]]
* [[M4 RPID/PAI | RPID/PAI]]

 

= Routing =

* [[M2 Routing Logic | Routing Logic]]
* [[M2 Regexp Examples|Regexp Examples]]
* [[M2_Connection_Points | Connection Points]]
** [[M2 Termination Points | Termination Points (TP) ]]
*** [[M2 TP Call Limit | TP Call Limit]]
** [[M2 Origination Points | Origination Points (OP) ]]
* [[M2 Source Transformation | Source Transformation]]
* [[M2 Destination Transformation | Destination Transformation]]
* [[M2 Routing Groups | Routing Groups (RG) ]]
* [[M2 Quality Routing | Quality Routing]]
* [[M2 Dial Peers | Dial Peers (DP) ]]
* [[M2_Directions_and_Destinations | Directions and Destinations]]
* [[M2_How_to_block_calls | How to block calls]]
* [[M2_Mobile_Number_Portability | Mobile Number Portability]]
* [[M4_Local_Number_Portability | Local Number Portability - US Jurisdictional Routing]]
 

= Billing =

* [[M2 Tariffs| Tariffs]]
* [[M2_Custom_Tariffs | Custom Tariffs]]
* [[M2_CDR_Disputes | CDR Disputes]]
* [[M2 EU Roaming Regulations | EU Roaming Regulations]]
* [[M2 Rates | Rates]]
** [[Rate Notifications | Rate Notifications]]
** [[M2 Blocked Rates | Blocked Rates]]
** [[M2 Work Days and Free Days | Work Days and Free Days]]
 

= Accounting =

* [[M2 Payments | Payments]]
* [[M2 Customer Invoices| Customer Invoices]]
* [[M2 Supplier Invoices| Supplier Invoices]]
* [[M2_CDR_Rerating | CDR Rerating]]
 

= Reporting =

* [[M2_Aggregates | Aggregates]]
* [[M2_Calls_by_Clients | Calls by Clients]]
* [[M2_Calls_List | Calls List]]
* [[M2_Quick_Stats | Quick Stats]]
* [[M2 Balance Report | Balance Report]]
* [[M2 Financial Status|Financial Status]]
* [[M2 CSV Export | CSV Export]]
* [[M2 Reports Examples | Reports Examples]]
* [[M2 Destination Groups Stats | Destination Groups Stats]]
* [[M2_Load_Stats | Load Stats]]
* [[M2_Calls_Dashboard | Calls Dashboard]]
* [[M2_Terminator_Active_Calls| Terminator Active Calls]]
 

= Maintenance/Troubleshooting =

* [[M2 Access Levels | Access Levels]]
* [[M2 CDR Management | CDR Management]]
* [[M2 Hangupcause Codes | Hangupcause Codes]]
** [[M2 Disconnect Code Changes | Disconnect Code Changes]]
* [[M4 Disconnect Codes]]
* [[M2 Warning Balance | Warning Balance]]
* [[M2 Alerts | Alerts]]
* [[Freeswitch]]
** [https://wiki.freeswitch.org/wiki/Codecs#Transcodable_codecs Freeswitch Codecs]
** [https://wiki.freeswitch.org/wiki/Codec_Negotiation Freeswitch Codec Negotiation]
** [[Freeswitch under NAT]]
** [[Freeswitch Port Range]]
** [[Freeswitch SNMP]]
* [[M2 Number Pools|Number Pools]]
* [[M2 Directions | Directions]]
* [[M2 Call Tracing | Call Tracing]]
* [[M2 Call Info | Call Info]]
* [[M2_disable_Q.850_Reason_header | Disable Q.850 Reason header]]
 

= Security =

* [[M2_Blocked_IPs | Block IPs]]
* [[M2_Blocked_Countries | Block Countries]]
* [[M2_Login_Failure_Report | Login_Failure_Report]]
* [[M2_Login_with_approved_IP%27s | Login with approved IP's]]
 

= I Have a Problem =

* [[M2_Ports_which_should_be_opened | Ports which should be opened]]
* [[Call Count Bigger That What We Can Process]]
* [[Sometimes Users Blocked Automatically]]
 

= User Portal =

* [[M2 User Dashboard | Dashboard]]
 

= Tutorials =

* [[M2 How to make first call | How to make first call]]
* [[M2 video demonstrations]]

M4 Settings

2021-10-11T09:52:22Z

Mindaugas: moved M2 settings to M2-M4 Settings

To change M2 Settings, go to '''MAINTENANCE - Settings'''

Just click on each point to expand.
 

=Invoices=
 
[[File:Invoices.png]]
 
*'''Number start''' – how the invoice number should start.
*'''Number length''' – the length in digits AFTER Number Start – e.g. Number Start is not counted into this length. This value is active only for first number type.
*'''Number type''' – select more appropriate number format. INV000001 means autoincremental number after "Number start" value. INV070601 means "Number start" + date + invoice max id.
*'''Duration format''' - time format in invoice. Available options - 'H:M:S', 'H:M', 'M'. When option 'M' is used, sub option Decimal places appear, where you can select precision.
 
'''XLSX'''
 
XLSX file to export an Invoice is made from your own XLSX format template and information from Invoices main window.
Example of template can be downloaded [http://www.kolmisoft.com/packets/x6_invoice_template.xlsx here].

When you already have a template for example with all data of your company, with drawn tables and so on, you need to define where should be shown the dynamic information of invoice. To do that you just need to define cell address in correct format.

Client Address Cell is different than other ones - once you will define this, all other Address Related Cells will be filled automatically and will not be editable. Also, no empty space will be left if any Address sub-cell is not defined. For example, if Client State is not defined in User's Settings, then this Cell will not be empty in Invoice - all Address Cells bellow will go up by one Cell. This allows nice Address formatting without leaving spaces if some Address data is not defined in User's settings.

*'''Comment''' - refers to Comment available in Invoice Details page. The Invoice needs to be recalculated after adding a comment, so that comment would be applied.

 

=Emails=
 
[[File:M2 Invoices.jpg]]
 
*'''Sending globally enable'''d – if this is checked, you will be able to use Mass Mailing and the system will send emails upon user registration.
*'''SMTP server''' – hostname of the server.
*'''Port''' – port of SMTP server.
*'''Login''' – username to your SMTP server.
*'''Password''' – password to your SMTP server.
*'''Batch size''' – value for Mass Mailing, or how many emails to send at once.
*'''From''' – email address to put into From: field in email. Acceptable formats are: example@email.com or John Smith <example@email.com>.
*'''Test email sending''' – save settings and press this to test email sending. Do not forget to save settings first!

P.S. Remember to set admin's e-mail in admin's personal settings. Without this test email sending will not work!
 

=Tax=
 
[[File:M2 Tax.jpg]]
 
*Settings are explained here: [[Multi-Tax system]]
 
=Security=
 
[[File:M2_settings_security.png]]
 
* '''Use strong passwords for users''' - password must contain at least one numeric value, capital and lowercase symbol and must at be at least 8 characters long.
* '''Admin login with approved IP only''' - security measure which allows to approve IP's that try to [[M2_Login_with_approved_IP%27s|login with Admin Account]].
* '''Enable IP report warning on login failure''' - show [[M2_Login_Failure_Report|warning]] on unsuccessful login attempts.
* '''Logout after password change''' - terminates all sessions of the User whose password is changed.
* '''Do not logout on session IP change''' - do not logout from M2 GUI if IP is changed.
 

=Active Calls=
 
[[File:M2_settings_active_calls.png]]
 

* '''How many maximum [[ M2 Active Calls|Active Calls]] to show in GUI''' – how many to show in GUI
* '''[[ M2 Active Calls|Active Calls]] refresh interval''' – [[ M2 Active Calls|Active Calls]] refresh interval in seconds
* '''Show [[ M2 Active Calls|Active Calls]] for Users''' – tick if you want to allow users to see [[ M2 Active Calls|Active Calls]]
* '''Show Servers in [[ M2 Active Calls|Active Calls]]'''

* '''Show Rates in [[ M2 Active Calls|Active Calls]]''' .
 
=Calls List=
 
[[File:M2_settings_last_calls.png]]
 
* '''Show Connection Point and it's CallerID in Calls List''' – shows additional column in [[Last Calls]] page with Connection Point and its CallerID information. Click to reach that Connection Point settings page.
* '''Show Answer Time in Calls List'''
* '''Show End Time in Calls List'''
* '''Show PDD in Calls List'''
* '''Show Terminated by in Calls List'''
* '''Show Usernames on PDF/CSV Export Files in Calls List''' – if checked, when a particular User in the Last Calls page search is selected, Last Calls PDF/CSV file name will be composed also of Name of selected User. If you are looking for All Users, no User Name will be used. (Name of User will be shown in Name of CSV/PDF file).
* '''Show Duration in Calls List''' - shows additional Duration column.
* '''Retrieve PCAP files from the Proxy Server''' - If enabled, clicking on 'Retrieve PCAP files' in [[M2 Call Info]] page will check for PCAP files in Proxy.
 

=Calls Dashboard=
 
[[File:M2 Call Dashboard.jpg]]
 
In the System Settings several adjustments can be made in order to customize the Calls Dashboard.
*'''Calls Dashboard refresh interval''': how often the statistics are updated (a positive integer representing minutes). 
*'''ASR''': as in the example, when lower than 30%, the cells will be colored red, greater than 50% value will result in the green color. Everything between will be set to yellow (only integers are allowed). 
*'''ACD''': as in the example, when lower than 60 seconds, the cells will be colored red, greater than 119 seconds value will result in the green color. Everything between will be set to yellow (only integers are allowed). 
*'''Margin''': as in the example, no coloring will be applied on Margin cells. 
 
'''Note:''' partial coloring is also possible. For example when the ASR is set to Red < 30 and Green > is left blank, only red coloring will be present for the ASR cells.
More information about [[M2 Calls Dashboard]]
 
=CDR Management=
 
This functionality is [[M2 CDR Management#Configuration|described here]].
 

=Visual=
 
[[File:M2 settings visual.png]]
* '''Items per page''' – the number of items to display per one page
* '''[[Global_date_format| Default date format]]''' – System default date format
* '''Default Time Format''' – System default time format
* '''Number digits''' – how many digits to display after a comma
* '''Currency Amount Number Digits (Decimal Places)''' - how many digits to display after a comma in monetary terms.
* '''Hide Connection Point passwords for users''' – do not display Connection Point passwords for users
* '''Show Full Source (CallerID Name and Number)'''
* '''Show user_billsec for Users instead of billsec''' – shows user_billsec instead of billsec in Users invoices and last calls. Notice that Billsec shows real Call duration, user_billsec shows Call duration after minimal time or increment applied. For example, if user tariff has 60 sec minimal time and user made a Call for 20 sec, then billsec will show 20 sec and user_billsec will show 60 sec (minimal time is applied).
* '''Default Number Decimal''' – with this option you can set default number decimal for all GUI
* '''Show Calls statistics to User for last''' – number of Calls statistics to show in days. For example, if you enter 5 days, users will only see 5 days old calls, they will not be able to check older calls.
* '''Show Detailed Quick Stats''' - shows detailed Quick Stats on main page.
* '''Cache ES Sync Status for last''' - caches ES Sync status for last X minutes. If value 0 is entered, then ES Sync Status will be changed with every refresh.
 

=Various=
 
[[File:M2 settings various.png]]
 

*'''Agreement number length''' – number length in digits.
*'''Change ANSWER to FAILED if HGC not equal to 16 for Users''' – changes the Hangupcause for users in call reports from Answered to Failed if Hangupcause is not 16.
* '''Server free space limit''' - if server free space is lower than this limit, warning will be displayed globally and email sent to admin every hour. Default value is 20%.
* '''Call Tracing Server''' - which server to use for call tracing. Useful if GUI server is on different server than Radius server.
* '''Delete outdated Rates older than''' - delete rates for which effective date is older than x days and for which exists same prefix with newer effective date. Default is 0, which means never delete.
* '''Use Tariff currency in CSV export''' - uses tariff currency in CSV export.
* '''Allow Dynamic Origination Point Authentication with Registration''' - WARNING: all IP addresses will be allowed to access your server to allow this functionality. This is additional risk to your system. Option is disabled by default.

 

=API=
 
[[File:M2 settings api.png]]
 
* '''Allow API globally''' – should we enable API globaly? When it is disabled, all settings below are also disabled and not editable.
* '''Allow GET API''' – should we allow GET method to be used for API? Good for testing - but do not use in production! It is unsafe.
* '''API Secret Key''' – key to [[MOR API hash construction | generate Hash]]
* '''XML API Extension''' – send XML output with HTML tag - this is used for broken .Net support, keep it unchecked if everything works for you.
* '''Allow API Login Redirect''' – if login is successful the customer will be redirected to MOR billing Main site.
* '''API Allow Payments''' - Allows to create payments via API
* '''Allow Connection Point to check balance over API''' - Allows Connection Point to check balance over API
* '''Disable hash checking''' – When it is on API functions can be used without sending hash. Default value: off.
* '''Uniquehash''' – admin's unique hash.
'''NOTE''' that M2 does not allow you to enable '''Allow API''' if '''API Secret Key''' is not entered. In such case you will get a message '''Invalid API secret key'''. '''Enter API Secret Key''' in order to fix this.
 

=Backups=
[[File:M2 settings backups.png]]
 
If Run Backup according below schedule is checked, the following settings become active:

*'''Exclude Archived Calls table''' – archived calls will not be present in the backup (calls_old table will be ignored).
*'''Store Backups on FTP server''' - stores Backups on FTP server. Please fill FTP server details at [http://wiki.kolmisoft.com/index.php/M2_settings#FTP FTP] tab.
*'''Month''' – in which month backup should be made.
*'''Day of every month''' – which day of every month backup should be made.
*'''Day of week''' – which day of the week backup should be made.
*'''Hour''' – which hour backup should be made.
*'''Keep on local server''' – how many backups to keep on the server. The system deletes the oldest one if the limit is reached.
*'''Don't start backup if disk space less than''' – checks disk space before making an auto backup.
 

=CSV Settings=
 
[[File:M2 settings csvsettings.png]]
 

* '''CSV Column Separator''' – how columns are separated in imported/exported CSV files.
* '''CSV Decimal Separator''' – how decimal parts in numbers are separated in imported/exported CSV files.
* ''' Archive CSV file when size reaches''' – if CSV file reaches a certain size, the system will archive it to save time to download it (0 means to archive never)
 

=Server Load=
 
[[File:M2 settings serverload.png]]
 
 
Settings for GUI Server and Database Server

* '''HDD utilisation higher than''' – Percentage of CPU time during which I/O requests were issued to the device (bandwidth utilization for the device), as reported by '''iostat''' %util column.
* '''CPU General Load higher than''' – Percentage of the CPU for user processes as reported by '''top''' %us column.
* '''CPU Load Stats 1 higher than''' – average load for '''one minute''' on the system as reported by '''top''' command
* '''CPU MySQL process higher than''' – Percentage of the CPU for MySQL process as reported by '''top''' command
Same applies for other processes (Ruby, Freeswitch, Asterisk,)
 
* '''Delete Server Load Stats older than''' – deletes internal servers load statistics older than defined number of days.
 

 
=Privacy=
 
[[File:M2 settings gdpr.png]]
 
* '''GDPR Activated''' – hides User data with notification "Data hidden due GDPR. Press to show data (action will be logged)".
 
=Payments=
[[File:M2_paypal_settings.png]]
 
* '''Activate Paypal Payments''' - yes or no. This will add PayPal payment menu in Users accounts Start page.
* '''Paypal Client ID''' - Paypal client ID (provided by Paypal).
* '''Secret Paypal Key''' - key to verify tranactions (provided by Paypal).
'''NOTE: Current tab is visible if PayPal addon is activated.'''
 

=FTP=
[[File:M2_FTP.png]]
 
Please fill up FTP server details if you want to store Archived calls or/and Backups to FTP server.

* '''IP''' - Enter FTP server IP.
* '''Port''' - Enter FTP server Port.
* '''Username''' - Enter FTP server Username.
* '''Password''' - Enter FTP server Password.
* '''Path for Archived Calls''' - Enter Path for Archived Calls.
* '''Path for Backups''' - Enter path for Backups.
 

=Mobile Number Portability=
'''Note: M2 Proxy server is required to use MNP''' 

* [[M2 Mobile Number Portability]]

[[File:mnp_settings.png]]
* '''Use Number Portability''' - Enable number portability.
* '''Server IP''' - The IP address of the MNP server that M2 will connect to.
* '''Port''' - The port number of the MNP server's DB that M2 will connect to.
* '''Username''' - The user name of the account used to connect to the MNP server's DB.
* '''Password''' - The password of the account used to connect to the MNP server's DB.
* '''DB Name''' - The name of MNP DB where MNP data is stored.
* '''Table Name''' - The table name from MNP '''DB Name''' DB where data is stored.
* '''Search Field''' - The name of the column in '''Table Name''' where number will be searched.
* '''Result Field''' - The name of the column in '''Table Name''' from where information about number's portability will be retrieved.
* '''Supported Prefixes''' - Either '''All Prefixes''' (default) or '''Only these prefixes'''. If '''Only these prefixes''' option is enabled, only selected prefixes will be active for MNP check.

'''Add to List''' button allows to add prefixes for '''Only these prefixes''' option.

'''Test DB Connection''' button allows us to test DB connection and check if DB details are correct or not.

=White Label=
[[File:white_lable_settings.png]]
 
* '''Logo''' - replaces logo shown in top left corner. Max size: 125x40, supported types: PNG, JPG.
* '''Favicon''' - replaces icon shown in browsers tab. Max size: 64x64, supported type: ICO.
* '''Footer''' - text shown in bottom of the page.

M4 Switch Manual

2021-10-11T09:48:51Z

Mindaugas: /* Billing */

<div align="center">
[[File:m2_logo.png|800px|link=|alt="M2 Class 4 Softswitch"]]
 
<center>M2 is class 4 softswitch with Billing and Routing with extended functionality, increased stability and professional support directly from the developers. It enables VoIP providers to offer wholesale/transit services.</center>
</div>
 

= General Info =

* [[M2 Switch | Introduction]]
* [[M2 Functionality]]
* [[M2 Network Architecture]]
* [[M4 System Architecture]]
* Codecs
** [[M2 Supported Codecs]]
** [[M2 Codec Negotiation]]
** [[M4 Supported Codecs]]
* [[M2 API]]
* [[M2 video demonstrations]]
* [[M2 Changelog]]

 

= Configuration =

* [[M2 Users | Users]]
* [[system.conf]]
* [[Performance Suggestions M2 | Performance Suggestions]]
* [[Destination Groups Policy]]
* [[Move MOR Database to M2]]
* [[M2 Caching]]
* [[M4 Media Bypass|Media Bypass]]
* [[M4 RPID/PAI | RPID/PAI]]

 

= Routing =

* [[M2 Routing Logic | Routing Logic]]
* [[M2 Regexp Examples|Regexp Examples]]
* [[M2_Connection_Points | Connection Points]]
** [[M2 Termination Points | Termination Points (TP) ]]
*** [[M2 TP Call Limit | TP Call Limit]]
** [[M2 Origination Points | Origination Points (OP) ]]
* [[M2 Source Transformation | Source Transformation]]
* [[M2 Destination Transformation | Destination Transformation]]
* [[M2 Routing Groups | Routing Groups (RG) ]]
* [[M2 Quality Routing | Quality Routing]]
* [[M2 Dial Peers | Dial Peers (DP) ]]
* [[M2_Directions_and_Destinations | Directions and Destinations]]
* [[M2_How_to_block_calls | How to block calls]]
* [[M2_Mobile_Number_Portability | Mobile Number Portability]]
* [[M4_Local_Number_Portability | Local Number Portability - US Jurisdictional Routing]]
 

= Billing =

* [[M2 Tariffs| Tariffs]]
* [[M2_Custom_Tariffs | Custom Tariffs]]
* [[M2_CDR_Disputes | CDR Disputes]]
* [[M2 EU Roaming Regulations | EU Roaming Regulations]]
* [[M2 Rates | Rates]]
** [[Rate Notifications | Rate Notifications]]
** [[M2 Blocked Rates | Blocked Rates]]
** [[M2 Work Days and Free Days | Work Days and Free Days]]
 

= Accounting =

* [[M2 Payments | Payments]]
* [[M2 Customer Invoices| Customer Invoices]]
* [[M2 Supplier Invoices| Supplier Invoices]]
* [[M2_CDR_Rerating | CDR Rerating]]
 

= Reporting =

* [[M2_Aggregates | Aggregates]]
* [[M2_Calls_by_Clients | Calls by Clients]]
* [[M2_Calls_List | Calls List]]
* [[M2_Quick_Stats | Quick Stats]]
* [[M2 Balance Report | Balance Report]]
* [[M2 Financial Status|Financial Status]]
* [[M2 CSV Export | CSV Export]]
* [[M2 Reports Examples | Reports Examples]]
* [[M2 Destination Groups Stats | Destination Groups Stats]]
* [[M2_Load_Stats | Load Stats]]
* [[M2_Calls_Dashboard | Calls Dashboard]]
* [[M2_Terminator_Active_Calls| Terminator Active Calls]]
 

= Maintenance/Troubleshooting =

* [[M2 Access Levels | Access Levels]]
* [[M2 CDR Management | CDR Management]]
* [[M2 Hangupcause Codes | Hangupcause Codes]]
** [[M2 Disconnect Code Changes | Disconnect Code Changes]]
* [[M4 Disconnect Codes]]
* [[M2 Warning Balance | Warning Balance]]
* [[M2 Alerts | Alerts]]
* [[Freeswitch]]
** [https://wiki.freeswitch.org/wiki/Codecs#Transcodable_codecs Freeswitch Codecs]
** [https://wiki.freeswitch.org/wiki/Codec_Negotiation Freeswitch Codec Negotiation]
** [[Freeswitch under NAT]]
** [[Freeswitch Port Range]]
** [[Freeswitch SNMP]]
* [[M2 Number Pools|Number Pools]]
* [[M2 Directions | Directions]]
* [[M2 Call Tracing | Call Tracing]]
* [[M2 Call Info | Call Info]]
* [[M2_disable_Q.850_Reason_header | Disable Q.850 Reason header]]
 

= Security =

* [[M2_Blocked_IPs | Block IPs]]
* [[M2_Blocked_Countries | Block Countries]]
* [[M2_Login_Failure_Report | Login_Failure_Report]]
* [[M2_Login_with_approved_IP%27s | Login with approved IP's]]
 

= I Have a Problem =

* [[M2_Ports_which_should_be_opened | Ports which should be opened]]
* [[Call Count Bigger That What We Can Process]]
* [[Sometimes Users Blocked Automatically]]
 

= User Portal =

* [[M2 User Dashboard | Dashboard]]
 

= Tutorials =

* [[M2 How to make first call | How to make first call]]
* [[M2 video demonstrations]]

M4 Switch Manual

2021-10-11T09:48:34Z

Mindaugas: /* Billing */

<div align="center">
[[File:m2_logo.png|800px|link=|alt="M2 Class 4 Softswitch"]]
 
<center>M2 is class 4 softswitch with Billing and Routing with extended functionality, increased stability and professional support directly from the developers. It enables VoIP providers to offer wholesale/transit services.</center>
</div>
 

= General Info =

* [[M2 Switch | Introduction]]
* [[M2 Functionality]]
* [[M2 Network Architecture]]
* [[M4 System Architecture]]
* Codecs
** [[M2 Supported Codecs]]
** [[M2 Codec Negotiation]]
** [[M4 Supported Codecs]]
* [[M2 API]]
* [[M2 video demonstrations]]
* [[M2 Changelog]]

 

= Configuration =

* [[M2 Users | Users]]
* [[system.conf]]
* [[Performance Suggestions M2 | Performance Suggestions]]
* [[Destination Groups Policy]]
* [[Move MOR Database to M2]]
* [[M2 Caching]]
* [[M4 Media Bypass|Media Bypass]]
* [[M4 RPID/PAI | RPID/PAI]]

 

= Routing =

* [[M2 Routing Logic | Routing Logic]]
* [[M2 Regexp Examples|Regexp Examples]]
* [[M2_Connection_Points | Connection Points]]
** [[M2 Termination Points | Termination Points (TP) ]]
*** [[M2 TP Call Limit | TP Call Limit]]
** [[M2 Origination Points | Origination Points (OP) ]]
* [[M2 Source Transformation | Source Transformation]]
* [[M2 Destination Transformation | Destination Transformation]]
* [[M2 Routing Groups | Routing Groups (RG) ]]
* [[M2 Quality Routing | Quality Routing]]
* [[M2 Dial Peers | Dial Peers (DP) ]]
* [[M2_Directions_and_Destinations | Directions and Destinations]]
* [[M2_How_to_block_calls | How to block calls]]
* [[M2_Mobile_Number_Portability | Mobile Number Portability]]
* [[M4_Local_Number_Portability | Local Number Portability - US Jurisdictional Routing]]
 

= Billing =

* [[M2 Tariffs| Tariffs]]
* [[M2_Custom_Tariffs | Custom Tariffs]]
* [[M2_CDR_Disputes | CDR Disputes]]
* [[M2 EU Roaming Regulations | EU Roaming Regulations]]
* [[M2 Rates | Rates]]
** [[Rate Notification | Rate Notifications]]
** [[M2 Blocked Rates | Blocked Rates]]
** [[M2 Work Days and Free Days | Work Days and Free Days]]
 

= Accounting =

* [[M2 Payments | Payments]]
* [[M2 Customer Invoices| Customer Invoices]]
* [[M2 Supplier Invoices| Supplier Invoices]]
* [[M2_CDR_Rerating | CDR Rerating]]
 

= Reporting =

* [[M2_Aggregates | Aggregates]]
* [[M2_Calls_by_Clients | Calls by Clients]]
* [[M2_Calls_List | Calls List]]
* [[M2_Quick_Stats | Quick Stats]]
* [[M2 Balance Report | Balance Report]]
* [[M2 Financial Status|Financial Status]]
* [[M2 CSV Export | CSV Export]]
* [[M2 Reports Examples | Reports Examples]]
* [[M2 Destination Groups Stats | Destination Groups Stats]]
* [[M2_Load_Stats | Load Stats]]
* [[M2_Calls_Dashboard | Calls Dashboard]]
* [[M2_Terminator_Active_Calls| Terminator Active Calls]]
 

= Maintenance/Troubleshooting =

* [[M2 Access Levels | Access Levels]]
* [[M2 CDR Management | CDR Management]]
* [[M2 Hangupcause Codes | Hangupcause Codes]]
** [[M2 Disconnect Code Changes | Disconnect Code Changes]]
* [[M4 Disconnect Codes]]
* [[M2 Warning Balance | Warning Balance]]
* [[M2 Alerts | Alerts]]
* [[Freeswitch]]
** [https://wiki.freeswitch.org/wiki/Codecs#Transcodable_codecs Freeswitch Codecs]
** [https://wiki.freeswitch.org/wiki/Codec_Negotiation Freeswitch Codec Negotiation]
** [[Freeswitch under NAT]]
** [[Freeswitch Port Range]]
** [[Freeswitch SNMP]]
* [[M2 Number Pools|Number Pools]]
* [[M2 Directions | Directions]]
* [[M2 Call Tracing | Call Tracing]]
* [[M2 Call Info | Call Info]]
* [[M2_disable_Q.850_Reason_header | Disable Q.850 Reason header]]
 

= Security =

* [[M2_Blocked_IPs | Block IPs]]
* [[M2_Blocked_Countries | Block Countries]]
* [[M2_Login_Failure_Report | Login_Failure_Report]]
* [[M2_Login_with_approved_IP%27s | Login with approved IP's]]
 

= I Have a Problem =

* [[M2_Ports_which_should_be_opened | Ports which should be opened]]
* [[Call Count Bigger That What We Can Process]]
* [[Sometimes Users Blocked Automatically]]
 

= User Portal =

* [[M2 User Dashboard | Dashboard]]
 

= Tutorials =

* [[M2 How to make first call | How to make first call]]
* [[M2 video demonstrations]]

How to set up SSL certificate with Let's Encrypt

2021-10-11T09:16:44Z

Mindaugas: /* Before proceeding */

== About Let's Encrypt ==
[https://letsencrypt.org/ Let's Encrypt] provides free valid SSL certificates

 
== Before proceeding ==
To proceed the following is needed:
* Domain name pointed to switch IP (it is not possible to create a Let's Encrypt SSL certificate for IP address)
* Email address to get notifications from Let's Encrypt
* SSH access to the server with root privileges

 

== Installation ==
In the example below let's assume that the domain name is example.com

Before installation, it is a good idea to backup /etc/httpd folder

cp -a /etc/httpd/ /usr/local/mor/backups/

 
=== Method 1 (using yum packages) ===
Based on this [https://www.digitalocean.com/community/tutorials/how-to-secure-apache-with-let-s-encrypt-on-centos-7 guide]

yum install certbot python2-certbot-apache mod_ssl

if installation is completed without errors, run certbot command (prepare to answer yes/no questions and enter the domain name(s) and email)

certbot --apache

If the command is completed successfully, going to <nowiki>https://example.com/billing</nowiki> should show a secure connection

if everything is OK, test certificate renewal and install renewal cron
certbot renew --dry-run

If successful it should show at the end

Congratulations, all simulated renewals succeeded:
Congratulations, all simulated renewals succeeded:
/etc/letsencrypt/live/example.com/fullchain.pem (success)
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Create a cron to renew certificates automatically

echo "20 0,12 * * * root /usr/bin/certbot renew" > /etc/cron.d/certbot_renewal_cron
chmod 644 /etc/cron.d/certbot_renewal_cron
service crond restart

This will try to renew the certificate two times every day. Certbot will try to actually renew certificates once the expiration day will be less than 30 days

If you get an error:

Unable to find a virtual host listening on port 80 which is currently needed for Certbot to prove to the CA that you control your domain. Please add a virtual host for port 80.

That means there is a problem with <VirtualHost *:80> configuration in /etc/httpd/httpd.conf

Check with:

apachectl -t -D DUMP_VHOSTS

 
=== Method 2 (using snap management system) ===
To streamline the install process across different Linux Distributions, the Let's Encrypt official guide use snapd management system

If you want to use snaps, please use this guide:

https://certbot.eff.org/lets-encrypt/centosrhel7-apache.html

Using this installation method, automatic renewal will be configured automatically (it will be systemd timer, not a simple cron)
systemctl list-timers
NEXT LEFT LAST PASSED UNIT ACTIVATES
Tr 2021-10-06 12:42:00 CEST 41min left Tr 2021-10-06 05:11:01 CEST 6h ago snap.certbot.renew.timer snap.certbot.renew.service

 
== Logs ==
Let's encrypt log
/var/log/letsencrypt/letsencrypt.log

 
== Accessing switch without /billing suffix ==
Follow the guide [[I see Apache test on Start page| here]]

Use https instead of http and domain names instead of 127.0.0.1

How to set up SSL certificate with Let's Encrypt

2021-10-11T09:16:21Z

Mindaugas:

== About Let's Encrypt ==
[https://letsencrypt.org/ Let's Encrypt] provides free valid SSL certificates

 
== Before proceeding ==
To proceed the following is needed:
* Domain name pointed to switch IP (it is not possible to create a Let's Encrypt SSL certificate for IP address)
* Email address to get notifications from Let's Encrypt
* SSH access to switch server with root privileges

 
== Installation ==
In the example below let's assume that the domain name is example.com

Before installation, it is a good idea to backup /etc/httpd folder

cp -a /etc/httpd/ /usr/local/mor/backups/

 
=== Method 1 (using yum packages) ===
Based on this [https://www.digitalocean.com/community/tutorials/how-to-secure-apache-with-let-s-encrypt-on-centos-7 guide]

yum install certbot python2-certbot-apache mod_ssl

if installation is completed without errors, run certbot command (prepare to answer yes/no questions and enter the domain name(s) and email)

certbot --apache

If the command is completed successfully, going to <nowiki>https://example.com/billing</nowiki> should show a secure connection

if everything is OK, test certificate renewal and install renewal cron
certbot renew --dry-run

If successful it should show at the end

Congratulations, all simulated renewals succeeded:
Congratulations, all simulated renewals succeeded:
/etc/letsencrypt/live/example.com/fullchain.pem (success)
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Create a cron to renew certificates automatically

echo "20 0,12 * * * root /usr/bin/certbot renew" > /etc/cron.d/certbot_renewal_cron
chmod 644 /etc/cron.d/certbot_renewal_cron
service crond restart

This will try to renew the certificate two times every day. Certbot will try to actually renew certificates once the expiration day will be less than 30 days

If you get an error:

Unable to find a virtual host listening on port 80 which is currently needed for Certbot to prove to the CA that you control your domain. Please add a virtual host for port 80.

That means there is a problem with <VirtualHost *:80> configuration in /etc/httpd/httpd.conf

Check with:

apachectl -t -D DUMP_VHOSTS

 
=== Method 2 (using snap management system) ===
To streamline the install process across different Linux Distributions, the Let's Encrypt official guide use snapd management system

If you want to use snaps, please use this guide:

https://certbot.eff.org/lets-encrypt/centosrhel7-apache.html

Using this installation method, automatic renewal will be configured automatically (it will be systemd timer, not a simple cron)
systemctl list-timers
NEXT LEFT LAST PASSED UNIT ACTIVATES
Tr 2021-10-06 12:42:00 CEST 41min left Tr 2021-10-06 05:11:01 CEST 6h ago snap.certbot.renew.timer snap.certbot.renew.service

 
== Logs ==
Let's encrypt log
/var/log/letsencrypt/letsencrypt.log

 
== Accessing switch without /billing suffix ==
Follow the guide [[I see Apache test on Start page| here]]

Use https instead of http and domain names instead of 127.0.0.1

How to set up SSL certificate with Let's Encrypt

2021-10-11T09:16:12Z

Mindaugas:

== About Let's Encrypt ==
[[https://letsencrypt.org/ Let's Encrypt]] provides free valid SSL certificates

 
== Before proceeding ==
To proceed the following is needed:
* Domain name pointed to switch IP (it is not possible to create a Let's Encrypt SSL certificate for IP address)
* Email address to get notifications from Let's Encrypt
* SSH access to switch server with root privileges

 
== Installation ==
In the example below let's assume that the domain name is example.com

Before installation, it is a good idea to backup /etc/httpd folder

cp -a /etc/httpd/ /usr/local/mor/backups/

 
=== Method 1 (using yum packages) ===
Based on this [https://www.digitalocean.com/community/tutorials/how-to-secure-apache-with-let-s-encrypt-on-centos-7 guide]

yum install certbot python2-certbot-apache mod_ssl

if installation is completed without errors, run certbot command (prepare to answer yes/no questions and enter the domain name(s) and email)

certbot --apache

If the command is completed successfully, going to <nowiki>https://example.com/billing</nowiki> should show a secure connection

if everything is OK, test certificate renewal and install renewal cron
certbot renew --dry-run

If successful it should show at the end

Congratulations, all simulated renewals succeeded:
Congratulations, all simulated renewals succeeded:
/etc/letsencrypt/live/example.com/fullchain.pem (success)
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Create a cron to renew certificates automatically

echo "20 0,12 * * * root /usr/bin/certbot renew" > /etc/cron.d/certbot_renewal_cron
chmod 644 /etc/cron.d/certbot_renewal_cron
service crond restart

This will try to renew the certificate two times every day. Certbot will try to actually renew certificates once the expiration day will be less than 30 days

If you get an error:

Unable to find a virtual host listening on port 80 which is currently needed for Certbot to prove to the CA that you control your domain. Please add a virtual host for port 80.

That means there is a problem with <VirtualHost *:80> configuration in /etc/httpd/httpd.conf

Check with:

apachectl -t -D DUMP_VHOSTS

 
=== Method 2 (using snap management system) ===
To streamline the install process across different Linux Distributions, the Let's Encrypt official guide use snapd management system

If you want to use snaps, please use this guide:

https://certbot.eff.org/lets-encrypt/centosrhel7-apache.html

Using this installation method, automatic renewal will be configured automatically (it will be systemd timer, not a simple cron)
systemctl list-timers
NEXT LEFT LAST PASSED UNIT ACTIVATES
Tr 2021-10-06 12:42:00 CEST 41min left Tr 2021-10-06 05:11:01 CEST 6h ago snap.certbot.renew.timer snap.certbot.renew.service

 
== Logs ==
Let's encrypt log
/var/log/letsencrypt/letsencrypt.log

 
== Accessing switch without /billing suffix ==
Follow the guide [[I see Apache test on Start page| here]]

Use https instead of http and domain names instead of 127.0.0.1

How to set up SSL certificate with Let's Encrypt

2021-10-11T09:15:39Z

Mindaugas:

== About Let's Encrypt ==
Let's Encrypt provides free valid SSL certificates

== Before proceeding ==
To proceed the following is needed:
* Domain name pointed to switch IP (it is not possible to create a Let's Encrypt SSL certificate for IP address)
* Email address to get notifications from Let's Encrypt
* SSH access to switch server with root privileges

 
== Installation ==
In the example below let's assume that the domain name is example.com

Before installation, it is a good idea to backup /etc/httpd folder

cp -a /etc/httpd/ /usr/local/mor/backups/

 
=== Method 1 (using yum packages) ===
Based on this [https://www.digitalocean.com/community/tutorials/how-to-secure-apache-with-let-s-encrypt-on-centos-7 guide]

yum install certbot python2-certbot-apache mod_ssl

if installation is completed without errors, run certbot command (prepare to answer yes/no questions and enter the domain name(s) and email)

certbot --apache

If the command is completed successfully, going to <nowiki>https://example.com/billing</nowiki> should show a secure connection

if everything is OK, test certificate renewal and install renewal cron
certbot renew --dry-run

If successful it should show at the end

Congratulations, all simulated renewals succeeded:
Congratulations, all simulated renewals succeeded:
/etc/letsencrypt/live/example.com/fullchain.pem (success)
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Create a cron to renew certificates automatically

echo "20 0,12 * * * root /usr/bin/certbot renew" > /etc/cron.d/certbot_renewal_cron
chmod 644 /etc/cron.d/certbot_renewal_cron
service crond restart

This will try to renew the certificate two times every day. Certbot will try to actually renew certificates once the expiration day will be less than 30 days

If you get an error:

Unable to find a virtual host listening on port 80 which is currently needed for Certbot to prove to the CA that you control your domain. Please add a virtual host for port 80.

That means there is a problem with <VirtualHost *:80> configuration in /etc/httpd/httpd.conf

Check with:

apachectl -t -D DUMP_VHOSTS

 
=== Method 2 (using snap management system) ===
To streamline the install process across different Linux Distributions, the Let's Encrypt official guide use snapd management system

If you want to use snaps, please use this guide:

https://certbot.eff.org/lets-encrypt/centosrhel7-apache.html

Using this installation method, automatic renewal will be configured automatically (it will be systemd timer, not a simple cron)
systemctl list-timers
NEXT LEFT LAST PASSED UNIT ACTIVATES
Tr 2021-10-06 12:42:00 CEST 41min left Tr 2021-10-06 05:11:01 CEST 6h ago snap.certbot.renew.timer snap.certbot.renew.service

 
== Logs ==
Let's encrypt log
/var/log/letsencrypt/letsencrypt.log

 
== Accessing switch without /billing suffix ==
Follow the guide [[I see Apache test on Start page| here]]

Use https instead of http and domain names instead of 127.0.0.1

How to set up SSL certificate with Let's Encrypt

2021-10-11T09:15:15Z

Mindaugas: /* Accessing switch without /billing suffix */

== About Let's Encrypt ==
Let's Encrypt provides free valid SSL certificates

== Before proceeding ==
To proceed the following is needed:
* Domain name pointed to switch IP (it is not possible to create a Let's Encrypt SSL certificate for IP address)
* Email address to get notifications from Let's Encrypt
* SSH access to switch server with root privileges

== Installation ==
In the example below let's assume that the domain name is example.com

Before installation, it is a good idea to backup /etc/httpd folder

cp -a /etc/httpd/ /usr/local/mor/backups/

=== Method 1 (using yum packages) ===
Based on this [https://www.digitalocean.com/community/tutorials/how-to-secure-apache-with-let-s-encrypt-on-centos-7 guide]

yum install certbot python2-certbot-apache mod_ssl

if installation is completed without errors, run certbot command (prepare to answer yes/no questions and enter the domain name(s) and email)

certbot --apache

If the command is completed successfully, going to <nowiki>https://example.com/billing</nowiki> should show a secure connection

if everything is OK, test certificate renewal and install renewal cron
certbot renew --dry-run

If successful it should show at the end

Congratulations, all simulated renewals succeeded:
Congratulations, all simulated renewals succeeded:
/etc/letsencrypt/live/example.com/fullchain.pem (success)
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Create a cron to renew certificates automatically

echo "20 0,12 * * * root /usr/bin/certbot renew" > /etc/cron.d/certbot_renewal_cron
chmod 644 /etc/cron.d/certbot_renewal_cron
service crond restart

This will try to renew the certificate two times every day. Certbot will try to actually renew certificates once the expiration day will be less than 30 days

If you get an error:

Unable to find a virtual host listening on port 80 which is currently needed for Certbot to prove to the CA that you control your domain. Please add a virtual host for port 80.

That means there is a problem with <VirtualHost *:80> configuration in /etc/httpd/httpd.conf

Check with:

apachectl -t -D DUMP_VHOSTS

 
=== Method 2 (using snap management system) ===
To streamline the install process across different Linux Distributions, the Let's Encrypt official guide use snapd management system

If you want to use snaps, please use this guide:

https://certbot.eff.org/lets-encrypt/centosrhel7-apache.html

Using this installation method, automatic renewal will be configured automatically (it will be systemd timer, not a simple cron)
systemctl list-timers
NEXT LEFT LAST PASSED UNIT ACTIVATES
Tr 2021-10-06 12:42:00 CEST 41min left Tr 2021-10-06 05:11:01 CEST 6h ago snap.certbot.renew.timer snap.certbot.renew.service

 
== Logs ==
Let's encrypt log
/var/log/letsencrypt/letsencrypt.log

 
== Accessing switch without /billing suffix ==
Follow the guide [[I see Apache test on Start page| here]]

Use https instead of http and domain names instead of 127.0.0.1

How to set up SSL certificate with Let's Encrypt

2021-10-11T09:15:05Z

Mindaugas: /* Logs */

== About Let's Encrypt ==
Let's Encrypt provides free valid SSL certificates

== Before proceeding ==
To proceed the following is needed:
* Domain name pointed to switch IP (it is not possible to create a Let's Encrypt SSL certificate for IP address)
* Email address to get notifications from Let's Encrypt
* SSH access to switch server with root privileges

== Installation ==
In the example below let's assume that the domain name is example.com

Before installation, it is a good idea to backup /etc/httpd folder

cp -a /etc/httpd/ /usr/local/mor/backups/

=== Method 1 (using yum packages) ===
Based on this [https://www.digitalocean.com/community/tutorials/how-to-secure-apache-with-let-s-encrypt-on-centos-7 guide]

yum install certbot python2-certbot-apache mod_ssl

if installation is completed without errors, run certbot command (prepare to answer yes/no questions and enter the domain name(s) and email)

certbot --apache

If the command is completed successfully, going to <nowiki>https://example.com/billing</nowiki> should show a secure connection

if everything is OK, test certificate renewal and install renewal cron
certbot renew --dry-run

If successful it should show at the end

Congratulations, all simulated renewals succeeded:
Congratulations, all simulated renewals succeeded:
/etc/letsencrypt/live/example.com/fullchain.pem (success)
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Create a cron to renew certificates automatically

echo "20 0,12 * * * root /usr/bin/certbot renew" > /etc/cron.d/certbot_renewal_cron
chmod 644 /etc/cron.d/certbot_renewal_cron
service crond restart

This will try to renew the certificate two times every day. Certbot will try to actually renew certificates once the expiration day will be less than 30 days

If you get an error:

Unable to find a virtual host listening on port 80 which is currently needed for Certbot to prove to the CA that you control your domain. Please add a virtual host for port 80.

That means there is a problem with <VirtualHost *:80> configuration in /etc/httpd/httpd.conf

Check with:

apachectl -t -D DUMP_VHOSTS

 
=== Method 2 (using snap management system) ===
To streamline the install process across different Linux Distributions, the Let's Encrypt official guide use snapd management system

If you want to use snaps, please use this guide:

https://certbot.eff.org/lets-encrypt/centosrhel7-apache.html

Using this installation method, automatic renewal will be configured automatically (it will be systemd timer, not a simple cron)
systemctl list-timers
NEXT LEFT LAST PASSED UNIT ACTIVATES
Tr 2021-10-06 12:42:00 CEST 41min left Tr 2021-10-06 05:11:01 CEST 6h ago snap.certbot.renew.timer snap.certbot.renew.service

 
== Logs ==
Let's encrypt log
/var/log/letsencrypt/letsencrypt.log

== Accessing switch without /billing suffix ==
Follow the guide [[I see Apache test on Start page| here]]

Use https instead of http and domain names instead of 127.0.0.1

How to set up SSL certificate with Let's Encrypt

2021-10-11T09:14:27Z

Mindaugas: /* Method 2 (using snap management system) */

== About Let's Encrypt ==
Let's Encrypt provides free valid SSL certificates

== Before proceeding ==
To proceed the following is needed:
* Domain name pointed to switch IP (it is not possible to create a Let's Encrypt SSL certificate for IP address)
* Email address to get notifications from Let's Encrypt
* SSH access to switch server with root privileges

== Installation ==
In the example below let's assume that the domain name is example.com

Before installation, it is a good idea to backup /etc/httpd folder

cp -a /etc/httpd/ /usr/local/mor/backups/

=== Method 1 (using yum packages) ===
Based on this [https://www.digitalocean.com/community/tutorials/how-to-secure-apache-with-let-s-encrypt-on-centos-7 guide]

yum install certbot python2-certbot-apache mod_ssl

if installation is completed without errors, run certbot command (prepare to answer yes/no questions and enter the domain name(s) and email)

certbot --apache

If the command is completed successfully, going to <nowiki>https://example.com/billing</nowiki> should show a secure connection

if everything is OK, test certificate renewal and install renewal cron
certbot renew --dry-run

If successful it should show at the end

Congratulations, all simulated renewals succeeded:
Congratulations, all simulated renewals succeeded:
/etc/letsencrypt/live/example.com/fullchain.pem (success)
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Create a cron to renew certificates automatically

echo "20 0,12 * * * root /usr/bin/certbot renew" > /etc/cron.d/certbot_renewal_cron
chmod 644 /etc/cron.d/certbot_renewal_cron
service crond restart

This will try to renew the certificate two times every day. Certbot will try to actually renew certificates once the expiration day will be less than 30 days

If you get an error:

Unable to find a virtual host listening on port 80 which is currently needed for Certbot to prove to the CA that you control your domain. Please add a virtual host for port 80.

That means there is a problem with <VirtualHost *:80> configuration in /etc/httpd/httpd.conf

Check with:

apachectl -t -D DUMP_VHOSTS

 
=== Method 2 (using snap management system) ===
To streamline the install process across different Linux Distributions, the Let's Encrypt official guide use snapd management system

If you want to use snaps, please use this guide:

https://certbot.eff.org/lets-encrypt/centosrhel7-apache.html

Using this installation method, automatic renewal will be configured automatically (it will be systemd timer, not a simple cron)
systemctl list-timers
NEXT LEFT LAST PASSED UNIT ACTIVATES
Tr 2021-10-06 12:42:00 CEST 41min left Tr 2021-10-06 05:11:01 CEST 6h ago snap.certbot.renew.timer snap.certbot.renew.service

== Logs ==
Let's encrypt log
/var/log/letsencrypt/letsencrypt.log

== Accessing switch without /billing suffix ==
Follow the guide [[I see Apache test on Start page| here]]

Use https instead of http and domain names instead of 127.0.0.1

How to set up SSL certificate with Let's Encrypt

2021-10-11T09:14:02Z

Mindaugas: /* Method 1 (using yum packages) */

== About Let's Encrypt ==
Let's Encrypt provides free valid SSL certificates

== Before proceeding ==
To proceed the following is needed:
* Domain name pointed to switch IP (it is not possible to create a Let's Encrypt SSL certificate for IP address)
* Email address to get notifications from Let's Encrypt
* SSH access to switch server with root privileges

== Installation ==
In the example below let's assume that the domain name is example.com

Before installation, it is a good idea to backup /etc/httpd folder

cp -a /etc/httpd/ /usr/local/mor/backups/

=== Method 1 (using yum packages) ===
Based on this [https://www.digitalocean.com/community/tutorials/how-to-secure-apache-with-let-s-encrypt-on-centos-7 guide]

yum install certbot python2-certbot-apache mod_ssl

if installation is completed without errors, run certbot command (prepare to answer yes/no questions and enter the domain name(s) and email)

certbot --apache

If the command is completed successfully, going to <nowiki>https://example.com/billing</nowiki> should show a secure connection

if everything is OK, test certificate renewal and install renewal cron
certbot renew --dry-run

If successful it should show at the end

Congratulations, all simulated renewals succeeded:
Congratulations, all simulated renewals succeeded:
/etc/letsencrypt/live/example.com/fullchain.pem (success)
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Create a cron to renew certificates automatically

echo "20 0,12 * * * root /usr/bin/certbot renew" > /etc/cron.d/certbot_renewal_cron
chmod 644 /etc/cron.d/certbot_renewal_cron
service crond restart

This will try to renew the certificate two times every day. Certbot will try to actually renew certificates once the expiration day will be less than 30 days

If you get an error:

Unable to find a virtual host listening on port 80 which is currently needed for Certbot to prove to the CA that you control your domain. Please add a virtual host for port 80.

That means there is a problem with <VirtualHost *:80> configuration in /etc/httpd/httpd.conf

Check with:

apachectl -t -D DUMP_VHOSTS

=== Method 2 (using snap management system) ===
To streamline the install process across different Linux Distributions, the Let's Encrypt official guide use snapd management system

If you want to use snaps, please use this guide:

https://certbot.eff.org/lets-encrypt/centosrhel7-apache.html

Using this installation method, automatic renewal will be configured automatically (it will be systemd timer, not a simple cron)
systemctl list-timers
NEXT LEFT LAST PASSED UNIT ACTIVATES
Tr 2021-10-06 12:42:00 CEST 41min left Tr 2021-10-06 05:11:01 CEST 6h ago snap.certbot.renew.timer snap.certbot.renew.service

== Logs ==
Let's encrypt log
/var/log/letsencrypt/letsencrypt.log

== Accessing switch without /billing suffix ==
Follow the guide [[I see Apache test on Start page| here]]

Use https instead of http and domain names instead of 127.0.0.1

M4 Local Number Portability

2021-10-08T10:07:50Z

Mindaugas: Created page with 'Documentation WIP = Intra/Inter/Indeter ='

Documentation WIP

= Intra/Inter/Indeter =

M4 Switch Manual

2021-10-08T10:06:19Z

Mindaugas: /* Routing */

<div align="center">
[[File:m2_logo.png|800px|link=|alt="M2 Class 4 Softswitch"]]
 
<center>M2 is class 4 softswitch with Billing and Routing with extended functionality, increased stability and professional support directly from the developers. It enables VoIP providers to offer wholesale/transit services.</center>
</div>
 

= General Info =

* [[M2 Switch | Introduction]]
* [[M2 Functionality]]
* [[M2 Network Architecture]]
* [[M4 System Architecture]]
* Codecs
** [[M2 Supported Codecs]]
** [[M2 Codec Negotiation]]
** [[M4 Supported Codecs]]
* [[M2 API]]
* [[M2 video demonstrations]]
* [[M2 Changelog]]

 

= Configuration =

* [[M2 Users | Users]]
* [[system.conf]]
* [[Performance Suggestions M2 | Performance Suggestions]]
* [[Destination Groups Policy]]
* [[Move MOR Database to M2]]
* [[M2 Caching]]
* [[M4 Media Bypass|Media Bypass]]
* [[M4 RPID/PAI | RPID/PAI]]

 

= Routing =

* [[M2 Routing Logic | Routing Logic]]
* [[M2 Regexp Examples|Regexp Examples]]
* [[M2_Connection_Points | Connection Points]]
** [[M2 Termination Points | Termination Points (TP) ]]
*** [[M2 TP Call Limit | TP Call Limit]]
** [[M2 Origination Points | Origination Points (OP) ]]
* [[M2 Source Transformation | Source Transformation]]
* [[M2 Destination Transformation | Destination Transformation]]
* [[M2 Routing Groups | Routing Groups (RG) ]]
* [[M2 Quality Routing | Quality Routing]]
* [[M2 Dial Peers | Dial Peers (DP) ]]
* [[M2_Directions_and_Destinations | Directions and Destinations]]
* [[M2_How_to_block_calls | How to block calls]]
* [[M2_Mobile_Number_Portability | Mobile Number Portability]]
* [[M4_Local_Number_Portability | Local Number Portability - US Jurisdictional Routing]]
 

= Billing =

* [[M2 Tariffs| Tariffs]]
* [[M2_Custom_Tariffs | Custom Tariffs]]
* [[M2_CDR_Disputes | CDR Disputes]]
* [[M2 EU Roaming Regulations | EU Roaming Regulations]]
* [[M2 Rates | Rates]]
** [[M2 Rate Notification | Rate Notifications]]
** [[M2 Blocked Rates | Blocked Rates]]
** [[M2 Work Days and Free Days | Work Days and Free Days]]
 

= Accounting =

* [[M2 Payments | Payments]]
* [[M2 Customer Invoices| Customer Invoices]]
* [[M2 Supplier Invoices| Supplier Invoices]]
* [[M2_CDR_Rerating | CDR Rerating]]
 

= Reporting =

* [[M2_Aggregates | Aggregates]]
* [[M2_Calls_by_Clients | Calls by Clients]]
* [[M2_Calls_List | Calls List]]
* [[M2_Quick_Stats | Quick Stats]]
* [[M2 Balance Report | Balance Report]]
* [[M2 Financial Status|Financial Status]]
* [[M2 CSV Export | CSV Export]]
* [[M2 Reports Examples | Reports Examples]]
* [[M2 Destination Groups Stats | Destination Groups Stats]]
* [[M2_Load_Stats | Load Stats]]
* [[M2_Calls_Dashboard | Calls Dashboard]]
* [[M2_Terminator_Active_Calls| Terminator Active Calls]]
 

= Maintenance/Troubleshooting =

* [[M2 Access Levels | Access Levels]]
* [[M2 CDR Management | CDR Management]]
* [[M2 Hangupcause Codes | Hangupcause Codes]]
** [[M2 Disconnect Code Changes | Disconnect Code Changes]]
* [[M4 Disconnect Codes]]
* [[M2 Warning Balance | Warning Balance]]
* [[M2 Alerts | Alerts]]
* [[Freeswitch]]
** [https://wiki.freeswitch.org/wiki/Codecs#Transcodable_codecs Freeswitch Codecs]
** [https://wiki.freeswitch.org/wiki/Codec_Negotiation Freeswitch Codec Negotiation]
** [[Freeswitch under NAT]]
** [[Freeswitch Port Range]]
** [[Freeswitch SNMP]]
* [[M2 Number Pools|Number Pools]]
* [[M2 Directions | Directions]]
* [[M2 Call Tracing | Call Tracing]]
* [[M2 Call Info | Call Info]]
* [[M2_disable_Q.850_Reason_header | Disable Q.850 Reason header]]
 

= Security =

* [[M2_Blocked_IPs | Block IPs]]
* [[M2_Blocked_Countries | Block Countries]]
* [[M2_Login_Failure_Report | Login_Failure_Report]]
* [[M2_Login_with_approved_IP%27s | Login with approved IP's]]
 

= I Have a Problem =

* [[M2_Ports_which_should_be_opened | Ports which should be opened]]
* [[Call Count Bigger That What We Can Process]]
* [[Sometimes Users Blocked Automatically]]
 

= User Portal =

* [[M2 User Dashboard | Dashboard]]
 

= Tutorials =

* [[M2 How to make first call | How to make first call]]
* [[M2 video demonstrations]]

M4 Switch Manual

2021-10-08T10:04:29Z

Mindaugas: /* Configuration */

<div align="center">
[[File:m2_logo.png|800px|link=|alt="M2 Class 4 Softswitch"]]
 
<center>M2 is class 4 softswitch with Billing and Routing with extended functionality, increased stability and professional support directly from the developers. It enables VoIP providers to offer wholesale/transit services.</center>
</div>
 

= General Info =

* [[M2 Switch | Introduction]]
* [[M2 Functionality]]
* [[M2 Network Architecture]]
* [[M4 System Architecture]]
* Codecs
** [[M2 Supported Codecs]]
** [[M2 Codec Negotiation]]
** [[M4 Supported Codecs]]
* [[M2 API]]
* [[M2 video demonstrations]]
* [[M2 Changelog]]

 

= Configuration =

* [[M2 Users | Users]]
* [[system.conf]]
* [[Performance Suggestions M2 | Performance Suggestions]]
* [[Destination Groups Policy]]
* [[Move MOR Database to M2]]
* [[M2 Caching]]
* [[M4 Media Bypass|Media Bypass]]
* [[M4 RPID/PAI | RPID/PAI]]

 

= Routing =

* [[M2 Routing Logic | Routing Logic]]
* [[M2 Regexp Examples|Regexp Examples]]
* [[M2_Connection_Points | Connection Points]]
** [[M2 Termination Points | Termination Points (TP) ]]
*** [[M2 TP Call Limit | TP Call Limit]]
** [[M2 Origination Points | Origination Points (OP) ]]
* [[M2 Source Transformation | Source Transformation]]
* [[M2 Destination Transformation | Destination Transformation]]
* [[M2 Routing Groups | Routing Groups (RG) ]]
* [[M2 Quality Routing | Quality Routing]]
* [[M2 Dial Peers | Dial Peers (DP) ]]
* [[M2_Directions_and_Destinations | Directions and Destinations]]
* [[M2_How_to_block_calls | How to block calls]]
* [[M2_Mobile_Number_Portability | Mobile Number Portability]]
 

= Billing =

* [[M2 Tariffs| Tariffs]]
* [[M2_Custom_Tariffs | Custom Tariffs]]
* [[M2_CDR_Disputes | CDR Disputes]]
* [[M2 EU Roaming Regulations | EU Roaming Regulations]]
* [[M2 Rates | Rates]]
** [[M2 Rate Notification | Rate Notifications]]
** [[M2 Blocked Rates | Blocked Rates]]
** [[M2 Work Days and Free Days | Work Days and Free Days]]
 

= Accounting =

* [[M2 Payments | Payments]]
* [[M2 Customer Invoices| Customer Invoices]]
* [[M2 Supplier Invoices| Supplier Invoices]]
* [[M2_CDR_Rerating | CDR Rerating]]
 

= Reporting =

* [[M2_Aggregates | Aggregates]]
* [[M2_Calls_by_Clients | Calls by Clients]]
* [[M2_Calls_List | Calls List]]
* [[M2_Quick_Stats | Quick Stats]]
* [[M2 Balance Report | Balance Report]]
* [[M2 Financial Status|Financial Status]]
* [[M2 CSV Export | CSV Export]]
* [[M2 Reports Examples | Reports Examples]]
* [[M2 Destination Groups Stats | Destination Groups Stats]]
* [[M2_Load_Stats | Load Stats]]
* [[M2_Calls_Dashboard | Calls Dashboard]]
* [[M2_Terminator_Active_Calls| Terminator Active Calls]]
 

= Maintenance/Troubleshooting =

* [[M2 Access Levels | Access Levels]]
* [[M2 CDR Management | CDR Management]]
* [[M2 Hangupcause Codes | Hangupcause Codes]]
** [[M2 Disconnect Code Changes | Disconnect Code Changes]]
* [[M4 Disconnect Codes]]
* [[M2 Warning Balance | Warning Balance]]
* [[M2 Alerts | Alerts]]
* [[Freeswitch]]
** [https://wiki.freeswitch.org/wiki/Codecs#Transcodable_codecs Freeswitch Codecs]
** [https://wiki.freeswitch.org/wiki/Codec_Negotiation Freeswitch Codec Negotiation]
** [[Freeswitch under NAT]]
** [[Freeswitch Port Range]]
** [[Freeswitch SNMP]]
* [[M2 Number Pools|Number Pools]]
* [[M2 Directions | Directions]]
* [[M2 Call Tracing | Call Tracing]]
* [[M2 Call Info | Call Info]]
* [[M2_disable_Q.850_Reason_header | Disable Q.850 Reason header]]
 

= Security =

* [[M2_Blocked_IPs | Block IPs]]
* [[M2_Blocked_Countries | Block Countries]]
* [[M2_Login_Failure_Report | Login_Failure_Report]]
* [[M2_Login_with_approved_IP%27s | Login with approved IP's]]
 

= I Have a Problem =

* [[M2_Ports_which_should_be_opened | Ports which should be opened]]
* [[Call Count Bigger That What We Can Process]]
* [[Sometimes Users Blocked Automatically]]
 

= User Portal =

* [[M2 User Dashboard | Dashboard]]
 

= Tutorials =

* [[M2 How to make first call | How to make first call]]
* [[M2 video demonstrations]]

Configuration from GUI

2021-10-07T09:02:55Z

Mindaugas: /* Emails */

=Where I can find this settings menu?=

You can find this menu in '''SETTINGS –> Setup –> Settings'''

[[File:Settings_path.png]]
 
== Global ==

'''SETTINGS –> Setup –> Settings –> [[Global_Settings | Global]]'''

* '''Company''' – name of the company.
* '''Company email''' – email address of the company.
* '''Version''' – version number.
* '''Copyright Title''' – copyright title supports html text format.
* '''Browser Title''' – browser title for MOR GUI.
* '''Front Page Text''' – some text to place on front page.
* '''Login Page Text''' – some text to place on login page
 

== Registration ==

'''SETTINGS –> Setup –> Settings –> Registration'''

* '''Enabled?''' – do we want to let users [[Online registration | register online]] automatically?
* '''Hide registration link in Login page?''' – tick this option if you do not want users to be able to register online.
* '''Default country'''
* '''Asterisk server IP''' – what IP should user connect his softphone/server to?
* '''Send Email to User after registration''' – just yes or no.
* '''Send Email to Admin after registration''' – just yes or no.
* '''Send Email To User after User was created''' – just yes or no.
* '''Send Email To Admin after User was created''' – just yes or no.
* '''[[ReCAPTCHA]] configuration'''
* '''[[User_Agreement|Terms and conditions]]'''
* '''Allow to create user and device with matching username and password''' – just yes or no. If this setting is not enabled - username and password from MOR GUI will have to be different than device's username and password.
* '''Enable VAT checking for EU companies''' – you can choose whether to check '''TAX Registration Number:''' during the [[Online registration]] or not. Done over [http://ec.europa.eu/taxation_customs/vies/?locale=lt EU page].
* '''Allow blank VAT for EU companies''' – allows to leave blank '''TAX Registration Number:''' field during the [[Online registration]]
 
===See also===

* [[Default user]]
 

== Invoices ==

'''SETTINGS –> Setup –> Settings –> Invoices'''

Invoice configuration is divided into '''Prepaid''' and '''Postpaid'''.
 
=== Settings ===

* '''Number start''' – how the invoice number should start.
* '''Number length''' – the length in digits AFTER Number Start – e.g. Number Start is not counted into this length. This value is active only for first number type.
* '''Number type''' – select more appropriate number format.
* '''Invoice period start''' – when invoices are issued, default is first day of the month.
* '''Show calls in detailed invoice''' – yes or no.
* '''[[Outstanding balance(Debt) | Show balance line]]''' – shows balance line in Invoice PDF files when Invoice is generated from first day of month till last one.
* '''Round finals to 2 decimals''' – round or not total in Invoices to 2 decimals.
* '''Use short file name'''
* '''Group Subscriptions''' - User's subscriptions will be grouped by service (only applies to PDF and XLSX invoice).
* '''Show Quantity''' - Show quantity of each service (only applies to PDF invoice).
* '''Invoice Page Limit:''' – invoice will be generated till this page limit. Additional page is added with an explanation that page limit was reached.
* ''' Rename 'DID owner cost' label in detailed PDF invoice:''' – text which will be used instead of '''DID owner cost''' in detailed PDF invoice.
* ''' Hide 'DID owner cost' line in detailed PDF invoice:''' – checkbox, which control whether or not DID owner cost should be shown in detailed PDF invoice.
* ''' Show Destination with Prefix in Detailed Invoice:''' - checkbox, if enabled, destination will be shown as '''Destination Name (prefix)'''.
* ''' Rename red 'INVOICE' label in Simplified PDF Invoice:'''
* ''' Rename red 'INVOICE' label in Detailed PDF Invoice:'''
* ''' Rename red 'INVOICE' label in PDF Invoice by CallerID:'''
 

=== Details ===

* '''Address format''' – changes field positioning in the invoice for the address. You must select it in order to show address in the invoice.
* '''Address line 1-4''' – address info.
* '''Bank details line 1-5''' – bank details info.
* '''Invoice balance line''' – line for balance (e.g. "Your current balance is")
* '''Invoice to pay Line'''
* '''End title''' – a title for the end of your invoice.

* '''Add Average rate in detailed invoice''' – adds average rate in detailed invoice.
* '''Show Time in Minute''' – shows time in mm:ss instead of hh:mm:ss, for example, not 02:13:42 but 133:42.
 

=== Additional ===

* '''Show additional details on separate page''' – enables additional custom page at the end of the invoice.
* '''Additional details''' – the information to be displayed in a custom page at the end of the invoice.
 
=== Functionality ===

* '''Invoice allow recalculate after send''' – allows recalculating invoices after being sent.
* '''Do not generate Invoices for blocked Users''' - if enabled Invoices will not be generated for blocked Users.
* '''Rename "Calls" label''' - changes 'Calls' name for Simplified Invoices and new Invoice XLSX. If you want to apply new 'Calls' name for old XLSX, you should go to Settings > Invoices > XLSX and mark 'New XLSX template apply for old Invoices'
* '''Start value for Invoice numbers''' - defines number from which Invoices numeration should start.
* '''Duration Format:''' - time format in invoice. This setting applies for XLSX type invoices (and PDF invoices generated from XLSX invoice) and Invoice Details page. Available options - 'H:M:S', 'H:M', 'M'. When option 'M' is used, sub option Decimal places appear, where you can select precision.
* '''Invoice Group By: Prefix / Destination'''
* '''Show Rates:No / Yes'''

 

=== XLSX ===
* '''XLSX Template''' - choose XLSX Template for Invoices.
* '''Send XLSX Invoices converted to PDF''' – If enabled XLSX invoices will be converted to PDF before sending over [[Invoices#Send_invoices_by_email_.28manual.29|Email]] or [[Cron_actions#Generate_Invoices_and_send_by_Email|using cron action]]
* '''Group regular Calls by Destination''' - Groups regular Calls be destination
 

===See also===

* [[Invoices]]
* [[Invoice configuration]]
 

== Emails ==

'''SETTINGS –> Setup –> Settings –> Emails'''

* ''' Sending globally enabled''' – if this is checked, you will be able to use Mass Mailing and the system will send emails upon user registration.
* ''' Add recipient first name and last name''' – if this is checked, it will show the user's first name and last name if they are entered in the User Settings.
* '''SMTP server''' – hostname of the server.
* '''Port''' – port of SMTP server.
* '''Login''' – username to your SMTP server.
* '''Password''' – password to your SMTP server.
* '''Batch size''' – value for Mass Mailing, or how many emails to send at once.
* '''From''' – email address to put into From: field in email. Acceptable formats are: '''example@email.com''' or '''John Smith <example@email.com>'''.
* '''Test email sending''' – save settings and press this to test email sending. Do not forget to save settings first!

'''P.S. Remember to set admin's e-mail in admin's personal settings. Without this test email sending will not work!'''

 
===See also===

* [[Emails|Mass Emails]]
* [[Email variables]]
 

== Various ==

'''SETTINGS –> Setup –> Settings –> Various'''

* '''Days for DID to close''' – how long to keep DID closed before making it free.
* '''Agreement number length''' – number length in digits.
* '''Change dahdi''' – Sometimes this is used to change "Zap" to something else in GUI, e.g. to "PSTN", mainly because not everybody knows what Zap stands for. PSTN is more common.
* '''Device PIN length''' – length for automatically generated PIN codes for devices.
* '''Device range MIN''' – from which extension automatic extension assigning starts.
* '''Device range MAX''' – till which extension automatic extension assigning goes.
** For example, from this interval: [Device range MIN, Device range MAX] MOR will select extensions for newly created Devices.
* '''Random Device Extension''' – when creating device, random number from '''Device Range''' will be taken.
* '''Enable "Allowed addresses" option for Devices:''' – allows [[Device_settings#Allowed_Addresses | Allowed Addresses]] functionality in Devices settings.
* '''Enable "Allowed addresses" option for Providers:''' – allows Allowed Addresses functionality in Providers settings.
* '''User wholesale tariff enabled''' – enables user wholesale tariffs.
* '''Play IVR for unauthenticated call'''
* '''Banned CLIs default IVR''' – default IVR to route banned numbers.
* '''Do not allow duplicate device user names'''
* '''Do not allow users to change their email addresses'''
* '''Logout link''' – a user will be redirected to this link after pressing "Logout"
* '''Change ANSWER to FAILED if HGC not equal to 16 for Users''' – changes the Hangupcause for users in call reports from Answered to Failed if Hangupcause is not 16.
* '''Inform when Devices are created or updated''' – check to get email about every newly created or updated Device.
* '''Show Usernames on PDF/CSV Export Files in Last Calls''' – if checked, when particular User in Last Calls page search is selected, Last Calls PDF/CSV file name will be composed also from Name of selected User. If you are looking for All Users, no User Name will be used. (Name of User will be shown in Name of CSV/PDF file).
* '''Do not allow PREPAID User balance drop below zero (block them instead)'''

* '''Do not block POSTPAID User when balance goes bellow zero on subscription count'''
* '''Allow identical email addresses to different Users''' – allows to create Users or Register users with identical email addresses. After checking this setting you will be not able to check '''Show forgot password''', because this functionality require unique email in all system. Setting can be unchecked if all emails are unique in system.
* '''Allow same IP and Port combinations in multiple Devices''' – allows to create Devices with the same IP and Port combination.
* '''Low Disk Space Alert''' – indicator when system should inform admin about low [[Multi_Server_support|Server]] space. By default 20%. Notice will appear in [[Integrity Check]] and every hour will send an email "Low Disk Space Alert". Which template can be found and edited in [[Emails]] page. Information about the Server and the remaining free space will be provided.
* '''Limit PDF size in Last Calls''' - limits how many pages can be exported from Last Calls to PDF. It takes a lot of system resources to generate PDF files therefore this limit should be low enough to prevent high load on system.
* '''Google Maps API key''' - the setting is necessary for using the Google Maps functionality. More on how to configure this key please check [[Get Google Maps key]].
* '''Allow login by email''' - allow users to login by email instead of username.
* '''Call Forwarding CallerID''' - allows to manage CallerID when [http://wiki.kolmisoft.com/index.php/Call_Flow#Change_Forward_action_by_Call forwarding is set by call].
** '''From Device''' - puts CallerID for the Device that is forwarding the call. If Device CallerID is empty, then originator's CallerID will be used.
** '''Same as comes - unchanged''' - leaves the CallerID as it comes from the originator.
** '''Same as comes - with Diversion''' - leaves the CallerID as it comes from the original caller and additionally adds SIP header Diversion with CallerID from the Device that is forwarding the call (header will not be added if Device does not have CallerID set).
* '''DID for Unassigned DID''' - this feature is used for calls coming from providers to system DIDs. Allows to redirect call to specific DID if client dials non existent DID. If empty, then this feature is disabled and call will be terminated with [http://wiki.kolmisoft.com/index.php/207_Not_clear_who_should_receive_call 207 Not clear who should receive call] hangup code.
* '''Default Music On Hold''' - allows to select Default Music On Hold.
* '''Use Extension in CallerID for Local Calls''' - overwrites original CallerID with Device Extension when making local calls. Outside calls are not affected by this setting.
*'''Send Recordings space warning Email''' - sends Email to Admin once a day if recordings exceed space limit.
*'''Hide Provider Payments from User Payment List''' - default off.

== Tax ==

'''SETTINGS –> Setup –> Settings –> Tax'''

Settings are explained here: [[Multi-Tax system]]
 
== Backups ==

'''SETTINGS –> Setup –> Settings –> Backups'''

Configuration is explained here: [[Backup system]]
 
== API ==

'''SETTINGS –> Setup –> Settings –> API'''

* '''Allow API''' – enable/disable API.
* '''Allow GET API''' – enable/disable GET in API - use only for testing!
* '''API Secret Key''' – secret key for API. This will be used as a password for signing queries to MOR API, check [[MOR_API | MOR API documentation]] for more information
* '''XML API Extension''' – .NET does not follow standards (surprise!); enable this setting if you are using it to get XML starting with HTTP tags.
* '''Allow API Login Redirect''' – enable/disable
* '''API allow registration''' – enable/disable registration through API
* '''API allow Payments''' – enable/disable payments through API
* '''API Payment confirmation''' – enable/disable payments confirmation through API
* '''[[Balance_in_phone|Allow devices to check balance over HTTP]]''' – enable/disable device balance checking
* '''[[MOR_API_rate_get|Allow devices to check rate over HTTP]]''' – enable/disable device rate checking
* '''Disable hash checking''' – lets you skip hash parameter using API
* '''Uniquehash''' – shows your uniquehash
* '''Send Email To Admin after API/Manual Payment''' - sends Email to Admin after API/Manual payment.
* '''Send Email to User after API/Manual Payment''' - sends Email to User after API/Manual payment.
* '''Send Email To Admin after API/Balance Update''' - sends Email to Admin after API/Balance Update.
 
===See also===

[[MOR API]]
 

== Functionality ==

'''SETTINGS –> Setup –> Settings –> Functionality'''
 
===FAX===

* '''Fax device enabled''' – enable/disable Fax device in MOR. When admin enables FAX, Functionality tab appears in Reseller's GUI configuration. He can then enable or disabled fax for his own users himself.
* '''Fax2Email From Sender''' – there is a field "From:" in an email form. When MOR sends Fax to Email, "Fax2Email From Sender" value is displayed in "From:" field.
* '''Allow Users to change FAX email''' - allow simple Users to add/remove/edit FAX emails in FAX Devices.
 

===CSV===

* '''CSV Column Separator''' – how columns are separated in imported/exported CSV files.
* '''CSV Decimal Separator''' – how decimal parts in numbers are separated in imported/exported CSV files.
* ''' Archive CSV file when size reaches''' – if CSV file reaches a certain size, the system will archive it to save time to download it (0 means to archive always)
 
===Active Calls===

* '''How many maximum [[Active_Calls|Active Calls]] to show in GUI''' – how many [[Active_Calls| Active Calls]] to show in GUI
* '''[[Active_Calls| Active Calls]] refresh interval''' – [[Active_Calls|Active Calls]] refresh interval in seconds
* '''Show [[Active_Calls|Active Calls]] for Users''' – tick if you want to allow users to see [[Active_Calls|Active Calls]]
* '''Show Servers in [[Active_Calls|Active Calls]]'''
* '''Show DIDs in [[Active_Calls|Active Calls]]'''
* '''Show localized Source in [[Active_Calls|Active Calls]]''' - if set, [[Active_Calls|Active Calls]] will show callerid number after localisations (if any) have been applied.
 

===Tariffs/Rates===

* '''Show rates for users''' – allows users to see rates
* '''Show rates without Tax''' – shows rates without TAX
* '''Show [[Advanced_Rates|Advanced Rates]] for users''' – allows users to see [[Advanced_Rates|Advanced Rates]]
* '''Show zero rates in LCR tariff export:''' – shows zero rates in LCR tariff exported file.
NOTE: if [[Custom Rates]] and/or Tariff Rates are set for the user, only the custom rates will be shown in the details of destination rates.
 

===Statement of Account===
* ''' PDF Settings ''' - allows to put Address lines of PDF file for Statement of Account.
*Address line 1: Street Address
*Address line 2: City, Country
*Address line 3: Phone, fax
*Address line 4: Web, email
*Bank details line 1
*Bank details line 2
*Bank details line 3
*Bank details line 4
*Bank details line 5
*Bank details line 6
*Bank details line 7
*Bank details line 8
 

==Privacy==

'''SETTINGS –> Setup –> Settings –> Privacy'''

* '''[[Privacy_to_hide_Destination_ends|Privacy to hide Destination ends]]'''
* '''[[GDPR]] Activated''' – hides User data with notification "Data hidden due GDPR. Press to show data (action will be logged)". Valid for Admin, Accountant, Reseller and Partner.

== Visual ==

'''SETTINGS –> Setup –> Settings –> Visual'''

* '''Items per page''' – the number of items to display per one page
* '''[[Global_date_format| Default date format]]''' – System default date format
* '''Default Time Format''' – System default time format
* '''Number digits''' – how many digits to display after a comma
* '''Hide Quick Stats in Start page''' – hide Quick stats from start page
* '''Hide device passwords for users''' – do not display device passwords for users
* '''Hide "Information about this page" link''' – hide HELP banner in GUI
* '''Hide "I want to" help links'''
* '''[[Remove_Manual_link_from_admin_GUI|Hide "Manual" link]]''' – hides "Manual" link
* '''Show logo on first page''' - untick to hide logo on the start page
* '''Show Full Source (CallerID Name and Number)'''
* '''Use <> brackets in CDR export''' - changes brackets in CDR export
* '''Hide payment options for postpaid users''' - will hide the payment option for all postpaid users (including Resellers if they are postpaid).
* '''Hide non-completed payments for user''' – hides non-completed payments (the ones which are started in MOR, but are not completed in a payment gateway website)
* '''Show only main page''' – this is a very advanced feature for those who want to hide default MOR menu tree on the left so that they could build their own menu using advanced techniques without modifying MOR GUI sources.
* '''Show forgot password''' – turns on '''[[MOR_forgot_user_password | Forgot password]]''' functionality.
* '''Hide Recordings for all users''' – hides recordings for all system users from menu and device settings.
* '''Show recordings with zero billsec''' – shows recordings with zero billsec
* '''Default Number Decimal''' – with this option you can set default number decimal for all GUI
* '''Show user_billsec for Users instead of billsec''' – shows user_billsec instead of billsec in Users invoices and last calls. Notice that Billsec shows real Call duration, user_billsec shows Call duration after minimal time or increment applied. For example, if user tariff has 60 sec minimal time and user made a Call for 20 sec, then billsec will show 20 sec and user_billsec will show 60 sec (minimal time is applied).

* '''Show Calls statistics to User for last''' – number of Calls statistics to show in days. For example, if you enter 5 days, users will only see 5 days old calls, they will not be able to check older calls.
* '''Show Device and it's CallerID in Last Calls''' – shows additional column in [[Last Calls]] page with Device and its CallerID information. Click to reach that Device settings page..
* '''Allow User to assign DID to Device''' – lets User to assign DID to Device.
* '''Allow User to assign DID to Trunk''' – lets User to Assign DID to Trunk.
* '''Show DID User instead of Device User in Last Calls''' - if enabled, always shows DID User name in Last Calls.
* '''New Menu Active''' - if enabled, changes main menu to the new structure.
* '''Show Replication Broken warning only for Admin''' - if enabled, shows Replication Broken warning message only for Admin account.
* '''Dropdown field in User's subscriptions''' - enables old style Service selection in Subscription form.
* '''Show detailed Quick Stats''' - shows modified quick stats of first page.
* '''Show Terminated by in Last Calls''' - show Terminated By column in [[Last Calls]], calls CSV/PDF export, and adds the possibility to select this column in [[CDR Export Templates]].
 

== Server load ==

'''SETTINGS –> Setup –> Settings –> Server load'''
 
Settings for GUI Server and Database Server

* '''HDD utilisation higher than''' – Percentage of CPU time during which I/O requests were issued to the device (bandwidth utilization for the device).
* '''CPU General Load higher than''' – CPU General load higher than – Percentage of the CPU for user processes.
* '''CPU Load Stats 1 higher than''' – average load per one minute on the system
* '''CPU MySQL process higher than''' – Percentage of the CPU for MySQL process
* '''CPU Ruby process higher than''' – Percentage of the CPU for Ruby process
* '''CPU Asterisk process (if present) higher than''' – Percentage of the CPU for Asterisk process
* '''Delete Server Load Stats older than''' – deletes internal servers load statistics older than defined number of days.
 

== Calls ==

'''SETTINGS –> Setup –> Settings –> Calls'''
* '''Retrieve PCAP files from the Proxy Server''' – default off. Works only when CCL module is activated.
 
[[Archived calls]]
 

== FTP ==
Please fill up FTP server details if you want to store Archived calls or/and Backups to FTP server.

* '''IP''' - Enter FTP server IP.
* '''Port''' - Enter FTP server Port.
* '''Username''' - Enter FTP server Username.
* '''Password''' - Enter FTP server Password.
* '''Path for Archived Calls''' - Enter Path for Archived Calls.
* '''Path for Backups''' - Enter path for Backups.
 

== Security ==
* '''Allow short passwords in devices'''
* '''Use strong passwords for users'''
* '''Admin login with approved IP only''' - security measure which allows to approve IP's that try to [[MOR_Login_with_approved_IP%27s|login with Admin Account]].
* '''Enable IP report warning on login failure''' - show [[MOR_Login_Failure_Report|warning]] on unsuccessful login attempts.
* '''Logout after password change''' - terminates all sessions of the User whose password is changed.
* '''Logout after closing browser window''' - terminates all sessions of the User after closing browser window.
* '''Do not logout on session IP change''' - do not logout from MOR GUI if IP is changed.
 

=See also=

* [[Server is overloaded]]

Business Model - GSM Termination

2021-10-07T09:02:35Z

Mindaugas:

= Minimizing risk of SIM blocking =

* Using CallerID Whitelist to only allow know good numbers to dial-out. That way minimizing the risk that Mobile operators will find out about SIM cards used for GSM Termination.
* [[Dynamic_Blacklist_Functionality | Blacklisting]] numbers which behave in suspect manner
* Placing GSM gateways in the populated areas: supermarket, stadium, etc
* http://www.stop-track.net/topic/index-en.html
 

= Anti-SIM blocking services =
* http://www.simprotection.com/
 

= Consultants for GMS termination business =

L&C Consulting
Stephane Lasserre
France
Skype: stephane.lasserre
Phone : +33 66 2 33 28 06
Email: stephane.lasserre@lnc-consulting.com

 
= See also =
* [[VoIP GSM gateways and SIM banks]]

Pilot Project

2021-10-07T08:54:41Z

Mindaugas: /* STEP 3 – Starting configurations and getting support */

== STEP 1 – Your goals ==

First step is to define your goals for the Pilot Project and the next step if those goals are achieved. Questions to be answered:

* Do you want to use our server or your?
* What are your main goals for the Pilot Project?
* If we achieve your goals, what would happen at the end of the Pilot Project?
* Which default currency do you want to use?
* Do you need an SSL certificate? If so, please the following information from you:
** the hostname you want to use for Kolmisoft Softswitch. This hostname should point to the IP address, where Kolmisoft Softswitch is installed
** email address you want to receive notifications from Let's Encrypt (or another SSL issuing authority)

 
== STEP 2 – Preparing a server and getting login ==

If you chose to use:
* Kolmisoft server - no action is needed.
* Your server - prepare it according to [[Installation|our installation instructions]].

Installation is usually completed within 48 hours.

Once the system is ready, you’ll get an email from noreply@kolmisoft.com with the text "COMMENT HIDDEN IN EMAIL".

For security purposes we don't send login details by email, so you'll have to log in to [https://support.kolmisoft.com/ Kolmisoft Support System] to get your credentials.

 
== STEP 3 – Starting configurations and getting support ==

'''PRIVATE TRAINING'''

All Pilot project users have 3 hours of private training included in their package.

You can schedule a training time by creating a ticket in the Kolmisoft Support System.

'''DOCUMENTATION'''

To achieve your pre-defined goals you need to start system configuration by following steps in wiki documentation:
• [[MOR_Manual|MOR manual]]
• [[M2_Switch_Manual|M2/M4 manual]]

You can find more information about the specific questions by entering a keyword or phrase in the search field on the left (see
the screenshot below).

[[File:Search_box_in_Kolmisoft_Wiki.png]]

If you don’t know, what to type, start with:
* '''MOR''' [[How_to_make_first_call|How to make a first call]]
* '''MOR''' [[Usual_configuration_sequence|Usual configuration sequence]]
* '''M2/M4''' [[M2_How_to_make_first_call|How to make a first call]]

'''SUPPORT'''

As the system is new for you, simply following the wiki documentation is not always enough.

As soon as you face some difficulty or feel that things are getting complicated, you can contact Kolmisoft engineers for help.

This is done by creating a ticket in the Kolmisoft Support System.

* [[Support_System_explanation|Support system explanation]]
* [[Create_new_Ticket_in_Ticket_System|How to create a new ticket]]
* [[Write_comment_to_the_Ticket|How to write a comment]]
* [[Support|Support plans and working hours]]

For some clients, it is strange why Kolmisoft uses a ticket system to resolve problems and questions instead of email, phone
or online chat.

The answer is simple – to assist our clients more efficiently.

Once you understand that keeping problems organized increases reaction time and rate of problem resolution, you will start enjoying the Kolmisoft support system.

However, it is also possible to contact our engineers by Skype ID: support_kolmisoft and join our [https://discord.gg/K4wNAyN Discord Channel].

 

== STEP 4 – Concluding results ==

One-two weeks before the Pilot project we will conclude the results – whether it was successful or not.

If it was successful, we will propose few options to be taken as a next step.

If it was not successful, we analyze the core issues and will try to improve ourselves to serve you better in the future.

 

== STEP 5 – Next step upon successful Pilot Project ==

If we achieve success together and you would like to continue the partnership with Kolmisoft, you can become our client.

It is possible to retain the same server which was used during the Pilot project or migrate to a new one.

Pilot Project

2021-10-07T08:54:11Z

Mindaugas: /* STEP 2 – Preparing a server and getting login */

== STEP 1 – Your goals ==

First step is to define your goals for the Pilot Project and the next step if those goals are achieved. Questions to be answered:

* Do you want to use our server or your?
* What are your main goals for the Pilot Project?
* If we achieve your goals, what would happen at the end of the Pilot Project?
* Which default currency do you want to use?
* Do you need an SSL certificate? If so, please the following information from you:
** the hostname you want to use for Kolmisoft Softswitch. This hostname should point to the IP address, where Kolmisoft Softswitch is installed
** email address you want to receive notifications from Let's Encrypt (or another SSL issuing authority)

 
== STEP 2 – Preparing a server and getting login ==

If you chose to use:
* Kolmisoft server - no action is needed.
* Your server - prepare it according to [[Installation|our installation instructions]].

Installation is usually completed within 48 hours.

Once the system is ready, you’ll get an email from noreply@kolmisoft.com with the text "COMMENT HIDDEN IN EMAIL".

For security purposes we don't send login details by email, so you'll have to log in to [https://support.kolmisoft.com/ Kolmisoft Support System] to get your credentials.

== STEP 3 – Starting configurations and getting support ==

'''PRIVATE TRAINING'''

All Pilot project users have 3 hours of private training included in their package.

You can schedule a training time by creating a ticket in the Kolmisoft Support System.

'''DOCUMENTATION'''

To achieve your pre-defined goals you need to start system configuration by following steps in wiki documentation:
• [[MOR_Manual|MOR manual]]
• [[M2_Switch_Manual|M2/M4 manual]]

You can find more information about the specific questions by entering a keyword or phrase in the search field on the left (see
the screenshot below).

[[File:Search_box_in_Kolmisoft_Wiki.png]]

If you don’t know, what to type, start with:
* '''MOR''' [[How_to_make_first_call|How to make a first call]]
* '''MOR''' [[Usual_configuration_sequence|Usual configuration sequence]]
* '''M2/M4''' [[M2_How_to_make_first_call|How to make a first call]]

'''SUPPORT'''

As the system is new for you, simply following the wiki documentation is not always enough.

As soon as you face some difficulty or feel that things are getting complicated, you can contact Kolmisoft engineers for help.

This is done by creating a ticket in the Kolmisoft Support System.

* [[Support_System_explanation|Support system explanation]]
* [[Create_new_Ticket_in_Ticket_System|How to create a new ticket]]
* [[Write_comment_to_the_Ticket|How to write a comment]]
* [[Support|Support plans and working hours]]

For some clients, it is strange why Kolmisoft uses a ticket system to resolve problems and questions instead of email, phone
or online chat.

The answer is simple – to assist our clients more efficiently.

Once you understand that keeping problems organized increases reaction time and rate of problem resolution, you will start enjoying the Kolmisoft support system.

However, it is also possible to contact our engineers by Skype ID: support_kolmisoft and join our [https://discord.gg/K4wNAyN Discord Channel].

 
== STEP 4 – Concluding results ==

One-two weeks before the Pilot project we will conclude the results – whether it was successful or not.

If it was successful, we will propose few options to be taken as a next step.

If it was not successful, we analyze the core issues and will try to improve ourselves to serve you better in the future.

 

== STEP 5 – Next step upon successful Pilot Project ==

If we achieve success together and you would like to continue the partnership with Kolmisoft, you can become our client.

It is possible to retain the same server which was used during the Pilot project or migrate to a new one.

Pilot Project

2021-10-07T08:53:59Z

Mindaugas: /* STEP 1 – Your goals */

== STEP 1 – Your goals ==

First step is to define your goals for the Pilot Project and the next step if those goals are achieved. Questions to be answered:

* Do you want to use our server or your?
* What are your main goals for the Pilot Project?
* If we achieve your goals, what would happen at the end of the Pilot Project?
* Which default currency do you want to use?
* Do you need an SSL certificate? If so, please the following information from you:
** the hostname you want to use for Kolmisoft Softswitch. This hostname should point to the IP address, where Kolmisoft Softswitch is installed
** email address you want to receive notifications from Let's Encrypt (or another SSL issuing authority)

== STEP 2 – Preparing a server and getting login ==

If you chose to use:
* Kolmisoft server - no action is needed.
* Your server - prepare it according to [[Installation|our installation instructions]].

Installation is usually completed within 48 hours.

Once the system is ready, you’ll get an email from noreply@kolmisoft.com with the text "COMMENT HIDDEN IN EMAIL".

For security purposes we don't send login details by email, so you'll have to log in to [https://support.kolmisoft.com/ Kolmisoft Support System] to get your credentials.

== STEP 3 – Starting configurations and getting support ==

'''PRIVATE TRAINING'''

All Pilot project users have 3 hours of private training included in their package.

You can schedule a training time by creating a ticket in the Kolmisoft Support System.

'''DOCUMENTATION'''

To achieve your pre-defined goals you need to start system configuration by following steps in wiki documentation:
• [[MOR_Manual|MOR manual]]
• [[M2_Switch_Manual|M2/M4 manual]]

You can find more information about the specific questions by entering a keyword or phrase in the search field on the left (see
the screenshot below).

[[File:Search_box_in_Kolmisoft_Wiki.png]]

If you don’t know, what to type, start with:
* '''MOR''' [[How_to_make_first_call|How to make a first call]]
* '''MOR''' [[Usual_configuration_sequence|Usual configuration sequence]]
* '''M2/M4''' [[M2_How_to_make_first_call|How to make a first call]]

'''SUPPORT'''

As the system is new for you, simply following the wiki documentation is not always enough.

As soon as you face some difficulty or feel that things are getting complicated, you can contact Kolmisoft engineers for help.

This is done by creating a ticket in the Kolmisoft Support System.

* [[Support_System_explanation|Support system explanation]]
* [[Create_new_Ticket_in_Ticket_System|How to create a new ticket]]
* [[Write_comment_to_the_Ticket|How to write a comment]]
* [[Support|Support plans and working hours]]

For some clients, it is strange why Kolmisoft uses a ticket system to resolve problems and questions instead of email, phone
or online chat.

The answer is simple – to assist our clients more efficiently.

Once you understand that keeping problems organized increases reaction time and rate of problem resolution, you will start enjoying the Kolmisoft support system.

However, it is also possible to contact our engineers by Skype ID: support_kolmisoft and join our [https://discord.gg/K4wNAyN Discord Channel].

 
== STEP 4 – Concluding results ==

One-two weeks before the Pilot project we will conclude the results – whether it was successful or not.

If it was successful, we will propose few options to be taken as a next step.

If it was not successful, we analyze the core issues and will try to improve ourselves to serve you better in the future.

 

== STEP 5 – Next step upon successful Pilot Project ==

If we achieve success together and you would like to continue the partnership with Kolmisoft, you can become our client.

It is possible to retain the same server which was used during the Pilot project or migrate to a new one.

Pilot Project

2021-10-07T08:53:48Z

Mindaugas: /* STEP 1 – Your goals */

== STEP 1 – Your goals ==

First step is to define your goals for the Pilot Project and the next step if those goals are achieved. Questions to be answered:

* Do you want to use our server or your?
* What are your main goals for the Pilot Project?
* If we achieve your goals, what would happen at the end of the Pilot Project?
* Which default currency do you want to use?
* Do you need an SSL certificate? If so, please the following information from you:
** the hostname you want to use for Kolmisoft Softswitch. This hostname should point to the IP address, where Kolmisoft Softswitch is installed
** email address you want to receive notifications from Let's Encrypt Ūor other SSL issuing authority)

== STEP 2 – Preparing a server and getting login ==

If you chose to use:
* Kolmisoft server - no action is needed.
* Your server - prepare it according to [[Installation|our installation instructions]].

Installation is usually completed within 48 hours.

Once the system is ready, you’ll get an email from noreply@kolmisoft.com with the text "COMMENT HIDDEN IN EMAIL".

For security purposes we don't send login details by email, so you'll have to log in to [https://support.kolmisoft.com/ Kolmisoft Support System] to get your credentials.

== STEP 3 – Starting configurations and getting support ==

'''PRIVATE TRAINING'''

All Pilot project users have 3 hours of private training included in their package.

You can schedule a training time by creating a ticket in the Kolmisoft Support System.

'''DOCUMENTATION'''

To achieve your pre-defined goals you need to start system configuration by following steps in wiki documentation:
• [[MOR_Manual|MOR manual]]
• [[M2_Switch_Manual|M2/M4 manual]]

You can find more information about the specific questions by entering a keyword or phrase in the search field on the left (see
the screenshot below).

[[File:Search_box_in_Kolmisoft_Wiki.png]]

If you don’t know, what to type, start with:
* '''MOR''' [[How_to_make_first_call|How to make a first call]]
* '''MOR''' [[Usual_configuration_sequence|Usual configuration sequence]]
* '''M2/M4''' [[M2_How_to_make_first_call|How to make a first call]]

'''SUPPORT'''

As the system is new for you, simply following the wiki documentation is not always enough.

As soon as you face some difficulty or feel that things are getting complicated, you can contact Kolmisoft engineers for help.

This is done by creating a ticket in the Kolmisoft Support System.

* [[Support_System_explanation|Support system explanation]]
* [[Create_new_Ticket_in_Ticket_System|How to create a new ticket]]
* [[Write_comment_to_the_Ticket|How to write a comment]]
* [[Support|Support plans and working hours]]

For some clients, it is strange why Kolmisoft uses a ticket system to resolve problems and questions instead of email, phone
or online chat.

The answer is simple – to assist our clients more efficiently.

Once you understand that keeping problems organized increases reaction time and rate of problem resolution, you will start enjoying the Kolmisoft support system.

However, it is also possible to contact our engineers by Skype ID: support_kolmisoft and join our [https://discord.gg/K4wNAyN Discord Channel].

 
== STEP 4 – Concluding results ==

One-two weeks before the Pilot project we will conclude the results – whether it was successful or not.

If it was successful, we will propose few options to be taken as a next step.

If it was not successful, we analyze the core issues and will try to improve ourselves to serve you better in the future.

 

== STEP 5 – Next step upon successful Pilot Project ==

If we achieve success together and you would like to continue the partnership with Kolmisoft, you can become our client.

It is possible to retain the same server which was used during the Pilot project or migrate to a new one.

Pilot Project

2021-10-07T08:53:16Z

Mindaugas:

== STEP 1 – Your goals ==

First step is to define your goals for the Pilot Project and the next step if those goals are achieved. Questions to be answered:

* Do you want to use our server or your?
* What are your main goals for the Pilot Project?
* If we achieve your goals, what would happen at the end of the Pilot Project?
* Which default currency do you want to use?
* Do you need an SSL certificate? If so, please the following information from you:
** the hostname you want to use for Kolmisoft Softswitch. This hostname should point to the IP address, where Kolmisoft softswitch is installed
** email address you want to receive notifications from Let's Encrypt

== STEP 2 – Preparing a server and getting login ==

If you chose to use:
* Kolmisoft server - no action is needed.
* Your server - prepare it according to [[Installation|our installation instructions]].

Installation is usually completed within 48 hours.

Once the system is ready, you’ll get an email from noreply@kolmisoft.com with the text "COMMENT HIDDEN IN EMAIL".

For security purposes we don't send login details by email, so you'll have to log in to [https://support.kolmisoft.com/ Kolmisoft Support System] to get your credentials.

== STEP 3 – Starting configurations and getting support ==

'''PRIVATE TRAINING'''

All Pilot project users have 3 hours of private training included in their package.

You can schedule a training time by creating a ticket in the Kolmisoft Support System.

'''DOCUMENTATION'''

To achieve your pre-defined goals you need to start system configuration by following steps in wiki documentation:
• [[MOR_Manual|MOR manual]]
• [[M2_Switch_Manual|M2/M4 manual]]

You can find more information about the specific questions by entering a keyword or phrase in the search field on the left (see
the screenshot below).

[[File:Search_box_in_Kolmisoft_Wiki.png]]

If you don’t know, what to type, start with:
* '''MOR''' [[How_to_make_first_call|How to make a first call]]
* '''MOR''' [[Usual_configuration_sequence|Usual configuration sequence]]
* '''M2/M4''' [[M2_How_to_make_first_call|How to make a first call]]

'''SUPPORT'''

As the system is new for you, simply following the wiki documentation is not always enough.

As soon as you face some difficulty or feel that things are getting complicated, you can contact Kolmisoft engineers for help.

This is done by creating a ticket in the Kolmisoft Support System.

* [[Support_System_explanation|Support system explanation]]
* [[Create_new_Ticket_in_Ticket_System|How to create a new ticket]]
* [[Write_comment_to_the_Ticket|How to write a comment]]
* [[Support|Support plans and working hours]]

For some clients, it is strange why Kolmisoft uses a ticket system to resolve problems and questions instead of email, phone
or online chat.

The answer is simple – to assist our clients more efficiently.

Once you understand that keeping problems organized increases reaction time and rate of problem resolution, you will start enjoying the Kolmisoft support system.

However, it is also possible to contact our engineers by Skype ID: support_kolmisoft and join our [https://discord.gg/K4wNAyN Discord Channel].

 
== STEP 4 – Concluding results ==

One-two weeks before the Pilot project we will conclude the results – whether it was successful or not.

If it was successful, we will propose few options to be taken as a next step.

If it was not successful, we analyze the core issues and will try to improve ourselves to serve you better in the future.

 

== STEP 5 – Next step upon successful Pilot Project ==

If we achieve success together and you would like to continue the partnership with Kolmisoft, you can become our client.

It is possible to retain the same server which was used during the Pilot project or migrate to a new one.

Pilot Project

2021-10-07T08:51:55Z

Mindaugas: /* STEP 5 – Next step upon successful Pilot Project */

== STEP 1 – Your goals ==

First step is to define your goals for the Pilot Project and the next step if those goals are achieved. Questions to be answered:

* Do you want to use our server or your?
* What are your main goals for the Pilot Project?
* If we achieve your goals, what would happen at the end of the Pilot Project?
* Which default currency do you want to use?
* Do you need an SSL certificate? If so, please the following information from you:
** the hostname you want to use for Kolmisoft softswitch. This hostname should point to the IP address, where Kolmisoft softswitch is installed
** email address you want to receive notifications from Let's Encrypt

== STEP 2 – Preparing a server and getting login ==

If you chose to use:
* Kolmisoft server - no action is needed.
* Your server - repare it according to [[Installation|our installation instructions]].

Installation is usually completed within 48 hours.

Once system is ready, you’ll get an email from noreply@kolmisoft.com with text "COMMENT HIDDEN IN EMAIL".

For security purposes we don't send login details by email, so you'll have to login to [https://support.kolmisoft.com/ Kolmisoft Support System] to get your credentials.

== STEP 3 – Starting configurations and getting support ==

'''PRIVATE TRAINING'''

All Pilot project users have 3 hours of private training included in their package.

You can schedule a training time by creating a ticket in the Kolmisoft Support System.

'''DOCUMENTATION'''

To achieve your pre-defined goals you need to start system configuration by following steps in wiki documentation:
• [[MOR_Manual|MOR manual]]
• [[M2_Switch_Manual|M2/M4 manual]]

You can find more information about the specific questions by entering a keyword or phrase in the search field on the left (see
the screenshot below).

[[File:Search_box_in_Kolmisoft_Wiki.png]]

If you don’t know, what to type, start with:
* '''MOR''' [[How_to_make_first_call|How to make a first call]]
* '''MOR''' [[Usual_configuration_sequence|Usual configuration sequence]]
* '''M2/M4''' [[M2_How_to_make_first_call|How to make a first call]]

'''SUPPORT'''

As the system is new for you, simply following the wiki documentation is not always enough.

As soon as you face some difficulty or feel that things are getting complicated, you can contact Kolmisoft engineers for help.

This is done by creating a ticket in the Kolmisoft Support System.

* [[Support_System_explanation|Support system explanation]]
* [[Create_new_Ticket_in_Ticket_System|How to create a new ticket]]
* [[Write_comment_to_the_Ticket|How to write a comment]]
* [[Support|Support plans and working hours]]

For some clients, it is strange why Kolmisoft uses a ticket system to resolve problems and questions instead of email, phone
or online chat.

The answer is simple – to assist our clients more efficiently.

Once you understand that keeping problems organized increases reaction time and rate of problem resolution, you will start enjoying the Kolmisoft support system.

However, it is also possible to contact our engineers by Skype ID: support_kolmisoft and join our [https://discord.gg/K4wNAyN Discord Channel].

 
== STEP 4 – Concluding results ==

One-two weeks before the Pilot project we will conclude the results – whether it was successful or not.

If it was successful, we will propose few options to be taken as a next step.

If it was not successful, we analyze the core issues and will try to improve ourselves to serve you better in the future.

 

== STEP 5 – Next step upon successful Pilot Project ==

If we achieve success together and you would like to continue partnership with Kolmisoft, you can become our client.

It is possible to retain the same server which was used during the Pilot project or migrate to a new one.

Pilot Project

2021-10-07T08:51:43Z

Mindaugas: /* STEP 4 – Concluding results */

== STEP 1 – Your goals ==

First step is to define your goals for the Pilot Project and the next step if those goals are achieved. Questions to be answered:

* Do you want to use our server or your?
* What are your main goals for the Pilot Project?
* If we achieve your goals, what would happen at the end of the Pilot Project?
* Which default currency do you want to use?
* Do you need an SSL certificate? If so, please the following information from you:
** the hostname you want to use for Kolmisoft softswitch. This hostname should point to the IP address, where Kolmisoft softswitch is installed
** email address you want to receive notifications from Let's Encrypt

== STEP 2 – Preparing a server and getting login ==

If you chose to use:
* Kolmisoft server - no action is needed.
* Your server - repare it according to [[Installation|our installation instructions]].

Installation is usually completed within 48 hours.

Once system is ready, you’ll get an email from noreply@kolmisoft.com with text "COMMENT HIDDEN IN EMAIL".

For security purposes we don't send login details by email, so you'll have to login to [https://support.kolmisoft.com/ Kolmisoft Support System] to get your credentials.

== STEP 3 – Starting configurations and getting support ==

'''PRIVATE TRAINING'''

All Pilot project users have 3 hours of private training included in their package.

You can schedule a training time by creating a ticket in the Kolmisoft Support System.

'''DOCUMENTATION'''

To achieve your pre-defined goals you need to start system configuration by following steps in wiki documentation:
• [[MOR_Manual|MOR manual]]
• [[M2_Switch_Manual|M2/M4 manual]]

You can find more information about the specific questions by entering a keyword or phrase in the search field on the left (see
the screenshot below).

[[File:Search_box_in_Kolmisoft_Wiki.png]]

If you don’t know, what to type, start with:
* '''MOR''' [[How_to_make_first_call|How to make a first call]]
* '''MOR''' [[Usual_configuration_sequence|Usual configuration sequence]]
* '''M2/M4''' [[M2_How_to_make_first_call|How to make a first call]]

'''SUPPORT'''

As the system is new for you, simply following the wiki documentation is not always enough.

As soon as you face some difficulty or feel that things are getting complicated, you can contact Kolmisoft engineers for help.

This is done by creating a ticket in the Kolmisoft Support System.

* [[Support_System_explanation|Support system explanation]]
* [[Create_new_Ticket_in_Ticket_System|How to create a new ticket]]
* [[Write_comment_to_the_Ticket|How to write a comment]]
* [[Support|Support plans and working hours]]

For some clients, it is strange why Kolmisoft uses a ticket system to resolve problems and questions instead of email, phone
or online chat.

The answer is simple – to assist our clients more efficiently.

Once you understand that keeping problems organized increases reaction time and rate of problem resolution, you will start enjoying the Kolmisoft support system.

However, it is also possible to contact our engineers by Skype ID: support_kolmisoft and join our [https://discord.gg/K4wNAyN Discord Channel].

 
== STEP 4 – Concluding results ==

One-two weeks before the Pilot project we will conclude the results – whether it was successful or not.

If it was successful, we will propose few options to be taken as a next step.

If it was not successful, we analyze the core issues and will try to improve ourselves to serve you better in the future.

== STEP 5 – Next step upon successful Pilot Project ==

If we achieve success together and you would like to continue partnership with Kolmisoft, you can become our client.

It is possible to retain the same server which was used during the Pilot project or migrate to a new one.

Pilot Project

2021-10-07T08:51:31Z

Mindaugas: /* STEP 3 – Starting configurations and getting support */

== STEP 1 – Your goals ==

First step is to define your goals for the Pilot Project and the next step if those goals are achieved. Questions to be answered:

* Do you want to use our server or your?
* What are your main goals for the Pilot Project?
* If we achieve your goals, what would happen at the end of the Pilot Project?
* Which default currency do you want to use?
* Do you need an SSL certificate? If so, please the following information from you:
** the hostname you want to use for Kolmisoft softswitch. This hostname should point to the IP address, where Kolmisoft softswitch is installed
** email address you want to receive notifications from Let's Encrypt

== STEP 2 – Preparing a server and getting login ==

If you chose to use:
* Kolmisoft server - no action is needed.
* Your server - repare it according to [[Installation|our installation instructions]].

Installation is usually completed within 48 hours.

Once system is ready, you’ll get an email from noreply@kolmisoft.com with text "COMMENT HIDDEN IN EMAIL".

For security purposes we don't send login details by email, so you'll have to login to [https://support.kolmisoft.com/ Kolmisoft Support System] to get your credentials.

== STEP 3 – Starting configurations and getting support ==

'''PRIVATE TRAINING'''

All Pilot project users have 3 hours of private training included in their package.

You can schedule a training time by creating a ticket in the Kolmisoft Support System.

'''DOCUMENTATION'''

To achieve your pre-defined goals you need to start system configuration by following steps in wiki documentation:
• [[MOR_Manual|MOR manual]]
• [[M2_Switch_Manual|M2/M4 manual]]

You can find more information about the specific questions by entering a keyword or phrase in the search field on the left (see
the screenshot below).

[[File:Search_box_in_Kolmisoft_Wiki.png]]

If you don’t know, what to type, start with:
* '''MOR''' [[How_to_make_first_call|How to make a first call]]
* '''MOR''' [[Usual_configuration_sequence|Usual configuration sequence]]
* '''M2/M4''' [[M2_How_to_make_first_call|How to make a first call]]

'''SUPPORT'''

As the system is new for you, simply following the wiki documentation is not always enough.

As soon as you face some difficulty or feel that things are getting complicated, you can contact Kolmisoft engineers for help.

This is done by creating a ticket in the Kolmisoft Support System.

* [[Support_System_explanation|Support system explanation]]
* [[Create_new_Ticket_in_Ticket_System|How to create a new ticket]]
* [[Write_comment_to_the_Ticket|How to write a comment]]
* [[Support|Support plans and working hours]]

For some clients, it is strange why Kolmisoft uses a ticket system to resolve problems and questions instead of email, phone
or online chat.

The answer is simple – to assist our clients more efficiently.

Once you understand that keeping problems organized increases reaction time and rate of problem resolution, you will start enjoying the Kolmisoft support system.

However, it is also possible to contact our engineers by Skype ID: support_kolmisoft and join our [https://discord.gg/K4wNAyN Discord Channel].

== STEP 4 – Concluding results ==

One-two weeks before the Pilot project we will conclude the results – whether it was successful or not.

If it was successful, we will propose few options to be taken as a next step.

If it was not successful, we analyze the core issues and will try to improve ourselves to serve you better in the future.

== STEP 5 – Next step upon successful Pilot Project ==

If we achieve success together and you would like to continue partnership with Kolmisoft, you can become our client.

It is possible to retain the same server which was used during the Pilot project or migrate to a new one.

File:Search box in Kolmisoft Wiki.png

2021-10-07T08:50:12Z

Mindaugas: uploaded a new version of "File:Search box in Kolmisoft Wiki.png"

Search Box in Kolmisoft Wiki

File:Echotest2.png

2021-10-06T14:26:33Z

Mindaugas: uploaded a new version of "File:Echotest2.png"

How to set up SSL certificate with Let's Encrypt

2021-10-06T11:20:13Z

Mindaugas: /* Instalation */

== About Let's Encrypt ==
Let's Encrypt provides free valid SSL certificates

== Before proceeding ==
To proceed the following is needed:
* Domain name pointed to switch IP (it is not possible to create a Let's Encrypt SSL certificate for IP address)
* Email address to get notifications from Let's Encrypt
* SSH access to switch server with root privileges

== Installation ==
In the example below let's assume that the domain name is example.com

Before installation, it is a good idea to backup /etc/httpd folder

cp -a /etc/httpd/ /usr/local/mor/backups/

=== Method 1 (using yum packages) ===
Based on this [https://www.digitalocean.com/community/tutorials/how-to-secure-apache-with-let-s-encrypt-on-centos-7 guide]

yum install certbot python2-certbot-apache mod_ssl

if installation is completed without errors, run certbot command (prepare to answer yes/no questions and enter the domain name(s) and email)

certbot --apache

If the command is completed successfully, going to <nowiki>https://example.com/billing</nowiki> should show a secure connection

if everything is OK, test certificate renewal and install renewal cron
certbot renew --dry-run

If successful it should show at the end

Congratulations, all simulated renewals succeeded:
Congratulations, all simulated renewals succeeded:
/etc/letsencrypt/live/example.com/fullchain.pem (success)
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Create a cron to renew certificates automatically

echo "20 0,12 * * * certbot renew > /var/log/certbot_renewal_cron.log 2&>1" > /etc/cron.d/certbot_renewal_cron
chmod 644 /etc/cron.d/certbot_renewal_cron
service crond restart

This will try to renew the certificate two times every day. Certbot will try to actually renew certificates once the expiration day will be less than 30 days

=== Method 2 (using snap management system) ===
To streamline the install process across different Linux Distributions, the Let's Encrypt official guide use snapd management system

If you want to use snaps, please use this guide:

https://certbot.eff.org/lets-encrypt/centosrhel7-apache.html

Using this installation method, automatic renewal will be configured automatically (it will be systemd timer, not a simple cron)
systemctl list-timers
NEXT LEFT LAST PASSED UNIT ACTIVATES
Tr 2021-10-06 12:42:00 CEST 41min left Tr 2021-10-06 05:11:01 CEST 6h ago snap.certbot.renew.timer snap.certbot.renew.service

== Logs ==
Let's encrypt log
/var/log/letsencrypt/letsencrypt.log

== Accessing switch without /billing suffix ==
Follow the guide [[I see Apache test on Start page| here]]

Use https instead of http and domain names instead of 127.0.0.1

SIP/2.0 480 Temporarily Unavailable

2021-10-05T09:09:30Z

Mindaugas:

Got SIP response 480 "Temporarily Unavailable". Possible reasons and solutions:

1. Call is rejected by provider/end device. In this case please check with the provider.

2. Call fails with HGC 20 due to unreachable/unregistered device/provider. In this case check device/provider registration status.

3. Call is rejected by MOR due to high load. In this case, there will be no CDR in the last calls section. More information on how to check and solve such issues is available [[Maximum loadavg limit exceeded|here]]

----
'''Check also:'''
* [[SIP Error Codes]]

Centos 6 repositories does not work anymore

2021-10-03T11:05:45Z

Mindaugas:

In file /etc/yum.repos.d/CentOS-Base.repo, comment out "mirrorlist" lines and add new "baseurl" lines.
File should look like:

# CentOS-Base.repo
#
# The mirror system uses the connecting IP address of the client and the
# update status of each mirror to pick mirrors that are updated to and
# geographically close to the client. You should use this for CentOS updates
# unless you are manually picking other mirrors.
#
# If the mirrorlist= does not work for you, as a fall back you can try the
# remarked out baseurl= line instead.
#
#

[base]
name=CentOS-$releasever - Base
#mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=os&infra=$infra
#baseurl=http://mirror.centos.org/centos/$releasever/os/$basearch/
baseurl=https://vault.centos.org/6.10/os/$basearch/
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-6

#released updates
[updates]
name=CentOS-$releasever - Updates
#mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=updates&infra=$infra
#baseurl=http://mirror.centos.org/centos/$releasever/updates/$basearch/
baseurl=https://vault.centos.org/6.10/updates/$basearch/
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-6

#additional packages that may be useful
[extras]
name=CentOS-$releasever - Extras
#mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=extras&infra=$infra
#baseurl=http://mirror.centos.org/centos/$releasever/extras/$basearch/
baseurl=https://vault.centos.org/6.10/extras/$basearch/
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-6

#additional packages that extend functionality of existing packages
[centosplus]
name=CentOS-$releasever - Plus
#mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=centosplus&infra=$infra
#baseurl=http://mirror.centos.org/centos/$releasever/centosplus/$basearch/
baseurl=https://vault.centos.org/6.10/centosplus/$basearch/
gpgcheck=1
enabled=0
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-6

#contrib - packages by Centos Users
[contrib]
name=CentOS-$releasever - Contrib
#mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=contrib&infra=$infra
#baseurl=http://mirror.centos.org/centos/$releasever/contrib/$basearch/
baseurl=https://vault.centos.org/6.10/contrib/$basearch/
gpgcheck=1
enabled=0
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-6

If repositories does not work after changes, run these commands:
yum clean all
yum makecache

If this does not help run:

yum update ca-certificates

If it gives such error:

[Errno 14] Peer cert cannot be verified or peer cert invalid. Trying other mirror…

In /etc/yum.conf in the [main] section add:

sslverify=false

And check that in the /etc/yum.repos.d/CenOS-Base.repo there are paths with https (if not, change from http to https) and retry yum update ca-certificates

If all ok - change https->http back (if you changed http->https before). And remove sslverify=false from /etc/yum.conf

Centos 6 repositories does not work anymore

2021-10-01T15:45:56Z

Mindaugas:

Centos 6 repositories does not work anymore

2021-10-01T15:45:32Z

Mindaugas:

In file /etc/yum.repos.d/CentOS-Base.repo, comment out "mirrorlist" lines and add new "baseurl" lines.
File should look like:

# CentOS-Base.repo
#
# The mirror system uses the connecting IP address of the client and the
# update status of each mirror to pick mirrors that are updated to and
# geographically close to the client. You should use this for CentOS updates
# unless you are manually picking other mirrors.
#
# If the mirrorlist= does not work for you, as a fall back you can try the
# remarked out baseurl= line instead.
#
#

[base]
name=CentOS-$releasever - Base
#mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=os&infra=$infra
#baseurl=http://mirror.centos.org/centos/$releasever/os/$basearch/
baseurl=https://vault.centos.org/6.10/os/$basearch/
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-6

#released updates
[updates]
name=CentOS-$releasever - Updates
#mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=updates&infra=$infra
#baseurl=http://mirror.centos.org/centos/$releasever/updates/$basearch/
baseurl=https://vault.centos.org/6.10/updates/$basearch/
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-6

#additional packages that may be useful
[extras]
name=CentOS-$releasever - Extras
#mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=extras&infra=$infra
#baseurl=http://mirror.centos.org/centos/$releasever/extras/$basearch/
baseurl=https://vault.centos.org/6.10/extras/$basearch/
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-6

#additional packages that extend functionality of existing packages
[centosplus]
name=CentOS-$releasever - Plus
#mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=centosplus&infra=$infra
#baseurl=http://mirror.centos.org/centos/$releasever/centosplus/$basearch/
baseurl=https://vault.centos.org/6.10/centosplus/$basearch/
gpgcheck=1
enabled=0
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-6

#contrib - packages by Centos Users
[contrib]
name=CentOS-$releasever - Contrib
#mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=contrib&infra=$infra
#baseurl=http://mirror.centos.org/centos/$releasever/contrib/$basearch/
baseurl=https://vault.centos.org/6.10/contrib/$basearch/
gpgcheck=1
enabled=0
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-6

If repositories does not work after changes, run these commands:
yum clean all
yum makecache

If this does not help run:

yum update ca-certificates

If it gives such error:

[Errno 14] Peer cert cannot be verified or peer cert invalid. Trying other mirror…

In /etc/yum.conf in the admin section add:

sslverify=false

And check that in the /etc/yum.repos.d/CenOS-Base.repo there are paths with https (if not, change from http to https) and retry yum update ca-certificates

If all ok - change https->http back. And remove sslverify=false from /etc/yum.conf