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

Caller id not showing ** PATTON MISCONFIGURATION

Status
Not open for further replies.

alanlumley

Joined
Jul 15, 2010
Messages
1
Reaction score
0
Everytime we have incoming calls on our phones it always appears as Anonymous, therefore we never know who is calling us until we answer our phones. I have a log file here, can anyone shed any light on it?

13:38:37.274 [CM503003]: Call(3): Call to sip:[email protected]:5060 has failed; Cause: 487 Request Terminated; from IP:192.168.254.60:58821
13:38:37.258 [CM503003]: Call(3): Call to sip:[email protected] has failed; Cause: 487 Request Terminated; from IP:192.168.254.7:2049
13:38:37.227 [CM503003]: Call(3): Call to sip:[email protected] has failed; Cause: 487 Request Terminated; from IP:192.168.254.6:1026
13:38:37.086 [CM503008]: Call(3): Call is terminated
13:38:29.162 [CM505001]: Ext.201: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CXPhone 4.0.10858.0] PBX contact: [sip:[email protected]:5060]
13:38:29.162 [CM503002]: Call(3): Alerting sip:[email protected]:58821;rinstance=634fbf3dd277f55d
13:38:29.068 [CM505001]: Ext.102: Device info: Device Identified: [Man: Snom;Mod: 3xx series;Rev: General] Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [snom360/7.3.30] PBX contact: [sip:[email protected]:5060]
13:38:29.068 [CM503002]: Call(3): Alerting sip:[email protected]:2049;line=unm649xw
13:38:29.052 [CM505001]: Ext.101: Device info: Device Identified: [Man: Snom;Mod: 3xx series;Rev: General] Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [snom370/7.3.27] PBX contact: [sip:[email protected]:5060]
13:38:29.052 [CM503002]: Call(3): Alerting sip:[email protected]:1026;line=prtekcth
13:38:29.021 [CM503025]: Call(3): Calling RingAll800:102Ext.102101Ext.101201Ext.201@[Dev:sip:[email protected]:58821;rinstance=634fbf3dd277f55d]
13:38:28.990 [CM503025]: Call(3): Calling RingAll800:102Ext.102101Ext.101201Ext.201@[Dev:sip:[email protected]:1026;line=prtekcth]
13:38:28.974 [CM503025]: Call(3): Calling RingAll800:102Ext.102101Ext.101201Ext.201@[Dev:sip:[email protected]:2049;line=unm649xw]
13:38:28.928 [CM503004]: Call(3): Route 1: RingAll800:102Ext.102101Ext.101201Ext.201@[Dev:sip:[email protected]:2049;line=unm649xw,Dev:sip:[email protected]:1026;line=prtekcth,Dev:sip:[email protected]:58821;rinstance=634fbf3dd277f55d]
13:38:28.912 [CM503010]: Making route(s) to <sip:[email protected]:5060>
13:38:28.912 [CM505002]: Gateway:[Patton Smartnode] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Patton SN4112 JO EUI 00A0BA046AB9 R5.3 2009-01-15 H323 SIP FXS FXO M5T SIP Stack/4.0.28.28] PBX contact: [sip:[email protected]:5060]
13:38:28.912 [CM503001]: Call(3): Incoming call from anonymous@(Ln.10000@Patton Smartnode) to <sip:[email protected]:5060>
13:38:28.787 [CM503012]: Inbound out-of-office hours rule (ALL) for 10000 forwards to DN:800
 
Re: Caller id not showing

Probably something on the patton itself - not detecting (And thus sending) the CID.

Post your patton config - put your pbx in verbose mode and post another call log - and please put the logs in code /code tags for easy readability.
 
Re: Caller id not showing

salter said:
Probably something on the patton itself - not detecting (And thus sending) the CID.

Perhaps set to pass the incoming call on to 3CX before receiving the CID burst (between first ring and second ring)?
 
Re: Caller id not showing

Anonymous -> something between patton + telco.
We have no reason to get the cid and put it as anonymous. We just send what we get. I would post the running config and open a support ticket on patton.
They will send you on how to make traces and debugging information. You can use the debug command.

I suspect you have analog right - you can proceed in your ticket much faster by sending them the following.
First confirm that CID can be passed through analog without patton. That rules out telco.
THen put these commands in a patton telnet session (depending on firmware - play around a bit but you will save time because they are still going to ask you for this)
debug ccfxo
debug call-control detail 5
debug fxo

Start wireshark
Replicate the problem.
Stop wireshark
Save telnet session output
take running-config from device

Fire up to patton.
 
Status
Not open for further replies.

Getting Started - Admin

Latest Posts

Forum statistics

Threads
141,629
Messages
748,936
Members
144,742
Latest member
Steffen Ekerdt
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.