Bad BUG on new version??

[Urbok]

I use 3cx with Italian Eutelia SIP voip provider. (http://www.euteliavoip.com)
I've upgraded to the latest version and now I have a problema with my voip registrered lines.

Some minutes after the correct registration (green light) the account goes to red and the log file says:
00:33:41.762 ClientRegs:nFailure [CM113010] Next registration will be attempted in 10 minutes
00:33:41.762 ClientRegs:nFailure [CM113006] Registration of sip:[email protected] has failed; reason=Service Unavailable
00:33:41.732 ClientRegs:nFailure [CM113010] Next registration will be attempted in 10 minutes
00:33:41.732 ClientRegs:nFailure [CM113006] Registration of sip:[email protected] has failed; reason=Service Unavailable
00:33:41.712 ClientRegs:nFailure [CM113010] Next registration will be attempted in 10 minutes
00:33:41.712 ClientRegs:nFailure [CM113006] Registration of sip:[email protected] has failed; reason=Service Unavailable
00:33:41.682 ClientRegs:nFailure [CM113010] Next registration will be attempted in 10 minutes
00:33:41.682 ClientRegs:nFailure [CM113006] Registration of sip:[email protected] has failed; reason=Service Unavailable
00:33:41.682 ClientRegs:nFailure [CM113010] Next registration will be attempted in 10 minutes
00:33:41.682 ClientRegs:nFailure [CM113006] Registration of sip:[email protected] has failed; reason=Service Unavailable
00:33:41.682 ClientRegs:nFailure [CM113010] Next registration will be attempted in 10 minutes
00:33:41.682 ClientRegs:nFailure [CM113006] Registration of sip:[email protected] has failed; reason=Service Unavailable
00:33:41.672 ClientRegs:nFailure [CM113010] Next registration will be attempted in 10 minutes
00:33:41.672 ClientRegs:nFailure [CM113006] Registration of sip:[email protected] has failed; reason=Service Unavailable


the strange thing is that these accounts works perfect !!! the light is red and the log say that a new registation attempt is done in 10 mins (reason=Service Unavailable)

This after the upgrade to the new version of 3 august.
I've also tried a new installation but nothing changed.
The accounts keep going in this strange offline status (works perfect if you call from inside and if you to call from outside.)

let me know because this is a bad bad thing.

 

[Ralph]

Odd

I want to make certain I understand this:

You are saying that even though the status lights for the lines show red, you can still make and recieve calls on them?

If so, does the light remain red even when they are in use?

Take care

 

[Urbok]

Yes. the light remain red and during conversation become orange as usual.

 

[SY]

Yes. the light remain red and during conversation become orange as usual.

1. It is up to provider to deliver calls even if response for registration request is marked as unsuccessful.
2. You can make call without registration.

Is there any additional information?

Thanks,
Stepan

 

[Cjay]

Yes. the light remain red and during conversation become orange as usual

I have seen the same sort of thing yesterday - VoIP Line indicating red but VoIP calls still working fine. I'm on version 3.1.2434.0 but did once see the same symptom on an earlier version so it may not be a bug in the new version. A manual 'Register the line' fixed it. I use VoipDiscount as my VoIP provider.

The only possible anomaly I can see in the 3cxPhoneSystemTrace at around the time the indicator may have gone red is this:

00:44:25.879|ClientRegistration.cxx(234)|Trace5|Resip|>>:requesting refresh of ClientRegistration sip:[email protected]
00:44:58.085|DialogUsageManager.cxx(1190)|Trace5|Resip|>>:Got: SipResp: 408 tid=ff64871a78754c63 cseq=REGISTER / 59 from(wire)
00:44:58.186|TuSelector.cxx(70)|Trace5|Resip|>>:Stats message
00:44:58.516|.\Registrar.cpp(460)|Trace5|Registrar|ClientRegs:nRequestRetry:Reg. request-retry: h=2; code=408
00:44:58.516|.\Registrar.cpp(469)|Trace5|Registrar|ClientRegs:nRequestRetry:ADS: hReg=2; attempt=0
00:44:58.516|.\CallEvents.cpp(78)|Trace5||FireStatusEvent:Fire event: Undefined; DN 10001
00:44:58.516|.\Registrar.cpp(477)|Log2|Registrar|ClientRegs:nRequestRetry:[CM113008] Registration attempt for Ln:10001@VoIPDiscount is scheduled in 120 sec.
00:45:58.142|TuSelector.cxx(70)|Trace5|Resip|>>:Stats message
00:46:54.753|.\StunClient.cpp(79)|Trace5|STUN|StunClient:rocess:STUN response received from 192.245.12.229
00:46:58.158|TuSelector.cxx(70)|Trace5|Resip|>>:Stats message
00:46:58.789|DialogUsageManager.cxx(1190)|Trace5|Resip|>>:Got: SipResp: 200 tid=b06aee4819094761 cseq=REGISTER [email protected]:5060 / 60 from(wire)
00:46:58.789|ClientRegistration.cxx(327)|Trace5|Resip|>>:Clearing service route ([])

[xxxxx is my SIP user registration and aaa.bbb.ccc.ddd is my IP]

Of course this may be a complete red herring but its the only anomalous registration attempt in the right sort of timeframe.

Cjay

 

[harry68]

Hi,

i have exactly the same problem with sipgate.at. It seems that 3CX generates for each registration attempt a new sip id. The service provider identifies the “new” sip id as new SIP end node (phone). After 50 registration with different phones – well it always the same line from 3CX point of view, but a new device for sipgate.at – registration will be rejected. A sip id should be unique, but should not change during registration renewal or reregistration if it is physically the same device or line.

Yes. the light remain red and during conversation become orange as usual

I have seen the same sort of thing yesterday - VoIP Line indicating red but VoIP calls still working fine. I'm on version 3.1.2434.0 but did once see the same symptom on an earlier version so it may not be a bug in the new version. A manual 'Register the line' fixed it. I use VoipDiscount as my VoIP provider.

The only possible anomaly I can see in the 3cxPhoneSystemTrace at around the time the indicator may have gone red is this:

00:44:25.879|ClientRegistration.cxx(234)|Trace5|Resip|>>:requesting refresh of ClientRegistration sip:[email protected]
00:44:58.085|DialogUsageManager.cxx(1190)|Trace5|Resip|>>:Got: SipResp: 408 tid=ff64871a78754c63 cseq=REGISTER / 59 from(wire)
00:44:58.186|TuSelector.cxx(70)|Trace5|Resip|>>:Stats message
00:44:58.516|.\Registrar.cpp(460)|Trace5|Registrar|ClientRegs:nRequestRetry:Reg. request-retry: h=2; code=408
00:44:58.516|.\Registrar.cpp(469)|Trace5|Registrar|ClientRegs:nRequestRetry:ADS: hReg=2; attempt=0
00:44:58.516|.\CallEvents.cpp(78)|Trace5||FireStatusEvent:Fire event: Undefined; DN 10001
00:44:58.516|.\Registrar.cpp(477)|Log2|Registrar|ClientRegs:nRequestRetry:[CM113008] Registration attempt for Ln:10001@VoIPDiscount is scheduled in 120 sec.
00:45:58.142|TuSelector.cxx(70)|Trace5|Resip|>>:Stats message
00:46:54.753|.\StunClient.cpp(79)|Trace5|STUN|StunClient:rocess:STUN response received from 192.245.12.229
00:46:58.158|TuSelector.cxx(70)|Trace5|Resip|>>:Stats message
00:46:58.789|DialogUsageManager.cxx(1190)|Trace5|Resip|>>:Got: SipResp: 200 tid=b06aee4819094761 cseq=REGISTER [email protected]:5060 / 60 from(wire)
00:46:58.789|ClientRegistration.cxx(327)|Trace5|Resip|>>:Clearing service route ([])

[xxxxx is my SIP user registration and aaa.bbb.ccc.ddd is my IP]

Of course this may be a complete red herring but its the only anomalous registration attempt in the right sort of timeframe.

Cjay

 

[aorlando]

Same problem here

It's since the last version of 3CX I had this problem with Eutelia VOIP alias SKYPHO.

I though to be the only in this situation.

In august I sent to 3CX Technical Support
SKYPHO credentials to test the problem and still they didn't answer me.

 

[nb]

This is not really a 3CX bug. It is a common feature practiced in the VOIP industry.

have you ever seen this sort of configuration in gateways -

<<Make call without registration>> and
<<Answer call without registration>>?

Linksys devices have this exact notation in their configuration.

Best Regards

 

[N_G]

Eutelia/Skypho is not a supported provider. You must be sure to use a supported provider.