Linphone SIP Settings

All about WTware on Raspberry. Wtware works with Raspberry Pi 3 Model B and Pi 2 Model B devices
http://www.winterminal.com
cody.duncan
Posts: 6
Joined: Tue May 23, 2017 4:06 am

Linphone SIP Settings

Postby cody.duncan » Tue May 23, 2017 4:19 am

Hello!
I am trying to setup the sip settings, and make a call. I am inputting the correct server IP, user and password but I am unable to make a call. My configuration file value is

Code: Select all

SIP=718503:PASSWORD@52.11.206.***, port:5060
***= the last 3 values in the IP.

Here is a snip from the error log when the call failed:

Code: Select all

17-32-28-961| [           SIP] [  658.240255] Call 1 with sip:7185@52.11.206.*** error.
17-32-28-965| [           SIP] [  658.240268] 2017-04-16 00:10:55:268 ortp-message-Linphone core [0x16764c0] notifying [call_state_changed]
17-32-28-966| [           SIP] [  658.240283] 2017-04-16 00:10:55:268 ortp-message-Call 0x1678368: moving from state LinphoneCallError to LinphoneCallReleased
17-32-28-970| [           SIP] [  658.240296] 2017-04-16 00:10:55:268 ortp-message-Linphone core [0x16764c0] notifying [call_state_changed]
17-32-28-970| [           SIP] [  658.240307] 2017-04-16 00:10:55:268 ortp-message-Call [0x1678368] freed.
17-32-28-974| [           SIP] [  658.240318] 2017-04-16 00:10:55:268 ortp-message-op [0x1679830] : set_or_update_dialog() current=[(nil)] new=[(nil)]
17-32-28-975| [           SIP] [  658.240330] 2017-04-16 00:10:55:268 ortp-message-Changing [client] [INVITE] transaction [0x1679720], from state [CALLING] to [TERMINATED]
17-32-28-978| [           SIP] [  658.240342] 2017-04-16 00:10:55:268 ortp-message-Client INVITE transaction [0x1679720] terminated
17-32-28-979| [           SIP] [  658.240353] 2017-04-16 00:10:55:268 ortp-message-Destroying op [0x1679830] of type [SalOpCall]
17-32-28-981| [           SIP] [  658.240364] 2017-04-16 00:10:55:268 ortp-message-transaction [0x1678fe8] channel state changed to [ERROR]
17-32-28-981| [           SIP] [  658.240375] 2017-04-16 00:10:55:268 ortp-message-Refresher: scheduling next timer in 60000 ms
17-32-28-984| [           SIP] [  658.240493] 2017-04-16 00:10:55:268 ortp-message-Register refresher [503] reason [io error] for proxy [sip:52.11.206.***:5060]
17-32-28-985| [           SIP] [  658.240507] Registration on sip:52.11.206.***:5060 failed: io error
17-32-28-987| [           SIP] [  658.240520] linphonec> 2017-04-16 00:10:55:268 ortp-message-Linphone core [0x16764c0] notifying [display_status]
17-32-28-987| [           SIP] [  658.240531] 2017-04-16 00:10:55:268 ortp-message-Refresher: scheduling next timer in 2000 ms
17-32-28-989| [           SIP] [  658.240541] 2017-04-16 00:10:55:268 ortp-message-Register refresher [408] reason [timeout] for proxy [sip:52.11.206.***:5060]
17-32-28-990| [           SIP] [  658.240554] Registration on sip:52.11.206.***:5060 failed: timeout
17-32-28-992| [           SIP] [  658.240564] linphonec> 2017-04-16 00:10:55:268 ortp-message-Linphone core [0x16764c0] notifying [display_status]
17-32-28-993| [           SIP] [  658.240580] 2017-04-16 00:10:55:268 ortp-message-Changing [client] [REGISTER] transaction [0x1678fe8], from state [TRYING] to [TERMINATED]
17-32-28-995| [           SIP] [  658.240591] 2017-04-16 00:10:55:268 ortp-message-Client internal REGISTER transaction [0x1678fe8] terminated
17-32-28-995| [           SIP] [  658.240655] 2017-04-16 00:10:55:269 ortp-message-Transaction [0x1679720] deleted
17-32-28-997| [            gm] [  658.241669] linphonec state LinphoneCallReleased id 1.
17-32-30-889| [           SIP] [  660.253703] 2017-04-16 00:10:57:282 ortp-message-Channel [0x16c3200] destroyed
17-32-30-896| [           SIP] [  660.253841] 2017-04-16 00:10:57:282 ortp-message-Transaction [0x1678fe8] deleted
17-32-30-897| [           SIP] [  660.253906] 2017-04-16 00:10:57:282 ortp-message-belle_sip_client_transaction_send_request(): waiting channel to be ready
17-32-30-907| [           SIP] [  660.253922] 2017-04-16 00:10:57:282 ortp-message-channel [0x16c3200]: starting resolution of 52.11.206.***
17-32-30-908| [           SIP] [  660.253965] 2017-04-16 00:10:57:282 ortp-message-channel 0x16c3200: state RES_IN_PROGRESS
17-32-30-915| [           SIP] [  660.253977] 2017-04-16 00:10:57:282 ortp-message-transaction [0x169d9c0] channel state changed to [RES_IN_PROGRESS]
17-32-30-917| [           SIP] [  660.254018] 2017-04-16 00:10:57:282 ortp-message-channel 0x16c3200: state RES_DONE
17-32-30-924| [           SIP] [  660.254030] 2017-04-16 00:10:57:282 ortp-message-transaction [0x169d9c0] channel state changed to [RES_DONE]
17-32-30-926| [           SIP] [  660.254073] 2017-04-16 00:10:57:282 ortp-message-channel 0x16c3200: state CONNECTING
17-32-30-929| [           SIP] [  660.254085] 2017-04-16 00:10:57:282 ortp-message-transaction [0x169d9c0] channel state changed to [CONNECTING]
17-32-30-930| [           SIP] [  660.254126] 2017-04-16 00:10:57:282 ortp-message-Trying to connect to [UDP://52.11.206.***:5060]
17-32-30-935| [           SIP] [  660.254250] 2017-04-16 00:10:57:282 ortp-message-Channel has local address 192.168.1.241:5060
17-32-30-936| [           SIP] [  660.254265] 2017-04-16 00:10:57:282 ortp-message-channel 0x16c3200: state READY
17-32-30-943| [           SIP] [  660.254340] 2017-04-16 00:10:57:282 ortp-message-transaction [0x169d9c0] channel state changed to [READY]
17-32-30-944| [           SIP] [  660.254354] 2017-04-16 00:10:57:282 ortp-message-Changing [client] [REGISTER] transaction [0x169d9c0], from state [INIT] to [TRYING]
17-32-30-950| [           SIP] [  660.254889] 2017-04-16 00:10:57:283 ortp-message-channel [0x16c3200]: message sent to [UDP://52.11.206.***:5060], size: [542] bytes
17-32-30-951| [           SIP] [  660.254905] REGISTER sip:52.11.206.*** SIP/2.0
17-32-30-957| [           SIP] [  660.254916] Via: SIP/2.0/UDP 192.168.1.241:5060;branch=z9hG4bK.ImZ9UoJUh;rport
17-32-30-958| [           SIP] [  660.254929] From: <sip:718503@52.11.206.***>;tag=0ftnTacuX
17-32-30-960| [           SIP] [  660.254940] To: sip:718503@52.11.206.***
17-32-30-961| [           SIP] [  660.254951] CSeq: 39 REGISTER
17-32-30-964| [           SIP] [  660.254961] Call-ID: kXKLM1IGip
17-32-30-964| [           SIP] [  660.254971] Max-Forwards: 70
17-32-30-968| [           SIP] [  660.254981] Supported: replaces, outbound
17-32-30-969| [           SIP] [  660.254991] Accept: application/sdp
17-32-30-971| [           SIP] [  660.255001] Accept: text/plain
17-32-30-972| [           SIP] [  660.255012] Accept: application/vnd.gsma.rcs-ft-http+xml
17-32-30-974| [           SIP] [  660.255023] Contact: <sip:718503@192.168.1.241;transport=udp>;+sip.instance="<urn:uuid:1a8fe48d-3dbb-44e9-9ddb-7244a83b6647>"
17-32-30-975| [           SIP] [  660.255036] Expires: 3600
17-32-30-978| [           SIP] [  660.255047] User-Agent: Linphonec/3.10.2 (belle-sip/1.5.0)


All help is appreciated!

akatik
SUPPORT
SUPPORT
Posts: 124
Joined: Mon Jan 17, 2005 6:30 pm
Contact:

Re: Linphone SIP Settings

Postby akatik » Tue May 23, 2017 10:23 am

Did you specify gateway ip? Show full log.

cody.duncan
Posts: 6
Joined: Tue May 23, 2017 4:06 am

Re: Linphone SIP Settings

Postby cody.duncan » Tue May 23, 2017 12:27 pm

akatik wrote:Did you specify gateway ip? Show full log.

The Full log is too large to post, so here is a drop box link:
https://www.dropbox.com/s/baim888z6dgc5t3/WTware_B8.27.EB.C6.EB.C9_2017-05-22_17-32-34.txt?dl=0

I don't know what you mean by gateway IP. I filled out all the settings in the sip section.
Screenshot 2017-05-23 02.25.36.png
Screenshot 2017-05-23 02.25.36.png (57.75 KiB) Viewed 556 times

aka
SUPPORT
SUPPORT
Posts: 554
Joined: Fri Dec 03, 2004 2:05 pm
Contact:

Re: Linphone SIP Settings

Postby aka » Tue May 23, 2017 12:44 pm

Gateway IP is not linphone. It's general TCP/IP network setting. As far as I understand, your terminal has no network access to SIP server:

Registration on sip:52.11.206.168:5060 failed: io error
..
Registration on sip:52.11.206.168:5060 failed: timeout


PS: there are plain text passwords for SIP and for RDP in log. Replace them and send logs to support@wtware.com next time.

cody.duncan
Posts: 6
Joined: Tue May 23, 2017 4:06 am

Re: Linphone SIP Settings

Postby cody.duncan » Tue May 23, 2017 7:11 pm

EDIT: Nevermind, I figured it out. When using DHCP from the wtconfig, it does not set the network gateway. I was unaware of this. How do I configure it to do so?

By gateway, do you mean the "Server" setting?
If so, does that mean I cannot connect to my Asterisk server?

Unless you mean the general gateway, if so, yes. It is 192.168.1.1 and is configured.

aka
SUPPORT
SUPPORT
Posts: 554
Joined: Fri Dec 03, 2004 2:05 pm
Contact:

Re: Linphone SIP Settings

Postby aka » Tue May 23, 2017 9:00 pm

cody.duncan wrote:Unless you mean the general gateway, if so, yes. It is 192.168.1.1 and is configured.

Yes, general gateway. By default, WTware DHCP thinks gateway is a machine where WTware DHCP is running. Change it:
Untitled.png
Untitled.png (46.27 KiB) Viewed 545 times


Return to “WTware on Raspberry Pi 3 / Raspberry Pi 2”

Who is online

Users browsing this forum: No registered users and 2 guests