3CX wrong identification with Panasonic KX-TEM824 ???

[pr0t31n_w13]

Heloo...

Sorry for bad english, and hope there is someone there can help me..

I'm using 3CX Phone System Version5.0.3790.0; and LinkSys SPA 2102... work fine with x-lite softphone and direct phone (single line)

then i connect SPA2102 with Panasonic PBX KX-TEM824

when i call FROM direct phone (attach at SPA2102) or xlite TO PBX KX-TEM824.. everything is OK..

BUT when i call FROM PBX KX-TEM824 TO X-lite softphone ID or direct phone (LINKSYS SPA2102) .. 3CX Ph System identify wrong ID..

example

x-lite phone id is 100@serverip
SPA2102 directphone ID is 200@serverip
SPA2102 -PBX KX-TEM824 ID- is 300@serverip

when from 300@serverip call to 200@serverip ; 3cx phone system identify destination is 2000@serverip where that id is not found, so call can not establish.
when from 300@serverip call to 100@serverip ; 3cx phone system identify destination is 1000@serverip where that id is not found, so call can not establish.

sometimes wrong identify destination is 1@serverip, or 20000@serverip where all ID is not register, so call can establish.

but when i make call from xlite or directphone to PBX, everything is fine....

how to solve that problem??


thanks a lot everyone...

660 2008-06-19 09:58:25 900 2222 No Answer <--- wrong identify ID (the correct ID is 222)
671 2008-06-19 11:22:58 600 8 No Answer <--- wrong identify ID (the correct ID is 800)
672 2008-06-19 11:26:13 101 600 No Answer
673 2008-06-19 11:26:21 101 700 Answered 00:00:13
674 2008-06-19 11:26:39 101 700 Answered 00:00:16
675 2008-06-19 11:26:59 101 600 Answered 00:00:13
676 2008-06-19 11:27:56 800 1 No Answer <------ worng (the correct ID is 100)
677 2008-06-19 11:28:13 800 222 Answered 00:00:38
678 2008-06-19 11:32:53 800 222 Answered 00:01:20
679 2008-06-19 11:36:57 222 900 Answered 00:00:53
680 2008-06-19 11:37:27 600 8 No Answer <---- wrong (the correct ID is 800)

 

[pr0t31n_w13]

09:02:30.062 Call::Terminate :[CM503008]: Call(3): Call is terminated
09:02:30.046 Call::RouteFailed :[CM503014]: Call(3): Attempt to reach [sip:[email protected]] failed. Reason: Not Found
09:02:30.046 CallCtrl:nSelectRouteReq :[CM503013]: Call(3): No known route to target: [sip:[email protected]]
09:02:30.015 CallCtrl:nIncomingCall :[CM503001]: Call(3): Incoming call from Ext.222 to [sip:[email protected]]


failed. Reason: Not Found.
wrong identification.. it haved to be [email protected] ; why 3CX identify as [email protected] ???

or this problem occur because Panasonic PBX TEM824 ???

can anyone help ?


thanks a lot!

 

[archie]

In this case PBX doesn't "identify" anything. It just prints what it get in SIP message.

 

[pr0t31n_w13]

thanks for reply archie...

so is this bug from 3CX or LinkSys SPA2102 ???

yesterday i search update firmware of LinkSys and found the new one, so i update all my linksys spa2102.

problem still occur..

anyway... Thanks a lot

and still waiting for help...

07:46:35.406 Call::Terminate :[CM503008]: Call(8): Call is terminated
07:46:35.390 Call::RouteFailed :[CM503014]: Call(8): Attempt to reach [sip:[email protected]] failed. Reason: Not Found
07:46:35.390 CallCtrl:nSelectRouteReq :[CM503013]: Call(8): No known route to target: [sip:[email protected]] <--- wrong identify
07:46:35.359 CallCtrl:nIncomingCall :[CM503001]: Call(8): Incoming call from Ext.333 to [sip:[email protected]] <--- wrong identify

(the right sip is [email protected])

07:40:53.296 Call::Terminate :[CM503008]: Call(3): Call is terminated
07:40:49.046 CallCtrl:nSelectRouteReq :[CM503004]: Call(3): Calling: Ext:222@[Dev:sip:[email protected]:5060] <----- correct identify
07:40:48.968 CallCtrl:nIncomingCall :[CM503001]: Call(3): Incoming call from Ext.333 to [sip:[email protected]] <----- correct identify
07:40:19.703 Call::Terminate :[CM503008]: Call(2): Call is terminated
07:40:19.687 Call::RouteFailed :[CM503014]: Call(2): Attempt to reach [sip:[email protected]] failed. Reason: Not Found
07:40:19.687 CallCtrl:nSelectRouteReq :[CM503013]: Call(2): No known route to target: [sip:[email protected]] <--- wrong identify
07:40:19.640 CallCtrl:nIncomingCall :[CM503001]: Call(2): Incoming call from Ext.333 to [sip:[email protected]] <--- wrong identify

 

[archie]

so is this bug from 3CX or LinkSys SPA2102 ???

Wasn't it clear enough from my comment?

As I see it - the problem is in DTMF detection between ATA and analogue phone. It seems it doubles digits sometimes. Try to adjust timings in your ATA settings.

 

[pr0t31n_w13]

so is this bug from 3CX or LinkSys SPA2102 ???

Wasn't it clear enough from my comment?

As I see it - the problem is in DTMF detection between ATA and analogue phone. It seems it doubles digits sometimes. Try to adjust timings in your ATA settings.

sorry... i try to understand you my english is not good enough, and this area (VOIP and PBX) are new for me.

anyway.. Problem Solved!!

Change DTMF Playback Level from -16 to 0 ; and DTMF Playback Length from 0.1 to 0.5 ( found solution at another forum that i found at google)

Thank to you Archie so i can focus at DTMF.. honestly i don't understand at all about VOIP. newbiee