unable to receive incoming call on 3CX system

[siu612]

We are trying to connect our IDAP trunk to our newly setup 3CX system. I can make outgoing call but when I try to dial in from external, my external phone got disconnected before my extension started to ring. I captured the log below from server showing device not identified so on and the incoming call was terminated. Is there some one able to explain that and advice how to fix it?

Log:

16:01:40.287 [CM503008]: Call(46): Call is terminated
16:01:40.177 [CM503007]: Call(46): Device joined: sip:[email protected]:5060
16:01:40.162 [CM503007]: Call(46): Device joined: sip:[email protected]:5060
16:01:33.737 [CM505001]: Ext.6688: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, no-replaces, able-no-sdp, recvonly] UserAgent: [Linksys/SPA962-6.1.5(a)] PBX contact: [sip:[email protected]:5060]
16:01:33.737 [CM503002]: Call(46): Alerting sip:[email protected]:5060
16:01:33.644 [CM503025]: Call(46): Calling Ext:Ext.6688@[Dev:sip:[email protected]:5060]
16:01:33.612 [CM503004]: Call(46): Route 1: Ext:Ext.6688@[Dev:sip:[email protected]:5060]
16:01:33.612 [CM503010]: Making route(s) to <sip:[email protected]:5060>
16:01:33.597 [CM503001]: Call(46): Incoming call from 61514567@(Ln.10001@Patton4960) to <sip:[email protected]:5060>
16:01:33.581 [CM503012]: Inbound office hours rule (Sara) for 10001 forwards to DN:6688

 

[leejor]

Are you able to make calls to Ext 6688 internally? Extension to extension?

 

[SY]

We are trying to connect our IDAP trunk to our newly setup 3CX system. I can make outgoing call but when I try to dial in from external, my external phone got disconnected before my extension started to ring. I captured the log below from server showing device not identified so on and the incoming call was terminated. Is there some one able to explain that and advice how to fix it?

Log:

16:01:40.287 [CM503008]: Call(46): Call is terminated
16:01:40.177 [CM503007]: Call(46): Device joined: sip:[email protected]:5060
16:01:40.162 [CM503007]: Call(46): Device joined: sip:[email protected]:5060
16:01:33.737 [CM505001]: Ext.6688: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, no-replaces, able-no-sdp, recvonly] UserAgent: [Linksys/SPA962-6.1.5(a)] PBX contact: [sip:[email protected]:5060]
16:01:33.737 [CM503002]: Call(46): Alerting sip:[email protected]:5060
16:01:33.644 [CM503025]: Call(46): Calling Ext:Ext.6688@[Dev:sip:[email protected]:5060]
16:01:33.612 [CM503004]: Call(46): Route 1: Ext:Ext.6688@[Dev:sip:[email protected]:5060]
16:01:33.612 [CM503010]: Making route(s) to <sip:[email protected]:5060>
16:01:33.597 [CM503001]: Call(46): Incoming call from 61514567@(Ln.10001@Patton4960) to <sip:[email protected]:5060>
16:01:33.581 [CM503012]: Inbound office hours rule (Sara) for 10001 forwards to DN:6688

"Device info: Device Not Identified: User Agent not matched" means that the PBX has no any additional information about this device. Nothing more.
It is not the reason to terminate call.

 

[leejor]

The call has moved to the point where it has "joined" the trunk and line, which is normal to that point. A "verbose" 3Cx log may show that a message has been returned from the set that 3CX doesn't like and the reason for the termination. That was why I asked if normal, internal calls completed to the extension successfully.