I purchased an obi212 and obi202. I haven't recieved them yet, waiting on amazon to deliver.
I plan on configuring sp1, sp2 and sp3(fax) as GV. sp4 will be callcentric 911,411. All outbound calls will use GV with the exception of 911 and 411. All GV inbound calls will travel through callcentric to use callerID service. This part of the config should be pretty easy.
The part of the setup I need help with is routing the LI terminal
I want the obi212 LI1 terminal to ring it's PH1 terminal and the obi202 PH1 terminal at the same time when receiving incoming call on the obi212 LI terminal. If the call is unanswered, I want it routed to google voice voicemail.
I figured this could be done using a voice gateway and obitalk PP, but I'm not sure how to do it.
It's a simple Line inbound route change. Send the call over the OBiTalk network to the OBi202.
Line InboundCallRoute: ph,pp(OBi202_OBi_Number)
This method requires a functioning OBiTalk network, it sometimes breaks. You could send the call directly over you local network to the OBi202, but you need to define a dummy trunk on each device.
You can make Line call from the OBi202 using the same method.
Quote from: azrobert on August 27, 2018, 07:26:28 AM
It's a simple Line inbound route change. Send the call over the OBiTalk network to the OBi202.
Line InboundCallRoute: ph,pp(OBi202_OBi_Number)
This method requires a functioning OBiTalk network, it sometimes breaks. You could send the call directly over you local network to the OBi202, but you need to define a dummy trunk on each device.
You can make Line call from the OBi202 using the same method.
As the 2 unit's will be running on the same network a dummy trunk sounds more reliable. Will this setup allow both units to ring at the same time and does it matter if the unit's are on different C classes ?
Both units will ring at the same time.
I'm assuming you're saying the units are setup as routers with different subnets. I don't own an OBi2x2, so I don't know what needs to be done. If the units were on real routers, you would need to setup a static route or port forward. Running the OBi's in Bridge mode would solve the problem. Maybe someone else will chime in.
Quote from: azrobert on August 27, 2018, 08:23:42 AM
Both units will ring at the same time.
I'm assuming you're saying the units are setup as routers with different subnets. I don't own an OBi2x2, so I don't know what needs to be done. If the units were on real routers, you would need to setup a static route or port forward. Running the OBi's in Bridge mode would solve the problem. Maybe someone else will chime in.
CentOS Linux server with several interfaces: eth0,eth1,eth2,ppp0,wlan0 all iterfaces are forwarding traffic between each other via iptables and all interfaces are assigned there own class C, except ppp0(DSL). I don't think it should be a problem connecting the devices.
Does the dummy trunk require a SIP as 3 GV and callcentric will use all 4 available SIPS ?
I didn't read your post closely and didn't realize you're using all 4 SP slots, so you don't have a free slot for a dummy trunk. However, you can use SP4 for both Callcentric and routing calls between units. When you route calls between OBi's and the receiving SP trunk is registered to a provider, you will have audio problems. Turning off discovering your public IP will fix the audio problem. You can setup a voice gateway on the OBi202 for routing outbound to Line.
OBi212 Line InboundCallRoute: ph,sp4(0@xx.xx.xx.xx:pppp)
xx.xx.xx.xx = IP address of OBi202
pppp = X_UserAgentPort of OBi202 SP4 Service
ITSP Profile D SIP
X_SpoofCallerID: Checked
Needed to pass CallerID
OBi202
ITSP Profile D SIP
X_DiscoverPublicAddress: Unchecked
Quote from: azrobert on August 27, 2018, 09:05:22 AM
I didn't read your post closely and didn't realize you're using all 4 SP slots, so you don't have a free slot for a dummy trunk. However, you can use SP4 for both Callcentric and routing calls between units. When you route calls between OBi's and the receiving SP trunk is registered to a provider, you will have audio problems. Turning off discovering your public IP will fix the audio problem. You can setup a voice gateway on the OBi202 for routing outbound to Line.
OBi212 Line InboundCallRoute: ph,sp4(0@xx.xx.xx.xx:pppp)
xx.xx.xx.xx = IP address of OBi202
pppp = X_UserAgentPort of OBi202 SP4 Service
OBi202
ITSP Profile D SIP
X_DiscoverPublicAddress: Unchecked
Sorry, that was my fault, I forgot I would need a dedicated number for the fax line on the obi202 ph2 and I edited the original post to add the 3rd GV number.
Ok, I kind of see what your doing. I was under the impression you could only add 1 terminal as per OBi-DigitMapCallRoute-Tutorial-v1-10.
On the OBI202 with the incoming port need to be routed to ph1 as ph2 will be fax ?
I'm guessing when call is picked up the traffic between devices is bidirectional ?
I may not use a 3rd GV number for the fax and that would leave an open SIP.
Which setup is most reliable, using a free SIP or sharing the Callcentric SIP ?
You are routing Line calls to OBi202 SP4. These will get the same routing as Callcentric to PH1.
bidirectional? - Yes
There shouldn't be any difference in reliability. When you test and everything works, it should continue to work.
Quote from: azrobert on August 27, 2018, 10:13:26 AM
You are routing Line calls to OBi202 SP4. These will get the same routing as Callcentric to PH1.
bidirectional? - Yes
There shouldn't be any difference in reliability. When you test and everything works, it should continue to work.
Thank You for the help. I'm still waiting for my devices do to this amazon issue:
https://www.amazon.com/sp?_encoding=UTF8&asin=&isAmazonFulfilled=0&isCBA=&marketplaceID=ATVPDKIKX0DER&orderID=112-4548922-6146633&seller=A4Y7D9G6IS7RN&tab=&vasStoreID= (https://www.amazon.com/sp?_encoding=UTF8&asin=&isAmazonFulfilled=0&isCBA=&marketplaceID=ATVPDKIKX0DER&orderID=112-4548922-6146633&seller=A4Y7D9G6IS7RN&tab=&vasStoreID=)
First time I had problems with amazon.
I was thinking of doing the basic configs via obitalk.com then disable external provisioning, and only config via the obi202 and obi212 web interface. Any thoughts on the best interface to configure with ?
You're required to setup GV via OBiTalk. After that it's personal preference. I dislike OBiTalk and I use the local interface. One thing that bothers me about OBiTalk is how it downloads changes. When making changes on different pages you have to Submit after each page change and each Submit will cause a download and a reboot. Using the local interface you make all your changes and reboot once. The problem with the local interface is GV changes require you have to revert back to OBiTalk. You can re-sync OBiTalk with your device by taking a config backup and importing it into OBiTalk, but this doesn't always work correctly.
Quote from: azrobert on August 27, 2018, 04:34:01 PM
You're required to setup GV via OBiTalk. After that it's personal preference. I dislike OBiTalk and I use the local interface. One thing that bothers me about OBiTalk is how it downloads changes. When making changes on different pages you have to Submit after each page change and each Submit will cause a download and a reboot. Using the local interface you make all your changes and reboot once. The problem with the local interface is GV changes require you have to revert back to OBiTalk. You can re-sync OBiTalk with your device by taking a config backup and importing it into OBiTalk, but this doesn't always work correctly.
Sounds like my early days in 1990's, before I knew what QA was :)
Thanks for all your help, I'm sure I'll have more questions and hope you don't mind me asking.
Quote from: dboling on August 27, 2018, 05:01:13 PM
I'm sure I'll have more questions and hope you don't mind me asking.
Ask as many questions as you want.
Quote from: azrobert on August 27, 2018, 09:05:22 AM
I didn't read your post closely and didn't realize you're using all 4 SP slots, so you don't have a free slot for a dummy trunk. However, you can use SP4 for both Callcentric and routing calls between units. When you route calls between OBi's and the receiving SP trunk is registered to a provider, you will have audio problems. Turning off discovering your public IP will fix the audio problem. You can setup a voice gateway on the OBi202 for routing outbound to Line.
OBi212 Line InboundCallRoute: ph,sp4(0@xx.xx.xx.xx:pppp)
xx.xx.xx.xx = IP address of OBi202
pppp = X_UserAgentPort of OBi202 SP4 Service
ITSP Profile D SIP
X_SpoofCallerID: Checked
Needed to pass CallerID
OBi202
ITSP Profile D SIP
X_DiscoverPublicAddress: Unchecked
Is there a default port number that should be used ?
Will there be a problem if I forward my GV number to both the OBI202 and the landline number ?
Do you know of a command line MOH server for Linux ?
The default port numbers are 5060-5063, but they get changed to 5080-5083 during the device setup. The port number you should use for SP4 is 5083. Verify this by using OBi Expert.
Voice Services -> SPx Service -> X_UserAgentPort
There shouldn't be any problems forwarding to your PSTN number. Both legs of the call will be sent to the OBi212, the first to arrive will ring the phone port. Just try it and see what happens.
I don't know any MOH servers.
This is a general OBi Expert guide:
From the OBiTalk dashboard click Edit Profile on the left column.
At the bottom of the page check "Enable OBi Expert..."
Click Submit Query.
Now you can go directly to OBi Expert from the dashboard by clicking on the ICON with the red E.
If you don't enable the OBi Expert button, you need 4 clicks to get to OBi Expert like this:
Click on the gear ICON, select OBi Expert, confirm and select OBi Expert again.
Click OBi Dashboard.
On the right of your OBixxx is an icon with a red E.
Click on it to enter OBi Expert.
To navigate click on the titles with the +
Then click on a sub-title
An example click on Service Providers
Then click ITSP Profile A General
There are 2 boxes to the right of each parameter
To change a value uncheck the box under OBiTalk Setting
Then uncheck the box under Device Default
Now change the value
After you have made all the necessary changes for that page, click Submit at the bottom of the page.
OBiTalk will download the configuration changes to the OBi and reboot it.
Wait until this process is complete before continuing to the next page.
You can only use one method, local interface or OBiTalk to configure your OBi.
If you use the local interface to configure your OBi you must disable OBiTalk auto provisioning, otherwise OBiTalk will overlay any changes you make.
System Management -> Auto Provisioning
Under OBiTalk Provisioning
Method: Disabled
Quote from: azrobert on August 29, 2018, 02:17:25 PM
The default port numbers are 5060-5063, but they get changed to 5080-5083 during the device setup. The port number you should use for SP4 is 5083. Verify this by using OBi Expert.
Voice Services -> SPx Service -> X_UserAgentPort
There shouldn't be any problems forwarding to your PSTN number. Both legs of the call will be sent to the OBi212, the first to arrive will ring the phone port. Just try it and see what happens.
I don't know any MOH servers.
This is a general OBi Expert guide:
From the OBiTalk dashboard click Edit Profile on the left column.
At the bottom of the page check "Enable OBi Expert..."
Click Submit Query.
Now you can go directly to OBi Expert from the dashboard by clicking on the ICON with the red E.
If you don't enable the OBi Expert button, you need 4 clicks to get to OBi Expert like this:
Click on the gear ICON, select OBi Expert, confirm and select OBi Expert again.
Click OBi Dashboard.
On the right of your OBixxx is an icon with a red E.
Click on it to enter OBi Expert.
To navigate click on the titles with the +
Then click on a sub-title
An example click on Service Providers
Then click ITSP Profile A General
There are 2 boxes to the right of each parameter
To change a value uncheck the box under OBiTalk Setting
Then uncheck the box under Device Default
Now change the value
After you have made all the necessary changes for that page, click Submit at the bottom of the page.
OBiTalk will download the configuration changes to the OBi and reboot it.
Wait until this process is complete before continuing to the next page.
You can only use one method, local interface or OBiTalk to configure your OBi.
If you use the local interface to configure your OBi you must disable OBiTalk auto provisioning, otherwise OBiTalk will overlay any changes you make.
System Management -> Auto Provisioning
Under OBiTalk Provisioning
Method: Disabled
I get it, provision from either local or OBITalk, NOT both.
I've done more research for MOH and it seems it just connects to a streaming server.
How would you write the rule to connect to the local streaming server say on 192.168.3.1:9000 and will the OBI handle mp3 streams ?
Is it possible to have to OBI202 dial the OBI212 LI port for free and 911 calls if Internet feed is down ?
Can the OBI202 and OBI212 transfer or conference the OBI202 LI terminal between each others extensions ?
Seems the more I research the my questions come up.
I never used MOH, so I can't help on this question.
You can setup a trunk group for 911. I'm assuming you are using Callcentric on SP4 for 911.
Modify the TG1 trunk list to: sp4,li
Add the following to the beginning of the phone OutboundCallRoute:
{911:tg1},
Add 911 to the Line and SP4 DigitMaps.
On the SP4 Service check X_NoRegNoCall
When 911 fails for SP4 the OBi212 will route the call to Line.
Conference and Transfer are standard features on all OBi's.
When on an active call, press Flash.
You will get a dial tone.
Call another number.
Hang up to transfer or Flash to conference.
You can setup rules to call the OBi202 phone ports.
Have you setup your OBi212 and OBi202?
Quote from: azrobert on August 30, 2018, 11:07:42 AM
I never used MOH, so I can't help on this question.
You can setup a trunk group for 911. I'm assuming you are using Callcentric on SP4 for 911.
Modify the TG1 trunk list to: sp4,li
Add the following to the beginning of the phone OutboundCallRoute:
{911:tg1},
Add 911 to the Line and SP4 DigitMaps.
On the SP4 Service check X_NoRegNoCall
When 911 fails for SP4 the OBi212 will route the call to Line.
Conference and Transfer are standard features on all OBi's.
When on an active call, press Flash.
You will get a dial tone.
Call another number.
Hang up to transfer or Flash to conference.
You can setup rules to call the OBi202 phone ports.
Have you setup your OBi212 and OBi202?
They just arrived in the mail 30 minutes ago. Configuring 202 now. usb-wifi won't be here until tomorrow.
Does the obi retrive GV voicemails ?
Call your own GV number to get the GV IVR. VM is one of the options.
Quote from: azrobert on August 27, 2018, 09:05:22 AM
I didn't read your post closely and didn't realize you're using all 4 SP slots, so you don't have a free slot for a dummy trunk. However, you can use SP4 for both Callcentric and routing calls between units. When you route calls between OBi's and the receiving SP trunk is registered to a provider, you will have audio problems. Turning off discovering your public IP will fix the audio problem. You can setup a voice gateway on the OBi202 for routing outbound to Line.
OBi212 Line InboundCallRoute: ph,sp4(0@xx.xx.xx.xx:pppp)
xx.xx.xx.xx = IP address of OBi202
pppp = X_UserAgentPort of OBi202 SP4 Service
ITSP Profile D SIP
X_SpoofCallerID: Checked
Needed to pass CallerID
OBi202
ITSP Profile D SIP
X_DiscoverPublicAddress: Unchecked
Now that the OBI202 and OBI212 have been installed I tried this configuration, however it does not work.
# Device IPs
OBI202: 192.168.3.61
OBI212: 192.168.3.60
SP4: Callcentric on both devices
## OBI212 Config
Physical Interfaces>LINE Port
InboundCallRoute: ph,sp4(0@192.168.3.61:5083)
Service Providers>ITSP Profile D>SIP
X_SpoofCallerID: Checked
## OBI202 Config
Service Providers>ITSP Profile D>SIP
X_DiscoverPublicAddress: Unchecked
Voice Services>SP4 Service
X_UserAgentPort: 5083
## Error Message from OBI212 Call History.
Call 1 09/01/2018 09:29:59
09:29:59 From LI1() Fork to:
PH1
SP4(0@192.168.3.61:5083)
09:29:59 Ringing (PH1)
09:29:59 Call Failed (404 Not Found; SP4(0@192.168.3.61:5083))
09:30:06 Call Connected (PH1)
09:56:03 Call Ended
I tested this config a few times and get the same error message. There are no blocked ports or IPs within the internal network.
A port scan of the OBI202 shows that 3 ports are open:
53: domain
80: http
18000: Beckman Instruments Inc.
I have the same setup (routing line calls to another device) except I'm using an OBi110 and an OBi200. I tried to reproduce your problem and couldn't get a 404 error. Your devices have the same subnet. Are you running them in bridge mode? I don't own an OBi2x2 and not familiar with all the settings, so you might need to get someone else to help.
You can get it to work over the OBiTalk network until you fix this.
## OBI212 Config
Physical Interfaces>LINE Port
InboundCallRoute: ph,pp(510111111)
Replace 510111111 with the OBi number of the OBi202
## OBI202 Config
Voice Services>OBiTalk Service
InboundCallRoute: ph
This is the default, but the setup process might add code to send calls to the Auto Attendant.
Quote from: azrobert on September 01, 2018, 09:11:33 AM
I have the same setup (routing line calls to another device) except I'm using an OBi110 and an OBi200. I tried to reproduce your problem and couldn't get a 404 error. Your devices have the same subnet. Are you running them in bridge mode? I don't own an OBi2x2 and not familiar with all the settings, so you might need to get someone else to help.
You can get it to work over the OBiTalk network until you fix this.
## OBI212 Config
Physical Interfaces>LINE Port
InboundCallRoute: ph,pp(510111111)
Replace 510111111 with the OBi number of the OBi202
## OBI202 Config
Voice Services>OBiTalk Service
InboundCallRoute: ph
This is the default, but the setup process might add code to send calls to the Auto Attendant.
I think the problem is with the OBI202. In order for the OBI212 to connect to it must have and open port to connect to. I'm not sure if it's UDP or TCP or if the OPI202 has firewall rules for each terminal. My first port scan was with fing which I don't trust. Currently I'm running a full UDP scan from the server using nmap, it's going to take a bit to complete.
[root@athome ~]# nmap -v -sU 192.168.3.61
PORT STATE SERVICE
53/udp open|filtered domain
67/udp open|filtered dhcps
10000/udp open|filtered ndmp
[root@athome ~]# nmap -v -r -sT 192.168.3.61
PORT STATE SERVICE
53/tcp open domain
80/tcp open http
For some reason the OBI202 isn't providing a port.
It's UDP
ServicesProviders>ITSP Profile x SIP ProxyServerTransport: UDP
Quote from: azrobert on September 01, 2018, 09:11:33 AM
I have the same setup (routing line calls to another device) except I'm using an OBi110 and an OBi200. I tried to reproduce your problem and couldn't get a 404 error. Your devices have the same subnet. Are you running them in bridge mode? I don't own an OBi2x2 and not familiar with all the settings, so you might need to get someone else to help.
You can get it to work over the OBiTalk network until you fix this.
## OBI212 Config
Physical Interfaces>LINE Port
InboundCallRoute: ph,pp(510111111)
This works for a temp fix. I'm guessing it won't work if Internet connection is down ?
Replace 510111111 with the OBi number of the OBi202
## OBI202 Config
Voice Services>OBiTalk Service
InboundCallRoute: ph
This is the default, but the setup process might add code to send calls to the Auto Attendant.
Quote from: dboling on September 01, 2018, 11:41:03 AM
This works for a temp fix. I'm guessing it won't work if Internet connection is down ?
It won't work when the internet is down or the OBiTalk network is having problems.
Quote from: azrobert on September 01, 2018, 12:33:12 PM
Quote from: dboling on September 01, 2018, 11:41:03 AM
This works for a temp fix. I'm guessing it won't work if Internet connection is down ?
It won't work when the internet is down or the OBiTalk network is having problems.
I don't know about you, but I'm tired with trying to get this to work correctly and need to take a break :) .
Either there's a bug in the software or OBI changed something in it's default configs. As a beta tester, maybe OBI will send you a OBI202 and OBI212 for you to test (N/C). I know on my end there is NO ports/IP's that are blocking and requests to the OBI units.
Quote from: azrobert on September 01, 2018, 09:11:33 AM
I have the same setup (routing line calls to another device) except I'm using an OBi110 and an OBi200. I tried to reproduce your problem and couldn't get a 404 error. Your devices have the same subnet. Are you running them in bridge mode? I don't own an OBi2x2 and not familiar with all the settings, so you might need to get someone else to help.
You can get it to work over the OBiTalk network until you fix this.
## OBI212 Config
Physical Interfaces>LINE Port
InboundCallRoute: ph,pp(510111111)
Replace 510111111 with the OBi number of the OBi202
## OBI202 Config
Voice Services>OBiTalk Service
InboundCallRoute: ph
This is the default, but the setup process might add code to send calls to the Auto Attendant.
I scanned all 65K+ ports on the OBI202 and found port 5083 to be open/filtered.
The wiki located at https://en.wikipedia.org/wiki/List_of_SIP_response_codes (https://en.wikipedia.org/wiki/List_of_SIP_response_codes) list the SIP error codes and for a 404 error code it says:
404 Not FoundThe server has definitive information that the user does not exist at the domain specified in the Request-URI. This status is also returned if the domain in the Request-URI does not match any of the domains handled by the recipient of the request.[1]:ยง21.4.5
What does the 0 represent in the config sp4(0@192.168.3.61:5083) ?
The zero is data that is passed to the OBi202. This is a requirement of the SIP URI syntax. Calls will pass data and CallerID. You can test for these in the SP4 X_InboundCallRoute.
Format of an inbound route rule:
{ CallerID > data : dest}
> is a separator
If only testing CallerID, separator is not required.
Examples:
{>0:ph}
Data = 0 and any CallerID will be sent to ph
{8005551212>800:ph}
Only CallerID 8005551212 and data 800 sent to ph
{8005551212:ph}
Only CallerID 8005551212 with any data sent to ph
ph or {ph}
All calls sent to ph
Quote from: azrobert on September 04, 2018, 09:16:25 AM
The zero is data that is passed to the OBi202. This is a requirement of the SIP URI syntax. Calls will pass data and CallerID. You can test for these in the SP4 X_InboundCallRoute.
Format of an inbound route rule:
{ CallerID > data : dest}
> is a separator
If only testing CallerID, separator is not required.
Examples:
{>0:ph}
Data = 0 and any CallerID will be sent to ph
{8005551212>800:ph}
Only CallerID 8005551212 and data 800 sent to ph
{8005551212:ph}
Only CallerID 8005551212 with any data sent to ph
ph or {ph}
All calls sent to ph
sp4(0@192.168.3.61:5083)
OK, I thought the 0 in this line was like user@192.168.3.61:5083 .
The verizon PSTN(LI) port on the 212 does not have caller ID. The line only has dial tone and 911.
Does the line not having callerID make a difference ?
I also do have a WIFI repeater between the OBI202 and the OBI212, when traffic is sent to the servers WIFI via the repeater, it uses the repeaters MAC address.
I've also enabled syslog for better diagnostics .
Is it possible for a test to put both devices on the same router? If you can't because of the Line connection, you can define a speed dial with the same rule to test.
sp4(0@192.168.3.61:5083)
I assume you are running the devices in Bridge mode because they have the same subnet. Is this correct?
Quote from: azrobert on September 04, 2018, 01:08:37 PM
Is it possible for a test to put both devices on the same router? If you can't because of the Line connection, you can define a speed dial with the same rule to test.
sp4(0@192.168.3.61:5083)
I assume you are running the devices in Bridge mode because they have the same subnet. Is this correct?
They are both on the same subnet.
wlan0 Link encap:Ethernet HWaddr F8:D1:11:6E:78:38
inet addr:192.168.3.1 Bcast:192.168.3.255 Mask:255.255.255.0
inet6 addr: fe80::fad1:11ff:fe6e:7838/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:119458670 errors:0 dropped:0 overruns:0 frame:0
TX packets:150943485 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:94065641101 (87.6 GiB) TX bytes:96751918482 (90.1 GiB)
I tested it a few dozen times today. I ran a tcpdump on wlan0 looking for the OBI212 to try and contact the OBI202 on port 5083. However there was no network traffic coming from the OBI212 on port 5083. I also unpluged the TP-link cpe210 (wireless relay) so both the OBI212 and OBI202 would be connected directly to the same access point, I still had the results.
There must be a bug in the firmware. Is there anyway to get OBI to check this out ?
This is the setting I asked about:
Router Configuration -> Lan Settings -> OperationMode: Bridge
Quote from: azrobert on September 04, 2018, 02:51:24 PM
This is the setting I asked about:
Router Configuration -> Lan Settings -> OperationMode: Bridge
Both OBI's are set to OperationMode:Router.
Both the OBI's have the wifi5G adapters installed and are not networked via LAN.
Maybe someone with an OBi2x2 can chime in on how to configure your setup. I still think you need to be in Bridge mode.
Quote from: azrobert on September 04, 2018, 03:27:54 PM
Maybe someone with an OBi2x2 can chime in on how to configure your setup. I still think you need to be in Bridge mode.
I set both OBI's to bridge, but no connection.
syslog for the call is:
Sep 4 18:49:06 obi212 [DAA]: FXO ring off
Sep 4 18:49:18 obi212 [DAA]: FXO ring on
Sep 4 18:49:22 obi212 CCTL:NewCallOn Term 10[3] ->,0@192.168.3.61:5083
Sep 4 18:49:22 obi212 [DAA]: FXO ONHOOK MONITOR
Sep 4 18:49:22 obi212 RTP:Del Channel
Sep 4 18:49:53 obi212 [DAA]: FXO ring off
Quote from: azrobert on September 04, 2018, 03:27:54 PM
Maybe someone with an OBi2x2 can chime in on how to configure your setup. I still think you need to be in Bridge mode.
OK, I got this to work, well 1/2 work. I seem have call control issues .
Here are the following setting I used.
# Device IPs
OBI202: 192.168.3.61
OBI212: 192.168.3.60
SP4: Callcentric on both devices
## OBI212 Config
Physical Interfaces>LINE Port
InboundCallRoute: ph,sp4(17771234567@192.168.3.61:5083)
Service Providers>ITSP Profile D>SIP
X_SpoofCallerID: Checked
## OBI202 and OBI212 Config
Service Providers>ITSP Profile D>SIP
X_DiscoverPublicAddress: Unchecked
Needed to use the username for callcentric instead of (0@192.168.3.61:5083).
Also needed to uncheck X_DiscoverPublicAddress: on both devices. Basically the OBI202 would get both rx and tx traffic and the OBI212 could only send tx traffic with no receive.
The issue that I seem to be having now is controlling the call between devices.
When I call I can talk and hear the call fine for 1/2 minute and I start getting (disconnect tone) but the call doesn't disconnect.
The OBI212 does not recognize when either the incoming (LI) call hangs up or when the OBI202 hangs up. It seems to take about 3 minutes for the OBI212(LI) to go onhook after the call ends.
If I hang up the OBI202 first the OBI212 call log gives the error: Call Ended (481 Call Leg/Transaction Does Not Exist)
If I hang up the OBI212(LI) first I don't get any errors.
Either way the OBI212 will not go onhook unless both side of the call hangs up and even then the OBI212 takes about 3 minutes to go onhook.
## Syslog LOG ##
Sep 16 06:13:02 obi212 [DAA]: FXO ring on
Sep 16 06:13:06 obi212 CCTL:NewCallOn Term 10[3] ->,17771234567@192.168.3.61:5083
Sep 16 06:13:06 obi202 CCTL:NewCallOn Term 1[0] ->,17771234567
Sep 16 06:13:06 obi202 fxst_ccapi_new_call: 17771234567->17771234567 name
Sep 16 06:13:06 obi202 [SLIC] CID to deliver: '' 17771234567
Sep 16 06:13:06 obi202 PARAM Cache Write Back(256 bytes)
Sep 16 06:13:29 obi202 GAPI:Refreshing tk
Sep 16 06:13:29 obi202 GAPI:Refreshing tk
Sep 16 06:13:29 obi202 GAPI:Refreshing tk
Sep 16 06:13:29 obi202 TCP:Connect OK(lhttpc)47
Sep 16 06:13:29 obi202 Trying to connect ssl
Sep 16 06:13:29 obi202 TCP:Connect OK(lhttpc)48
Sep 16 06:13:29 obi202 Trying to connect ssl
Sep 16 06:13:29 obi202 TCP:Connect OK(lhttpc)49
Sep 16 06:13:29 obi202 Trying to connect ssl
Sep 16 06:13:30 obi202 TC:ssl connected
Sep 16 06:13:30 obi202 TC:ssl connected
Sep 16 06:13:30 obi202 TC:ssl connected
Sep 16 06:13:30 obi202 LHC:Response OK
Sep 16 06:13:30 obi202 GAPI:refresh tk ok
Sep 16 06:13:30 obi202 LHC:Response OK
Sep 16 06:13:30 obi202 PARAM Cache Write Back(256 bytes)
Sep 16 06:13:30 obi202 GAPI:refresh tk ok
Sep 16 06:13:30 obi202 LHC:Response OK
Sep 16 06:13:30 obi202 GAPI:refresh tk ok
Sep 16 06:13:31 obi202 PARAM Cache Write Back(512 bytes)
Sep 16 06:13:33 obi212 [DAA]: FXO ring off
Sep 16 06:13:33 obi212 RTP:Del Channel
Sep 16 06:13:33 obi202 RTP:Del Channel
Sep 16 06:13:33 obi212 [DAA]: FXO ONHOOK MONITOR
Sep 16 06:13:43 obi212 OB==>CRLFCRLF
Sep 16 06:13:43 obi212 OB==>CRLFCRLF
Sep 16 06:13:44 obi212 OB:<==CRLF
Sep 16 06:13:44 obi212 OB:<==CRLF 1
Sep 16 06:13:44 obi212 OB:<==CRLF
Sep 16 06:13:44 obi212 OB:<==CRLF 1
Sep 16 06:14:12 obi212 [DAA]: FXO ring on
Sep 16 06:14:16 obi212 CCTL:NewCallOn Term 10[3] ->,17771234567@192.168.3.61:5083
Sep 16 06:14:16 obi202 CCTL:NewCallOn Term 1[0] ->,17771234567
Sep 16 06:14:16 obi202 fxst_ccapi_new_call: 17771234567->17771234567 name
Sep 16 06:14:16 obi202 [SLIC] CID to deliver: '' 17771234567
Sep 16 06:14:22 obi202 [SLIC]:Slic#0 OFF HOOK
Sep 16 06:14:22 obi202 [CNG] cng_det_init 0.
Sep 16 06:14:22 obi202 RTP:DtmfTxMtd:1(1),0
Sep 16 06:14:22 obi202 [DSP]: set FXS(0) DTMF detection level to (3)
Sep 16 06:14:22 obi212 RTP:DtmfTxMtd:1(1),0
Sep 16 06:14:22 obi212 [DAA]: FXO OFFHOOK
Sep 16 06:14:22 obi212 [DAA]: detecting disconnect tone, reinit: 1
Sep 16 06:14:22 obi212 RTP:Start->c0a8033d:17102(80 160);0;0;0:0:0;0(43)
Sep 16 06:14:22 obi212 [DAA] FXO ring off
Sep 16 06:14:22 obi202 RTP:Start->c0a8033c:17104(80 160);0;0;0:0:0;0(45)
Sep 16 06:14:52 obi202 OB==>CRLFCRLF
Sep 16 06:14:52 obi202 OB:<==CRLF
Sep 16 06:14:52 obi202 OB:<==CRLF 1
Sep 16 06:15:09 obi202 OB==>CRLFCRLF
Sep 16 06:15:10 obi202 OB:<==CRLF
Sep 16 06:15:10 obi202 OB:<==CRLF 1
Sep 16 06:15:14 obi202 TCP:Broken Connection(HTTPD) 44 0
Sep 16 06:15:22 obi202 [SLIC]:Slic#0 ONHOOK
Sep 16 06:15:22 obi202 RTP:Del Channel
Sep 16 06:15:28 obi212 [LI0] ---- S/W TONE ON (level: default) : , @ 354020 ----
Sep 16 06:15:35 obi202 OB==>CRLFCRLF
Sep 16 06:15:35 obi202 OB:<==CRLF
Sep 16 06:15:35 obi202 OB:<==CRLF 1
Sep 16 06:15:53 obi202 PRD:1st down
Sep 16 06:15:54 obi202 PRD:1st success
Sep 16 06:15:54 obi202 PRD:NOPriFbToTry
Sep 16 06:15:54 obi202 DLG:Retry1->cc0bc0a9:5080
Sep 16 06:15:59 obi212 Send() error 104
Sep 16 06:15:59 obi212 HTTPD: SendHeader Failed
Sep 16 06:16:40 obi212 IPC: Event 8
Sep 16 06:16:40 obi212 IPC: Event 7
Quote from: azrobert on August 27, 2018, 09:05:22 AM
OBi212 Line InboundCallRoute: ph,sp4(0@xx.xx.xx.xx:pppp)
xx.xx.xx.xx = IP address of OBi202
pppp = X_UserAgentPort of OBi202 SP4 Service
ITSP Profile D SIP
X_SpoofCallerID: Checked
Needed to pass CallerID
OBi202
ITSP Profile D SIP
X_DiscoverPublicAddress: Unchecked
I was able to get this to work with sp4(0@xx.xx.xx.xx:pppp)
On the OBI202 I need to go to Voice Services>SP4 Service>X_EnforceRequestUserID and UnCheck it.
There is a bug on the OBI212 that causes it not to release the Line Port. I'm going to start a new topic in firmware regarding the bug.
Quote from: dboling on September 17, 2018, 09:08:28 AM
I was able to get this to work with sp4(0@xx.xx.xx.xx:pppp)
On the OBI202 I need to go to Voice Services>SP4 Service>X_EnforceRequestUserID and UnCheck it.
The default is unchecked, so why was it checked? Did you use a wizard to define CC and it checked the setting?
Outbound OBi202 calls can be routed to Line. I can show you how if you're interested. I'm doing this on my OBi200/OBi110 and use a "9" prefix to identify these calls.
I used the OBItalk web interface. The plan was to get it setup then dump the web interface. it was checked on both the OBI202 and OBI212.
I just posted at http://www.obitalk.com/forum/index.php?topic=14971.0 (http://www.obitalk.com/forum/index.php?topic=14971.0) with the issue I'm having.
Quote from: azrobert on September 17, 2018, 10:14:28 AM
Quote from: dboling on September 17, 2018, 09:08:28 AM
I was able to get this to work with sp4(0@xx.xx.xx.xx:pppp)
On the OBI202 I need to go to Voice Services>SP4 Service>X_EnforceRequestUserID and UnCheck it.
Outbound OBi202 calls can be routed to Line. I can show you how if you're interested. I'm doing this on my OBi200/OBi110 and use a "9" prefix to identify these calls.
Yes, I'd like to set it up for when the internet in down, so I can dial 911 from the obi202 to the obi212 Line Port.
I only have incoming calls and 911 service on the Verizon landline.
Since nobody on this forum has any ideas what the issue is with my OBi212 I decided it must be defective and called Amazon for a replacement. It should be here in a few days.
Quote from: dboling on September 18, 2018, 06:01:27 AM
Yes, I'd like to set it up for when the internet in down, so I can dial 911 from the obi202 to the obi212 Line Port.
OBi202
Voice Services -> Gateways and Trunk Groups -> Voice Gateway 1
Name: OBi212
Access Number: sp4(xx.xx.xx.xx:pppp)
DigitMap: (911)
AuthUserID: dboling
xx.xx.xx.xx = IP address of OBi212
pppp = X_UserAgentPort of OBi212 SP4 Service
Physical Interfaces -> Phone1/2 Port
Add following to the beginning of the OutboundCallRoute:
{(Mvg1):vg1},
OBi212
ITSP Profile D SIP
X_DiscoverPublicAddress: Unchecked
SP4 Service -> X_InboundCallRoute:
{dboling>911:li},{ph}
That's very nice. I was wondering how to write a voice gateway.
How to I access it ?
Currently I have E911 via callcentric and just need to dial 911.
If O dial 911 it rings callcentric and the OBI212 line port ?
Routing an outbound call is a 2 step process.
The Phone Port DigitMap validates the dialed number.
The last rule (Mpli) will include the rules in primary line's DigitMap.
If the dialed number doesn't match a rule, you will receive a fast busy.
If the dialed number matches a rule in the DigitMap, the phone port OutboundCallRoute will get control and route the call to the primary line using rule {(Mpli):pli}
If you want to route 911, you need to place a rule to the left of {(Mpli):pli}
My example placed the Line routing rule 1st, so 911 will only be routed to the OBi212/Line.
I assume you have a rule routing 911 to SP4. It will be ignored.
A trunk group is used to route a call to 1 or more additional trunks when the primary trunk fails.
You define a TG with a list of trunks
When the TG gets control, it will compare the dialed number to the DigitMap of the 1st trunk.
If there is a match, the call will be routed to that trunk.
If there is no match or the call fails, the TG will try the next trunk in the list.
The TG can be used for normal routing and not just failover
SP1 DigitMap: (1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|011xx.)
SP4 DigitMap: (911)
SP4 X_NoRegNoCall: Checked
ITSP D SIP TimerB: 6000
VG1 DigitMap: (911)
Trunk Group1
Trunk List: sp4,vg1,sp1
DigitMap: ((Msp1)|(Msp4))
Phone1/2 Port
OutboundCallRoute: set it to default
PrimayLine: Trunk Group 1
Dial 911
The call is routed to SP4
If the call fails it will be routed to VG1
Dial 8005551212
The call will not be routed to SP4 because no match with SP4 DigitMap
Same with VG1
The call is routed to SP1
The TG will timeout after 32 seconds before failing over to the next trunk.
With X_NoRegNoCall it will failover immediately when the trunk isn't registered.
TimerB will change the timeout from 32 seconds to 6. This will prevent a long timeout when the trunk is down, but the OBi202 still thinks it's registered.