It's a current bug introduced by the decision to go TCP for internal
communications. This means conneciton from proxy to registrar will
remain TCP. however, since bria set the transport=tls explicitly, it
escaped checking and attempted to go out TLS from proxy to registrar.
Open a jira and assign to me please. Thanks.
On 07/12/2012 05:51 PM, Kumaran wrote:
On 7/12/2012 3:19 PM, Mircea Carasel wrote:
On Thu, Jul 12, 2012 at 12:32 PM, Kumaran
<[email protected]
<mailto:[email protected]>> wrote:
Hi All,
We can't able to register Bria through TLS....Please check
the attached logs
I see in the bria log:
[12-07-12]14:44:42.698 | 3920 | Debug | CCM | "[state:EState_Ready][T|T]
[URI:[email protected]
<mailto:uri%[email protected]>]" |
sua::CSIPAccess::OnRegistrationTimedoutRecommendingDUMRestart
[12-07-12]14:44:42.698 | 1960 | Warning | AbstractPhone | "SIP registration failed;
reason: 'SipError'; SIP error-code: 408; error-phrase: 'Request Timeout'" |
cpsi::AccountImpl::OnRegistrationStatusChanged
[12-07-12]14:44:42.698 | 3920 | Debug | CCM |
"[state:EState_Ready][T|T] [URI:[email protected]
<mailto:uri%[email protected]>]" |
sua::CSIPAccess::DoWorkForRestartDUMEvent
This is a request timed out error, does not look to be related to TLS
itself.
I assume you used sipxecs bria login URL in bria login screen, right?
That went through, logged you in and then tried to register user 207,
is this correct?
Mircea
Hi Mircea,
Yes,you are right...But I can Register Bria either through UDP/TCP.....
Regards,
Kumaran T
_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev/
_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev/
