Losing caller ID from POTS thru OBi110

FreePBX
1

I have a POTS line from Comcast that I connected to my PIAF using an OBi110 as FXO port. Everything works fine EXCEPT that the caller ID is being rewritten when passed to my Panasonic cordless phone.

If I call in through one of my VOIP trunks, the logs look like this:

[2018-10-02 12:48:12] VERBOSE[5240][C-000000e7] pbx.c: -- Executing [s@macro-user-callerid:1] Set("SIP/VI_In1-00000153", "TOUCH_MONITOR=1538506083.339") in new stack
[2018-10-02 12:48:12] VERBOSE[5240][C-000000e7] pbx.c: -- Executing [s@macro-user-callerid:2] Set("SIP/VI_In1-00000153", "AMPUSER=13035552525") in new stack
[2018-10-02 12:48:12] VERBOSE[5240][C-000000e7] pbx.c: -- Executing [s@macro-user-callerid:3] GotoIf("SIP/VI_In1-00000153", "0?report") in new stack
[2018-10-02 12:48:12] VERBOSE[5240][C-000000e7] pbx.c: -- Executing [s@macro-user-callerid:4] ExecIf("SIP/VI_In1-00000153", "1?Set(REALCALLERIDNUM=13035552525)") in new stack

This is correctly recognizing the caller ID number.

If I call in through my POTS line, the logs look like this:

[2018-10-02 12:38:21] VERBOSE[5129][C-000000e6] pbx.c: -- Executing [s@macro-user-callerid:1] Set("SIP/ObiTrunk1-00000151", "TOUCH_MONITOR=1538505501.337") in new stack
[2018-10-02 12:38:21] VERBOSE[5129][C-000000e6] pbx.c: -- Executing [s@macro-user-callerid:2] Set("SIP/ObiTrunk1-00000151", "AMPUSER=ObiTrunk1") in new stack
[2018-10-02 12:38:21] VERBOSE[5129][C-000000e6] pbx.c: -- Executing [s@macro-user-callerid:3] GotoIf("SIP/ObiTrunk1-00000151", "0?report") in new stack
[2018-10-02 12:38:21] VERBOSE[5129][C-000000e6] pbx.c: -- Executing [s@macro-user-callerid:4] ExecIf("SIP/ObiTrunk1-00000151", "1?Set(REALCALLERIDNUM=ObiTrunk1)") in new stack

The caller ID number is being recognized as the trunk name “OBiTrunk1” instead of as the actual caller ID number.

I do have a caller ID subscription from Comcast and it works fine. The caller ID displays correctly if this same phone is plugged directly into the Comcast phone modem.

I have not found any settings in OBi Expert setup to change how the caller ID is passed. I don’t know if the caller ID is being rewritten by the OBi110 or by Asterisk. It is being changed from the actual caller ID number to the trunk name.

In my inbound route. CallerID number, CID priority route, CID name prefix are blank. Privacy manager is off. There is no CID lookup source. CID Superfecta is off.

Does anyone have any suggestions on how I can get the caller ID to pass through correctly?

2

For the ITSP Profile in question -> SIP, turn on X_SpoofCallerID.

If it was already on or that doesn’t help, check whether the OBi Call History shows the correct caller ID.

If not, post a screenshot of your Line Port settings.

If Call History is correct, post your trunk settings (mask any passwords, account numbers, phone numbers or other personal information).

1 Like
3

Stewart,

Thanks. I turned X_SpoofCallerID back on. I’ve had it both ways.

My OBi call history does not register the caller ID of the incoming call. It only shows the Peer Number for SP2 (my POTS number that was dialed). I’ve attached a screenshot. HOWEVER, under Line port status, it does show the last caller info with caller ID name & number. So it is receiving the info. It’s not recording it into the call log or passing it on.

4

Just guessing here, if Comcast MTA sends a full 2 seconds of first ring before the caller ID, your RingDelay might not be long enough. Try setting it to 4000 and test. If that works, see if 3000 is reliable.

If the above doesn’t help, post a screenshot of Line Port showing Port Settings and Ring Detection. If we can’t spot anything there, maybe syslog will give a clue.

1 Like
5

Stewart, I’ll try 4000 ms later today. 3000 ms did not get the caller ID, though it was noticably slower in putting the call through. 5000 ms was such a long delay that Comcast gave up ringing before the OBi picked up, so the calls did not go through.

6

Stewart, do you have a copy of the syslog server? OBihai apparently doesn’t have it on their website anymore.

7

Something very strange must have happened. Comcast would normally ring for at least a minute (60000 ms) before giving up. Possibilities include: You have a setting at Comcast to send the call to voicemail after only 5 seconds (you might have done this if your PBX normally answers immediately with an IVR and you’re using Comcast voicemail as failover if the PBX is down or inaccessible). Something or someone else bridged on the line picked up (fax machine, alarm system, your wife, etc.). A (possibly related) technical problem caused the OBi to trip the ring but not forward the call to the PBX.

What does Call History show for the 5000 ms case?

I don’t use a special syslog server, preferring to just use Wireshark. That way, SIP packets copied to syslog (turn on X_SipDebugOption for the SPx in question) get correctly parsed.

1 Like
8

Stewart,
Thanks so much! That’s exactly what was going on. I just needed Comcast to ring longer and I’m getting the caller ID. And 4000 ms is enough when 3000 was not.
Steve

9

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.