News:

On Tuesday September 6th the forum will be down for maintenance from 9:30 PM to 11:59 PM PDT

Main Menu

Single-Stage Dialing Through Any OBi Trunk

Started by RonR, June 27, 2011, 10:45:14 PM

Previous topic - Next topic

RonR

This article illustrates how to configure 1 to 98 OBi100/OBi110/OBi202 devices plus any number of OBiON Apps for single-stage dialing capability.  Any OBi or OBiON App can initiate a call through any trunk of any OBi.  OBi's are named #2 through #99, with no OBi named #1 due to Speed Dial #1 being forced to be an OBiON App by the OBiTALK Web Portal.

Three OBi100/OBi110/OBi202 devices will be used to illustrate the configuration steps.  The dialing syntax from an OBi or OBiON App to another OBi is:


     18005551212  ->  Local PrimaryLine
**1 18005551212  ->  Local SP1 Service
**2 18005551212  ->  Local SP2 Service
**8 18005551212  ->  Local LINE Port
**9 200123456      ->  Local OBiTALK Service

    2*18005551212  ->  OBi #2 PrimaryLine
2 **1 18005551212  ->  OBi #2 SP1 Service
2 **2 18005551212  ->  OBi #2 SP2 Service
2 **8 18005551212  ->  OBi #2 LINE Port
2 **9 200123456      ->  OBi #2 OBiTALK Service

    3*18005551212  ->  OBi #3 PrimaryLine
3 **1 18005551212  ->  OBi #3 SP1 Service
3 **2 18005551212  ->  OBi #3 SP2 Service
3 **8 18005551212  ->  OBi #3 LINE Port
3 **9 200123456      ->  OBi #3 OBiTALK Service

    4*18005551212  ->  OBi #4 PrimaryLine
4 **1 18005551212  ->  OBi #4 SP1 Service
4 **2 18005551212  ->  OBi #4 SP2 Service
4 **8 18005551212  ->  OBi #4 LINE Port
4 **9 200123456      ->  OBi #4 OBiTALK Service


OBi #   :  OBiTALK #
====      =======
OBi #2  :  200123002
OBi #3  :  200123003
OBi #4  :  200123004


Voice Services -> OBiTALK Service -> InboundCallRoute (OBi100/OBi110):

{(Mcot)>(<*1:>(Msp1)),(Mcot)>(<**1:>(Msp1)):sp1},{(Mcot)>(<*2:>(Msp2)),(Mcot)>(<**2:>(Msp2)):sp2},
{(Mcot)>(<*8:>(Mli)),(Mcot)>(<**8:>(Mli)):li},{(Mcot)>(<*9:>(Mpp)),(Mcot)>(<**9:>(Mpp)):pp},
{(Mcot)>(Mpli):pli},{(Mcot):aa},{ph}


Voice Services -> OBiTALK Service -> InboundCallRoute (OBi202):

{(Mcot)>(<*1:>(Msp1)),(Mcot)>(<**1:>(Msp1)):sp1},{(Mcot)>(<*2:>(Msp2)),(Mcot)>(<**2:>(Msp2)):sp2},
{(Mcot)>(<*3:>(Msp3)),(Mcot)>(<**3:>(Msp3)):sp3},{(Mcot)>(<*4:>(Msp4)),(Mcot)>(<**4:>(Msp4)):sp4},
{(Mcot)>(<*8:>(Mli)),(Mcot)>(<**8:>(Mli)):li},{(Mcot)>(<*9:>(Mpp)),(Mcot)>(<**9:>(Mpp)):pp},
{(Mcot)>(Mpli):pli},{(Mcot):aa},{ph1,ph2}

Note: Replace pli above (2 places) with the OBi's PHONE Port -> PrimaryLine trunk name (sp1,sp2,li,pp,tg1) as the OBi won't do it for you.


User Settings -> User Defined Digit Maps -> User Defined Digit MapX:

Label : cot
DigitMap : (200123002|200123003|200123004)

Note: These are trusted caller OBiTALK numbers.  This DigitMap should also contain the OBiTALK numbers of any OBiON Apps that are used.


In the PHONE Port and Auto Attendant DigitMap's, change [1-9]x?*(Mpli) to [1-9]x?*@@.

In the PHONE Port and Auto Attendant OutboundCallRoute's, change {([1-9]x?*(Mpli)):pp} to {([1-9]x?*@@.):pp}


Speed Dial #2 : PP(ob200123002)
Speed Dial #3 : PP(ob200123003)
Speed Dial #4 : PP(ob200123004)

yhfung

Thanks RonR for summarising our previous threads in a single thread such that it can be more concise and easy to read.

YH
Hong Kong and China OBi Users Group
www.telecom-cafe.com

facaletz

Quote from: RonR on June 27, 2011, 10:45:14 PM
This article illustrates how to configure 1 to 98 OBi100/OBi110 devices plus any number of OBiON Apps for single-stage dialing capability.  Any OBi or OBiON App can initiate a call through any trunk of any OBi.  OBi's are named #2 through #99, with no OBi named #1 due to Speed Dial #1 being forced to be an OBiON App by the OBiTALK Web Portal.

Three OBi100/OBi110 devices will be used to illustrate the configuration steps.  The dialing syntax from an OBi or OBiON App to another OBi is:


      18005551212  ->  Local PrimaryLine
**1 18005551212  ->  Local SP1 Service
**2 18005551212  ->  Local SP2 Service
**8 18005551212  ->  Local LINE Port
**9 200123456      ->  Local OBiTALK Service

     2*18005551212  ->  OBi #2 PrimaryLine
2 **1 18005551212  ->  OBi #2 SP1 Service
2 **2 18005551212  ->  OBi #2 SP2 Service
2 **8 18005551212  ->  OBi #2 LINE Port
2 **9 200123456      ->  OBi #2 OBiTALK Service

     3*18005551212  ->  OBi #3 PrimaryLine
3 **1 18005551212  ->  OBi #3 SP1 Service
3 **2 18005551212  ->  OBi #3 SP2 Service
3 **8 18005551212  ->  OBi #3 LINE Port
3 **9 200123456      ->  OBi #3 OBiTALK Service

     4*18005551212  ->  OBi #4 PrimaryLine
4 **1 18005551212  ->  OBi #4 SP1 Service
4 **2 18005551212  ->  OBi #4 SP2 Service
4 **8 18005551212  ->  OBi #4 LINE Port
4 **9 200123456      ->  OBi #4 OBiTALK Service


OBi #   :  OBiTALK #
====      =======
OBi #2  :  200123002
OBi #3  :  200123003
OBi #4  :  200123004


Voice Services -> OBiTALK Service -> InboundCallRoute:

{(Mcot)>(Mpli):pli},{(Mcot)>(<*1:>(Msp1)):sp1},{(Mcot)>(<*2:>(Msp2)):sp2},{(Mcot)>(<*8:>(Mli)):li},
{(Mcot)>(<*9:>(Mpp)):pp},{(Mcot)>(<**1:>(Msp1)):sp1},{(Mcot)>(<**2:>(Msp2)):sp2},
{(Mcot)>(<**8:>(Mli)):li},{(Mcot)>(<**9:>(Mpp)):pp},{(Mcot):aa},{ph}

Note: Replace pli above (2 places) with the OBi's PHONE Port -> PrimaryLine trunk name (sp1,sp2,li,pp,tg1) as the OBi won't do it for you.


User Settings -> User Defined Digit Maps -> User Defined Digit MapX:

Label : cot
DigitMap : (200123002|200123003|200123004)

Note: These are trusted caller OBiTALK numbers.  This DigitMap should also contain the OBiTALK numbers of any OBiON Apps that are used.


In the PHONE Port and Auto Attendant DigitMap's, change [1-9]x?*(Mpli) to [1-9]x?*@@.

In the PHONE Port and Auto Attendant OutboundCallRoute's, change {([1-9]x?*(Mpli)):pp} to {([1-9]x?*@@.):pp}


Speed Dial #2 : PP(ob200123002)
Speed Dial #3 : PP(ob200123003)
Speed Dial #4 : PP(ob200123004)

Hi there,It is nice,it is beautiful BUT depends how many Obis You want to sell,if the Obi meant to be for dummy end users like me ,i mean 99.999% of the population,Youl'll better consider putting all that stuff in the box,and leave us a few places where to put just REAL Phone or obi numbers and VOALA no headache!!
G'd Day from Down Under!

RonR

Quote from: facaletz on July 30, 2011, 03:17:31 PM
Hi there,It is nice,it is beautiful BUT depends how many Obis You want to sell,if the Obi meant to be for dummy end users like me ,i mean 99.999% of the population,Youl'll better consider putting all that stuff in the box,and leave us a few places where to put just REAL Phone or obi numbers and VOALA no headache!!
G'd Day from Down Under!

I don't sell OBi's.  I'm just a regular user like yourself.

QBZappy

Quote from: facaletz on July 30, 2011, 03:17:31 PM
Hi there,It is nice,it is beautiful BUT depends how many Obis You want to sell,if the Obi meant to be for dummy end users like me ,i mean 99.999% of the population,Youl'll better consider putting all that stuff in the box,and leave us a few places where to put just REAL Phone or obi numbers and VOALA no headache!!
G'd Day from Down Under!

Straight to the point. There is a strong message here.
Owner of the 1st OBi110/100 units in service in Canada & South America. 1st OBi202 on my street. 1st OBi1032 in Montreal.

facaletz

RonR!! You ,,regular'' users should get some slices from the bread!!!I thought you're promoting your own product.
It is ,,trendy'' now to trow the unfinished product on the market and put clever minds to finish it off for you!!
If u buy a computer you don't program it,just use it . Have a nice working week ahead...the weekend is just around the corner!

earthtoobi

Ron: Quick question on the digitmap:

You mentioned change Phone/AutoAttendant:
{([1-9]x?*(Mpli)):pp} to {([1-9]x?*@@.):pp}

if my understanding is right, the above means: No digit or single digit(starts with a  digit in the range 1-9) with a * after that and anything after the *.

if my understanding of the above is correct, then Obi speed dial references(gateway) can only be from 2-9 and cannot be 2 thru 99.

RonR

Quote from: earthtoobi on August 02, 2011, 11:34:55 AM
You mentioned change Phone/AutoAttendant:
{([1-9]x?*(Mpli)):pp} to {([1-9]x?*@@.):pp}

([1-9]x?*@@.)

[1-9]x? matches one- or two-digits in the range 1 - 99

* matches an *

@@. matches anything

earthtoobi

thanks Ron.


1. [1-9] in itself is a digit that can be from 1-9.
2. x?:zero or one digit between 0-9.

effectively the above give a range of 1-99.

RonR

Quote from: earthtoobi on August 02, 2011, 12:30:21 PM
1. [1-9] in itself is a digit that can be from 1-9.
2. x?:zero or one digit between 0-9.

effectively the above give a range of 1-99.

That's it!

Everton

#10
In My case I have only one (1) OBi110 Device and three (3) Android Phones and I want to be able to use Single-Stage Dialing Through Any OBi Trunk from any one of the three phones.  Following your detail procedure, I made the following changes.


     18005551212  ->  Local PrimaryLine
**1 18005551212  ->  Local SP1 Service (Goggle Voice setup on SP1 - Local Primary Line)
**2 18005551212  ->  Local SP2 Service (VOIP.ms setup on SP2)
**8 18005551212  ->  Local LINE Port     (not used at this time)
**9 200123456     ->  Local OBiTALK Service

Also have CallWithUs setup for outgoing on Voice Gateway3 (for International calls only!)

   
  My OBi
End Points                                        OBi No.    
=============                         ============
OBi #1 (Home)                             :  200123456
OBi #1 (Everton)                          :  290234561

I have three Android Mobile Devices each with the OBiON App for Android loaded and setup two (2) additional OBiTALK Accounts, which generates two additional OBiTALK Numbers (290XXXXX2 and 290XXXXX3).  So, there are a total of three (3) OBiTALK Numbers as shown below, with  OBi No. 290234561, assigned to my main OBiTalk Account.

OBiTALK #                                                        My OBiTALK No.
=============                                             ===============
OBiON #1 (Everton Mobile Phone)                        :   290234561
OBiON #2 (Friend 1  Mobile Phone)                       :  290XXXXX2
OBiON #3 (Friend 2  Mobile Phone)                       :  290XXXXX3



Voice Services -> OBiTALK Service -> InboundCallRoute:

{(Mcot)>(Msp1):sp1},{(Mcot)>(<*1:>(Msp1)):sp1},{(Mcot)>(<*2:>(Msp2)):sp2},{(Mcot)>(<*8:>(Mli)):li},
{(Mcot)>(<*9:>(Mpp)):pp},{(Mcot)>(<**1:>(Msp1)):sp1},{(Mcot)>(<**2:>(Msp2)):sp2},
{(Mcot)>(<**8:>(Mli)):li},{(Mcot)>(<**9:>(Mpp)):pp},{(Mcot):aa},{ph}

Note: Replace pli above (2 places) with the OBi's PHONE Port -> PrimaryLine trunk name (sp1,sp2,li,pp,tg1) as the OBi won't do it for you.


User Settings -> User Defined Digit Maps -> User Defined Digit MapX:

Label : cot
DigitMap : (200123456|290234561|290XXXXX2|290XXXXX3)

Note: These are trusted caller OBiTALK numbers.  This DigitMap should also contain the OBiTALK numbers of any OBiON Apps that are used.


In the PHONE Port and Auto Attendant DigitMap's, change [1-9]x?*(Mpli) to [1-9]x?*@@.

In the PHONE Port and Auto Attendant OutboundCallRoute's, change {([1-9]x?*(Mpli)):pp} to {([1-9]x?*@@.):pp}


Speed Dial #2 : PP(ob200123456)

We also have each OBiTALK numbers as part of the speed dial and trusted callers list!

For Mobile Device, Everton, I have added Friend 1 and Friend 2 to "My Circle of Trust", and for Friend 1, I have added Everton and Friend 2 to the "My Circle of Trust" and finally, for Friend 2, I have added Everton and Friend 1 to the "My Circle of Trust".

After making the changes outlined above, I did a test call from OBiON #2 (Friend 1) to a VOIP.ms number and the phone did not ring, yet I got their voice mail.  I also, call a Target Store and was able to speak to someone (that works).

Looking at what I did, could you spot what could cause the VOIP.ms number (Physical analog phone) to NOT ring.  This number is also listed as a speed dial and trusted caller on all three OBiTALK App and the OBi110 speed dial list!!!

RonR

#11
Quote from: Everton on August 09, 2011, 07:14:02 AM
Also have CallWithUs setup for outgoing on Voice Gateway3 (for International calls only!)

If you want access to Voice Gateway3 (presumably **3) from OBiON Apps, you will need to add it to the InboundCallRoute.

Voice Services -> OBiTALK Service -> InboundCallRoute:

{(Mcot)>(Msp1):sp1},{(Mcot)>(<*1:>(Msp1)):sp1},{(Mcot)>(<*2:>(Msp2)):sp2},{(Mcot)>(<*3:>(Mvg3)):vg3},
{(Mcot)>(<*8:>(Mli)):li},{(Mcot)>(<*9:>(Mpp)):pp},{(Mcot)>(<**1:>(Msp1)):sp1},{(Mcot)>(<**2:>(Msp2)):sp2},
{(Mcot)>(<**3:>(Mvg3)):vg3},{(Mcot)>(<**8:>(Mli)):li},{(Mcot)>(<**9:>(Mpp)):pp},{(Mcot):aa},{ph}

Quote from: Everton on August 09, 2011, 07:14:02 AM
We also have each OBiTALK numbers as part of the speed dial and trusted callers list!

For Mobile Device, Everton, I have added Friend 1 and Friend 2 to "My Circle of Trust", and for Friend 1, I have added Everton and Friend 2 to the "My Circle of Trust" and finally, for Friend 2, I have added Everton and Friend 1 to the "My Circle of Trust".

Trusted Callers and Circle of Trust on the OBiTALK Web Portal should not be used.  All Trusted Caller / Circle of Trust security is handled by the changes described in this thread.  Trusted Caller's OBiTALK numbers should simply be added to this list (as you've already done):

User Settings -> User Defined Digit Maps -> User Defined Digit MapX:

Label : cot
DigitMap : (200123456|290234561|290XXXXX2|290XXXXX3)

Quote from: Everton on August 09, 2011, 07:14:02 AM
After making the changes outlined above, I did a test call from OBiON #2 (Friend 1) to a VOIP.ms number and the phone did not ring, yet I got their voice mail.  I also, call a Target Store and was able to speak to someone (that works).

Looking at what I did, could you spot what could cause the VOIP.ms number (Physical analog phone) to NOT ring.  This number is also listed as a speed dial and trusted caller on all three OBiTALK App and the OBi110 speed dial list!!!

Again, do not use the OBiTALK Web Portal's Trusted Caller / Circle of Trust mechanisms.

If VOIP.ms voicemail answered, then your call obviously went through to VOIP.ms and the OBi has no control over whether the phone on that end rings or not.

QBZappy

Quote from: RonR on August 09, 2011, 09:40:38 AM
Trusted Callers and Circle of Trust on the OBiTALK Web Portal should not be used.  All Trusted Caller / Circle of Trust security is handled by the changes described in this thread.  Trusted Caller's OBiTALK numbers should simply be added to this list (as you've already done):

Implied in this comment is the fact that the OBi should be setup either via the OBi web portal or the OBi unit directly. OBi is designed to be programmed  either way. Users must pick one method. Obviously RonR has designed his code to be setup on the OBi unit directly, making you choose the OBi unit configuration method.

If / when OBi integrates "Single-Stage Dialing Through Any OBi Trunk"  into one of their wizards it looks like RonR is generously offering his time to support this.
Owner of the 1st OBi110/100 units in service in Canada & South America. 1st OBi202 on my street. 1st OBi1032 in Montreal.

RonR

Quote from: QBZappy on August 09, 2011, 10:33:41 AM
Quote from: RonR on August 09, 2011, 09:40:38 AM
Trusted Callers and Circle of Trust on the OBiTALK Web Portal should not be used.  All Trusted Caller / Circle of Trust security is handled by the changes described in this thread.  Trusted Caller's OBiTALK numbers should simply be added to this list (as you've already done):

Implied in this comment is the fact that the OBi should be setup either via the OBi web portal or the OBi unit directly. OBi is designed to be programmed  either way. Users must pick one method. Obviously RonR has designed his code to be setup on the OBi unit directly, making you choose the OBi unit configuration method.

There is nothing unique about the configuration described in this thread.  Users are free to implement the changes described here directly through the OBi (requiring that Auto Provisoning be disabled) or through the OBiTALK Web Portal (requiring that Auto Provisioning be enabled).

Trusted Caller / Circle of Trust is wholly controlled by rules in the OBi's InboundCallRoute.  Since configuration through the OBiTALK Web Portal generates an InboundCallRoute that limits single-stage dialing to the PrimaryLine only, it's necessary to use a custom set of InboundCallRoute rules to provide single-stage dialing through any OBi trunk.  The OBiTALK Web Portal does not provide Trusted Caller / Circle of Trust support for custom InboundCallRoute rules.  As such, the OBiTALK Web Portal cannot be used for Trusted Caller / Circle of Trust configuration in this case.

Quote from: QBZappy on August 09, 2011, 10:33:41 AM
If / when OBi integrates "Single-Stage Dialing Through Any OBi Trunk"  into one of their wizards it looks like RonR is generously offering his time to support this.

If the OBiTALK Web Portal supported "Single-Stage Dialing Through Any OBi Trunk", there wouldn't be a need for a custom set of InboundCallRoute rules as described in this thread.  Regardless of what is integrated in the future, I hope to continue generously offering my time to support users any way I can.

Everton

Quote from: RonR on August 09, 2011, 09:40:38 AM
Quote from: Everton on August 09, 2011, 07:14:02 AM
Also have CallWithUs setup for outgoing on Voice Gateway3 (for International calls only!)

If you want access to Voice Gateway3 (presumably **3) from ONiON Apps, you will need to add it to the InboundCallRoute.

Voice Services -> OBiTALK Service -> InboundCallRoute:

{(Mcot)>(Msp1):sp1},{(Mcot)>(<*1:>(Msp1)):sp1},{(Mcot)>(<*2:>(Msp2)):sp2},{(Mcot)>(<*3:>(Mvg3)):vg3},
{(Mcot)>(<*8:>(Mli)):li},{(Mcot)>(<*9:>(Mpp)):pp},{(Mcot)>(<**1:>(Msp1)):sp1},{(Mcot)>(<**2:>(Msp2)):sp2},
{(Mcot)>(<**3:>(Mvg3)):vg3},{(Mcot)>(<**8:>(Mli)):li},{(Mcot)>(<**9:>(Mpp)):pp},{(Mcot):aa},{ph}


Great, you are one step ahead of me, since this was going to be my next question!  Thanks and I did go ahead and add this feature.  Maybe you should add it to you general writeup.

Turns out the reason the phone did not ring is that I had a call filtering associated with the CID associated with SP1, which sent the calls to voice mail without ringing the phone...LOL!!  Once I removed the VOIP.ms filter the calls came through.  I couldn't understand why the calls work to some numbers and not the VOIP.ms DID.

I also, removed all the "My Circle of Trust" and "Trusted Callers" setup from all three OBiONs!

BTW, your writeup, although appearing intimating at first glance, is actually quite simple.  Excellent work/creativity!!  Thanks for your help on this.

eduMIA

RonR as per your previous reply, you mentioned that this is possible:
- If you want to use two Google Voice accounts and be able to handle four calls, (each Google Voice account can handle two calls) you would want to use Trunk Group1 as your PrimaryLine.  Then when SP1 has two calls, calls number 3 and number four will go to SP2. Before I purchased the devices Obihai also mentioned that this will work.
I have configured and tested the gv accounts, the problem is that when making call3 instead of being handled by sp2 I get a service provider rejected the call, reason 503 message.
I called Obihai support line and the rep told me that trunk works as a "fail over", if sp1 is not working then it goes to sp2...!!!????
I have in the Outbound settings-Phone primary line the Trunk Group 1 and Trunk Group 1 has sp1,sp2 and is enable.
Am I missing something? Do I also have to configure DigitMap and OutboundCallRoute.?
Your help is appreciated!

RonR

You don't need to modify the PHONE Port DigitMap or OutboundCallRoute to use Trunk Group1.

Trunk Group1 defaults to sp1,sp2.  You simply need to set:

Physical Interfaces -> PHONE Port -> PrimaryLine : Trunk Group 1

SP1 will be used for outgoing calls first, followed by SP2 if all sessions of SP1 are in use.

When you implement the changes described in this thread, replace {(Mcot)>(Mpli):pli} with {(Mcot)>(Mtg1):tg1} to have Trunk Group1 also used for single-stage dialing through the PrimaryLine.

lhm.

#17
Not working for me. I can dial out through the pap2 connected ObiOn-Pc App, works fine including **9 222 222 222 , just can't switch trunks. ie:**3  still tries to go out on tg1. The call log shows that **3 18005551212 is trying to go out on SP1 (part of tg1) which results in a busy signal as it is also sending **3. All other settings are per the RonR's instruction. Phone connected to Obi100 will switch trunks (**3 and **2) and connect/call fine including **9 222 222 222. Trying **2 gives the same result as **3. 

What am I missing? I am using only one Obi100 w/provisioning disabled.

ObiTalk
{(Mcot)>(Mtg1):tg1},{(Mcot)>(<*1:>(Msp1)):sp1},{(Mcot)>(<*2:>(Msp2)):sp2},{(Mcot)>(<*3:>(Mvg1)):vg1},{(Mcot)>(<*8:>(Mli)):li}, {(Mcot)>(<*9:>(Mpp)):pp},{(Mcot)>(<**1:>(Msp1)):sp1},{(Mcot)>(<**2:>(Msp2)):sp2},{(Mcot)>(<**3:>(Mvg1)):vg1},{(Mcot)>(<**8:>(Mli)):li},{(Mcot)>(<**9:>(Mpp)):pp},{(Mcot):aa},{ph}

AA DigitMap ([1-9]x?*@@.|[1-9]|[1-9][0-9]|<00:$1>|0|**1(Msp1)|**2(Msp2)|**9(Mpp)|(Mpli))          
AA OutboundCallRoute {([1-9]x?*@@.):pp},{0:ph},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2},{(<**9:>(Mpp)):pp},{(Mpli):pli}      

Phone Port
DigitMap ([1-9]x?*@@.|[1-9]|[1-9][0-9]|911|**0|***|#|*1(Msp1)|*2(Msp2)|**3(Mvg1)|**2(Mvg2)|**6(Mvg6)|**7(Mvg7)|**9(Mpp)|(Mpli)|x.*x.)

OutboundCallRoute {([1-9]x?*@@.):pp},{**0:aa},{***:aa2},{(<*1:>(Msp1)):sp1},{(<*2:>(Msp2)):sp2},{(<**3:>(Mvg1)):vg1},{(<**2:>(Mvg2)):vg2}, {(<**6:>(Mvg6)):vg6},{(<**7:>(Mvg7)):vg7},{(<**8:>(Mli)):li},{(<**9:>(Mpp)):pp},{(Mpli):pli}


RonR

lhm.,

What is the Trunk Group1 -> DigitMap?

lhm.

#19
Digit Map is (Msp1)

The Trunk List is sp1,sp2,vg1,vg2