V1.0.22 - Slow connection

Discussion in 'iOS' started by janofsky, Jan 31, 2011.

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

    Joined:
    Jun 13, 2009
    Messages:
    14
    Likes Received:
    0
    I have installed 3cx 1.0.22 on and Iphone. The phone registers via wifi to my 3cx pbx or via 3g thru the tunnel to my 3cx pbx. However the app is soooo slow, after hitting the call button it takes over 90 seconds to be call another extension. It also takes over 90 seconds after receiving an incoming ring and pressing answer for the phone to answer. In the meantime the Iphone is non-responsive. The same is true when I register to another SIP provider. Any suggestions.

    Eric
     
  2. StefanW

    StefanW Head of Customer Support and Training
    Staff Member 3CX Support

    Joined:
    Jun 2, 2009
    Messages:
    1,215
    Likes Received:
    87
    Re: 3cx App for Iphone 4 4 4.2.1 just sooooooo slow

    http://www.3cx.com/forums/every-new-post-must-contain-18726.html
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. janofsky

    Joined:
    Jun 13, 2009
    Messages:
    14
    Likes Received:
    0
    Re: 3cx App for Iphone 4 4 4.2.1 just sooooooo slow

    3cx App for Iphone 4 4 4.2.1 just sooooooo slow
    by janofsky » Sun Jan 30, 2011 10:02 pm

    I have installed 3cx 1.0.22 on and Iphone. The phone registers via wifi to my 3cx pbx or via 3g thru the tunnel to my 3cx pbx. However the app is soooo slow, after hitting the call button it takes over 90 seconds to be call another extension. It also takes over 90 seconds after receiving an incoming ring and pressing answer for the phone to answer. In the meantime the Iphone is non-responsive. The same is true when I register to another SIP provider. Any suggestions.

    Eric
    Device Info
    -------------------------------------------------------
    Phone Model: [iPhone
    Generation: ,,4G,
    Firmware Version: [4.2.1]
    Jailbreak: |NO]
    Cydia Installed:|NO]

    Issue Info
    -------------------------------------------------------
    Handset: [Phone|
    Contacts: |Exchange|e]
    Connection: [WiFi|3G] same problem with both
    Server: [Internal|External] same problem with both
     
  4. StefanW

    StefanW Head of Customer Support and Training
    Staff Member 3CX Support

    Joined:
    Jun 2, 2009
    Messages:
    1,215
    Likes Received:
    87
    re: 3CX Tunnel? In the 3CxPhoen for iphone is no tunnel integrated. so how you do this? Do you use 3CX Sip Proxy manager?

    Give me pls a screenshot when the phone "hangs" to see what you dial and how the keyboard looks like.
    Also is your PBX on Port 5060?
    Do you have BT connected devices to the phone?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. janofsky

    Joined:
    Jun 13, 2009
    Messages:
    14
    Likes Received:
    0
    No


    I have also tried to use Gizmo proxy01sipphone,com. the iphone registers but response is very slow. I have no problem with my pc 3cx client.
     
  6. shiftf7

    Joined:
    Mar 12, 2009
    Messages:
    22
    Likes Received:
    0
    I have exactly the same issue with the 3CX iphone app - everything works but it takes approx 30 seconds from hitting the dial button for the phone to actually dial anything (including internal extentions). This happens on both my iPAD and my iPhone - both internally or externally. Once the call has connected - it works fine. Just seems to be a huge delay somewhere in the initial connection.

    The above video is exactly the issue - apart from a slightly smaller delay of 30 second.

    Device Info
    -------------------------------------------------------
    Phone Model: iPAD V1 and iPhone 3Gs
    Generation: 3Gs
    Firmware Version: 4.2.1
    Jailbreak: NO
    Cydia Installed: NO

    Issue Info
    -------------------------------------------------------
    Handset: Phone
    Contacts: Local
    Connection: WiFi
    Server: Internal
     
  7. StefanW

    StefanW Head of Customer Support and Training
    Staff Member 3CX Support

    Joined:
    Jun 2, 2009
    Messages:
    1,215
    Likes Received:
    87
    we most likely found the source of the issue.
    Plz run a test for me, can you plug an head set in the device with a mic (which comes with the iPhone)?I have the feeling we try to find an audio source which is not present at the time and we hang in an ideal time out...
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  8. janofsky

    Joined:
    Jun 13, 2009
    Messages:
    14
    Likes Received:
    0
    No improvement, it still took about 5 minutes to call from internal to the network.

    :26.859

    Currently active calls [none]

    16:43:01.750

    [CM504001]: Ext.13: new contact is registered. Contact(s): [sip:13@192.168.163.120:5060/13,sip:13@76.126.239.193:5060/13,sip:13@10.56.64.93:5060/13,sip:13@166.205.139.38:55522/13]

    16:42:56.562

    Currently active calls [none]

    16:42:24.531

    Currently active calls [none]

    16:41:54.421

    Currently active calls [none]

    16:41:24.390

    Currently active calls [none]

    16:40:54.250

    Currently active calls [none]

    16:40:24.078

    Currently active calls [none]

    16:39:52.078

    Currently active calls [none]

    16:39:21.484

    Currently active calls [none]

    16:38:51.390

    Currently active calls [none]

    16:38:33.203

    [CM503008]: Call(14): Call is terminated

    16:38:21.296

    Currently active calls - 1: [14]

    16:38:11.609

    [MS210005] C:14.1:Answer provided. Connection(proxy mode):192.168.163.75:7052(7053)

    16:38:11.609

    [MS210001] C:14.3:Answer received. RTP connection[unsecure]: 127.0.0.1:40610(40611)

    16:38:11.609

    Remote SDP is set for legC:14.3

    16:38:11.343

    [MS210004] C:14.3:Offer provided. Connection(proxy mode): 127.0.0.1:7056(7057)

    16:38:11.296

    [MS210000] C:14.1:Offer received. RTP connection: 192.168.163.120:4000(4001)

    16:38:11.281

    Remote SDP is set for legC:14.1

    16:38:10.906

    Session 25362 of leg C:14.1 is confirmed

    16:38:10.750

    [CM503007]: Call(14): Device joined: sip:99@127.0.0.1:40600;rinstance=6dd5c7167d4f53c3

    16:38:10.734

    [CM503007]: Call(14): Device joined: sip:13@192.168.163.120:5060

    16:38:10.718

    [MS210005] C:14.1:Answer provided. Connection(proxy mode):192.168.163.75:7052(7053)

    16:38:10.703

    [MS210001] C:14.3:Answer received. RTP connection[unsecure]: 127.0.0.1:40610(40611)

    16:38:10.703

    Remote SDP is set for legC:14.3

    16:38:10.687

    [CM505001]: Ext.99: Device info: Device Identified: [Man: 3CX Ltd.;Mod: Voice Mail Menu;Rev: 1] Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CX Voice Mail Menu] PBX contact: [sip:99@127.0.0.1:5060]

    16:38:10.687

    [CM503002]: Call(14): Alerting sip:99@127.0.0.1:40600;rinstance=6dd5c7167d4f53c3

    16:38:09.937

    [CM503003]: Call(14): Call to sip:14@192.168.163.75:5060 has failed; Cause: 487 Request Terminated; from IP:192.168.163.190:60126

    16:38:09.765

    [CM503025]: Call(14): Calling Ext:Ext.99@[Dev:sip:99@127.0.0.1:40600;rinstance=6dd5c7167d4f53c3]

    16:38:09.750

    [MS210004] C:14.3:Offer provided. Connection(proxy mode): 127.0.0.1:7056(7057)

    16:38:09.718

    [CM503005]: Call(14): Forwarding: Ext:Ext.99@[Dev:sip:99@127.0.0.1:40600;rinstance=6dd5c7167d4f53c3]

    16:37:50.703

    Currently active calls - 1: [14]

    16:37:39.890

    [CM505001]: Ext.14: 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:14@192.168.163.75:5060]

    16:37:39.890

    [CM503002]: Call(14): Alerting sip:14@192.168.163.190:60126;rinstance=eca5c3dee0aa92af

    16:37:39.671

    [CM503025]: Call(14): Calling Ext:Ext.14@[Dev:sip:14@192.168.163.190:60126;rinstance=eca5c3dee0aa92af]

    16:37:39.656

    [MS210006] C:14.2:Offer provided. Connection(by pass mode): 192.168.163.120:4000(4001)

    16:37:39.656

    [MS210000] C:14.1:Offer received. RTP connection: 192.168.163.120:4000(4001)

    16:37:39.625

    Remote SDP is set for legC:14.1

    16:37:39.609

    [CM503004]: Call(14): Route 1: Ext:Ext.14@[Dev:sip:14@192.168.163.190:60126;rinstance=eca5c3dee0aa92af]

    16:37:39.609

    [CM503010]: Making route(s) to <sip:14@192.168.163.75>

    16:37:39.609

    [CM505001]: Ext.13: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CXPhone for iPhone 1.0.22] PBX contact: [sip:13@192.168.163.75:5060]

    16:37:39.578

    [MS210000] C:14.1:Offer received. RTP connection: 192.168.163.120:4000(4001)

    16:37:39.562

    Remote SDP is set for legC:14.1

    16:37:39.562

    [CM503001]: Call(14): Incoming call from Ext.13 to <sip:14@192.168.163.75>

    16:37:39.546

    [CM500002]: Info on incoming INVITE:



    INVITE sip:14@192.168.163.75 SIP/2.0



    Via: SIP/2.0/UDP 192.168.163.120:5060;rport=5060;branch=z9hG4bKPjmhVImQ8I1khuiR3Tyuye2Y2Y6EDXCbxX



    Max-Forwards: 70



    Contact: "3cx home"<sip:13@192.168.163.120:5060>



    To: <sip:14@192.168.163.75>



    From: "3cx home"<sip:13@192.168.163.75>;tag=XLSO-G9Fz5Khn65OlXgnnaL2F2aQ64E.



    Call-ID: EOhesGuno0dfFUayAoKUOl86.sTBJiMG



    CSeq: 17989 INVITE



    Session-Expires: 1800



    Min-SE: 90



    Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS



    Proxy-Authorization: Digest username="13",realm="3CXPhoneSystem",nonce="414d535c0367b8d345:9f861bd015a3145f2074cfb8ccf22642",uri="sip:14@192.168.163.75",response="add9380a50bfc304876dbbfcb70df1df",algorithm=MD5



    Supported: replaces, 100rel, timer, norefersub



    User-Agent: 3CXPhone for iPhone 1.0.22



    Content-Length: 0





    16:37:20.578

    Currently active calls [none]

    16:36:48.562

    Currently active calls [none]

    16:36:18.109

    Currently active calls [none]

    16:35:46.109

    Currently active calls [none]

    16:35:15.968

    Currently active calls [none]

    16:35:15.796

    [MS105000] C:13.2: No RTP packets were received:remoteAddr=130.94.88.94:18844,extAddr=0.0.0.0:0,localAddr=192.168.163.75:7050

    16:35:14.515

    [CM503008]: Call(13): Call is terminated

    16:35:11.875

    Session 25330 of leg C:13.1 is confirmed

    16:35:11.843

    [CM503007]: Call(13): Device joined: sip:17472721772@proxy01.sipphone.com:5060

    16:35:11.812

    [CM503007]: Call(13): Device joined: sip:12@192.168.163.59:5060

    16:35:11.796

    [MS210003] C:13.1:Answer provided. Connection(transcoding mode[unsecure]):192.168.163.75:7048(7049)

    16:35:11.796

    [MS210001] C:13.2:Answer received. RTP connection[unsecure]: 130.94.88.94:18844(18845)

    16:35:11.781

    Remote SDP is set for legC:13.2

    16:35:11.781

    [CM505003]: Provider:[Gizmo 17472721772] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [] PBX contact: [sip:17472721772@192.168.163.75:5060]

    16:35:11.781

    [CM503002]: Call(13): Alerting sip:17472721772@proxy01.sipphone.com:5060

    16:35:11.109

    [CM503025]: Call(13): Calling VoIPline:18005551212@(Ln.10009@Gizmo 17472721772)@[Dev:sip:17472721772@proxy01.sipphone.com:5060]

    16:35:11.062

    [MS210002] C:13.2:Offer provided. Connection(transcoding mode): 192.168.163.75:7050(7051)

    16:35:11.031

    [CM503004]: Call(13): Route 1: VoIPline:18005551212@(Ln.10009@Gizmo 17472721772)@[Dev:sip:17472721772@proxy01.sipphone.com:5060]

    16:35:10.968

    [CM503010]: Making route(s) to <sip:18005551212@192.168.163.75>

    16:35:10.968

    [MS210000] C:13.1:Offer received. RTP connection: 192.168.163.59:16400(16401)

    16:35:10.968

    Remote SDP is set for legC:13.1

    16:35:10.968

    [CM505001]: Ext.12: Device info: Device Identified: [Man: Linksys;Mod: SPA series;Rev: General] Capabilities:[reinvite, no-replaces, able-no-sdp, recvonly] UserAgent: [Linksys/SPA3102-5.1.10(GW)] PBX contact: [sip:12@192.168.163.75:5060]

    16:35:10.921

    [CM503001]: Call(13): Incoming call from Ext.12 to <sip:18005551212@192.168.163.75>

    16:35:10.890

    [CM500002]: Info on incoming INVITE:



    INVITE sip:18005551212@192.168.163.75 SIP/2.0



    Via: SIP/2.0/UDP 192.168.163.59:5060;branch=z9hG4bK-4126e96f



    Max-Forwards: 70



    Contact: "12"<sip:12@192.168.163.59:5060>



    To: <sip:18005551212@192.168.163.75>



    From: "12"<sip:12@192.168.163.75>;tag=1c8d2bd02cf86ae3o0



    Call-ID: 8b476c14-dd17876f@192.168.163.59



    CSeq: 102 INVITE



    Expires: 240



    Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER



    Proxy-Authorization: Digest username="12",realm="3CXPhoneSystem",nonce="414d535c0367b83e74:2ebfee156173f52a117d61cfcf97528c",uri="sip:18005551212@192.168.163.75",algorithm=MD5,response="503dd0b050c8562493013c32c2cf420a"



    Supported: x-sipura, replaces



    User-Agent: Linksys/SPA3102-5.1.10(GW)



    Content-Length: 0



    Remote-Party-ID: 12 <sip:12@192.168.163.75>;screen=yes;party=calling





    16:35:15.968

    Currently active calls [none]

    16:35:15.796

    [MS105000] C:13.2: No RTP packets were received:remoteAddr=130.94.88.94:18844,extAddr=0.0.0.0:0,localAddr=192.168.163.75:7050

    16:35:14.515

    [CM503008]: Call(13): Call is terminated

    16:35:11.875

    Session 25330 of leg C:13.1 is confirmed

    16:35:11.843

    [CM503007]: Call(13): Device joined: sip:17472721772@proxy01.sipphone.com:5060

    16:35:11.812

    [CM503007]: Call(13): Device joined: sip:12@192.168.163.59:5060

    16:35:11.796

    [MS210003] C:13.1:Answer provided. Connection(transcoding mode[unsecure]):192.168.163.75:7048(7049)

    16:35:11.796

    [MS210001] C:13.2:Answer received. RTP connection[unsecure]: 130.94.88.94:18844(18845)

    16:35:11.781

    Remote SDP is set for legC:13.2

    16:35:11.781

    [CM505003]: Provider:[Gizmo 17472721772] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [] PBX contact: [sip:17472721772@192.168.163.75:5060]

    16:35:11.781

    [CM503002]: Call(13): Alerting sip:17472721772@proxy01.sipphone.com:5060

    16:35:11.109

    [CM503025]: Call(13): Calling VoIPline:18005551212@(Ln.10009@Gizmo 17472721772)@[Dev:sip:17472721772@proxy01.sipphone.com:5060]

    16:35:11.062

    [MS210002] C:13.2:Offer provided. Connection(transcoding mode): 192.168.163.75:7050(7051)

    16:35:11.031

    [CM503004]: Call(13): Route 1: VoIPline:18005551212@(Ln.10009@Gizmo 17472721772)@[Dev:sip:17472721772@proxy01.sipphone.com:5060]

    16:35:10.968

    [CM503010]: Making route(s) to <sip:18005551212@192.168.163.75>

    16:35:10.968

    [MS210000] C:13.1:Offer received. RTP connection: 192.168.163.59:16400(16401)

    16:35:10.968

    Remote SDP is set for legC:13.1

    16:35:10.968

    [CM505001]: Ext.12: Device info: Device Identified: [Man: Linksys;Mod: SPA series;Rev: General] Capabilities:[reinvite, no-replaces, able-no-sdp, recvonly] UserAgent: [Linksys/SPA3102-5.1.10(GW)] PBX contact: [sip:12@192.168.163.75:5060]

    16:35:10.921

    [CM503001]: Call(13): Incoming call from Ext.12 to <sip:18005551212@192.168.163.75>

    16:35:10.890

    [CM500002]: Info on incoming INVITE:



    INVITE sip:18005551212@192.168.163.75 SIP/2.0



    Via: SIP/2.0/UDP 192.168.163.59:5060;branch=z9hG4bK-4126e96f



    Max-Forwards: 70



    Contact: "12"<sip:12@192.168.163.59:5060>



    To: <sip:18005551212@192.168.163.75>



    From: "12"<sip:12@192.168.163.75>;tag=1c8d2bd02cf86ae3o0



    Call-ID: 8b476c14-dd17876f@192.168.163.59



    CSeq: 102 INVITE



    Expires: 240



    Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER



    Proxy-Authorization: Digest username="12",realm="3CXPhoneSystem",nonce="414d535c0367b83e74:2ebfee156173f52a117d61cfcf97528c",uri="sip:18005551212@192.168.163.75",algorithm=MD5,response="503dd0b050c8562493013c32c2cf420a"



    Supported: x-sipura, replaces



    User-Agent: Linksys/SPA3102-5.1.10(GW)



    Content-Length: 0



    Remote-Party-ID: 12 <sip:12@192.168.163.75>;screen=yes;party=calling





    16:34:43.968

    Currently active calls [none]

    16:34:13.765

    Currently active calls [none]

    16:33:58.312

    [CM504001]: Ext.13: new contact is registered. Contact(s): [sip:13@192.168.163.120:5060/13,sip:13@76.126.239.193:5060/13,sip:13@166.205.139.38:55522/13]

    16:33:57.26

    Re: V1.0.22 - Slow connection
    by StefanW » Fri Feb 11, 2011 2:35 am

    we most likely found the source of the issue.
    Plz run a test for me, can you plug an head set in the device with a mic (which comes with the iPhone)?I have the feeling we try to find an audio source which is not present at the time and we hang in an ideal time out...
     
  9. StefanW

    StefanW Head of Customer Support and Training
    Staff Member 3CX Support

    Joined:
    Jun 2, 2009
    Messages:
    1,215
    Likes Received:
    87
    the log only shows me that you call from 13 to 14 and 14 dont pick up so you end up at 99.
    But i have the feeling that the start of the call dowsa not reach the pbx at the beginning so there the call hangs.
    and this i can not see in the logs.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  10. shiftf7

    Joined:
    Mar 12, 2009
    Messages:
    22
    Likes Received:
    0
    I tried with the headphones - there is still a 13-15 second delay from the time I press the dial button and connection to the PBX. So still a problem. iPhone is x102 dialing DR on 803.

    09:53:01.536 [CM503008]: Call(4259): Call is terminated
    09:52:56.771 [MS210005] C:4259.1:Answer provided. Connection(proxy mode):172.22.22.208:7018(7019)
    09:52:56.770 [MS210001] C:4259.2:Answer received. RTP connection[unsecure]: 127.0.0.1:40832(40833)
    09:52:56.769 Remote SDP is set for legC:4259.2
    09:52:56.564 [MS210004] C:4259.2:Offer provided. Connection(proxy mode): 127.0.0.1:7020(7021)
    09:52:56.563 [MS210000] C:4259.1:Offer received. RTP connection: 172.22.22.35:4004(4005)
    09:52:56.562 Remote SDP is set for legC:4259.1
    09:52:56.355 Session 665870 of leg C:4259.1 is confirmed
    09:52:56.151 [CM503007]: Call(4259): Device joined: sip:803@127.0.0.1:40600;rinstance=30b5e299784e750a
    09:52:56.149 [CM503007]: Call(4259): Device joined: sip:102@172.22.22.35:5060
    09:52:56.147 [MS210005] C:4259.1:Answer provided. Connection(proxy mode):172.22.22.208:7018(7019)
    09:52:56.144 [MS210001] C:4259.2:Answer received. RTP connection[unsecure]: 127.0.0.1:40832(40833)
    09:52:56.142 Remote SDP is set for legC:4259.2
    09:52:56.137 [CM505001]: Ext.803: Device info: Device Identified: [Man: 3CX Ltd.;Mod: 3CX IVR;Rev: 1] Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CX IVR] PBX contact: [sip:803@127.0.0.1:5060]
    09:52:56.137 [CM503002]: Call(4259): Alerting sip:803@127.0.0.1:40600;rinstance=30b5e299784e750a
    09:52:55.988 [CM503025]: Call(4259): Calling Ext:Ext.803@[Dev:sip:803@127.0.0.1:40600;rinstance=30b5e299784e750a]
    09:52:55.986 [MS210004] C:4259.2:Offer provided. Connection(proxy mode): 127.0.0.1:7020(7021)
    09:52:55.942 [CM503004]: Call(4259): Route 1: Ext:Ext.803@[Dev:sip:803@127.0.0.1:40600;rinstance=30b5e299784e750a]
    09:52:55.941 [CM503010]: Making route(s) to <sip:803@172.22.22.203>
    09:52:55.941 [MS210000] C:4259.1:Offer received. RTP connection: 172.22.22.35:4004(4005)
    09:52:55.940 Remote SDP is set for legC:4259.1
    09:52:55.939 [CM505001]: Ext.102: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CXPhone for iPhone 1.0.22] PBX contact: [sip:102@172.22.22.203:5060]
    09:52:55.934 [CM503001]: Call(4259): Incoming call from Ext.102 to <sip:803@172.22.22.203>
    09:52:55.930 [CM500002]: Info on incoming INVITE:
    INVITE sip:803@172.22.22.203 SIP/2.0
    Via: SIP/2.0/UDP 172.22.22.35:5060;rport=5060;branch=z9hG4bKPjOlVdMebJdNrGe9VEQDlC364JAjQZSVDW
    Max-Forwards: 70
    Contact: "Andrew"<sip:102@172.22.22.35:5060>
    To: <sip:803@172.22.22.203>
    From: "Andrew"<sip:102@172.22.22.203>;tag=F4KULMPGjVuWFTTVZkJ4Owi5mJrjwCIH
    Call-ID: 6CtgKpccsC7fIEgI3UvyDDNRK7v6jYJj
    CSeq: 19759 INVITE
    Session-Expires: 1800
    Min-SE: 90
    Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS
    Proxy-Authorization: Digest username="102",realm="3CXPhoneSystem",nonce="414d535c03698c7790:b46e5431bb9130293c0c0680d6066425",uri="sip:803@172.22.22.203",response="16f5176b4f90e861be05582d76c805ea",algorithm=MD5
    Supported: replaces, 100rel, timer, norefersub
    User-Agent: 3CXPhone for iPhone 1.0.22
    Content-Length: 0

    09:52:48.811 Currently active calls [none]
     
  11. StefanW

    StefanW Head of Customer Support and Training
    Staff Member 3CX Support

    Joined:
    Jun 2, 2009
    Messages:
    1,215
    Likes Received:
    87
    the probl. cant be traced by the log of the pbx.
    if you start makign the call the call is stuck in the phone.
    if u press the reload button in the pbx after you dialed in the phone you will see the call is not at this stage in the system.
    so pbx dont know about the call at this time...
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  12. janofsky

    Joined:
    Jun 13, 2009
    Messages:
    14
    Likes Received:
    0

    That was my point, the 3cx iphone client is stuck.

    I tried making a call from a 3cx pc client to the 3cx iphone client. The iphone rang relatively quickly but when I tried to answer the iphone would not pick up in a reasonable amount of time (60 seconds) and then I terminated the call from the 3cx pc client but the iphone kept on ringing and I had to terminate the 3cx client on the iphone.

    Any suggestions?
     
  13. lynnabelone

    Joined:
    Feb 15, 2011
    Messages:
    1
    Likes Received:
    0
    Hello all,
    I am new member of this forum.So I have bought a new Iphone.But The connection was very slow.Please give me some ideas.Thanks.
     
  14. shiftf7

    Joined:
    Mar 12, 2009
    Messages:
    22
    Likes Received:
    0
    I agree, the delay seems on the iPhone device not the PBX. Is there a way to solve this issue please?
     
  15. StefanW

    StefanW Head of Customer Support and Training
    Staff Member 3CX Support

    Joined:
    Jun 2, 2009
    Messages:
    1,215
    Likes Received:
    87
    we send 2day a new version to apple to be uploaded to the app store, lets see if this fixes the issues and take it from there
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  16. sfweb

    Joined:
    Feb 17, 2011
    Messages:
    1
    Likes Received:
    0
    I also facing same problem.

     
  17. StefanW

    StefanW Head of Customer Support and Training
    Staff Member 3CX Support

    Joined:
    Jun 2, 2009
    Messages:
    1,215
    Likes Received:
    87
    so new version is out, plz give it a go, leave TCP off for now, due to we brought back the MultiTask by Force
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  18. shiftf7

    Joined:
    Mar 12, 2009
    Messages:
    22
    Likes Received:
    0
    Stefan,
    Thank you for the update, I installed this lastest version 1.0.23 and I still have the delay between hitting the green dial button and contact with the 3CX systems (around 12 seconds). It is the same as it was in 1.0.22.
    I have tried it with earphones and with/without Bluetooth enabled - but no change in behaviour.
    Same on local LAN or remote - perhaps I should get an Android phone :)
    Andrew.
     
  19. janofsky

    Joined:
    Jun 13, 2009
    Messages:
    14
    Likes Received:
    0
    Stefan

    there is still a delay. is there a debug feature which I can provide you?

    Eric
     
  20. Vali_3CX

    Vali_3CX Well-Known Member
    Staff Member 3CX Support

    Joined:
    Dec 12, 2008
    Messages:
    1,479
    Likes Received:
    67
    Hi Eric, Andrew

    Currently we are working to review/redesign our "mobile" versions of our 3CXPhone - I mean for Android and iPhone. In case of iPhone, all 1.0.21-1.0.23 tried to address/fix some significant bugs and issues and to make it more stable. Next release has already planned to review the whole audio support. You may try the Android version, obviously, but my opinion is that at this current stage, the iPhone's is more stable and reliable.

    Regards
    vali
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
Thread Status:
Not open for further replies.