• V20: 3CX Re-engineered. Get V20 for increased security, better call management, a new admin console and Windows softphone. Learn More.

SOLVED - Strange Patton Smartnode 4960 Caller Name problem

Status
Not open for further replies.

star1

Bronze Partner
Joined
Apr 7, 2010
Messages
43
Reaction score
0
We have a Patton SN 4960 connected to a US T1 circuit. The unit is working smoothly with 3CX with one exception. We're having a problem with receiving caller name. I've debugged it and we're receiving it on time from the provider. When we enable the caller-name option in the ISDN interface, 3CX correctly receives it.

The problem is that when it's enabled, we're no longer able to make outbound calls on the T1. It seems that the caller-name option is 2 way. Meaning that when enabled, it receives & transmits name presentation info. Our telco provider apparently doesn't like us sending presentation info because the call is getting disconnected. Here's some ISDN debug info from the patton.

Is there a way to only receive the info and not send. I'm thinking maybe there's a way to create a mapping table to strip caller name presentation info for calls going to ISDN, but I'm not comfortable enough with mappings.

Any advice is much appreciated. I'm including ISDN logs below of good/bad calls in case anyone's interested.

Thanks,
Eric

Good Call
23:35:18 ICC > [IF_ISDN_0] NEW CALL. Allocated Endpoint IF_ISDN_0-00a98508
23:35:18 ICC > [EP IF_ISDN_0-00a98508] do not reroute because: no endpoint with call key: YzhjODczMTBlYWVlNzE0MTJhYzQxODQyNzU0NGQwMTM.
23:35:18 ICC > [EP IF_ISDN_0-00a98508] AOC-S User << Call Setup
23:35:18 ICC > [EP IF_ISDN_0-00a98508] AOC-D User << Call Setup
23:35:18 ICC > [EP IF_ISDN_0-00a98508] AOC-E User << Call Setup
23:35:18 ICC > [EP IF_ISDN_0-00a98508] >> [080005]
SETUP (NI2 User)
[04039090A2]
Bearer capability : 3.1kHz Audio - CCITT
circuit mode - 64kBit/s - G.711 U-law
[1E028583]
Progress indicator : origination address is non-ISDN
private network serving remote user - CCITT
[6C0C008039313437353036373131]
Calling party number : 9147501212
unknown number - unknown numbering plan
presentation allowed - user provided not screened
[700C803139313734333234373030]
Called party number : 19174321313
unknown number - unknown numbering plan

23:35:18 ICC > [EP IF_ISDN_0-00a98508] Set state to CALL INITIATED
23:35:18 ICC > [EP IF_ISDN_0-00a98508] State: CALL INITIATED, Event: PEER CONNECTED
23:35:18 ICC > [EP IF_ISDN_0-00a98508] Hold State: IDLE, Hold Event: PEER CONNECTED
23:35:18 ICC > [IF_ISDN_0] << Message: primitive=43
23:35:18 ICC > [EP IF_ISDN_0-00a98508] << [080002]
CALL PROCEEDING (NI2 User)
[1803A98381]
Channel id : 1 - exclusive
other interface - is not d-channel - CCITT - b-channel units

23:35:18 ICC > [EP IF_ISDN_0-00a98508] State: CALL INITIATED, Event: TERMINAL PROCEEDING IND
23:35:18 ICC > [EP IF_ISDN_0-00a98508] Set state to OUTGOING PROCEEDING
23:35:22 ICC > [IF_ISDN_0] << Message: primitive=44
23:35:22 ICC > [EP IF_ISDN_0-00a98508] << [080003]
PROGRESS (NI2 User)
[1E028188]
Progress indicator : inband information available
private network serving local user - CCITT

23:35:22 ICC > [EP IF_ISDN_0-00a98508] State: OUTGOING PROCEEDING, Event: TERMINAL PROGRESS IND
23:35:22 ICC > [EP IF_ISDN_0-00a98508] State: OUTGOING PROCEEDING, Event: PEER INBAND INFO


This is what happens when we pass the caller name through when it's enabled

23:32:56 ICC > [IF_ISDN_0] NEW CALL. Allocated Endpoint IF_ISDN_0-00dce1b8
23:32:56 ICC > [EP IF_ISDN_0-00dce1b8] do not reroute because: no endpoint with call key: NTY2N2U5MzlmNzk0NTI0YjE3ZmQ3YjBlMzNkYjI2NGY.
23:32:56 ICC > [EP IF_ISDN_0-00dce1b8] AOC-S User << Call Setup
23:32:56 ICC > [EP IF_ISDN_0-00dce1b8] AOC-D User << Call Setup
23:32:56 ICC > [EP IF_ISDN_0-00dce1b8] AOC-E User << Call Setup
23:32:56 ICC > [EP IF_ISDN_0-00dce1b8] CNIP << Name Request
23:32:56 ICC > [EP IF_ISDN_0-00dce1b8] >> [080005]
SETUP (NI2 User)
[04039090A2]
Bearer capability : 3.1kHz Audio - CCITT
circuit mode - 64kBit/s - G.711 U-law
[1C189FA115020101020100800D2245726963204D616E64656C22]
Facility : Invoke : invokeid: 00000001
global operation
invoke {
present = 1
local = 0
argumentnamePresentationAllowedSimple = '"JOHN DOE"'
}
[1E028583]
Progress indicator : origination address is non-ISDN
private network serving remote user - CCITT
[6C0C008039313437353036373131]
Calling party number : 9147501212
unknown number - unknown numbering plan
presentation allowed - user provided not screened
[700C803139313734333234373030]
Called party number : 19174321313
unknown number - unknown numbering plan

23:32:56 ICC > [EP IF_ISDN_0-00dce1b8] Set state to CALL INITIATED
23:32:56 ICC > [EP IF_ISDN_0-00dce1b8] State: CALL INITIATED, Event: PEER CONNECTED
23:32:56 ICC > [EP IF_ISDN_0-00dce1b8] Hold State: IDLE, Hold Event: PEER CONNECTED
23:32:56 ICC > [IF_ISDN_0] << Message: primitive=43
23:32:56 ICC > [EP IF_ISDN_0-00dce1b8] << [080002]
CALL PROCEEDING (NI2 User)
[1803A98381]
Channel id : 1 - exclusive
other interface - is not d-channel - CCITT - b-channel units

23:32:56 ICC > [EP IF_ISDN_0-00dce1b8] State: CALL INITIATED, Event: TERMINAL PROCEEDING IND
23:32:56 ICC > [EP IF_ISDN_0-00dce1b8] Set state to OUTGOING PROCEEDING
23:32:56 ICC > [IF_ISDN_0] << Message: primitive=34
23:32:56 ICC > [EP IF_ISDN_0-00dce1b8] << [080045]
DISCONNECT (NI2 User)
[080282A9]
Cause : temporary failure
public network serving local user - CCITT - Q.931

23:32:56 ICC > [EP IF_ISDN_0-00dce1b8] State: OUTGOING PROCEEDING, Event: TERMINAL DISCONNECT IND
23:32:56 ICC > [EP IF_ISDN_0-00dce1b8] Set state to DISCONNECT INDICATION
 
First, I must say that after working with Cisco voip gateways for years, the Patton configuration is a breath of fresh air.

I was able to solve the problem using mapping tables and a complex function in order to maintain the 3CX recommended config. Here's my config that then has to be applied to your ISDN interface.

Code:
mapping-table calling-pi to calling-e164 MP_REM_CLIR
    map restricted to ""

  mapping-table calling-name to calling-name MP_REM_CNAM
    map default to ""

  complex-function CF_MAP_FOR_ISDN
    execute 1 MP_REM_CLIR
    execute 2 MP_REM_CNAM

Hope this helps.

-Eric
 
Re: SOLVED - Strange Patton Smartnode 4960 Caller Name probl

We just went through this same problem and the telecom made a change that helped us. They enabled PCN ALW on the TDM switch to allow the two way caller ID. We were getting Error #98, Invalid message for call state when we dailed local numbers. After the change we have CID names and local calls working in harmony.
 
Status
Not open for further replies.
Get 3CX - Absolutely Free!

Link up your team and customers Phone System Live Chat Video Conferencing

Hosted or Self-managed. Up to 10 users free forever. No credit card. Try risk free.

3CX
A 3CX Account with that email already exists. You will be redirected to the Customer Portal to sign in or reset your password if you've forgotten it.