Browsed by
Tag: external line

Connect to sonetel

Connect to sonetel

“sonetel.com” is a VoIP carrier who can provide local phone numbers. We can add “external line” to work with their servers. According to its description, there are some special items need to be cared:

  • Sonetel uses email address as SIP account and
  • It deploys SBC or proxy to process all incoming SIP messages.

Here we give a simplel example to describe how to work with Sonetel. We assume the SIP account is “abc@gmail.com”.

In MSS, please cilck menu “data > external line” to add a record.

Configure Sonetel lline
Configure Sonetel lline

In “Basic” tab, the line type should be “Connect to peer VoIP server”, the Account should be “abc” and the Domain is “gmail.com”.

By the way, the Password is the password you sign up in Sonetel, not your own email password.

Since all SIP messages are processed by sonetel SBC/Proxy, we need configure “outbound” information in the “Outgoing call” tab. Please refer to following figure.

Sonetel SBC
Sonetel SBC

The Sonetel proxy address is “sip.sonetel.com” which should be described in the email sent by sonetel.

No-answer timer in external line

No-answer timer in external line

In the external line “outgoing calls” configuration, we add an item “no-answer timer”. This item is used to limit the no-answer timer value when make outgoing calls. Please refer to attached figure.

No-answer timer value
No-answer timer vaule in outgoing calls of external line.

By default, its value is zero that means the line will use system default no-answer timer value. If it is set a value, the line will use it firstly.

For example, if it is set to be “15”, then the line will force to release the call in 15 seconds if peer side doesn’t answer the call.

DNS problem

DNS problem

Yesterday our data center has a DNS problem. In fact, it seems its DNS system was crashed. It made our servers failed to register all external lines. Then cloud system detected that all external lines were configured with wrong configurations. To avoid sending spam messages to peer sides or peer voip providers, our system will cut all “wrong” configurations automatically.

That’s too BAD news!

We promise this problem will not happen again. All our servers have been upgraded to enable several DNS systems including Google DNS.

We are very sorry for this problem. If your external lines are off, please configure them back manually.

Thank you for your patience and continued support.

disable “only permit incoming call”

disable “only permit incoming call”

V19 is updated to support some new features in external line. We add a new item “maximum simultaneous outgoing call” in “outgoing call” tab.

This new item can limit how many concurrent calls can be processed by the external line. It it is configured to be zero, that mean the line cannot make any outgoing call.

That also means previous item “only permit incoming call” is unnecessary, so we cut this item together.

Refine called number

Refine called number

V14.4 is updated to support a new feature in “dial plan” process. This feature is “refine called number”.

“Refine called number” can be used to refine called number before calls are routed to external lines or SIP trunks. It is the last chance to change called number to fit different requirements from peer VoIP servers.

For example, one of our customer has two VOIP accounts. One is from local provider, another is from international provider. These two VoIP providers have different number format requirements, and our customer only want to has one kind of dial plan for both of them. So we can configure “refine called number” to refine the final destination number to fit it. This scenario is illustrated below.

Scenario

As described above, there are two VoIP accounts, and users need dial “90xxxx” to make outbound calls. “9” is MSS default outgoing call prefix. “0” is required by local VoIP provider. At the same time, the international VoIP provider requires that the number format should be “0086xxxx”.

After compare these number formats, we can find that we only need change prefix “0” to “0086” for international VoIP account.

Step 1: configure an independent “outgoing group ID” for international VoIP account

Please click menu “Data / External line” and select the account to edit, then please click “Outgoing call” tab and configure following item:

Outgoing group ID = 1

Step 2: configure “number transition”

We need configure a new record to change preifx “0” to “0086”. Please click menu “Dial plan / Transition” to add a new record:

Transition ID = 1
Transition type = Replace
Start position = 0
Length = 1
Replace string = 0086

Step 3: refine called number for specific outgoing group

Please click menu “Dial plan / Refine called number” to add a new record:

Outgoing group ID = 1 <== defined in step 1
Called number prefix = 0
Transition ID = 1 <== defined in step 2

Here we maybe have a problem: the called number prefix is “0”, why? why not analyze “9” prefix? It is because that “9” has been deleted in “analyze called number” procedure and the number has been changed to “0xxxx” before it is sent to external line or SIP trunk, so we should analyze prefix “0” to refine final called number.

Two external lines, how to use specific one by dialing different called number prefix?

Two external lines, how to use specific one by dialing different called number prefix?

Description

One of our customers has two different VoIP accounts, for example (1) 1234 and (2) 5678. It is required to select account “1234” if users dial “9xxxx” numbers and select account “5678” if users dial “8xxxx” numbers. The final numbers should delete these prefix “9” or “8” and “xxxx” should be sent to VoIP providers.

Solution

We can use MSS powerful “dial plan” features to fit this requirement.

By default, MSS uses called number prefix “9” to distinguish outgoing calls to outsides. If there are several external lines and without any special configuration, MSS will select one of them in round-robin for each call. Now what we need do is to configure different called number prefix and select different external line for them.

Step 1: configure number transition

In this step, we need configure a record to delete number prefix “8” or “9” from called numbers. Please click menu “Dial plan / Transition” to add a record illustrated below.

Transition ID = 1
Transition type = delete
Start position = 0
Length = 1

Step 2: add new “Analyze called number” records

According to requirement, we need indicate MSS to analyze called number prefix “8” and “9” to use different specific external line. Please click menu “Dial plan / Analyze called number” to add two records.

Record 1: analyze called number prefix “9”

Dial plan = default
Called number prefix = 9
Route type = external line
Specific external line = 1234 <== use specific external line
Change called number = yes
Transition ID = 1 <== configured in step 1
Re-analyze after transition = no

Record 2: analyze called number prefix “8”

Dial plan = default
Called number prefix = 8
Route type = external line
Specific external line = 5678 <== use specific external line 
Change called number = yes
Transition ID = 1 <== configured in step 1
Re-analyze after transition = no
Trigger hunt-group for external lines incoming calls

Trigger hunt-group for external lines incoming calls

Some customers use external lines to connect VoIP providers’ servers. So it is required to trigger hunt-group for all incoming calls from such external lines.

Lets’ assume the external line number/account is ‘123456’, so we just need trigger HG service according to this number.

Please click menu “services / multi-line hunting group / Detection configuration” to add a new record as following:

dial plan = default
called number = 123456 <-- this is the external line number
... ...

Others are same with HG service document:

http://www.myvoipapp.com/docs/mss_services/hunting_group/index.html

If the external line is configured with auto-attendant or routed to another destination number, what is the result? Don’t worry. HG detection has higher priority than these services, that means HG will be triggered even you configured AA or destination number in external line.

I cannot find my external lines, why?

I cannot find my external lines, why?

Some customers will find that their external lines configuration were gone when they sign into their cloud-mss accounts.

What happened to their accounts?

The root reason is that these customers maybe configure wrong external lines information, such as invalid password, then cloud-mss fails to register these external lines to VoIP carriers. cloud-mss will try to register them for lots of times. In this scenario, peer VoIP carriers could treat cloud-mss as a spammer or an attacker, and they will block or filter cloud-mss messages, that could effect other cloud-mss customers.

To avoid that, if cloud-mss always fail to register an external line for lots of times, it will report this external line to background administrator system, and this external line will be deleted automatically.

That’s why you cannot find your external line information. So please double check your information or check with your VoIP providers, then try to configure them again.

How to redirect external line incoming call to an hunting-group

How to redirect external line incoming call to an hunting-group

By default, incoming calls from external lines will be routed to local users or auto-attendants.

But in some deployment, customers require that incoming call from external lines should be routed to hunting-group. Then local users can answer the incoming calls in round-robin order.

It is very easy to do that in MSS. Do you remember that we need configure a called number to trigger hunting-group, right? In this table, you only need configure it with external line number.

For example, external line is “1234567”, then in the “hunting group detection” configuration, we only need configure detection called number to be “1234567” to trigger hunting-group.