Inbound call problems

Status
Not open for further replies.

yaquaholic

Joined
Apr 17, 2013
Messages
5
Reaction score
0
Hello fellow users,

I recently started in a new position and one of my responsibilities is to look after the Grandstream VOIP/PSTN 3CX setup we have here. Anyway first day on the job and the phones system starts playing up, any caller dialing our PSTN line does not connect, but dialing the VOIP number does. On the GXW4104 we can see the line go "Line 1: busy Connected, idle" and we're hearing the ringtone as we dial in, but then the GXW4104 drops back to "Line 1: Connected, idle", but the ringtone keeps going on the phone we dial from.

The chap who implemented the system left a nice PDF detailing the config of our GXW4104, that was working fine, until the day I arrived. Typically they would just restart the GXW4104 and all would be sorted, but not on this Monday morning.I have checked this against the device's config and all looks identical. We have tried getting 3CX Phone System to create the configuration, but no joy here.

So could I ask some assistance from the forum group to possibly point a finger in the right direction to where I(we) are going wrong please? Below are screenshots from the various config pages that might help...










Any ideas?

Many thanks - yaquaholic
 

Attachments

  • Status.JPG
    Status.JPG
    61.4 KB · Views: 575
  • BasicSettings.jpg
    BasicSettings.jpg
    170.7 KB · Views: 574
  • AdvancedSettings.jpg
    AdvancedSettings.jpg
    178.2 KB · Views: 574
  • Channels.JPG
    Channels.JPG
    140.4 KB · Views: 574
  • DialPlan.JPG
    DialPlan.JPG
    63.4 KB · Views: 574
  • FXO-Lines-1.JPG
    FXO-Lines-1.JPG
    64.2 KB · Views: 574
  • FXO-Lines-2.JPG
    FXO-Lines-2.JPG
    106 KB · Views: 574
  • Profile1.JPG
    Profile1.JPG
    141.1 KB · Views: 574
Re: Intermittent outward bound VOIP call problems

Some more screen shots...




Thanks.
 

Attachments

  • Profile2.JPG
    Profile2.JPG
    143.4 KB · Views: 574
  • 3CX-Status.JPG
    3CX-Status.JPG
    39.4 KB · Views: 574
do the log files or system logs show anything of consequence?
 
The only thing that stands out is:
Code:
18-Apr-2013 18:19:20.615   [CM503003]: Call(C:197): Call to <sip:[email protected]:5060> has failed; Cause: 487 Request Terminated/INVITE from 192.168.1.23:5060
18-Apr-2013 18:19:20.615   Session 145053 has failed in leg L:197.3[Extn] ; Cause: 487 Request Terminated/INVITE from 192.168.1.23:5060
18-Apr-2013 18:19:20.595   L:197.5[Extn]: Terminating targets, reason: SIP ;cause=487 ;text="Request Terminated"
18-Apr-2013 18:19:20.595   Leg L:197.5[Extn] is terminated: Cause: 487 Request Terminated/INVITE from 192.168.1.22:5060
18-Apr-2013 18:19:20.595   L:197.5[Extn] got Terminated Recv 487/INVITE from 192.168.1.22:5060 tid=7f6962321e5db502 Call-ID=ZmUyNTk4NmEyYjVlYjdjMTU0NGY3YjM4YmNmODYyNjk.:
SIP/2.0 487 Request Terminated

Does anyone know what Cause 487 might mean?

Thanks.
 
487= Request Terminated ...Request has terminated by bye or cancel

It doesn't tell you much, unfortunately.

I'm not sure what this has to do with the gateway as it is a failed call between extensions.
 
Status
Not open for further replies.