3CX vs Patton SN4171 E1 Trunking

Discussion in '3CX Phone System - General' started by sigma, May 8, 2018.

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

    Joined:
    Aug 27, 2017
    Messages:
    20
    Likes Received:
    3
    Hi all,

    We are a bit lost in space with 3CX config of a E1 Trunk (some legacy stuff) - due to the fact that we - as pure IP guys - the PSTN world is *not* our famous playground.
    It would be highly appreciated if someone of you guys has already made nice experiences with 3CX E1 Trunking based on Patton SN4171.

    The story:
    Actually we facing some issues with the proper CallerID signaling on a E1 Trunk (...)
    Of course there are some special things in the game:
    3CX PBX --> SN4171 <--PRI--> Cisco 2811 --> Corp. H.Q. BROAD

    Status:
    Outbound from 3CX to remote party:
    • Caller Number - OK
    • Caller name - OK
    • Voice (talk/listen) - OK
    --
    Inbound from remote party to 3CX:
    • Caller Number - not OK
    • Caller name - not OK
    • Voice (talk/listen) - OK
    --

    I assume this need to be tweaked on the Trunk -> "Outbound Parameters"
    In order to avoid to get a nightmare, I'd like to raise the flag and ask for your opinions and experiences in advance.

    Many Thanks
    Max
     
  2. eddv123

    eddv123 Well-Known Member

    Joined:
    Aug 15, 2017
    Messages:
    1,248
    Likes Received:
    175
    Hi Max,

    First and foremost Caller-ID is a paid service with ISDN - have you confirmed with your provider that it is paid and enabled on the line(s) you have ?

    You can trace from the Patton command line specifically for caller-id with the command “debug media‐gateway all”.
     
  3. sigma

    Joined:
    Aug 27, 2017
    Messages:
    20
    Likes Received:
    3
    Hi - thanks

    I forgot to mention that the E1 trunk is not a public, but a private, proprietary trunk.

    BR
     
  4. eddv123

    eddv123 Well-Known Member

    Joined:
    Aug 15, 2017
    Messages:
    1,248
    Likes Received:
    175
    Hi Sigma,

    So to confirm, you are mimicking an ISDN trunk internally ? what is the use case for this ? are you migrating PBX or something like that ?
     
  5. YiannisH_3CX

    YiannisH_3CX Support Team
    Staff Member 3CX Support

    Joined:
    May 10, 2016
    Messages:
    6,388
    Likes Received:
    455
    Since the issue is with incoming calls to 3CX then i would recommend looking at an incoming invite towards 3CX. That should tell you what information is being passed to 3CX and if any of the Inbound parameters needs adjusting so you can read the information from the correct field.
     
  6. sigma

    Joined:
    Aug 27, 2017
    Messages:
    20
    Likes Received:
    3
    Gents,

    I have to apologize because the "Status" I mentioned earlier is 180 degree wrong -

    Here is the correct one:

    Status:
    Inbound from remote party to 3CX:
    Caller Number - OK
    Caller name - OK
    Voice (talk/listen) - OK
    --
    Outbound from 3CX party to remote party:
    Caller Number - not OK
    Caller name - not OK
    Voice (talk/listen) - OK
    --

    Sorry for this confusion !

    BR, Max
     
  7. eddv123

    eddv123 Well-Known Member

    Joined:
    Aug 15, 2017
    Messages:
    1,248
    Likes Received:
    175
    Then do the opposite of what Yiannish suggested :)

    Trace an outbound call via the logging and PCAP and take a look, have you got the caller ID set where it need to be (trunk an/or extension) you are ringing from ?
     
  8. YiannisH_3CX

    YiannisH_3CX Support Team
    Staff Member 3CX Support

    Joined:
    May 10, 2016
    Messages:
    6,388
    Likes Received:
    455
    Then as eddv123 suggested trace a call from 3CX and make sure all information is where is should be. If you know the SIP fields required for the caller ID to be correctly presented at the other side then you can adjust accordingly.
     
  9. sigma

    Joined:
    Aug 27, 2017
    Messages:
    20
    Likes Received:
    3
    OK - need to go onsite - do some re-cabling of old E1 GW(active) to SN4171 (new intended to migrate), ...

    will be back asap

    Thx
     
    YiannisH_3CX likes this.
  10. YiannisH_3CX

    YiannisH_3CX Support Team
    Staff Member 3CX Support

    Joined:
    May 10, 2016
    Messages:
    6,388
    Likes Received:
    455
    Let us know of what you find and if further assistance is needed
     
  11. sigma

    Joined:
    Aug 27, 2017
    Messages:
    20
    Likes Received:
    3
    case is still open
     
  12. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,855
    Likes Received:
    301
    What is at the other end of the E1? A PBX?
     
  13. eddv123

    eddv123 Well-Known Member

    Joined:
    Aug 15, 2017
    Messages:
    1,248
    Likes Received:
    175
    This is what I thought also, it sounds like a standard ISDN/Legacy PBX migration possibly.
     
Thread Status:
Not open for further replies.