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

Caller ID Number Not Shown

Status
Not open for further replies.

Stuck

Joined
Oct 13, 2007
Messages
6
Reaction score
0
Hello,

I just purchased a Patton Smartnode 4112 (2-Port FXO gateway) to replace the Grandstream GXW4104 we were using due to unacceptable sound quality & delays during conversation.

The sound quality is much better with the Patton, however, I cannot get the caller ID number to display anylonger on our inbound calls. I have the Patton setup to answer after 2 ring bursts.

Could someone please offer some pointers as to where the problem may be? We can't live without caller ID.

Thanks in Advance! :)

10:11:40.187 StratLink::eek:nHangUp [CM104001] Call(10): Ext.102 hung up call; cause: BYE; from IP:192.168.1.2
10:01:36.890 CallLegImpl::eek:nConnected [CM103001] Call(10): Created audio channel for Ln:10000@Patton SmartNode 4112 (192.168.1.101:4878) with Media Server (192.168.1.5:7038)
10:01:36.890 StratInOut::eek:nConnected [CM104005] Call(10): Setup completed for call from Ext.102 to Ln:10000@Patton SmartNode 4112
10:01:36.890 CallLegImpl::eek:nConnected [CM103001] Call(10): Created audio channel for Ext.102 (192.168.1.2:5004) with Media Server (192.168.1.5:7036)
10:01:32.812 CallConf::eek:nIncoming [CM103002] Call(10): Incoming call from 102 (Ext.102) to sip:[email protected]:5060
05:58:21.265 StratInOut::eek:nHangUp [CM104007] Call(9): Call from Ln:10000@Patton SmartNode 4112 to 999 has been terminated by Ln:10000@Patton SmartNode 4112; cause: BYE; from IP:192.168.1.101
05:57:30.171 CallConf::eek:nProvisional [CM103003] Call(9): Ext.101 is ringing
05:57:24.718 MediaServerReporting::DTMFhandler [MS211000] Call(9) Ln:10000@Patton SmartNode 4112: DTMF (RTP) from 192.168.1.101:4876 arrived. in-band DTMF tone detection is turned off.
05:57:20.046 CallLegImpl::eek:nConnected [CM103001] Call(9): Created audio channel for Ln:10000@Patton SmartNode 4112 (192.168.1.101:4876) with Media Server (192.168.1.5:7032)
05:57:20.015 CallConf::eek:nIncoming [CM103002] Call(9): Incoming call from 10000 (Ln:10000@Patton SmartNode 4112) to sip:[email protected]
05:57:00.843 StratInOut::eek:nHangUp [CM104007] Call(8): Call from Ln:10000@Patton SmartNode 4112 to 999 has been terminated by Ln:10000@Patton SmartNode 4112; cause: BYE; from IP:192.168.1.101
05:56:32.203 CallConf::eek:nProvisional [CM103003] Call(8): Ext.102 is ringing
05:56:26.734 MediaServerReporting::DTMFhandler [MS211000] Call(8) Ln:10000@Patton SmartNode 4112: DTMF (RTP) from 192.168.1.101:4874 arrived. in-band DTMF tone detection is turned off.
05:56:23.906 CallLegImpl::eek:nConnected [CM103001] Call(8): Created audio channel for Ln:10000@Patton SmartNode 4112 (192.168.1.101:4874) with Media Server (192.168.1.5:7028)
05:56:23.890 CallConf::eek:nIncoming [CM103002] Call(8): Incoming call from 10000 (Ln:10000@Patton SmartNode 4112) to sip:[email protected]
04:39:27.671 StratInOut::eek:nHangUp [CM104007] Call(7): Call from Ln:10000@Patton SmartNode 4112 to 999 has been terminated by Ln:10000@Patton SmartNode 4112; cause: BYE; from IP:192.168.1.101
04:39:00.296 CallConf::eek:nProvisional [CM103003] Call(7): Ext.102 is ringing
04:38:54.859 MediaServerReporting::DTMFhandler [MS211000] Call(7) Ln:10000@Patton SmartNode 4112: DTMF (RTP) from 192.168.1.101:4872 arrived. in-band DTMF tone detection is turned off.
04:38:47.984 CallLegImpl::eek:nConnected [CM103001] Call(7): Created audio channel for Ln:10000@Patton SmartNode 4112 (192.168.1.101:4872) with Media Server (192.168.1.5:7024)
04:38:47.937 CallConf::eek:nIncoming [CM103002] Call(7): Incoming call from 10000 (Ln:10000@Patton SmartNode 4112) to sip:[email protected]
04:33:32.578 StratInOut::eek:nHangUp [CM104007] Call(6): Call from Ln:10000@Patton SmartNode 4112 to 999 has been terminated by Ln:10000@Patton SmartNode 4112; cause: BYE; from IP:192.168.1.101
04:32:41.093 CallConf::eek:nProvisional [CM103003] Call(6): Ext.102 is ringing
04:32:35.531 MediaServerReporting::DTMFhandler [MS211000] Call(6) Ln:10000@Patton SmartNode 4112: DTMF (RTP) from 192.168.1.101:4870 arrived. in-band DTMF tone detection is turned off.
04:32:30.781 CallLegImpl::eek:nConnected [CM103001] Call(6): Created audio channel for Ln:10000@Patton SmartNode 4112 (192.168.1.101:4870) with Media Server (192.168.1.5:7020)
04:32:30.734 CallConf::eek:nIncoming [CM103002] Call(6): Incoming call from 10000 (Ln:10000@Patton SmartNode 4112) to sip:[email protected]
23:16:09.671 StratLink::eek:nHangUp [CM104001] Call(5): Ext.102 hung up call; cause: BYE; from IP:192.168.1.2
23:15:49.343 CallLegImpl::eek:nConnected [CM103001] Call(5): Created audio channel for Ln:10000@Patton SmartNode 4112 (192.168.1.101:4868) with Media Server (192.168.1.5:7018)
23:15:49.343 StratInOut::eek:nConnected [CM104005] Call(5): Setup completed for call from Ext.102 to Ln:10000@Patton SmartNode 4112
23:15:49.343 CallLegImpl::eek:nConnected [CM103001] Call(5): Created audio channel for Ext.102 (192.168.1.2:5004) with Media Server (192.168.1.5:7016)
23:15:45.125 CallConf::eek:nIncoming [CM103002] Call(5): Incoming call from 102 (Ext.102) to sip:[email protected]:5060
22:55:35.671 StratInOut::eek:nHangUp [CM104007] Call(4): Call from Ln:10000@Patton SmartNode 4112 to 999 has been terminated by Ln:10000@Patton SmartNode 4112; cause: BYE; from IP:192.168.1.101
22:54:43.703 CallConf::eek:nProvisional [CM103003] Call(4): Ext.101 is ringing
22:54:38.140 MediaServerReporting::DTMFhandler [MS211000] Call(4) Ln:10000@Patton SmartNode 4112: DTMF (RTP) from 192.168.1.101:4866 arrived. in-band DTMF tone detection is turned off.
22:54:27.234 CallLegImpl::eek:nConnected [CM103001] Call(4): Created audio channel for Ln:10000@Patton SmartNode 4112 (192.168.1.101:4866) with Media Server (192.168.1.5:7012)
22:54:27.187 CallConf::eek:nIncoming [CM103002] Call(4): Incoming call from 10000 (Ln:10000@Patton SmartNode 4112) to sip:[email protected]
22:52:29.015 StratInOut::eek:nHangUp [CM104007] Call(3): Call from Ln:10000@Patton SmartNode 4112 to 999 has been terminated by Ln:10000@Patton SmartNode 4112; cause: BYE; from IP:192.168.1.101
22:51:51.968 CallConf::eek:nProvisional [CM103003] Call(3): Ext.102 is ringing
22:51:46.515 MediaServerReporting::DTMFhandler [MS211000] Call(3) Ln:10000@Patton SmartNode 4112: DTMF (RTP) from 192.168.1.101:4864 arrived. in-band DTMF tone detection is turned off.
22:51:36.125 CallLegImpl::eek:nConnected [CM103001] Call(3): Created audio channel for Ln:10000@Patton SmartNode 4112 (192.168.1.101:4864) with Media Server (192.168.1.5:7008)
22:51:36.078 CallConf::eek:nIncoming [CM103002] Call(3): Incoming call from 10000 (Ln:10000@Patton SmartNode 4112) to sip:[email protected]
22:46:52.906 StratInOut::eek:nHangUp [CM104007] Call(2): Call from Ln:10000@Patton SmartNode 4112 to 102 has been terminated by Ln:10000@Patton SmartNode 4112; cause: BYE; from IP:192.168.1.101
22:46:47.640 CallConf::eek:nProvisional [CM103003] Call(2): Ext.102 is ringing
22:46:42.187 MediaServerReporting::DTMFhandler [MS211000] Call(2) Ln:10000@Patton SmartNode 4112: DTMF (RTP) from 192.168.1.101:4864 arrived. in-band DTMF tone detection is turned off.
22:46:31.968 CallLegImpl::eek:nConnected [CM103001] Call(2): Created audio channel for Ln:10000@Patton SmartNode 4112 (192.168.1.101:4864) with Media Server (192.168.1.5:7004)
22:46:31.937 CallConf::eek:nIncoming [CM103002] Call(2): Incoming call from 10000 (Ln:10000@Patton SmartNode 4112) to sip:[email protected]
22:38:05.203 StratInOut::eek:nHangUp [CM104007] Call(1): Call from Ln:10000@Patton SmartNode 4112 to 102 has been terminated by Ln:10000@Patton SmartNode 4112; cause: BYE; from IP:192.168.1.101
22:37:49.062 CallConf::eek:nProvisional [CM103003] Call(1): Ext.102 is ringing
22:37:43.453 MediaServerReporting::DTMFhandler [MS211000] Call(1) Ln:10000@Patton SmartNode 4112: DTMF (RTP) from 192.168.1.101:4866 arrived. in-band DTMF tone detection is turned off.
22:37:31.937 CallLegImpl::eek:nConnected [CM103001] Call(1): Created audio channel for Ln:10000@Patton SmartNode 4112 (192.168.1.101:4866) with Media Server (192.168.1.5:7000)
22:37:31.421 CallConf::eek:nIncoming [CM103002] Call(1): Incoming call from 10000 (Ln:10000@Patton SmartNode 4112) to sip:[email protected]
21:56:04.812 ListenConnect [CM114000] SL: connected RJ-PC:0/PHPExtension_0 at [RJ-PC:0]/PHPExtension_0
21:56:03.265 ClientRegs::eek:nSuccess [CM113005] Registration of sip:[email protected] is successful
21:56:02.765 ExtLine::Register [CM110004] Send registration for "Adhesive Solutions LLC"<sip:[email protected]>
21:56:02.765 ExtLine::Register [CM110001] Use External IP for device line registration DN='10005' device='BroadVoice VOIP'
21:56:02.453 StunClient::process [CM115002] STUN resolved external IP=72.86.125.231:49152 by server 64.69.76.23
21:56:02.390 StunClient::process [CM115001] Send initial STUN request to 64.69.76.23
21:56:02.281 CallMgr::Stack::thread [CM106001] ** Enter Stack Loop **
21:55:57.890 IVRConnected [CM111000] IVR Server is connected
21:55:57.890 ListenConnect [CM114000] SL: connected RJ-PC:5483/IVRServer at [RJ-PC:5483]/IVRServer
21:55:57.015 ListenConnect [CM114000] SL: connected RJ-PC:0/VoiceBoxManagerService at [RJ-PC:0]/VoiceBoxManagerService
21:55:54.187 CallMgr::DumThread::thread [CM100004] ** Enter DUM Thread **
21:55:54.000 DBA [CM109000] ** Database connection Ok **
21:55:53.906 CallMgr::Stack::Initialize [CM106000] ** Adding transports **
21:55:53.906 MediaServerConnected [CM112000] Media Server is connected
21:55:53.906 CallMgr::Initialize [CM100003] ** Initializing SIP stack **
21:55:53.906 ListenConnect [CM114000] SL: connected RJ-PC:0/MediaServer at [RJ-PC:0]/MediaServer
21:55:53.906 CallMgr::Initialize [CM100002] Default Local IP address: 192.168.1.5:5060
21:55:53.406 CallMgr::Initialize [CM100001] Version: 3.1.2434.0
21:55:53.406 CallMgr::Initialize [CM100000] Start 3CX PhoneSystem Call Manager
21:55:53.406 LoadLicenceInfo [CM100008] Licence loading error
 
Have you tried a longer ring? Might need more time to pick up the info before passing it along to 3CX.
 
check the field settings in other options of your gateway. I don't have a patton gateway, but i know i had to fiddle for ages to get the caller-id working.

I also had to make sure that it was definitely being passed down our isdn 30 (E1) (which it wasn't!)....but that's a bit OT really seeing as you have had Caller-ID in the past.
 
Thanks to all for your help, greatly appreciated!

I actually did try increasing the ring number to 3, however still no caller ID. After messing around with the settings for this Patton gateway for several hours, installing the latest firmware, etc., I have decided to send it back and try another brand.........so the search remains. Suppose I will try the Audiocodes MP-114 next, hopefully this will give us sound quality AND caller ID. :wink:
 
Hi Stuck,

Patton should be the prefect match with 3CX. Actually, it should be not easy to config. But mark my words – Patton are rock solid devices. Once you set it up, you will forget it and never have to touch it again.

Do you report your issue to Patton's support team and work with them to investigate your issue? What caller id type at your region? The caller id works at your previous grandstream gateway or not? Just to confirm again your PSTN send the called party number to your gateway.

Is it possible to post your Patton config file to here for us to investigate?
 
Hello Ricky, thank you for your reply!

For the time being I just re-connected the Grandstream gxw-4104 gateway until we can decide what direction we want to go.

You will see from our 3CX logs that the caller ID is coming thru as Incoming call from 10000 (Ln:10000@Patton SmartNode 4112).

We are in the US and I set the caller id type to Bell.

The caller ID did always display fine with with the Grandstream gateway!

I may give the Patton gateway another try over the weekend when our phone lines aren't busy. So perhaps i can then post the Patton gateway configs for you to examine.

Thanks Again!
 
Stick with the Patton. I can tell you for sure not to go with the Audiocodes. I setup 4 of them for custoemrs and could never get the echo out of the conversation! I worked with 3CX support and Audiocodes (through my distributor) for several months and nothing would fix it. I installed a Patton for one of my customers that is still on 3CX and it was great. He does not have Caller ID so I was not able to find out that part of the puzzle. I just installed mine (Smartnode 4114) today and I have the same issue with Caller ID. I am sure it is something that can be fixed. I might try the older firmware and repost since the only thing that seems to be buggy with the older firmware (Patton 4.x) according to the website (3CX) is faxing and I have dedicated fax. I will try it and repost.
 
Hey Stuck I just put my gateway back to 4.2 and recreated the configuration in the PBX and generated a new file using the Patton 4.x template and my Caller ID is now working. I think they have some issues with the v5.x firmware that will be addressed in the next build. Give it a try and post your results. I know you will be much happier with the Patton than with the Audiocodes.

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