Ring once then fails (487 Request Terminated) - Intermittent

[Sambo]

Good evening,
I seem to be having an intermittent problem - maybe 3 times a day on average, where my phones will ring once but then the phones stop ringing, the call will then ring on a mobile (cell phone - for the Americans) and be able to be answered.
(Our Voip provider, Engin (Australian), has a setting for calls to be diverted to another number if there is no Voip registration)

My setup is:
- 3cx V10 SP4
- Running on Vista
- 3x SPA-942 (Firmware 6.1.5.a)

Here is the log for one of the calls in question:

16:06:15.853 [CM506001]: STUN request to resolve SIP external IPort mapping is sent to STUN server [ V4 96.9.132.83:3478 UDP target domain=unspecified mFlowKey=0 ] over Transport [ V4 192.168.0.5:5060 UDP target domain=unspecified mFlowKey=0 ]
16:06:03.958 [CM503003]: Call(38): Call to sip:[email protected] has failed; Cause: 487 Request Terminated; from IP:192.168.0.6:5060
16:06:03.954 [CM503003]: Call(38): Call to sip:[email protected] has failed; Cause: 487 Request Terminated; from IP:192.168.0.4:5060
16:06:03.856 [CM503008]: Call(38): Call is terminated
16:06:00.761 Currently active calls - 1: [38]
16:05:58.291 [CM505001]: Ext.102: Device info: Device Identified: [Man: Linksys;Mod: SPA series;Rev: General] Capabilities:[reinvite, no-replaces, able-no-sdp, recvonly] UserAgent: [Linksys/SPA942-6.1.5(a)] PBX contact: [sip:[email protected]:5060]
16:05:58.291 [CM503002]: Call(38): Alerting sip:[email protected]:5060
16:05:58.283 [CM505001]: Ext.101: Device info: Device Identified: [Man: Linksys;Mod: SPA series;Rev: General] Capabilities:[reinvite, no-replaces, able-no-sdp, recvonly] UserAgent: [Linksys/SPA942-6.1.5(a)] PBX contact: [sip:[email protected]:5060]
16:05:58.283 [CM503002]: Call(38): Alerting sip:[email protected]:5060
16:05:58.214 [CM503025]: Call(38): Calling RingAll800[Ext.101,Ext.102]@[Dev:sip:[email protected]:5060]
16:05:58.207 [CM503025]: Call(38): Calling RingAll800[Ext.101,Ext.102]@[Dev:sip:[email protected]:5060]
16:05:58.154 [CM503004]: Call(38): Route 1: RingAll800[Ext.101,Ext.102]@[Dev:sip:[email protected]:5060,Dev:sip:[email protected]:5060]
16:05:58.153 [CM503010]: Making route(s) to <sip:[email protected]:5060>
16:05:58.150 [CM505003]: Provider:[Engin - AU] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [] PBX contact: [sip:[email protected]:5060]
16:05:58.147 [CM503001]: Call(38): Incoming call from 0424195895@(Ln.10000@Engin - AU) to <sip:[email protected]:5060>
16:05:57.853 [CM503012]: Inbound out-of-office hours rule (unnamed) for 10000 forwards to DN:800

If somebody could assist in why this could be occurring it would be much appreciated!

Thanks,
Sam

 

[Felixcat]

Re: Ring once then fails (487 Request Terminated) - Intermit

I'm having this problem too - system will work fine but the occasionally phones will ring 2-3 times then call is dropped. Clling party hears ringing tone then a long hum then of course they hang up as the call is disconnected. I have tried a SPA 3102 as my pstn gateway and due to echo problems as well as this issue I switched to Grandstream GXW4104 which made no difference to the dropped calls. Looking at the log the calls successfully reach the extensions but then are rejected with code 487. My pstn is Virgin Media (UK) and I have read this issue could be caused by incompatible CLI info being sent by the pstn provider. My CLI works faultlessly every time even on the dropped calls it's displayed on the handsets (a mixture of Grandstream and Snom M9). I guess the next step would be to disable CLI at the GXW4104 but this is a najoir plus for the system and if it won't display CLI might well lead to me looking for another system. I'm running 3cx version 10 with service pack 4 build 22052 on a Windows 7 machine. Grandstream GXW4101 is running 1.3.4.10 software as suggested by 3cx.

Any help would be appreciated!

 

[leejor]

Re: Ring once then fails (487 Request Terminated) - Intermit

The only other thing that I would try myself...is to change (remove temporarily) the extensions in the ring group, one at a time, and try changing the outside destination, perhaps sent the call to voicemail or another extension instead for testing.

Intermittent issues are very difficult to track down, and are the cause of much hair pulling. You just have to keep changing the variables around until the problem stops. Once you remove or change something that "corrects" the problem, and you can confirm that by putting things back the way they were, then you have to determine why that is causing the problem, some other conflicting setting?