CallerID changing

Discussion in '3CX Phone System - General' started by izaxon, Aug 1, 2010.

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

    Joined:
    Aug 1, 2010
    Messages:
    4
    Likes Received:
    0
    Hi,

    I have the following setup:
    POTS => SPA-3102 => 3CX => PAP2T => phones

    When I get a call it is routed from POTS to the phones. First I see the correct caller ID (external number) and then it changes to 10001 which is the virtual extension number for the SPA-3102 connection.
    I just want to see the correct caller ID number and not the virt. ext. no. on the phones. Does anyone know how to change the settings to get it to work?

    Cheers,
    Johan
     
  2. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,368
    Likes Received:
    228
    Caller ID (analogue) is sent in one "burst", name and number fields. Could it be that the call display device is only capable of displaying one field at a time (cycling) and the outside number and the 10001 are, in fact, both being sent? Is the PAT2t set for North American type CID? Have you tried a display capable of showing both name and number fields at the same time?
     
  3. izaxon

    Joined:
    Aug 1, 2010
    Messages:
    4
    Likes Received:
    0
    Hi,

    It seems like first the correct number is sent, then also 10001 is sent.
    On the phone I can see two phone numbers on the caller list, both at with the same timestamp.

    How do I change the PAP2T caller id type? (I run 3CX in Sweden, Europe.)

    Thanks,
    Johan
     
  4. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,368
    Likes Received:
    228
    In the Regional Tab, you should see Caller ID Method. There should be a setting for Finland & Sweden, I guess you two countries use the same DTMF CID method.
     
  5. izaxon

    Joined:
    Aug 1, 2010
    Messages:
    4
    Likes Received:
    0
    Thanks,

    The CallerID Method was already set to Finland & Sweden. So, what else could be wrong? Why is the caller ID info for the extension (10001 in my case) sent after the real (first burst?) phone number?

    Log of an incoming call:
    11:16:41.527 [CM503008]: Call(188): Call is terminated
    11:16:37.658 [CM503007]: Call(188): Device joined: sip:10@192.168.0.110:5060
    11:16:37.643 [CM503007]: Call(188): Device joined: sip:10001@192.168.0.129:5062
    11:16:37.627 [CM505001]: Ext.10: Device info: Device Identified: [Man: Linksys;Mod: SPA Series;Rev: General] Capabilities:[reinvite, no-replaces, able-no-sdp, recvonly] UserAgent: [Linksys/PAP2T-5.1.6(LS)] PBX contact: [sip:10@192.168.0.116:5060]
    11:16:37.627 [CM503002]: Call(188): Alerting sip:10@192.168.0.110:5060
    11:16:34.819 [CM503025]: Call(188): Calling Ext:Ext.10@[Dev:sip:10@192.168.0.110:5060]
    11:16:34.788 [CM503004]: Call(188): Route 1: Ext:Ext.10@[Dev:sip:10@192.168.0.110:5060]
    11:16:34.788 [CM503010]: Making route(s) to <sip:10@192.168.0.116:5060>
    11:16:34.788 [CM505002]: Gateway:[PSTN] Device info: Device Identified: [Man: Linksys;Mod: SPA Series;Rev: General] Capabilities:[reinvite, no-replaces, able-no-sdp, recvonly] UserAgent: [Linksys/SPA3102-5.1.10(GW)] PBX contact: [sip:10001@192.168.0.116:5060]
    11:16:34.757 [CM503001]: Call(188): Incoming call from 10001@(Ln.10001@PSTN) to <sip:10@192.168.0.116:5060>
    11:16:34.757 [CM503012]: Inbound out-of-office hours rule (unnamed) for 10001 forwards to DN:10
    11:16:34.538 [CM503008]: Call(187): Call is terminated
    11:16:28.891 [CM503025]: Call(187): Calling Ext:Ext.10@[Dev:sip:10@192.168.0.110:5060]
    11:16:28.860 [CM503004]: Call(187): Route 1: Ext:Ext.10@[Dev:sip:10@192.168.0.110:5060]
    11:16:28.860 [CM503010]: Making route(s) to <sip:10@192.168.0.116:5060>
    11:16:28.860 [CM505002]: Gateway:[PSTN] Device info: Device Identified: [Man: Linksys;Mod: SPA Series;Rev: General] Capabilities:[reinvite, no-replaces, able-no-sdp, recvonly] UserAgent: [Linksys/SPA3102-5.1.10(GW)] PBX contact: [sip:10001@192.168.0.116:5060]
    11:16:28.844 [CM503001]: Call(187): Incoming call from 10001@(Ln.10001@PSTN) to <sip:10@192.168.0.116:5060>
    11:16:28.829 [CM503012]: Inbound out-of-office hours rule (unnamed) for 10001 forwards to DN:10
    11:16:28.532 [CM503008]: Call(186): Call is terminated
    11:16:22.932 [CM503025]: Call(186): Calling Ext:Ext.10@[Dev:sip:10@192.168.0.110:5060]
    11:16:22.916 [CM503004]: Call(186): Route 1: Ext:Ext.10@[Dev:sip:10@192.168.0.110:5060]
    11:16:22.916 [CM503010]: Making route(s) to <sip:10@192.168.0.116:5060>
    11:16:22.916 [CM505002]: Gateway:[PSTN] Device info: Device Identified: [Man: Linksys;Mod: SPA Series;Rev: General] Capabilities:[reinvite, no-replaces, able-no-sdp, recvonly] UserAgent: [Linksys/SPA3102-5.1.10(GW)] PBX contact: [sip:10001@192.168.0.116:5060]
    11:16:22.901 [CM503001]: Call(186): Incoming call from 0702358310@(Ln.10001@PSTN) to <sip:10@192.168.0.116:5060>
    11:16:22.870 [CM503012]: Inbound out-of-office hours rule (unnamed) for 10001 forwards to DN:10

    Thanks,
    Johan
     
  6. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,368
    Likes Received:
    228
    Unfortunately I'm not familiar with CID methods outside of the Bellcore type used in North America. Perhaps the system used in Finland allows for additional information to be sent later. I would start doing a search specific to the CID used in your country. It could be a setting but it may also just be the 3CX is handling it. If your CID devices are number only, then they may have a problem handling more than one number sent to them. That may also be the case with other DTMF bases CID systems, so you may be in a similar situation to countries other than Finland and Sweden. A quick search came up with something like this. http://forum.voxilla.com/cisco-linksys-sipura-voip-support-forum/problem-dtmf-caller-id-17687.html


    You may find something more relevant to your particular problem searching the Finnish or Swedish version of Google or another search engine.
     
  7. izaxon

    Joined:
    Aug 1, 2010
    Messages:
    4
    Likes Received:
    0
    Hi,
    I followed the link and made the suggested change to PSTN Ring Timeout value (from 5 to 6 seconds) in the SPA-3102 unit. That solved it. Now Caller ID is presented correctly! :)

    Thank you very much for the help! Very much appreciated!

    /J
     
Thread Status:
Not open for further replies.