News:

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

Main Menu

NEED HELP CONNECTING (2) OBI110 FOR REMOTE PAGING ACCESS

Started by miteldavid, August 19, 2013, 08:25:43 AM

Previous topic - Next topic

miteldavid

I am newbie trying to install (2) Obi110 for paging access to a remote site. Both units are connected to a network at a school under different subnets, but subnets are ping one another. I can call each other with some ip routing and speed dial today. But what I like to accomplish is being able pick up a telephone in (site A) connected to #1 OBi110 telephone port and be connected to #2 OBi110 in remote (site B) with Simplex PA Intercom Dial tone connected to the Line port of the #2 OBi110 and be able to dial any digit over Simplex PA system and page over head. Simplex PA system would be the Dial tone. Thanks in advance!

ianobi

This may be the first paging question we have had on this forum! According to the OBiDeviceAdminGuide:

QuoteUsing the OBi as a Paging System
You may connect the OBi PHONE port to an external PA system via an RJ11-to-Line-Out connector (available at many poular electronics shops), and enable the PHONE port option UseForPagingOnly. In this configuration, the phone port is expected to be "off-hook" all the time. The OBi will automatically answer incoming calls. It will not accept call-waiting. When the phone port goes from on-hook to off-hook, in case the user needs to dial * * * to invoke the IVR, the OBi will play a dial tone for 5 seconds. After 5 seconds the OBi will turn silent and be ready to accept an incoming call to page.

If you connect the Phone Port of your #2 OBi110 to the PA, then call it from OBi #1, you should be connected through to the PA system. Looks like OBi #2 will auto-answer any incoming call and connect to the Phone Port.


Quotewhat I like to accomplish is being able pick up a telephone in (site A) connected to #1 OBi110 telephone port and be connected to #2 OBi110 in remote (site B)

This requires #1 OBi110 to be configured as a "hot-line" to #2 OBi110. This can be done, but then you lose any other functions that #1 OBi110 might be useful for. Is it not good enough to use the speed dial you have set up to connect through to #2 OBi110?

Looks like an interesting project. Let us know how it progresses.



QBZappy

I have experimented with the paging feature in the past. It worked as advertized. Considering the cost of dedicated paging systems out there, this is a very low cost solution if someone needs this feature.
Owner of the 1st OBi110/100 units in service in Canada & South America. 1st OBi202 on my street. 1st OBi1032 in Montreal.

drgeoff

Quote from: ianobi on August 19, 2013, 09:31:57 AM

Quotewhat I like to accomplish is being able pick up a telephone in (site A) connected to #1 OBi110 telephone port and be connected to #2 OBi110 in remote (site B)

This requires #1 OBi110 to be configured as a "hot-line" to #2 OBi110. This can be done, but then you lose any other functions that #1 OBi110 might be useful for. Is it not good enough to use the speed dial you have set up to connect through to #2 OBi110?

An alternative compromise is to configure #1 OBi110 as a "warm line".  If no digits are dialled within say 5 seconds of taking the phone off-hook then #1 OBi calls #2 OBi.  If digits are dialled within the time-out period they are used in the normal way.  (This is how my OBi110 and wife's mother's PAP2 are configured for calling each other.)

miteldavid

Thanks to all for the quick response! I would like to try setting up as a hotline can any please help me out with settings for both OBi110?

ianobi

It looks like you have worked out how to directly call from #1 OBi to #2 OBi using IP addresses via a speed dial. If you post the speed dial info here, then I will propose a hot line config tomorrow (my time zone!).

I would try this in two stages. Leave #1 OBi as it is for now, connect #2 OBi to the PA as suggested above and test it out using the speed dial, then move on to a hot line config.

ianobi

Here's an example of "hot-line" working using direct IP addresses. I would suggest this is the last thing to put in place after all else has been proved to work.

In both OBi110s I have used sp2, mostly because I have used this in previous posts and I'm doing a lazy cut and paste for some of this post . This has only been proved to work between two OBi devices in the same subnet. However, if you have made successful direct IP calls between your two OBi devices (with speech both ways), then this should also work. Just in case, keep a note of your original settings.


#1 OBi:

Service Providers -> ITSP Profile B -> SIP -> ProxyServer : 127.0.0.1

Voice Services -> SP2 Service -> Enable : (checked)
Voice Services -> SP2 Service -> AuthUserName : 87654321
Voice Services -> SP2 Service -> X_RegisterEnable : (unchecked)
Voice Services -> SP2 Service -> X_ServProvProfile : B
Voice Services -> SP2 Service -> X_UserAgentPort : 5473
Voice Services -> SP2 Service -> CallerIDName : Whatever

Physical Interfaces > Phone Port > DigitMap:
(<:@192.168.1.10:5471>)

Physical Interfaces > Phone Port > OutboundCallRoute
{(@@.):sp2}


#2 OBi:

Service Providers -> ITSP Profile B -> SIP -> ProxyServer : 127.0.0.1

Voice Services -> SP2 Service -> Enable : (checked)
Voice Services -> SP2 Service -> AuthUserName : 12345678
Voice Services -> SP2 Service -> X_RegisterEnable : (unchecked)
Voice Services -> SP2 Service -> X_ServProvProfile : B
Voice Services -> SP2 Service -> X_UserAgentPort : 5471
Voice Services -> SP2 Service -> CallerIDName : Anything

Voice Services -> SP2 Service -> X_InboundCallRoute:
{(87654321):li}


Security is provided by changing the UserAgentPorts to be different from the standard 5060. This rule {(87654321):li} only allows a device with CallerID of 87654321 to access the #2 OBi line. Other CallerIDs could be added.
I would disable the unused spX – sp1 in this example.


Option:

#2 OBi could also be accessed via the OBiTALK network from any OBi device. Security can be ensured by restricting access to certain CallerIDs. In this case CallerID = Device's OBiTALK number. For example:

#2 OBi
Voice Services -> OBiTALK Service -> InboundCallRoute:
{(200111111|200222222|200333333):li}

Only OBi devices 200111111, 200222222 and 200333333 are allowed to call into #2 OBi.

Edit: Various changes made to enable use #2 OBi's Line Port rather than Phone Port.

miteldavid

Ianobi,
I installed and connected Simplex PA system Intercom dail tone to OBi110 #2 phone port. As you described. When I go off hook from the phone connected to phone port on OBi110 #1 and dial 1# spd 1 = sp2(av@10.100.11.5:5061) and call OBi110 #2 it would ring once and pick up with silence. I monitered the Simplex PA system while connected to phone port on OBi110 #2 with test set (linemans phone). I could hear the call come from OBi110 #1 and OBi110 #2 pick up the call, but not connect to Simplex PA. At this stage Caller hears silence. While caller still connected and I'm still monitering the line I can go off hook and open loop and then caller is connected to Simplex PA Intercom dial tone and is able to dial a Simplex page code and page over head. I am controlling off hook condition at this stage with my test set. I started Polking around with Obi110 #2 Tip-Ring Voltage Polarity settings and changed default value to IdlePolarity = Reverse, ConnectPolarity = Reverse. Now I am able to call from OBi110 #1 to Obi110 #2 call is picked up and connected to Simplex PA Sytem Intercom dial tone and also able to dial a Simplex code and page overhead, this is great! But now when I hang up and go on hook from phone connected to OBi110 #1 and go off hook and try to call and connect a second time, third time, etc it rings once Obi110 #2 picks up and silence. No Simplex Intercom dial tone is heard for about 3 min and somtimes longer. Could it be that the Simplex PA system is not getting a disconnect signal from OBi110 #2 phone port?

miteldavid

Ianobi, sorry I forgot to mention in my last post the setting for UseForPagingOnly was (checked on) during the whole process of testing. OBi110 #2 would pick up and answer under this condition!

ianobi

We are all learning on this one!

QuoteCould it be that the Simplex PA system is not getting a disconnect signal from OBi110 #2 phone port?

I think that this is likely. The OBi simply stays off-hook. It assumes that it is connected to a simple PA system, that is just an amplifier. I'm guessing your system has some sort of telecoms interface?

Does the Simplex system accept ringing and answer a call in a normal telecoms way? If so it might be we should put #2 OBi back to its default settings (not set for paging) and connect the Simplex system to the Line Port. If this is the case, then this setting needs to be changed to direct the incoming call to the Line Port:

#2 OBi
Voice Services -> SP2 Service -> X_InboundCallRoute: {li}

miteldavid

Ianobi, The Simplex does not answer ringing calls, but you can go off hook with an analog phone connected to Simplex page port and get Intercom dial tone. I will try your other scenerio and move Simplex PA port from Tel port to Line port on Obi110 #2 and reconfigure per your advice. Question how will the line port on the obi110 #2 pick up the call from OBi110 #1 and connect to Simplex PA port?

ianobi

My mistake. The line port will put out a loop like an analogue phone, so should be ok.

This rule should direct the incoming call from #1 OBi to the Line Port and seize the Simplex Page Port:

#2 OBi
Voice Services -> SP2 Service -> X_InboundCallRoute: {li}

Your speed dial directs the call to #2 OBi port 5061, which is sp2. The above rule should do the rest - we hope  :)

miteldavid

Ianobi, I reconfigured OBi110 per Instructions.

#2 OBi
Voice Services -> SP2 Service -> X_InboundCallRoute: {li}

When I dial 1# from phone connected to OBi110 #1. I get recorded message saying
(The number you dialed sp2av@10.100.11.5.5061 was rejected by service provider. reason 503).

I'm assuming it has to something with speed dial entry #1 sp2(av@10.100.11.5:5061) on OBi110 #1.

ianobi

Try sp2(@10.100.11.5:5061) The reject message may be coming from the Simplex PA.

To see exactly what each OBi is receiving and sending you will need to look into Status > Call History. This can only be accessed via each OBi's local web page. Dial ***1 from the phone attached to each OBi's Phone Port and it will tell you the IP address. User Name and Password will be "admin".

miteldavid

Ianobi,

I changed Speed Dials 1. sp2(@10.100.11.5:5061) on OBi110 #1. same message

call history shows on OBi110 #1 reads-

call 50 - 8/20/2013 -
terminal id - PHONE 1 - SP2
Peer Name - blank - blank
Peer Number - 100 - av@10.100.11.5:5061
Direction - outbound -outbound
08:34:01 - new call - blank
08:34:02 - blank - call connected
08:34:08 - end call  - blank


Thanks for your help on this one!

ianobi

I'm not sure what to make of that info. I would expect the latest call in Call History to be "Call 1".

It seems odd that sp2 outbound shows "av@10.100.11.5:5061" when the speed dial is "@10.100.11.5:5061".


QBZappy

Quote from: miteldavid on August 20, 2013, 11:41:15 AM
The Simplex does not answer ringing calls, but you can go off hook with an analog phone connected to Simplex page port and get Intercom dial tone.

@miteldavid

1) I'm not certain I have understood everything. Does OBi2 connected directly to the PA system work as you expect it? How far apart are these two OBi units? If the analogue phone attached to OBi2 works, can a long extension or cordless phone to your far away location simplify the setup?

2) Another way is to use the OBiAPP on your computer or smartphone, using OBi2 as a gateway. This should also work if your reply is affirmative above.

3) Bridging the two OBi's should work using either OBiTALK or SIP approach. SIP should be more reliable because it has fewer dependencies.
li=PA system connected to line port
a) OBi1=>OBi2 (via hotline or speed dial) using sip uri config
b) OBi2 inbound call route => li

The Paging system solution as offered by the OBi is via audio cable to some amplified sound system. In your specific topology the OBi paging method is not an obvious solution. Also, I think you should make sure that DTMF is used on OBi2 connected to the PA system. You have a full fledged PA system going on there. It seems to act like a co line. Without knowing any specifics you may need to play around with the connect disconnect values to get it right. You might have some luck with the seller or manufacturer. To make things simple you can say you are trying to connect to a PBX system.

Owner of the 1st OBi110/100 units in service in Canada & South America. 1st OBi202 on my street. 1st OBi1032 in Montreal.

miteldavid

Ianobi,

sorry I posted the wrong call history report when I get back onsite tomorrow I will post the correct one's. On another note I programmed Obi110 #2 Voice Services -> SP2 Service -> X_InboundCallRoute: {li} and connected Simplex PA access port to line port. I continued to monitor with test set (lineman's analog phone). When calling from OBi110 #1 to OBi110 #2 and rings I can hear from my test set the Simplex Intercom dial tone for a split second  hear a burst of ringing, tone or even voltage breaks loop on PA system then call is connected at this point the simplex system is off hook before being connected to line and in this state the Simplex system is waiting for feature access code to be completed. On the calling side I can hear one ring the OBi110 #2 pickup and silence, I tried to dial any Simplex access code but get error tone from PA system instead. Is there any way to get rid of that burst of ringing, tone so it does not break loop on PA system before being connected? Could there be any digits being passed through line port of Obi110 #2 causing loop to break? Thanks!

QBZappy,

1) The OBi110 #2 does not work like I expect. When calling from OBi110 #1 to OBi110 #2 and rings I can hear from my test set the Simplex Intercom dial tone for a split second  hear a burst of ringing, tone or even voltage breaks loop on PA system then call is connected at this point the simplex system is off hook before being connected to line and in this state the Simplex system is waiting for feature access code to be completed. On the calling side I can hear one ring the OBi110 #2 picks up and silence, I tried to dial any Simplex access code but get error tone from PA system instead. I connected my test set to phone port of OBi110 #2 when go off hook and dial # I'm immediately connected to Simplex PA intercom dial tone and able to dial any Simplex feature code access page feature. Works like a champ in this scenario. Both OBi110 are about 5-6 blocks from each other. (1) at the School District and (1) at a Elementary School. Cordless would not work for this set up.

2) I'd rather not use OBIAPP but if its the only way to get to work then it is an option.

3) The OBi110 are bridged using easy sip set up with IP and speed dial.This configuration is already set up. l

i=PA system connected to line port
a) OBi1=>OBi2 (via hotline or speed dial) using sip uri config (using speed dial config).
b) OBi2 inbound call route => li

The OBi paging method seem to work better I could call OBi110 #2 call is picked up automatically. after page tone, I was able to get intercom dial tone from Simplex PA system and dial Simplex feature code and access paging feature. The only problem under this scenario when I would hang up the phone the Simplex PA system would remain off hook and waiting for disconnect signal. PA access port is like a C.O. its as easy plugin in a analog phone going off hook getting intercom dial tone and dialing feature codes hang up to disconnect. It used to work when it was connected to Digital PBX trunk port at the school. Now they have a VOIP PBX at district and Per nodes at all school's that dont support trunk ports. I apologize for all my ranting about this set up and thank you guys for helping me out!

QBZappy

Quote from: miteldavid on August 21, 2013, 12:16:08 AM
I connected my test set to phone port of OBi110 #2 when go off hook and dial # I'm immediately connected to Simplex PA intercom dial tone and able to dial any Simplex feature code access page feature. Works like a champ in this scenario.

Since you confirm that this leg of the connection works, we should focus on the OBi1=>OBi2 part of the equation. I seems that there is something lost in the translation. The PA system is analogue, it likely only understand tones in DTMF. On the OBi2 did you try setting tones to DTMF to 'inband' (Service Providers->ITSP Profile X->General->DTMFMethod)? Play around with these settings and see if it makes a difference. There are also other DTMF and other variable settings in the 'Physical Interfaces' which may neeed to be tweaked.
Owner of the 1st OBi110/100 units in service in Canada & South America. 1st OBi202 on my street. 1st OBi1032 in Montreal.

ianobi

It just so happens that my home setup consists of two OBi110's, so I have set up a simulation:

Tel -- #1 OBi - - - subnet - - - #2 OBi ---- XLink

The XLink is a GSM device that has a FXS port for an analogue phone to plug into, then you can dial via Bluetooth connected cell phones.


I find that using a speed dial in this format sp2(@10.100.11.5:5061) works fine and I get the dial tone from the XLink. Anything before the "@" OBi will attempt to send out as tones / digits.

In Call History for #1 OBi I would expect to see:

terminal id -    PHONE 1 -                       SP2
Peer Name -    blank -                              blank
Peer Number - sp2(@10.100.11.5:5061)      @10.100.11.5:5061


I went on to the full set up with "hot-line" working. It was so fast that I thought nothing had happened. I picked up the phone attached to #1 OBi and got dial tone from the XLink instantly and successfully dialled a call.

I need to rework my reply #6 as we are now using the OBi110 Line Port and security will have to done differently, which changes to Phone Port DigitMap – working on this now.

The Line Port method is definitely the way to go as using the OBi paging system keeps the OBi Phone Port off-hook all the time holding up the PA system.

Still working on a few items for this setup, but basics are working fine here. There may be a glitch or two to iron out between the #2 OBi and the PA system.