OBiTALK Community

General Support => Day-to-Day Use => Topic started by: marty01 on January 07, 2024, 06:51:37 AM

Title: OBi300 + Anveo, Check voicemail, *99
Post by: marty01 on January 07, 2024, 06:51:37 AM
Got a OBi300 box, and simple landline phone all hooked up. Phone number and service is from:

https://www.anveo.com/enter.asp

Able to make and receive phone calls. Want to check voice mails from the phone. When I dial *99 I hear a busy signal. How to make this work?

Contacted support at Anveo and HP / OBi / Poly. Getting no help with this issue.

Think I need to configure OBi300 devise to allow *99 star code to pass through to Anveo. Digit Map if I am understanding correctly? Look at OBiTALK website > OBi Dashboard > OBi Expert Configuration Menu > Enter OBi Expert > User Settings > User Defined Digit Maps. Please see 2 images of User Defined Digit Maps.

PLEASE NOTE THAT I DO NOT KNOW IF THIS IS THE RIGHT PLACE TO CHANGE DIGIT MAP CONFIGURATIONS?
User_Defined_Digit_Maps01.png
User_Defined_Digit_Maps02.png

So how to check voicemails from the phone?

Thanks for the help!
Title: Re: OBi300 + Anveo, Check voicemail, *99
Post by: drgeoff on January 07, 2024, 07:39:32 AM
Wrong place.  Should be Physical Interfaces, Phone1 Port, Digit Map.
Title: Re: OBi300 + Anveo, Check voicemail, *99
Post by: marty01 on January 07, 2024, 09:44:33 AM
OK... Please see 4 print screens of PHONE1 Port
[Sorry, you aren't allowed to post any more attachments. 79.6 KB]
Will make second post.
ps01PHONE1_Port_PHONE_Port_Ringer01.png
ps02PHONE1_Port_Port_Settings01.png
ps03PHONE1_Port_Calling_Features01.png
ps04PHONE1_Port_Calling_Features02_Call Fowarding.png   
Title: Re: OBi300 + Anveo, Check voicemail, *99
Post by: marty01 on January 07, 2024, 09:46:22 AM
Please see 5th print screen of PHONE1 Port
ps05PHONE1_Port_Timers_Tip-Ring Voltage Polarity01.png

Where does *99 digit map go?
Title: Re: OBi300 + Anveo, Check voicemail, *99
Post by: drgeoff on January 07, 2024, 09:59:14 AM
What is your question?
Title: Re: OBi300 + Anveo, Check voicemail, *99
Post by: marty01 on January 07, 2024, 10:09:18 AM
Where does *99 digit map go?
Title: Re: OBi300 + Anveo, Check voicemail, *99
Post by: azrobert on January 07, 2024, 10:11:02 AM
Assuming Anveo is defined on SP1:
Service Providers -> ITSP Profile A General -> DigitMap:
Add *99| after the beginning parenthesis.

Physical Interfaces -> Phone Port1 -> DigitMap
Add *99| after the beginning parenthesis.

Edit:
Phone port digit map validates the dialed number.
Service provider digit map is used to route the number.
Title: Re: OBi300 + Anveo, Check voicemail, *99
Post by: marty01 on January 07, 2024, 10:40:48 AM
OK...

Service Providers > ITSP Profile A General

or

Physical Interfaces > PHONE1 Port

Where should I make changes to Digit Map *99 so I can check voicemail from phone?
Title: Re: OBi300 + Anveo, Check voicemail, *99
Post by: drgeoff on January 07, 2024, 10:43:22 AM
Or:

Physical Interfaces -> Phone Port1 -> DigitMap
Add *99| after the beginning parenthesis.

Physical Interfaces -> Phone Port1 -> OutboundCallRoute
Add {(*99:sp1)}, before everything else already present.  The comma separator must be included.

Note that you need to clear both boxes at the right hand end of each line to make it editable.
Title: Re: OBi300 + Anveo, Check voicemail, *99
Post by: drgeoff on January 07, 2024, 10:45:38 AM
Quote from: marty01 on January 07, 2024, 10:40:48 AMOK...

Service Providers > ITSP Profile A

or

Physical Interfaces > PHONE1 Port

Where should I make changes to Digit Map *99 so I can check voicemail from phone?
There is no DigitMap named *99. You add the characters *99 in the places indicated by azrobert or myself.
Title: Re: OBi300 + Anveo, Check voicemail, *99
Post by: marty01 on January 07, 2024, 11:12:11 AM
Exactly where should I add the characters *99? In one place or all the places mentioned by Azrobert and Drgeoff?

To clarify:

Service Providers -> ITSP Profile A General -> DigitMap

Physical Interfaces -> Phone Port1 -> DigitMap

Physical Interfaces -> Phone Port1 -> OutboundCallRoute
Title: Re: OBi300 + Anveo, Check voicemail, *99
Post by: drgeoff on January 07, 2024, 11:21:47 AM
Either make the additions in the two places that azrobert told you or the two places that I did.  Note that the additions are not just the three characters *99.
Title: Re: OBi300 + Anveo, Check voicemail, *99
Post by: marty01 on January 07, 2024, 11:35:53 AM
OK Drgeoff wins.

Physical Interfaces -> Phone Port1 -> DigitMap
Add *99| after the beginning parenthesis.
([1-9]x?*(Mpli)|[1-9]S9|[1-9][0-9]S9|911|**0|***|#|##|**70(Mli)|**8(Mbt)|**81(Mbt)|**82(Mbt2)|**1(Msp1)|**2(Msp2)|**3(Msp3)|**4(Msp4)|**9(Mpp)|(Mpli))

Change to:
(*99[1-9]x?*(Mpli)|[1-9]S9|[1-9][0-9]S9|911|**0|***|#|##|**70(Mli)|**8(Mbt)|**81(Mbt)|**82(Mbt2)|**1(Msp1)|**2(Msp2)|**3(Msp3)|**4(Msp4)|**9(Mpp)|(Mpli))

Physical Interfaces -> Phone Port1 -> OutboundCallRoute
Add {(*99:sp1)}, before everything else already present.  The comma separator must be included.
{([1-9]x?*(Mpli)):pp},{(<##:>):li},{(<**70:>(Mli)):li},{(<**82:>(Mbt2)):bt2},{(<**81:>(Mbt)):bt},{(<**8:>(Mbt)):bt},{**0:aa},{***:aa2},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2},{(<**3:>(Msp3)):sp3},{(<**4:>(Msp4)):sp4},{(<**9:>(Mpp)):pp},{(Mpli):pli}
Change to:
{(*99:sp1)},{([1-9]x?*(Mpli)):pp},{(<##:>):li},{(<**70:>(Mli)):li},{(<**82:>(Mbt2)):bt2},{(<**81:>(Mbt)):bt},{(<**8:>(Mbt)):bt},{**0:aa},{***:aa2},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2},{(<**3:>(Msp3)):sp3},{(<**4:>(Msp4)):sp4},{(<**9:>(Mpp)):pp},{(Mpli):pli}
Is this correct?
Title: Re: OBi300 + Anveo, Check voicemail, *99
Post by: drgeoff on January 07, 2024, 11:39:52 AM
No. It appears that you cannot read and follow instructions.  Try again.
Title: Re: OBi300 + Anveo, Check voicemail, *99
Post by: marty01 on January 07, 2024, 12:18:53 PM
Sorry, I am not the sharpest tool in the shed. Appears that I forgot the vertical bar.

QuoteTo type the vertical bar on most keyboards, press Shift + \.

||||||||||||

I learned a new keyboard character. This is exciting!

Lets try again.

Physical Interfaces -> Phone Port1 -> DigitMap
Add *99| after the beginning parenthesis.
([1-9]x?*(Mpli)|[1-9]S9|[1-9][0-9]S9|911|**0|***|#|##|**70(Mli)|**8(Mbt)|**81(Mbt)|**82(Mbt2)|**1(Msp1)|**2(Msp2)|**3(Msp3)|**4(Msp4)|**9(Mpp)|(Mpli))
Change to:
(*99|[1-9]x?*(Mpli)|[1-9]S9|[1-9][0-9]S9|911|**0|***|#|##|**70(Mli)|**8(Mbt)|**81(Mbt)|**82(Mbt2)|**1(Msp1)|**2(Msp2)|**3(Msp3)|**4(Msp4)|**9(Mpp)|(Mpli))
The second code in post above ↑ think that is correct?

Is this all correct?
Title: Re: OBi300 + Anveo, Check voicemail, *99
Post by: drgeoff on January 07, 2024, 02:08:49 PM
Looks OK but the proof of the pudding is in the eating.
Title: Re: OBi300 + Anveo, Check voicemail, *99
Post by: marty01 on January 07, 2024, 04:29:02 PM
Test complete!

Physical Interfaces -> Phone Port1 -> DigitMap
Add *99| after the beginning parenthesis.
and
Physical Interfaces -> Phone Port1 -> OutboundCallRoute
Add {(*99:sp1)}, before everything else already present.  The comma separator must be included.

See Print Screen of before I clicked the Submit button.
done01.png
IT BROKE :(
No service configured error. Please log into Obitalk and configure your device.

Click - Revert All to OBiTALK Settings
FIXED :)
Can make and receive calls.

Notes on the RED exclamation mark !
QuoteIf you really want to remove the "!" mark, you need to uncheck the OBiTALK setting checkbox first and check the Device Default checkbox next to these two parameters. And then "submit" you modification again.  Also check the OBiTALK setting if you like OBiTALK to manage them for you in the future.

Lets try the Azrobert method.

Assuming Anveo is defined on SP1:
Service Providers -> ITSP Profile A General -> DigitMap:
Add *99| after the beginning parenthesis.

IT WORKS! :)  Dial *99 to access voicemail from the phone. Works perfectly. I am happy. See print screen of after I clicked the Submit Button.
done02.png

Now we have a new issue. Will start a new topic.

Voicemail Notification Stutter Dial Tone
Title: Re: OBi300 + Anveo, Check voicemail, *99
Post by: drgeoff on January 08, 2024, 03:32:38 AM
I probably got the () pair misplaced.  More likely that

{(*99):sp1},

or even

{*99:sp1},

would have worked.