Setup: Small office 1 reception obi 202 and 1 back office obi 202 and 2 phones. I though we can call obi to obi but when I dial the other obi number it will not connect. I am dialing the direct 9 digit number associated with the obi.
Also when A call comes in and answered at the reception desk is there any way to transfer the call to the obi in my back office? She usually puts the call on hold and I walk up to the front and answer it there. ???
Using the default settings you need to dial **9xxxxxxxxx (xxxxxxxxx is the OBi number).
To transfer a call:
Flash (you will get dial tone)
Dial **9xxxxxxxxx
Hang up when extension answers.
You can setup a Speed Dial instead of dialing **9xxxxxxxx
User Settings -> Speed Dials -> Select a SD number
pp(xxxxxxxxx) xxxxxxxxx= OBi Number
You can also set it up to ring a specific phone port on the OBi202.
just tried the **9 and obi number but I get the obi attendant and then have to dial 1 to get the other obi to ring.
the speed dial options just give the same rejection "The number you dialed was rejected by the service provider reason 404"
Change the following on the receiving OBi202.
Voice Services -> OBiTalk Service -> X_InboundCallRoute: ph
---------------------------------------
After transferring a call hit Flash instead of hanging up to get a 3 way conference.
Sorry about the Speed Dials, I don't use OBiTalk.
From the Dashboard Speed Dials are on the left column.
You probably have a Speed Dial already defined.
It will be in this format PP(obxxxxxxxxx)
Both formats are correct.
Dial the 1 or 2 digit speed dial number.
Yes I see the speed dials already setup! Thank-you BUT I still get the rejection notice
Under obitalk service there is only InboundCallRoute NOT x_InboundCallRoute that is only under SP1 Service
MAYBE It does not work because I setup an ip phone on one of the obi 200 and the obi uses it as a proxy?? Each obi has its own number and speed dial setup on the obi dashboard, but the speed dials just dial **9 and obi number but I get rejections from the service provider??
I shouldn't do this stuff from my failing memory. LOL
You are correct, it's InboundCallRoute.
The SP trunks have X_InboundCallRoute.
Let's start over.
Again, I don't use OBiTalk.
If I suggest or say something that's not correct, please someone jump in and correct me.
I think you setup a separate OBiTalk userid for each OBi202.
You then added the OBi202 to the other userid's Circle of Trust.
That is why you were directed to the Auto Attendant when you called the other OBi202.
Remove the OBi202 from the COT.
You don't need the COT to call the other OBi202.
I don't know if after you removed the rules from the InboundCallRoute OBiTalk re-added them because of the COT entry.
I forgot the default Speed Dial might be in the format **9xxxxxxxxx
This should work, but I like the format PP(xxxxxxxxx)
The Trunk setup as a Proxy will not affect OBi to OBi calling via OBiTalk network.
Check the following and see if it's still setup correctly.
Voice Services -> OBiTalk Service -> InboundCallRoute: ph
Is it still failing?
What is the error message?
Sorry I had REAL work to do!
OK so I removed the obi from the dashboard set it up under a different email address and added each obi to the others COT, still getting errors THE COULDNT COMPLETE CALL message. Let me ask this question both the obis are using the same GV numbers could THAT be the problem? ??? BTW THANKS for all the help I have tried getting help in the past with no answers! I have tried to setup Obiplus to do this that way but I could never get it to work. I am very positive about it working this way! Been using the obis for couple of years now and wanting them to use the ip phones and be able to transfer call and intercom would be GREAT HELP
Sorry, you didn't understand me. I thought you had 2 emails and had the OBi202s in COT. I also thought that was causing the problem. When the OBi is in COT you will be sent to the Auto Attendant.
Can you setup both OBi202s under 1 email?
Don't do anything.
I'm going to do this another way.
I'll post back in a few minutes.
Which SPx is setup for the Proxy?
SP4 I setup just like in the tutorial
http://www.obihai.com/docs/OBi-VoIP-Device-Attach-Legacy-IP-Phone-Workbook-v1-0.pdf
EXACT configuration. Same office same router 1 obi 200 with ip phone attached. 1 desk phone connected to obi 202, 1 obi 202 with desk phone and ip phone connected. Only reason using both ip and desk is to keep using obi's while sorting this out. I tried configuring obiplus but it never worked. The Cisco ip phones are very nice but I guess I can just use the regular phones on the obis if it does not work. All 3 obi's are on same dashboard with GV configured on S1 and another GV on SP2.
I haven't forgotten you.
I have about 3/4 of the config complete for your 3 OBi's.
I'm setting up the Obi's to talk directly to each other using your LAN (not over the OBiTalk Network).
I have a bunch of things to do.
I will finish the config latter tonight.
I'm assuming you have a free SP (SP3) trunk on each OBi2xx.
Please post if this is not true.
I don't like using OBiTalk to call other OBi's on your LAN.
The call goes up to the OBiTalk server and back to the other OBi.
It also adds another point of possible failure.
Using the below configuration the call only uses your local network.
You also don't have to do anything with COT.
Dial 100 to ring phone port#1 on OBi202#1
Dial 101 to ring phone port#2 on OBi202#1
Dial 200 to ring phone port#1 on OBi202#2
Dial 201 to ring phone port#2 on OBi202#2
Dial 202 to ring IP phone connected to OBi202#2
Dial 300 to ring phone port#1 on OBi200
Dial 301 to ring IP phone connected to OBi200
You should assign static IP addresses to all devices.
Hopefully, I didn't make any mistakes.
OBi202#1 (IP Address 192.168.1.100)
Service Providers -> ITSP Profile C -> SIP -> ProxyServer : 127.0.0.1
Service Providers -> ITSP Profile C -> SIP -> X_DiscoverPublicAddress: (unchecked)
Voice Services -> SP3 Service -> AuthUserName : OBi202a
Voice Services -> SP3 Service -> X_RegisterEnable : (unchecked)
Voice Services -> SP3 Service -> X_ServProvProfile : C
Replace your Voice Services -> SP3 Service -> X_InboundCallRoute with following:
{OBi202b|OBi200>100:ph},{OBi202b|OBi200>101:ph2},{ph}
Physical Interfaces -> Phone Port1 -> DigitMap
Add AFTER the beginning parenthesis: 101|200|201|202|300|301|
It will look like this:
(101|200|201|202|300|301|.....the current settings....)
Physical Interfaces -> Phone Port1
Add the following to the beginning of the OutboundCallRoute:
{101:ph2},{(Mp2p):sp3},
Physical Interfaces -> Phone Port2 -> DigitMap
Add AFTER the beginning parenthesis: 100|200|201|202|300|301|
It will look like this:
(100|200|201|202|300|301|.....the current settings....)
Physical Interfaces -> Phone Port2
Add the following to the beginning of the OutboundCallRoute:
{100:ph},{(Mp2p):sp3},
User Settings -> User Defined Digit Maps
Label: p2p
DigitMap: ((200|201)<:@192.168.1.101:5062>|202<:@192.168.1.111:5060>|300<:@192.168.1.102:5062>|301<:@192.168.1.112:5060>)_____________________________________________________________________________
OBi202#2 (IP Address 192.168.1.101)
w/IP Phone (IP Address 192.168.1.111)
Service Providers -> ITSP Profile C -> SIP -> ProxyServer : 127.0.0.1
Service Providers -> ITSP Profile C -> SIP -> X_DiscoverPublicAddress: (unchecked)
Voice Services -> SP3 Service -> AuthUserName : OBi202b
Voice Services -> SP3 Service -> X_RegisterEnable : (unchecked)
Voice Services -> SP3 Service -> X_ServProvProfile : C
Replace your Voice Services -> SP3 Service -> X_InboundCallRoute with following:
{OBi202a|OBi200>200:ph},{OBi202a|OBi200>201:ph2},{ph}
Physical Interfaces -> Phone Port1 -> DigitMap
Add AFTER the beginning parenthesis: 100|101|201|202|300|301|
It will look like this:
(100|101|201|202|300|301|.....the current settings....)
Physical Interfaces -> Phone Port1
Add the following to the beginning of the OutboundCallRoute:
{201:ph2},{(Mp2p):sp3},
Physical Interfaces -> Phone Port2 -> DigitMap
Add AFTER the beginning parenthesis: 100|101|200|202|300|301|
It will look like this:
(100|101|200|202|300|301|.....the current settings....)
Physical Interfaces -> Phone Port2
Add the following to the beginning of the OutboundCallRoute:
{200:ph},{(Mp2p):sp3},
User Settings -> User Defined Digit Maps
Label: p2p
DigitMap: ((100|101)<:@192.168.1.100:5062>|202<:@192.168.1.111:5060>|300<:@192.168.1.102:5062>|301<:@192.168.1.112:5060>)_____________________________________________________________________________
OBi200 (IP Address 192.168.1.102)
w/IP Phone (IP Address 192.168.1.112)
Service Providers -> ITSP Profile C -> SIP -> ProxyServer : 127.0.0.1
Service Providers -> ITSP Profile C -> SIP -> X_DiscoverPublicAddress: (unchecked)
Voice Services -> SP3 Service -> AuthUserName : OBi200
Voice Services -> SP3 Service -> X_RegisterEnable : (unchecked)
Voice Services -> SP3 Service -> X_ServProvProfile : C
Replace your Voice Services -> SP3 Service -> X_InboundCallRoute with following:
{OBi202a|OBi202b>300:ph},{ph}
Physical Interfaces -> Phone Port1 -> DigitMap
Add AFTER the beginning parenthesis: 100|101|200|201|202|301|
It will look like this:
(100|101|200|201|202|301|.....the current settings....)
Physical Interfaces -> Phone Port1
Add the following to the beginning of the OutboundCallRoute:
{(Mp2p):sp3},
User Settings -> User Defined Digit Maps
Label: p2p
DigitMap: ((100|101)<:@192.168.1.100:5062>|(200|201)<:@192.168.1.101:5062>|202<:@192.168.1.111:5060>|301<:@192.168.1.112:5060>)
Working on this now as I have time. Just checking under digit maps for each station 192.168.1.103 and 192.168.1.113 is this a mistake? What do they address? Were they supposed to be .102 and .112
I had more mistakes than you posted.
I corrected the above config.
Here are the extensions:
OBi202#1 (IP Address 192.168.1.100) - Exten 100 and 101
OBi202#2 (IP Address 192.168.1.101) - Exten 200 and 201
w/IP Phone (IP Address 192.168.1.111) - Exten 202
OBi200 (IP Address 192.168.1.102) - Exten 300
w/IP Phone (IP Address 192.168.1.112) - Exten 301
OK so I double and triple checked everything. Do I need to reboot the obi's? Calls out work and all but not the calling each others obi's
If you use OBitalk to configure your OBi's after you click Submit, the changes will be downloaded and the OBi will re-boot. You should wait until this process is complete before proceeding to the next configuration page. I don't know what will happen if you don't wait.
What happens after you dial an extension like 200?
Do you get a busy signal, silence or an error message?
Sorry, but I have to ask the next question.
Did you use the IP addresses I coded in my example?
I didn't say it, but I meant you to replace them will the real device IP addresses.
100 & 200 long wait then"ext 201 has not received a response from the service provider" I cannot connect phone to phone but they all work outgoing calls.
I know what you mean BUT I did change the ip addresses to correspond with MY network and the devoices ip address.
When you say you dont use obitalk HOW do you set them up without it? I mean I setup then go into obiexpert.
Quote from: azrobert on October 24, 2014, 02:16:13 PM
If you use OBitalk to configure your OBi's after you click Submit, the changes will be downloaded and the OBi will re-boot. You should wait until this process is complete before proceeding to the next configuration page. I don't know what will happen if you don't wait.
SOMETIMES THIS TAKES A LOOOOOOONG TIME!
What happens after you dial an extension like 200?
Do you get a busy signal, silence or an error message? dead air 30sec then the number you dialed 100 has not received a response from the service provider.
Sorry, but I have to ask the next question.
Did you use the IP addresses I coded in my example? No
I didn't say it, but I meant you to replace them will the real device IP addresses. I replaced them with my devices ip addresses.
In the OBi200 definition the user defined digit map is missing a verticle bar before "(200|201)". It should be like this:
DigitMap: ((100|101)<:@192.168.1.100:5062>|(200|201)<:@192.168.1.101:5062>|202<:@192.168.1.111:5060>|301<:@192.168.1.112:5060>)
Please check the call history of the OBi202 you dialing from.
Log directly into the OBi using the local interface.
Key the IP address of the OBi into a Web Browser.
Hit Enter
The UserID and default Password are both "admin".
Click Status on the left column.
Then click Call History.
The right column should show the outbound call like this:
sp3(200@xx.xx.xx.xx)
For security reasons this forum recommends changing the X_UserAgentPort.
Voice Services -> SP3 Service -> X_UserAgentPort
Did you change the user agent port on the receiving OBi202?
In the User Defined DigitMap the port ":5062" must match the X_UserAgentPort of SP3 on the receiving OBi2xx.
You register the IP Phone to SP4. Correct?
I didn't change anything on SP4, so the changes should not affect the IP Phone from registering.
VERY strange for some reason I can login to the OBi200 but not into either 202 I just get a big REQUESTED URL NOT FOUND So I hooked a laptop right into its lan port keyed in the same url and was able to login..
The right column shows: ph1
ringing
Since you could only login to the OBi200 I assume this is the call history for the OBi200.
It shows the Phone Port is ringing.
Is it actually ringing?
Check the time stamp.
Is this entry from a previous call?
What did you dial and from which OBi did you dial from to get this result?
What does the left column show?
Quote from: Dranon2 on October 27, 2014, 08:22:18 AM
VERY strange for some reason I can login to the OBi200 but not into either 202 I just get a big REQUESTED URL NOT FOUND So I hooked a laptop right into its lan port keyed in the same url and was able to login..
The right column shows: ph1
ringing
Not strange at all. The 202 contains a router. There is a parameter 'AccessFromWAN' (on the page System Management - Device Admin) which has default setting 'No'. The Device Admin Guide describes it thus:
_____________________________________________________________
Allow access the OBi device management web pages from the WAN side
Note: Option available on OBi202/OBi302 only
_____________________________________________________________
(Unfortunately the missing 'to' in the above extract is not the only case of poor English and careless proof-reading in that document.)
I tried the OBi200 config on my OBi200 and OBi110.
It worked.
My Phone Port DigitMap was already setup to accept 3 digit dialed numbers, so I didn't change anything.
I copied the above p2p User Defined DigitMap and changed the IP addresses and port numbers.
I added {(Mp2p):sp4}, to the beginning of my Phone Port OutboundCallRoute.
That's all the changes I made.
The rest of the config is for inbound calls.
SP4 is where I defined my dummy trunk.
The call history left column showed:
From PH1
The call history right column showed:
To SP4(100@192.168.1.110:5061)
Ringing
Call Ended (486 Busy Here)
I got a Busy because my OBi110 was not configured correctly.
I just wanted to see if the call would go out with my config.
You should see similar entries in your OBi200 call history.
If not, please log into your OBi200 via the local interface and post the following:
Phone Port DigitMap and OutboundCallRoute
p2p User Defined DigitMap
I want you to use the Local Interface because I want to know if the code is getting to the OBi200 correctly.
You navigate the configuration similar to OBiTalk.
Don't make any changes using the local interface because they will be overlayed by OBiTalk.
OK I got the obi a and OBIb able to call each other! YAY ;D Caller id says private caller though so we wont know if its an outside call or inside? Must be another setting somewhere. Still cannot get the ip phones able to call each other or the obi's. I know I have the port's messed up somehow (At least I think thats whats wrong)
Great news!
What about OBi200?
I forgot about callerid.
The callerid sent is the AuthUserName of the SP3 trunk of the originating OBi.
I guess your phones can't display an alpha callerid.
It will take a fair amount of modifications if you want to show the extn# as callerid.
An easier change would be to show 100, 200 or 300 depending on the originating OBi.
Everywhere to see OBi202a, OBi202b and OBi200 in the config, change them to 100, 200 and 300.
Let me know if you want the extension number to show. You would need a separate User Defined DigitMap for each extension. For me it would be several cut and pastes with a few modifications, so I don't mind.
You should be able to call the IP Phones with the current config, but I intentionally didn't setup the IP Phone to call the other extns. You need code in the SP4 InboundCallRoute and I didn't want to mess with SP4 until we got this to work.
I'm not going to do anything until you let me know how you want to handle callerid.
I might be wrong about callerid.
I think the Out of Area is the callername not callerid, so sending a numeric callerid might not fix the Out of Area.
In the Voice Servives -> SP3 Service there is a CallerIDName setting.
I never used that setting and don't have time to try testing it.
Maybe you can try it.
Whatever is easier for the call Id I just would prefer it did not say "private caller"
The i.p. phones when they call an obi ext i.e 100 or 200 they just get a busy signal When the obi tries to call an ip phone just get the "dah dah dah the number you called was rejected by the service provider reason is 404"
Under SP3 caller features CallerIDName I put in "front desk" on the 202a and back office on the 202b and it shows up as FRONT desk private caller! YAY ;D
Now I just need to get the ip phones working the same way!
The following is to add outbound calls to extensions for IP Phones.
userid is the Auth UserID of the IP Phone.
OBi202#2
Add to the beginning Voice Services -> SP4 Service -> X_InboundCallRoute:
{userid>200:ph},{userid>201:ph2},{userid>(Mp2p):sp3},
OBI200
Add to the beginning Voice Services -> SP4 Service -> X_InboundCallRoute:
{userid>300:ph},{userid>(Mp2p):sp3},
****************************************************
For "Out of Area", like I said above:
An easier change would be to show 100, 200 or 300 depending on the originating OBi.
Everywhere to see OBi202a, OBi202b and OBi200 in the config, change them to 100, 200 and 300.
I guessing here and I don't have time to test.
You might have to use a 10 digit number instead of 100, 200 or 300.
*****************************************************
Calling the IP phone:
A 404 response code is not found.
If you had the IP address wrong you would get a timeout, so I think this is a port problem.
You probably can setup several accounts on the IP Phone.
Check what port number you used for the OBi definition, then change 5060 to this port.
If this isn't the problem, maybe the number we send to the IP phone needs to match the Auth UserID.
Quote from: azrobert on October 27, 2014, 06:37:32 PM
The following is to add outbound calls to extensions for IP Phones.
userid is the Auth UserID of the IP Phone. DIDID YOU MEAN AuthUserName here?
OBi202#2
Add to the beginning Voice Services -> SP4 Service -> X_InboundCallRoute:
{userid>200:ph},{userid>201:ph2},{userid>(Mp2p):sp3},
OBI200
Add to the beginning Voice Services -> SP4 Service -> X_InboundCallRoute:
{userid>300:ph},{userid>(Mp2p):sp3},
****************************************************
For "Out of Area", like I said above:
An easier change would be to show 100, 200 or 300 depending on the originating OBi.
Everywhere to see OBi202a, OBi202b and OBi200 in the config, change them to 100, 200 and 300.
I guessing here and I don't have time to test.
You might have to use a 10 digit number instead of 100, 200 or 300.
*****************************************************
Calling the IP phone:
A 404 response code is not found.
If you had the IP address wrong you would get a timeout, so I think this is a port problem.
You probably can setup several accounts on the IP Phone.
Check what port number you used for the OBi definition, then change 5060 to this port. ALL THE PORTS ARE 5060 otherwise the ip phone wouldn't register.
Has to be something else? ip phones cannot call obi and obi cannot call ip phones mmmmm
If this isn't the problem, maybe the number we send to the IP phone needs to match the Auth UserID. AuthUserName??
Also WHERE can I go to learn all this syntax stuff?? Is this kind of exclusive to the obi or is this like a language that other devices use? I love these obi's I just struggle so hard to learn HOW to program them. I tried for weeks to get obiplus working and never got it right, there was no help on the forum and no where to learn the syntax so I could trouble shoot. Anyway I like this solution better! We dont have to dial 9 first to get an outside line
QuoteDID YOU MEAN AuthUserName here?
Yes
Here is the OBi user guide.
http://www.obihai.com/docs/OBiDeviceAdminGuide.pdf
I think it does a good job of explaining DigitMaps, but good luck with complex routing.
If you want I could explain some of code above. First, I think you should understand how the OBi processes calls. I explained some of this before. I'll see if I can find some of my previous posts on the forum.