obi110 bridge with no Internet?

<< < (3/5) > >>

flipdee:
I get callerid on OBi #1 using all default callerid settings (I was expecting to have to change FSK (Bell 202) with being in the UK.
Call 1   12/12/2011    01:30:56   

Terminal ID   LINE1   
Peer Name      
Peer Number   0xxxxxxxxxx   
Direction   Inbound   Inbound
01:30:56   Ringing   Forking to:SP2(_g1192.168.1.62:5061*), PHONE1
01:31:04   End Call   

However I just get the following on OBi #2
Call 1   12/12/2011    01:30:57   

Terminal ID   SP2   PHONE1
Peer Name      
Peer Number      
Direction   Inbound   Inbound
01:30:57   Ringing   
01:31:05   End Call   
And no callerid appearing on the pots telephone.

Not absolutely necessary but it would be nice.

flipdee

P.S. I meant to say, I assume callerid does work on an FXS device connected to an OBi110?

Stewart:
RonR, two questions:

On outbound calls to the PSTN, couldn't you set up the system so it "hotlines" to a number on the other OBi that dials "nothing" on the LINE port, so you would hear PSTN dial tone and could dial through?  This would have several advantages:

1. Faster call setup time; you wouldn't have to accumulate DTMF and then send it back out.
2. If the digit map otherwise couldn't determine end-of-number, you would avoid an interdigit timeout.
3. On calls that would be dialed manually, if the PSTN line is in use elsewhere, you'd find out before taking the effort to dial.

On calls from the PSTN to remote OBi(s), couldn't you set up SPx (instead of VGx) to point to the other OBi(s), so you could pass caller ID?  Of course, this would be limited to a maximum of two remotes -- additional units would be called via VGx and would not receive caller ID.

RonR:
Quote from: Stewart on December 11, 2011, 05:45:01 pm

On outbound calls to the PSTN, couldn't you set up the system so it "hotlines" to a number on the other OBi that dials "nothing" on the LINE port, so you would hear PSTN dial tone and could dial through?  This would have several advantages:

1. Faster call setup time; you wouldn't have to accumulate DTMF and then send it back out.
2. If the digit map otherwise couldn't determine end-of-number, you would avoid an interdigit timeout.
3. On calls that would be dialed manually, if the PSTN line is in use elsewhere, you'd find out before taking the effort to dial.


That approach might work.  Give it a try and see.

Quote from: Stewart on December 11, 2011, 05:45:01 pm

On calls from the PSTN to remote OBi(s), couldn't you set up SPx (instead of VGx) to point to the other OBi(s), so you could pass caller ID?  Of course, this would be limited to a maximum of two remotes -- additional units would be called via VGx and would not receive caller ID.


AFAIK, CallerID can only be passed when one of the trunks being bridged is the OBiTALK trunk.  The last I knew, Obihai intentionally retricts passing CallerID when the OBiTALK trunk is not involved:

Enhancements & Fixes in Maintenance Release 1.3.0(2575):
Version 1.3 highlights:
- Allow Caller-id spoofing for calls bridged via OBiTALK service. But use the obi number for circle-of-trust authentication.

When v1.3 first came out, it was noted that CallerID was not being passed on things like SIP/SIP and GV/SIP.

Stewart:
Though my OBi is presently down so I can't test, its SP2 had been registered to PBXes as a sub-PBX and successfully passed caller ID on incoming PSTN calls.  PBXes then forked the call to IP phones, registered as extensions.

RonR:
Stewart,

The approach you suggested works given the following changes:


OBi #1:

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

OBi #2:

Physical Interfaces -> PHONE Port -> DigitMap : (<S0:+>|...)

Physical Interfaces -> PHONE Port -> OutboundCallRoute : {+:vg1},...


OBi #2 hot dials OBi #1 and you get PSTN dialtone.  However, you lose the ability to use Speed Dials and Auto Attendant 2 (*** configuration) from OBi #2.

If it's important have the ability to get real PSTN dialtone on OBi #2, I would suggest the following changes:


OBi #1:

Voice Services -> SP2 Service -> X_InboundCallRoute : {>(<+:>|(Mli)):li}

OBi #2:

Physical Interfaces -> PHONE Port -> OutboundCallRoute:

{([1-9]x?*(Mpli)):pp},{(<#:+>|911):vg1},{**0:aa},{***:aa2},{(<**1:>(Msp1)):sp1},
{(<**2:>(Msp2)):sp2},{(<**8:>(Mli)):li},{(<**9:>(Mpp)):pp},{(Mpli):vg1}


This allows dialing # from OBi #2 to get real PSTN dialtone from OBi #1.  This also allows 911 from OBi #2 to go out the LINE Port of OBi #1.

Navigation

[0] Message Index

[#] Next page

[*] Previous page