Grandstream GXW-4104 Problems

Discussion in '3CX Phone System - General' started by technicalpc, Aug 15, 2007.

  1. technicalpc

    Joined:
    Jun 25, 2007
    Messages:
    12
    Likes Received:
    0
    Hi all !!!

    I'd like to congratulate the 3cx team. I've been using this system for about 2 weeks now and it's incredible !!!!

    I've read a lot of topics in this forum but I couldn't find anybody with this problem, the thing is that when I try to place a call with the phone GXP2000 and gateway Grandstream GXW-4104, most of the times the FXO is not picked. You can see the light of the selected FXO turn on and then off inmediately. After a few tries I can place a call normally. This thing is driving me crazy, I've changed lots of settings but I cannot make it work. I'll show the debug files hoping that some of you guys can find the answer. Right now every settings are just like the 3cx support page says, except the "Round-robin and/or Flexible:" which is "rr:1;rr:2;rr:3;rr:4;" because whenever the gateway picked a line it went to the last FXO Line Connected, in my case is number 3, then 2 and 1 at last, with this configuration is working good.

    Now, I have 3 FXO but have registered 4 with 3CX, could this cause any problem??

    I haven't configured Digital Receptionist.

    The problem is with Outbound only, the incoming are perfect.


    These are the debugs for the grandstream when it don't pick the FXO:

    08-13-2007 18:56:56 User.Debug 192.168.1.245 GS_LOG: [00:0B:82:0D:C7:4F][000][FF50][01000037] fxo_ctl.c 1081 Port:0 DAA ST: 2 EV: 13
    08-13-2007 18:56:20 User.Info 192.168.1.245 GS_LOG: [00:0B:82:0D:C7:4F][000][FF50][01000037] 583 cm_utility.c Port:0 Sess:0 gw_st: 1 cs_st: 0
    08-13-2007 18:56:19 User.Debug 192.168.1.245 GS_LOG: [00:0B:82:0D:C7:4F][000][FF50][01000037] fxo_ctl.c 982 1113 Port:0 DAA ST: 2 CS: 0
    08-13-2007 18:56:19 User.Debug 192.168.1.245 GS_LOG: [00:0B:82:0D:C7:4F][000][FF50][01000037] fxo_ctl.c 1081 Port:0 DAA ST: 2 EV: 2
    08-13-2007 18:56:19 User.Info 192.168.1.245 GS_LOG: [00:0B:82:0D:C7:4F][000][FF50][01000037] 1463 sip.c Received SIP message: 3 Acc:0
    08-13-2007 18:56:19 User.Debug 192.168.1.245 GS_LOG: [00:0B:82:0D:C7:4F][000][FF50][01000037] 617 cm_control.c sip sees:0 sess st:0 call st:1 0
    08-13-2007 18:56:19 User.Info 192.168.1.245 GS_LOG: [00:0B:82:0D:C7:4F][000][FF50][01000037] fxo_ctl.c 186 Port:0 DAA Hangup 2
    08-13-2007 18:56:19 User.Info 192.168.1.245 GS_LOG: [00:0B:82:0D:C7:4F][000][FF50][01000037] 598 cm_utility.c Port:0 Sess:0 gw_st: 1 cs_st: 0 from#: 115
    08-13-2007 18:56:19 User.Debug 192.168.1.245 GS_LOG: [00:0B:82:0D:C7:4F][000][FF50][01000037] 856 sip.c Sess: 0 SIP/2.0 487 Request Cancelled Via: SIP/2.0/UDP 192.168.1.250:5060;branch=z9hG4bK-d87543-4a111a178f113d10-1--d87543-;rport From: "104"<sip:104@192.168.1.250:5060>;tag=06120e49 To: "786XXXXXXX"<sip:786XXXXXXX@192.168.1.245:5060>;tag=0f20351314b0f8d7 Call-ID: NTQyYWM3M2FlMWFjOTAyMjMwMDRiYzZiZTJlZTUxMWU. CSeq: 1 INVITE User-Agent: Grandstream GXW4104 (HW 0001, Ch:0) 1.0.0.55 Content-Length: 0
    08-13-2007 18:56:19 User.Info 192.168.1.245 GS_LOG: [00:0B:82:0D:C7:4F][000][FF50][01000037] 683 sip.c Sess: 0 Send SIP message: 487 To 192.168.1.250:5060
    08-13-2007 18:56:19 User.Debug 192.168.1.245 GS_LOG: [00:0B:82:0D:C7:4F][000][FF50][01000037] 856 sip.c Sess: 0 SIP/2.0 200 OK Via: SIP/2.0/UDP 192.168.1.250:5060;branch=z9hG4bK-d87543-4a111a178f113d10-1--d87543-;rport From: "104"<sip:104@192.168.1.250:5060>;tag=06120e49 To: "786XXXXXXX"<sip:786XXXXXXX@192.168.1.245:5060>;tag=7a217d4284273137 Call-ID: NTQyYWM3M2FlMWFjOTAyMjMwMDRiYzZiZTJlZTUxMWU. CSeq: 1 CANCEL User-Agent: Grandstream GXW4104 (HW 0001, Ch:0) 1.0.0.55 Supported: replaces, timer, 100rel, path Content-Length: 0
    08-13-2007 18:56:19 User.Info 192.168.1.245 GS_LOG: [00:0B:82:0D:C7:4F][000][FF50][01000037] 683 sip.c Sess: 0 Send SIP message: 200 To 192.168.1.250:5060
    08-13-2007 18:56:19 User.Info 192.168.1.245 GS_LOG: [00:0B:82:0D:C7:4F][000][FF50][01000037] 1463 sip.c Received SIP message: 5 Acc:0
    08-13-2007 18:55:55 User.Debug 192.168.1.245 GS_LOG: [00:0B:82:0D:C7:4F][000][FF50][01000037] fxo_ctl.c 982 1113 Port:0 DAA ST: 2 CS: 2
    08-13-2007 18:55:55 User.Debug 192.168.1.245 GS_LOG: [00:0B:82:0D:C7:4F][000][FF50][01000037] fxo_ctl.c 1081 Port:0 DAA ST: 4 EV: 2
    08-13-2007 18:55:55 User.Debug 192.168.1.245 GS_LOG: [00:0B:82:0D:C7:4F][000][FF50][01000037] fxo_ctl.c 1081 Port:0 DAA ST: 4 EV: 18
    08-13-2007 18:55:55 User.Debug 192.168.1.245 GS_LOG: [00:0B:82:0D:C7:4F][000][FF50][01000037] fxo_ctl.c 982 1218 Port:0 DAA ST: 4 CS: 2
    08-13-2007 18:55:55 User.Debug 192.168.1.245 GS_LOG: [00:0B:82:0D:C7:4F][000][FF50][01000037] fxo_ctl.c 1081 Port:0 DAA ST: 3 EV: 3
    08-13-2007 18:55:55 User.Debug 192.168.1.245 GS_LOG: [00:0B:82:0D:C7:4F][000][FF50][01000037] fxo_ctl.c 336 Port:0 app ST: 1 DAA CS: 2
    08-13-2007 18:55:55 User.Debug 192.168.1.245 GS_LOG: [00:0B:82:0D:C7:4F][000][FF50][01000037] fxo_ctl.c 982 875 Port:0 DAA ST: 3 CS: 2
    08-13-2007 18:55:55 User.Debug 192.168.1.245 GS_LOG: [00:0B:82:0D:C7:4F][000][FF50][01000037] fxo_ctl.c 1081 Port:0 DAA ST: 2 EV: 1
    08-13-2007 18:55:55 User.Debug 192.168.1.245 GS_LOG: [00:0B:82:0D:C7:4F][000][FF50][01000037] 752 sip_handle_invite.c Port:0 Wait Dialtone: 1 Dial: 786XXXXXXX When FXO is ready
    08-13-2007 18:55:55 User.Debug 192.168.1.245 GS_LOG: [00:0B:82:0D:C7:4F][000][FF50][01000037] 256 cm_dialplan.c Dialplan segs: 1 1001 0 1 0
    08-13-2007 18:55:55 User.Info 192.168.1.245 GS_LOG: [00:0B:82:0D:C7:4F][000][FF50][01000037] 620 sip_handle_invite.c Port:0 Sess:0;1 1 0;1 100;0
    08-13-2007 18:55:55 User.Info 192.168.1.245 GS_LOG: [00:0B:82:0D:C7:4F][000][FF50][01000037] 568 sip_handle_invite.c Sess: 0 INVITE From="104"<sip:104@192.168.1.250:5060>;tag=06120e49 To="786XXXXXXX"<sip:786XXXXXXX@192.168.1.245:5060>
    08-13-2007 18:55:55 User.Debug 192.168.1.245 GS_LOG: [00:0B:82:0D:C7:4F][000][FF50][01000037] 856 sip.c Sess: 0 SIP/2.0 100 Trying Via: SIP/2.0/UDP 192.168.1.250:5060;branch=z9hG4bK-d87543-4a111a178f113d10-1--d87543-;rport From: "104"<sip:104@192.168.1.250:5060>;tag=06120e49 To: "786XXXXXXX"<sip:786XXXXXXX@192.168.1.245:5060> Call-ID: NTQyYWM3M2FlMWFjOTAyMjMwMDRiYzZiZTJlZTUxMWU. CSeq: 1 INVITE User-Agent: Grandstream GXW4104 (HW 0001, Ch:0) 1.0.0.55 Content-Length: 0
    08-13-2007 18:55:55 User.Info 192.168.1.245 GS_LOG: [00:0B:82:0D:C7:4F][000][FF50][01000037] 683 sip.c Sess: 0 Send SIP message: 100 To 192.168.1.250:5060
    08-13-2007 18:55:55 User.Info 192.168.1.245 GS_LOG: [00:0B:82:0D:C7:4F][000][FF50][01000037] fxo_ctl.c 166 Port:0 DAA Pickup 2
    08-13-2007 18:55:55 User.Info 192.168.1.245 GS_LOG: [00:0B:82:0D:C7:4F][000][FF50][01000037] fxo_ctl.c 243 Port:0 DAA LS: 1 CS: 0
    08-13-2007 18:55:55 User.Info 192.168.1.245 GS_LOG: [00:0B:82:0D:C7:4F][000][FF50][01000037] 1463 sip.c Received SIP message: 2 Acc:0


    This is for the 3CX:

    17:57:45.281 StratInOut::eek:nHangUp [CM104007] Call(169): Call from Ext.100 to 305XXXXXXX has been terminated by Ext.100; cause: CANCEL; from IP:192.168.1.100 (HERE I HUNG UP)
    17:57:02.578 CallConf::eek:nIncoming [CM103002] Call(169): Incoming call from 100 (Ext.100) to sip:9305XXXXXXX@192.168.1.250
    17:56:51.000 StratLink::eek:nHangUp [CM104001] Call(168): Ext.100 hung up call; cause: BYE; from IP:192.168.1.100
    17:56:47.875 CallLegImpl::eek:nConnected [CM103001] Call(168): Created audio channel for Ln:10000@GXW4104 (192.168.1.245:5020) with third party (192.168.1.100:5004)
    17:56:47.875 StratInOut::eek:nConnected [CM104005] Call(168): Setup completed for call from Ext.100 to Ln:10000@GXW4104
    17:56:47.875 CallLegImpl::eek:nConnected [CM103001] Call(168): Created audio channel for Ext.100 (192.168.1.100:5004) with third party (192.168.1.245:5020)
    17:56:47.875 CallConf::eek:nProvisional [CM103003] Call(168): Ln:10000@GXW4104 is ringing
    17:56:44.718 CallConf::eek:nIncoming [CM103002] Call(168): Incoming call from 100 (Ext.100) to sip:9786XXXXXXX@192.168.1.250


    I really hope somebody can help me I'm a newbie with this kind of systems.

    THANK YOU GUYS!!!!!
     
  2. technicalpc

    Joined:
    Jun 25, 2007
    Messages:
    12
    Likes Received:
    0
    As I see seem that not much people know about this problem, I've contacted grandstream and this is what they told me:
    "According to country to are currently located please verify that your FXO lines characteristics configured properly with PSTN line(AC termination impedance),I also recommend you to configure parameter Wait for Dial-Tone(Y/N):to Y, and Min Delay Before Dial PSTN: to 300."

    All done and is the same... :cry:
     
  3. Nick Galea

    Nick Galea Site Admin

    Joined:
    Jun 6, 2006
    Messages:
    1,733
    Likes Received:
    44
    Hi,

    Thanks for your nice feedback :)

    We use a grandstream here and it works out of the box. If it works some times and some times not, i get the impression it might be a hardware failure or else some problem with the line itself. Any chance of trying it with a second one or with another line, for example at home or something?
     
  4. technicalpc

    Joined:
    Jun 25, 2007
    Messages:
    12
    Likes Received:
    0
    I'll try bringing the system @ home to check there. I'll let you know.
    Thanks.
     
  5. slinc

    Joined:
    Aug 7, 2007
    Messages:
    37
    Likes Received:
    0
    technicalpc,

    I am having a similar problem. Everything works fine for a while and then suddenly I am unable to place outbound calls. Inbound works fine. I am also using a Grandstream gateway also.

    In order to get it to work again I have to reboot the Grandstream gateway.

    If you find a solution please post it on this forum. Thanks.
     
  6. tjabaut

    tjabaut New Member

    Joined:
    Jul 24, 2007
    Messages:
    138
    Likes Received:
    0
    I am having a similar problem but with an AudioCodes gateway.

    I believe the problem lies in having only 3 line but all four configured in 3cx. If 3cx uses a round robin it may try to pick the forth line that actually does not have a line attached to it.

    I am not sure as we are using different equipment, but in my testing this fixed my problem.
     
  7. technicalpc

    Joined:
    Jun 25, 2007
    Messages:
    12
    Likes Received:
    0
    Hi tjabaut,

    I've already made these configuration with 2, 3 and 4 fxo registered, and the results were the same.

    I had similar problems too, but in Grandstream you can add this line in "Round-robin and/or Flexible:" which is "rr:1;rr:2;rr:3;rr:4;", this solved my problem with Round-Robin going backwards.

    I can tell that I'm testing the system at home and so far is working perfectly (I just can't hear my voice speaking thru the gxp2000, but it could be the router and is not the problem I'm testing), I've placed like 10 calls with no problem. So, tomorrow I'm going to change the switch and/or cabling new fxo lines just to make sure if any of these two may be. I'll keep you guys posted.

    ...and thanks a lot for the replies.
     
  8. namster

    Joined:
    Sep 15, 2007
    Messages:
    4
    Likes Received:
    0
    Problem with GXW4104 when making outbound calls

    I have the same problem making outbound calls with the GXW4104 unit. I have 4 pstn lines connected to this unit. It happens imtermittently....I have the latest firmware: 1.0.1.2 and the problem still exists.

    Please help!
    Thank You
     

Share This Page