linphone-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Linphone-users] Linphone SIP registration stopped working - DNS pro


From: sebalis
Subject: Re: [Linphone-users] Linphone SIP registration stopped working - DNS problem (or not)
Date: Mon, 30 Jan 2017 17:37:17 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0

On 2017-01-30 17:07, Russell Treleaven wrote:
217.10.68.152 stun.sipgate.net <http://stun.sipgate.net>
217.10.79.9 sipgate.de <http://sipgate.de>

Thank you! With these changes, Linphone can use this account. It does not work for the other two SIP accounts (unsurprisingly). If this helps, here is the debug output:

[...]
message: 2017-01-30 17:27:45:656 New local ip address is 10.1.0.100
message: 2017-01-30 17:27:45:656 SIP network reachability state is now [UP]
message: 2017-01-30 17:27:45:656 Resolver is using DNS server(s):
message: 2017-01-30 17:27:45:656        10.1.0.1
message: 2017-01-30 17:27:45:656 No SRV result for 
[_stun._udp.stun.sipgate.net], trying A/AAAA.
message: 2017-01-30 17:27:45:656 Resolver is using DNS server(s):
message: 2017-01-30 17:27:45:656        10.1.0.1
message: 2017-01-30 17:27:45:656 stun.sipgate.net resolved to 217.10.68.152
message: 2017-01-30 17:27:45:656 Stun server resolution successful.
message: 2017-01-30 17:27:45:656 Media network reachability state is now [UP]
message: 2017-01-30 17:27:45:656 LinphoneProxyConfig [0x1408b70] about to 
register (LinphoneCore version: 3.10.2)
message: 2017-01-30 17:27:45:659 belle_sip_client_transaction_send_request(): 
waiting channel to be ready
message: 2017-01-30 17:27:45:659 channel [0x151f040]: starting resolution of 
sipgate.de
message: 2017-01-30 17:27:45:659 channel 0x151f040: state RES_IN_PROGRESS
message: 2017-01-30 17:27:45:659 transaction [0x1515670] channel state changed 
to [RES_IN_PROGRESS]
message: 2017-01-30 17:27:45:659 Resolver is using DNS server(s):
message: 2017-01-30 17:27:45:659        10.1.0.1
message: 2017-01-30 17:27:45:660 No SRV result for [_sip._udp.sipgate.de], 
trying A/AAAA.
message: 2017-01-30 17:27:45:660 Resolver is using DNS server(s):
message: 2017-01-30 17:27:45:660        10.1.0.1
message: 2017-01-30 17:27:45:660 sipgate.de resolved to 217.10.79.9
message: 2017-01-30 17:27:45:660 channel 0x151f040: state RES_DONE
message: 2017-01-30 17:27:45:660 transaction [0x1515670] channel state changed 
to [RES_DONE]
message: 2017-01-30 17:27:45:660 channel 0x151f040: state CONNECTING
message: 2017-01-30 17:27:45:660 transaction [0x1515670] channel state changed 
to [CONNECTING]
message: 2017-01-30 17:27:45:660 Trying to connect to [UDP://217.10.79.9:5060]
message: 2017-01-30 17:27:45:660 belle_sip_get_src_addr_for(): af_inet6=0
message: 2017-01-30 17:27:45:660 Channel has local address 10.1.0.100:5060
message: 2017-01-30 17:27:45:660 channel 0x151f040: state READY
message: 2017-01-30 17:27:45:660 transaction [0x1515670] channel state changed 
to [READY]
message: 2017-01-30 17:27:45:660 Changing [client] [REGISTER] transaction 
[0x1515670], from state [INIT] to [TRYING]
message: 2017-01-30 17:27:45:660 channel [0x151f040]: message sent to 
[UDP://sipgate.de:5060], size: [527] bytes

This is followed by the contents of a SIP register request, but as the connection works (I successfully did a test call) you surely don’t need to see it. The debug log always had messages for the other two accounts with errors matching the previous one for sipgate, and these errors are of course still there.

sebalis
(Offline in 10 minutes, back two hours after that)




reply via email to

[Prev in Thread] Current Thread [Next in Thread]