Dismiss Notice
We would like to remind you that we’re updating our login process for all 3CX forums whereby you will be able to login with the same credentials you use for the Partner or Customer Portal. Click here to read more.

3cx Inbound Duplication problme

Discussion in '3CX Phone System - General' started by hoosier1077, Mar 5, 2011.

Thread Status:
Not open for further replies.
  1. hoosier1077

    Joined:
    Mar 5, 2011
    Messages:
    52
    Likes Received:
    0
    Hello,
    I have really tried to research my problem, but just cant seem to find the solution. So I figured I would try the experts... I have my 3cx server all setup on my local network. I have a static public ip address from my isp and have configured my firewall as instructed for the 3cx pbx to work with inphonex voip provider. I am able to call out and recieve, however I am still testing the sytem out to see if it will work for out company. So... I am calling in to the pbx from my cell phone, most of the time it comes trough just fine, however sometimes the call comes in duplicated. So its as if 2 calls come in from my cell phone at the same time to the same number. Here is the log from 3cx....

    10:32:46.314 [CM503003]: Call(3): Call to sip:100@66.158.163.130:5060 has failed; Cause: 487 Request Terminated; from IP:76.214.127.46:53619
    10:32:46.299 [CM503003]: Call(2): Call to sip:100@66.158.163.130:5060 has failed; Cause: 487 Request Terminated; from IP:76.214.127.46:53619
    10:32:46.221 [CM503003]: Call(1): Call to sip:100@66.158.163.130:5060 has failed; Cause: 487 Request Terminated; from IP:76.214.127.46:53619
    10:32:46.127 [CM503008]: Call(3): Call is terminated
    10:32:46.111 [CM503008]: Call(2): Call is terminated
    10:32:46.096 [CM503008]: Call(1): Call is terminated
    10:32:35.674 [CM505001]: Ext.100: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CXPhone 5.0.14900.0] PBX contact: [sip:100@10.22.95.132:5060]
    10:32:35.674 [CM503002]: Call(1): Alerting sip:100@76.214.127.46:53619;rinstance=16b7f193036520fd
    10:32:35.580 [CM505001]: Ext.100: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CXPhone 5.0.14900.0] PBX contact: [sip:100@10.22.95.132:5060]
    10:32:35.580 [CM503002]: Call(3): Alerting sip:100@76.214.127.46:53619;rinstance=16b7f193036520fd
    10:32:35.455 [CM505001]: Ext.100: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CXPhone 5.0.14900.0] PBX contact: [sip:100@10.22.95.132:5060]
    10:32:35.455 [CM503002]: Call(2): Alerting sip:100@76.214.127.46:53619;rinstance=16b7f193036520fd
    10:32:35.377 [CM503025]: Call(1): Calling Ext:Ext.100@[Dev:sip:100@76.214.127.46:53619;rinstance=16b7f193036520fd]
    10:32:35.362 [CM503025]: Call(3): Calling Ext:Ext.100@[Dev:sip:100@76.214.127.46:53619;rinstance=16b7f193036520fd]
    10:32:35.362 [CM503025]: Call(2): Calling Ext:Ext.100@[Dev:sip:100@76.214.127.46:53619;rinstance=16b7f193036520fd]
    10:32:35.330 [CM503004]: Call(3): Route 1: Ext:Ext.100@[Dev:sip:100@76.214.127.46:53619;rinstance=16b7f193036520fd]
    10:32:35.330 [CM503010]: Making route(s) to <sip:100@10.22.95.132:5060>
    10:32:35.330 [CM503004]: Call(2): Route 1: Ext:Ext.100@[Dev:sip:100@76.214.127.46:53619;rinstance=16b7f193036520fd]
    10:32:35.330 [CM503010]: Making route(s) to <sip:100@10.22.95.132:5060>
    10:32:35.330 [CM503004]: Call(1): Route 1: Ext:Ext.100@[Dev:sip:100@76.214.127.46:53619;rinstance=16b7f193036520fd]
    10:32:35.330 [CM503010]: Making route(s) to <sip:100@10.22.95.132:5060>
    10:32:35.315 [CM505003]: Provider:[Main Inphonex] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [] PBX contact: [sip:5947913@10.22.95.132:5060]
    10:32:35.315 [CM503001]: Call(3): Incoming call from 13177100787@(Ln.10000@Main Inphonex) to <sip:100@10.22.95.132:5060>
    10:32:35.315 [CM503012]: Inbound out-of-office hours rule (unnamed) for 10000 forwards to DN:100
    10:32:35.299 [CM505003]: Provider:[Main Inphonex] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [] PBX contact: [sip:5947913@10.22.95.132:5060]
    10:32:35.299 [CM503001]: Call(2): Incoming call from 13177100787@(Ln.10000@Main Inphonex) to <sip:100@10.22.95.132:5060>
    10:32:35.299 [CM503012]: Inbound out-of-office hours rule (unnamed) for 10000 forwards to DN:100
    10:32:35.284 [CM505003]: Provider:[Main Inphonex] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [] PBX contact: [sip:5947913@10.22.95.132:5060]
    10:32:35.268 [CM503001]: Call(1): Incoming call from 13177100787@(Ln.10000@Main Inphonex) to <sip:100@10.22.95.132:5060>
    10:32:35.174 [CM503012]: Inbound out-of-office hours rule (unnamed) for 10000 forwards to DN:100
    10:32:30.424 [CM504001]: Ext.100: new contact is registered. Contact(s): [sip:100@76.214.127.46:53619;rinstance=16b7f193036520fd/100]
    10:32:01.144 [CM504001]: Ext.IVRForward: new contact is registered. Contact(s): [sip:IVRForward@127.0.0.1:40600;rinstance=6ac791a8449a59fd/IVRForward]
    10:32:01.129 [CM504001]: Ext.EndCall: new contact is registered. Contact(s): [sip:EndCall@127.0.0.1:40600;rinstance=65d9066b3c4f88da/EndCall]
    10:32:01.113 [CM504001]: Ext.800: new contact is registered. Contact(s): [sip:800@127.0.0.1:40600;rinstance=d3853e66e2b5ccee/800]
    10:32:00.988 [CM504001]: Ext.999: new contact is registered. Contact(s): [sip:999@127.0.0.1:40600;rinstance=dfb8c1b48fc48a1a/999]
    10:31:59.129 [CM504001]: Ext.*1: new contact is registered. Contact(s): [sip:*1@127.0.0.1:40000;rinstance=7c029457e93f999b/*1]
    10:31:59.129 [CM504001]: Ext.*0: new contact is registered. Contact(s): [sip:*0@127.0.0.1:40000;rinstance=cf948344a677641f/*0]
    10:31:59.019 [CM504001]: Ext.*777: new contact is registered. Contact(s): [sip:*777@127.0.0.1:40000;rinstance=bdb485cf0f9e87df/*777]
    10:31:57.176 [CM504004]: Registration succeeded for: 10000@Main Inphonex
    10:31:56.910 [CM504003]: Sent registration request for 10000@Main Inphonex

    As you can see sometimes the call even comes in 3 times in duplication. I have setup the inphonex provider and it registers just fine, I have my external number set as my DID that i got from them, and that all seems to be working fine as well. Its just these duplication problems that I cant figure out. It wouldnt be a huge deal, however since im testing the sytem out I only have the 2 sim. call, so if my call comes in duplication I get that "License limit reached" error. I really appreciate any help you can provide. Thanks.
     
  2. abc123

    abc123 Active Member

    Joined:
    Nov 9, 2009
    Messages:
    712
    Likes Received:
    1
    We would need to see the invite from inphonex to really tell you the problem.

    You can switch to verbose logging and restart the services and then try.

    The reason being is that 3cx is seeing multiple invites from inphonex. Without seeing the full request we cannot see why, but i suspect they are sending the request multiple times and changing the call id so 3cx sees it as a new request (Correctly) rather than a retransmission of the original invite.

    Can you post the logs in verbose mode with the 2 (or 3) invites?:
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. hoosier1077

    Joined:
    Mar 5, 2011
    Messages:
    52
    Likes Received:
    0
    Hey thanks for getting back to me... Hope this sheds some light, let me know if you need anymore from logs.

    13:04:17.262 Currently active calls - 2: [2,3]
    13:04:09.388 [CM503008]: Call(1): Call is terminated
    13:03:56.810 Session 23 of leg C:1.1 is confirmed
    13:03:56.654 [CM503007]: Call(3): Device joined: sip:999@127.0.0.1:40600;rinstance=87e16d0059158c09
    13:03:56.638 [CM503007]: Call(3): Device joined: sip:5947913@sip.inphonex.com:5060
    13:03:56.638 [MS210003] C:3.1:Answer provided. Connection(transcoding mode[unsecure]):10.22.95.132:7004(7005)
    13:03:56.638 [MS210001] C:3.2:Answer received. RTP connection[unsecure]: 127.0.0.1:40614(40615)
    13:03:56.638 Remote SDP is set for legC:3.2
    13:03:56.622 [CM505001]: Ext.999: Device info: Device Identified: [Man: 3CX Ltd.;Mod: Voice Mail Menu;Rev: General] Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CX Voice Mail Menu] PBX contact: [sip:999@127.0.0.1:5060]
    13:03:56.622 [CM503002]: Call(3): Alerting sip:999@127.0.0.1:40600;rinstance=87e16d0059158c09
    13:03:56.622 [CM503007]: Call(2): Device joined: sip:999@127.0.0.1:40600;rinstance=87e16d0059158c09
    13:03:56.607 [CM503007]: Call(2): Device joined: sip:5947913@sip.inphonex.com:5060
    13:03:56.607 [MS210003] C:2.1:Answer provided. Connection(transcoding mode[unsecure]):10.22.95.132:7002(7003)
    13:03:56.607 [MS210001] C:2.2:Answer received. RTP connection[unsecure]: 127.0.0.1:40612(40613)
    13:03:56.607 Remote SDP is set for legC:2.2
    13:03:56.591 [CM505001]: Ext.999: Device info: Device Identified: [Man: 3CX Ltd.;Mod: Voice Mail Menu;Rev: General] Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CX Voice Mail Menu] PBX contact: [sip:999@127.0.0.1:5060]
    13:03:56.591 [CM503002]: Call(2): Alerting sip:999@127.0.0.1:40600;rinstance=87e16d0059158c09
    13:03:56.576 [CM503007]: Call(1): Device joined: sip:999@127.0.0.1:40600;rinstance=87e16d0059158c09
    13:03:56.576 [CM503007]: Call(1): Device joined: sip:5947913@sip.inphonex.com:5060
    13:03:56.576 [MS210003] C:1.1:Answer provided. Connection(transcoding mode[unsecure]):10.22.95.132:7000(7001)
    13:03:56.576 [MS210001] C:1.2:Answer received. RTP connection[unsecure]: 127.0.0.1:40610(40611)
    13:03:56.576 Remote SDP is set for legC:1.2
    13:03:56.560 [CM505001]: Ext.999: Device info: Device Identified: [Man: 3CX Ltd.;Mod: Voice Mail Menu;Rev: General] Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CX Voice Mail Menu] PBX contact: [sip:999@127.0.0.1:5060]
    13:03:56.560 [CM503002]: Call(1): Alerting sip:999@127.0.0.1:40600;rinstance=87e16d0059158c09
    13:03:56.357 [CM503025]: Call(3): Calling Ext:Ext.999@[Dev:sip:999@127.0.0.1:40600;rinstance=87e16d0059158c09]
    13:03:56.357 [MS210002] C:3.2:Offer provided. Connection(transcoding mode): 127.0.0.1:7010(7011)
    13:03:56.341 [CM503025]: Call(2): Calling Ext:Ext.999@[Dev:sip:999@127.0.0.1:40600;rinstance=87e16d0059158c09]
    13:03:56.341 [MS210002] C:2.2:Offer provided. Connection(transcoding mode): 127.0.0.1:7008(7009)
    13:03:56.341 [CM503025]: Call(1): Calling Ext:Ext.999@[Dev:sip:999@127.0.0.1:40600;rinstance=87e16d0059158c09]
    13:03:56.341 [MS210002] C:1.2:Offer provided. Connection(transcoding mode): 127.0.0.1:7006(7007)
    13:03:56.294 [CM503005]: Call(3): Forwarding: Ext:Ext.999@[Dev:sip:999@127.0.0.1:40600;rinstance=87e16d0059158c09]
    13:03:56.279 [CM503005]: Call(2): Forwarding: Ext:Ext.999@[Dev:sip:999@127.0.0.1:40600;rinstance=87e16d0059158c09]
    13:03:56.279 [CM503005]: Call(1): Forwarding: Ext:Ext.999@[Dev:sip:999@127.0.0.1:40600;rinstance=87e16d0059158c09]
    13:03:56.279 [CM503016]: Call(3): Attempt to reach <sip:100@10.22.95.132:5060> failed. Reason: Not Registered
    13:03:56.279 [CM503017]: Call(3): Target is not registered: Ext:Ext.100
    13:03:56.279 [CM503010]: Making route(s) to <sip:100@10.22.95.132:5060>
    13:03:56.279 [CM503016]: Call(2): Attempt to reach <sip:100@10.22.95.132:5060> failed. Reason: Not Registered
    13:03:56.279 [CM503017]: Call(2): Target is not registered: Ext:Ext.100
    13:03:56.263 [CM503010]: Making route(s) to <sip:100@10.22.95.132:5060>
    13:03:56.263 [CM503016]: Call(1): Attempt to reach <sip:100@10.22.95.132:5060> failed. Reason: Not Registered
    13:03:56.263 [CM503017]: Call(1): Target is not registered: Ext:Ext.100
    13:03:56.263 [CM503010]: Making route(s) to <sip:100@10.22.95.132:5060>
    13:03:56.263 [MS210000] C:3.1:Offer received. RTP connection: 208.239.76.177:12490(12491)
    13:03:56.247 Remote SDP is set for legC:3.1
    13:03:56.247 [CM505003]: Provider:[Main Inphonex] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [] PBX contact: [sip:5947913@10.22.95.132:5060]
    13:03:56.247 [CM503001]: Call(3): Incoming call from 13177100787@(Ln.10000@Main Inphonex) to <sip:100@10.22.95.132:5060>
    13:03:56.232 [CM503012]: Inbound out-of-office hours rule (unnamed) for 10000 forwards to DN:100
    13:03:56.232 Looking for inbound target: called=5947913-0kdb518f8i0q2; caller=13177100787
    13:03:56.232 [MS210000] C:2.1:Offer received. RTP connection: 208.239.76.177:37376(37377)
    13:03:56.216 Remote SDP is set for legC:2.1
    13:03:56.216 [CM505003]: Provider:[Main Inphonex] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [] PBX contact: [sip:5947913@10.22.95.132:5060]
    13:03:56.216 [CM503001]: Call(2): Incoming call from 13177100787@(Ln.10000@Main Inphonex) to <sip:100@10.22.95.132:5060>
    13:03:56.216 [CM503012]: Inbound out-of-office hours rule (unnamed) for 10000 forwards to DN:100
    13:03:56.216 Looking for inbound target: called=5947913-0kdb518f8i0q2; caller=13177100787
    13:03:56.169 [MS210000] C:1.1:Offer received. RTP connection: 208.239.76.177:54808(54809)
    13:03:56.169 Remote SDP is set for legC:1.1
    13:03:56.169 [CM505003]: Provider:[Main Inphonex] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [] PBX contact: [sip:5947913@10.22.95.132:5060]
    13:03:56.154 [CM503001]: Call(1): Incoming call from 13177100787@(Ln.10000@Main Inphonex) to <sip:100@10.22.95.132:5060>
    13:03:56.029 [CM500002]: Info on incoming INVITE:
    INVITE sip:5947913@10.22.95.132:5060;rinstance=7876247691f41940 SIP/2.0
    Via: SIP/2.0/UDP 208.239.76.177:5060;branch=z9hG4bKievcpephnv81jrjih7rfisopk1
    Max-Forwards: 69
    Contact: <sip:208.239.76.177:5060;transport=udp;wlsscid=1ae4691c270666;appsessionid=app-6dkon9n0iato>
    To: <sip:5947913-0kdb518f8i0q2@10.0.5.77:5060;rinstance=7876247691f41940;transport=udp;useradd=66.158.163.130;userport=48647>
    From: "WIRELESS CALLER"<sip:13177100787@208.239.76.177>;tag=SD3bpj301-a2d4329f
    Call-ID: SD3bpj301-ddc9dfc45d54235777c8be3011988a1b-gurpko2
    CSeq: 1 INVITE
    Min-SE: 90
    Supported: timer
    Content-Length: 0
    X-UUID: c70dac33fb484829a410c7de8013ae99
    X-DID: 3172883905

    13:03:56.029 [CM500002]: Info on incoming INVITE:
    INVITE sip:5947913@10.22.95.132:5060;rinstance=7876247691f41940 SIP/2.0
    Via: SIP/2.0/UDP 208.239.76.177:5060;branch=z9hG4bK8llmmf97ffe8jk4o0prruajkv2
    Max-Forwards: 69
    Contact: <sip:208.239.76.177:5060;transport=udp;wlsscid=1ae4691c270666;appsessionid=app-6dkon9n0iato>
    To: <sip:5947913-0kdb518f8i0q2@10.0.5.77:5060;rinstance=7876247691f41940;transport=udp;useradd=66.158.163.130;userport=9091>
    From: "WIRELESS CALLER"<sip:13177100787@208.239.76.177>;tag=SD33qv201-d43129d1
    Call-ID: SD33qv201-3b7b76d9d8bd2110fa6fb4e2d83d6aed-gurpko2
    CSeq: 1 INVITE
    Min-SE: 90
    Supported: timer
    Content-Length: 0
    X-UUID: c70dac33fb484829a410c7de8013ae99
    X-DID: 3172883905

    13:03:56.029 [CM503012]: Inbound out-of-office hours rule (unnamed) for 10000 forwards to DN:100
    13:03:56.013 Looking for inbound target: called=5947913-0kdb518f8i0q2; caller=13177100787
    13:03:56.013 [CM500002]: Info on incoming INVITE:
    INVITE sip:5947913@10.22.95.132:5060;rinstance=675f73cfd79a5f1a SIP/2.0
    Via: SIP/2.0/UDP 208.239.76.177:5060;branch=z9hG4bKal1lmcmbtdt630gh8hs5vgpo63
    Max-Forwards: 69
    Contact: <sip:208.239.76.177:5060;transport=udp;wlsscid=1ae4691c270666;appsessionid=app-6dkon9n0iato>
    To: <sip:5947913-0kdb518f8i0q2@10.0.5.77:5060;rinstance=675f73cfd79a5f1a;transport=udp;useradd=66.158.163.130;userport=50354>
    From: "WIRELESS CALLER"<sip:13177100787@208.239.76.177>;tag=SD3354901-8d97367f
    Call-ID: SD3354901-6aa1770fad12ca33b8c3d3bf9bd136e9-gurpko2
    CSeq: 1 INVITE
    Min-SE: 90
    Supported: timer
    Content-Length: 0
    X-UUID: c70dac33fb484829a410c7de8013ae99
    X-DID: 3172883905
     
  4. abc123

    abc123 Active Member

    Joined:
    Nov 9, 2009
    Messages:
    712
    Likes Received:
    1
    Contact your VOIP provider.

    They are 3 distinctly different invites and so 3cx is correctly treating them as such.

    Get them to run a wireshark and make the call and they will see the same thing
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. abc123

    abc123 Active Member

    Joined:
    Nov 9, 2009
    Messages:
    712
    Likes Received:
    1
    You dont happen to have multiple registrations to this voip provider on your 3cx do you? With the same username and password?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  6. hoosier1077

    Joined:
    Mar 5, 2011
    Messages:
    52
    Likes Received:
    0
    Ive only got one registration setup in 3cx.... I used my did that i got from them as my external number, however i havent setup any additional did's within 3cx. So if you look at my "voip provider" section within 3cx, and go over to the did tab, there is nothing in there. I was guessing that I would need to add did's there if I were to purchase anymore than just the one main number. I believe that its setup correctly that way, but let me know if that doesnt sound right. I will attach some screenshots if you think it would be worth taking a look at.
     
  7. hoosier1077

    Joined:
    Mar 5, 2011
    Messages:
    52
    Likes Received:
    0
    Also, Ive setup both ways so it this doesnt seem to make a difference. Since I have a static public ip with the nat and ports mapping setup I wouldnt need to run the stun server right? Just want to make sure I have that part configured correctly as well, but as I said, it happens either way.
     
  8. abc123

    abc123 Active Member

    Joined:
    Nov 9, 2009
    Messages:
    712
    Likes Received:
    1
    They are sending you 3 distinctly individual invites.

    The reason i asked if you had multiple registrations (maybe through testing or some make a mistake thinking it is one registration per did) is that if they had 3 active registrations in their system from you in the same place then they are also correct in sending the 3 invites if you had no special routing.

    We are launching our own VOIP Provider service this month and one of our features is you can have multiple registrations and have them all ring or just route to one registration for a number.

    But you say you only have one voip provider set up and so the problem is back with infonex. Call them and let them know
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  9. hoosier1077

    Joined:
    Mar 5, 2011
    Messages:
    52
    Likes Received:
    0
    will do, thanks.
     
Thread Status:
Not open for further replies.