Dismiss Notice
We would like to remind you that we’re updating our login process for all 3CX forums whereby you will be able to login with the same credentials you use for the Partner or Customer Portal. Click here to read more.

SPA-3102 Fix

Discussion in 'Windows' started by sigma1, May 27, 2010.

Thread Status:
Not open for further replies.
  1. sigma1

    sigma1 Active Member

    Joined:
    Nov 20, 2009
    Messages:
    542
    Likes Received:
    1
    Not too long ago I was browsing for a solution to why the 3102 doesn't pass the caller ID. I saw everything from increasing this time to the other thing.

    Here's the solution (replace template)
     

    Attached Files:

    • 3102.txt
      File size:
      59.6 KB
      Views:
      158
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  2. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    11,094
    Likes Received:
    327
    In North America this value really needs to be a "3" or above to collect the CID info. Otherwise the 3102 doesn't wait long enough before sending the call info on to 3CX.
    I'm assuming that this provisions the 3102 with a "0"

    <PSTN_Answer_Delay_2_ ua="na">0</PSTN_Answer_Delay_2_>



    And this (yes) sends incoming PSTN calls through to the FXS jack, which is fine if you don't want to use the 3102 as a 3CX trunk.

    <PSTN_Ring_Thru_Line_1_2_ ua="na">Yes</PSTN_Ring_Thru_Line_1_2_>
     
Thread Status:
Not open for further replies.