bad callerid over PSTN

Discussion in '3CX Phone System - General' started by radix, Jan 20, 2009.

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

    Joined:
    Feb 5, 2008
    Messages:
    23
    Likes Received:
    0
    Using v7 4744, mini version
    with a patton 4554 r5.2
    client v7 on vista.


    Configured outgoing caller id is 1234560
    for each extension there is an DDI rule defined for inbound calls.
    With client v7 when any extension dials a number over PTSN (ISDN) an 3 is appened at the end of caller id like
    1234563.
    When the softphone v7 is used to dial out , the right caller id is shown (1234560).

    Anyone know why the v7 client i appending a 3 at the end of the caller id? And on the same computer/ same extension with v7 softphone everything look ok?
    This happens on all instalation of client v7.

    Thanks
     
  2. William400

    William400 Well-Known Member

    Joined:
    Aug 21, 2006
    Messages:
    1,005
    Likes Received:
    0
    Hi

    You are referring to the V7 client and V7 softphone. Can you please tell us the exact build of each from the Help > About ?

    If you register both V7 Client and V7 softphone as ext 100 (or any extension in your range) do you still replicate the issue? If NOT check the outbound caller ID of the extensions that display the issue.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. radix

    Joined:
    Feb 5, 2008
    Messages:
    23
    Likes Received:
    0
    HI,

    v7 client: 7.0.4184
    softphone: 3.0.4959

    if I register both with the same extension I get different caller ids.

    EDIT:
    Not anymore after an re-install. now both clients append an "3" at the end of the number

    -radix
     
  4. radix

    Joined:
    Feb 5, 2008
    Messages:
    23
    Likes Received:
    0
    This is the log from patton 4554

    Code:
    Active Calls
    ============
    Call      Call-Leg              State               Address        Display        Charge       
    -----------------------------------------------------------------------------------------------
                                                                                                   
    00988850                                                                                       
              IF_SIP_1-009a57e8/ac  CONNECTED           3              n/a            n/a          
              IF_ISDN_1-00e2bab0/a  CONNECTED           01511xxxx34   n/a            5 units (subT
    
    
    
    as you can see the address is listed like "3". On the 3cx Port/status the caller ID is listed correctly.
    Where come this "3§ from ... and how can I change it to a "0" ?
     
  5. Vali_3CX

    Vali_3CX Well-Known Member
    Staff Member 3CX Support

    Joined:
    Dec 12, 2008
    Messages:
    1,477
    Likes Received:
    67
    Hi, radix

    After reinstalling phones, the PBX or Patton? (I'm asking because we were not able to reproduce that issue on our tests, therefore we try to collect as much as possible relevant informations, which might be useful to locate and fix the problem.) Is there any outbound rule, or anything else you can figure out, you assigned as "3" in the whole configuration?

    thanks
    vali
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  6. radix

    Joined:
    Feb 5, 2008
    Messages:
    23
    Likes Received:
    0
    Hi,

    after reinstalling the softphone.
    I have only one outbound rule wich is just doing the stripping of the first digit (0) from the tel. number.
    The extensions have no outbound caller id defined. Each line from the patton 4554 have the same outbound caller id.
    The patton configuration is the configuration generated by 3cx. The only change that i've made in patton's config is on the call router/cofiguration -> append land code (0) and append interantional code (00).

    If you need configs/screenshots from configs I can post'em here.

    Thanks
     
  7. William400

    William400 Well-Known Member

    Joined:
    Aug 21, 2006
    Messages:
    1,005
    Likes Received:
    0
    Hi

    At this stage it would be best to see the logs of such a call.

    Can you please Paste the Verbose logging of such a call. Please paste the section from INVITE upwards, up till the call it routing to destination.

    Select first line, hold SHIFT...select top most line, then click 'Copy Selected text'. This will allow us to see where the '3' appears from.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  8. radix

    Joined:
    Feb 5, 2008
    Messages:
    23
    Likes Received:
    0
    Hi,

    Here is the logging.

    Code:
    10:35:48.416  [CM503008]: Call(147): Call is terminated
    
    10:35:48.416  [CM503008]: Call(147): Call is terminated
    
    10:35:13.838  [CM503007]: Call(147): Device joined: sip:10002@192.168.45.13:5062
    
    10:35:13.823  [CM503007]: Call(147): Device joined: sip:31@10.30.24.3:5070;rinstance=6599e39ab8ced8d4
    
    10:35:02.057  [CM503002]: Call(147): Alerting sip:10002@192.168.45.13:5062
    
    10:34:55.432  [CM503004]: Call(147): Calling: Unknown:015117403134@(Ln.10002@Patton 4554)@[Dev:sip:10002@192.168.45.13:5062, Dev:sip:10001@192.168.45.13:5060]
    
    10:34:55.338  [CM503010]: Making route(s) to <sip:0015117403134@troubadix.actinium.de:5060>
    
    10:34:55.323  [CM505001]: Ext.31: Device info: Device Identified: [Man: 3CX Ltd.;Mod: 3CX VoIP Client;Rev: General] Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CX Phone 7.0.4184.0] Transport: [sip:192.168.45.10:5060]
    
    10:34:55.307  [CM503001]: Call(147): Incoming call from Ext.31 to <sip:0015117403134@troubadix.actinium.de:5060>
    
    10:33:49.463  [CM504001]: Ext.31: new contact is registered. Contact(s): [sip:31@10.30.24.3:5070;rinstance=6599e39ab8ced8d4/31]
    

    some screenshots
    port status:
    http://i4.photobucket.com/albums/y115/radu_colceriu/3cx01.gif

    config:
    [​IMG]

    If a call is forwarded to an external line over a forwarding rule the right caller id is shown.
     
  9. William400

    William400 Well-Known Member

    Joined:
    Aug 21, 2006
    Messages:
    1,005
    Likes Received:
    0
    Hi

    The logging is not Verbose. Can you please explain what number you called and what extra '3' appeared?

    Please bear in mind that we do not know your config so please elboarate on the call made, number dialed , expects outcome etc!!

    Are you saying that E164 caused the issue?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  10. radix

    Joined:
    Feb 5, 2008
    Messages:
    23
    Likes Received:
    0
    Hi,

    Sorry for the previous log. Didn't know that I must restart the server that the verbosee logging get activated.
    Here is the verbose log:
    Code:
    18:08:02.126  [CM503008]: Call(1): Call is terminated
    
    18:08:02.126  [CM503008]: Call(1): Call is terminated
    
    18:07:59.585  Session 77 of leg C:1.1 is confirmed
    
    18:07:58.716  [CM503007]: Call(1): Device joined: sip:10001@192.168.45.13:5060
    
    18:07:58.716  [CM503007]: Call(1): Device joined: sip:31@10.30.24.4:5070;rinstance=e899c450d11e41f7
    
    18:07:58.716  [MS210007] C:1.1:Answer provided. Connection(by pass mode): 192.168.45.13:4986(4987)
    
    18:07:58.699  [MS210001] C:1.2:Answer received. RTP connection: 192.168.45.13:4986(4987)
    
    18:07:58.699  Remote SDP is set for legC:1.2
    
    18:07:53.371  [CM503002]: Call(1): Alerting sip:10001@192.168.45.13:5060
    
    18:07:46.059  [MS210006] C:1.2:Offer provided. Connection(by pass mode): 192.168.145.1:42000(42001)
    
    18:07:46.042  [CM503004]: Call(1): Calling: Unknown:015117403134@(Ln.10001@Patton 4554)@[Dev:sip:10001@192.168.45.13:5060, Dev:sip:10002@192.168.45.13:5062]
    
    18:07:45.944  [MS210000] C:1.1:Offer received. RTP connection: 192.168.145.1:42000(42001)
    
    18:07:45.944  [CM503010]: Making route(s) to <sip:0015117403134@troubadix.actinium.de:5060>
    
    18:07:45.927  Remote SDP is set for legC:1.1
    
    18:07:45.927  [CM505001]: Ext.31: Device info: Device Identified: [Man: 3CX Ltd.;Mod: 3CX VoIP Client;Rev: General] Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CX Phone 7.0.4184.0] Transport: [sip:192.168.45.10:5060]
    
    18:07:45.911  [CM503001]: Call(1): Incoming call from Ext.31 to <sip:0015117403134@troubadix.actinium.de:5060>
    
    18:07:45.518  [CM500002]: Info on incoming INVITE:
    
      INVITE sip:0015117403134@troubadix.actinium.de:5060 SIP/2.0
    
      Via: SIP/2.0/UDP 10.30.24.4:5070;branch=z9hG4bK-d8754z-22474b531436f96e-1---d8754z-;rport=5070
    
      Max-Forwards: 70
    
      Contact: <sip:31@10.30.24.4:5070>
    
      To: <sip:0015117403134@troubadix.actinium.de:5060>
    
      From: "3CXPhone"<sip:31@troubadix.actinium.de:5060>;tag=7b4b0803
    
      Call-ID: ZGQ5MGNmMDVhZDM3YTkwMDIwNjZiYjFjOGUxNDUyZWM.
    
      CSeq: 2 INVITE
    
      Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO
    
      Proxy-Authorization: Digest username="31",realm="3CXPhoneSystem",nonce="12877031265:0d883fa6aafddd5285df4fb81f366090",uri="sip:0015117403134@troubadix.actinium.de:5060",response="0ac120e6c782d75c3fcdfb542587daf2",algorithm=MD5
    
      Supported: replaces
    
      User-Agent: 3CX Phone 7.0.4184.0
    
      Content-Length: 0
    
      
    
    18:07:41.632  [CM504001]: Ext.31: new contact is registered. Contact(s): [sip:31@10.30.24.4:5070;rinstance=e899c450d11e41f7/31]
    
    Little about my config:
    So I have 2 ISDN lines (4 channels) with the same tel. nr (2772780) connected to a patton 4554 and 3cx v7 as PBX. There are defined extensions from 21 - 49. I have defined Inbound rules for DID to the extensions. Working great.
    As outbound rule I have defined that if the first digit is 0 the call to be directed to the patton gateway.
    The patton has firmware R5.2, the configuration is generated by 3cx.
    3cx IP: 192.168.45.10
    patton IP: 192.168.45.13

    About the call.
    All calls In/Out works great.
    In the PTSN Devices, for each line I defined as Outbound Caller Id : 0049 8382 2772780.

    In the provided log I've called from internal extension 31 to the external number 015117403134 (mobile phone). The call was working great except that it was displayed the number +49 8382 2772783 instead 0049 8382 2772780 on the mobile phone display. In the extension there is no outbound caller id defined.
    If I define a forward all rule for the extension 31 to the 015117403134 and then I call the 0049 8382 27727831 from another tel. on the
    015117403134 telefhone I get the correct number displayed (0049 8382 2772780).

    I've repeated this tests from the extensions 27, 31, 42 and all the time I get an 3 appended (+49 8382 2772783 ) so it looks that have nothing to do with the extension number.

    Actually what I want o have is that doesn't matter which extension make an call outside the display number should be 2772780.

    Thanks
     
  11. William400

    William400 Well-Known Member

    Joined:
    Aug 21, 2006
    Messages:
    1,005
    Likes Received:
    0
    Hi

    To get technical support on this one, you can contact our technical support
    (This requires commercial edition with support package). If you have a
    commercial edition, but no support package, you can purchase one here:
     
    https://erp.3cx.com/orderform/support.aspx
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  12. radix

    Joined:
    Feb 5, 2008
    Messages:
    23
    Likes Received:
    0
    I have a commercial version with 2 years support.
    I'll get in touch with the support.

    Thanks.
     
Thread Status:
Not open for further replies.