CircleNet would like to introduce ourselves to the Obi world
azrobert:
zorlac,
Yes, it's all one string.
It's for an OBi202 using VG1 for outbound calls.
You have to modify other DigitMaps and this might not fit your setup.
Read some of the previous posts.
I have a question for you.
How did you paste that picture in your post?
I have a Windows 7 machine and it has the Snipping Tool.
I can paste a Snip into Word using the Special Paste, but I can't paste a Snip anywhere else.
Thanks
zorlac:
Quote from: azrobert on April 25, 2014, 09:05:59 pm
zorlac,
I have a question for you.
How did you paste that picture in your post?
I have a Windows 7 machine and it has the Snipping Tool.
I can paste a Snip into Word using the Special Paste, but I can't paste a Snip anywhere else.
Thanks
Man, I'd be grateful to help you!
I'm running Linux but in Windoze the print screen key will usually capture the screen to the clipboard and then I'd paste it into a simple graphics program (Irfanview maybe?) for cropping/save as .jpg.
I use tinypic to host the pics and copy the [ img]this url[/img] to post here.
I hope that's kinda clear.
azrobert:
Quote from: zorlac on April 25, 2014, 09:18:53 pm
I'm running Linux but in Windoze the print screen key will usually capture the screen to the clipboard and then I'd paste it into a simple graphics program (Irfanview maybe?) for cropping/save as .jpg.
I use tinypic to host the pics and copy the [ img]this url[/img] to post here.
After the print screen I used Paint to crop the image. I could paste the image into a Word document instead of the special paste required by an image captured by the Snipping tool. It's not that important to me to go thru the trouble of hosting the image somewhere. I thought there might be a way just to paste the image directly into a post. See how much I knew about this stuff. Anyway, I know how to do it now.
Thanks
zorlac:
OK this config works (on my obi100) but there is a ~13sec ring pause. :(
DigitMap: ([1-9]x?*(Mpli)|[1-9]S9|[1-9][0-9]S9|911|**0|***|#|**1(Msp1)|**2(Msp2)|**9(Mpp)|(Mpli))
OutboundCallRoute: {(Mvg1):vg1},{([1-9]x?*(Mpli)):pp},{**0:aa},{***:aa2},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2},{(<**9:>(Mpp)):pp},{(Mpli):pli}
Pressing # after dialing cuts the delay to ~5sec so it seems that maybe 10sec of my delay is coming from my digit map.
Sam, I know you have bigger fish to fry, but some stock config strings for the obi box parameters would be real handy!
Thanks
ianobi:
@ azrobert & dial.tone
I'm coming very late to this party - I note that I missed the beer on offer :)
Quote
[1-9]S9
[1-9][0-9]S9
The above rules are for speed dials and allow numbers 1 thru 9 and 10 thru 99.
I don't know why they have a 9 second delay.
I would change them to:
[1-9]
[1-9][0-9]
By coincidence, I was just answering a question on speed dials. I would urge you to put back the "S9" delays in your Phone Port DigitMap. The purpose of the S9 delays is to prevent numbers such as 911 being seen by the OBi as speed dial 9 followed by digits 11 etc.
If you declutter your digit maps, as I also like to do, then often we remove these rules:
xx.|(Mipd)|[^*#]@@.
Removing these rules in the Primary Line DigitMap (Mpli) removes a two second delay in the overall Phone Port DigitMap. This is mostly good, but we are then back to the 911 situation. If you have removed the S9 delays then when you dial 911 the 9 will instantly be matched as a speed dial and digits 11 will most likely not match anywhere.
If dialling numbers longer than three digits there is no problem as the number will be matched elsewhere most likely in the Primary Line DigitMap. Therefore the S9 should not affect normal numbers. If you press # during the S9 delay period, then that tells the OBi you have finished dialling. Pressing 8# results in speed dial 8 being used with no delay.
Navigation
[0] Message Index
[#] Next page
[*] Previous page