3CX vs Patton SN4171 E1 Trunking

[sigma]

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

 

[eddv123]

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”.

 

[sigma]

Hi - thanks

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

BR

 

[eddv123]

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 ?

 

[YiannisH_3CX]

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.

 

[sigma]

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

 

[eddv123]

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 ?

 

[YiannisH_3CX]

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.

 

[sigma]

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]

Let us know of what you find and if further assistance is needed

 

[sigma]

case is still open

 

[leejor]

What is at the other end of the E1? A PBX?

 

[eddv123]

This is what I thought also, it sounds like a standard ISDN/Legacy PBX migration possibly.