Author Topic: Troubleshooting: YateBTS + bladeRF + Raspbery Pi 3  (Read 3887 times)

wright3189

  • Newbie
  • *
  • Posts: 9
    • View Profile
Troubleshooting: YateBTS + bladeRF + Raspbery Pi 3
« on: April 20, 2016, 06:29:20 PM »
Having some trouble getting YateBTS running on Raspberry Pi 3 with the bladeRF x40. I've followed this guide precisely: https://github.com/Nuand/bladeRF/wiki/Setting-up-Yate-and-YateBTS-with-the-bladeRF, but I keep getting a transceiver error. I have it working fine on my laptop, but I need it working on the Pi.

2016-04-20_23:49:09.359643 <mbts:NOTE> TRXManager.cpp:88:sendCommandPacket: TRX link timeout on attempt 1
2016-04-20_23:49:10.360989 <mbts:NOTE> TRXManager.cpp:88:sendCommandPacket: TRX link timeout on attempt 2
2016-04-20_23:49:11.361334 <mbts:NOTE> TRXManager.cpp:88:sendCommandPacket: TRX link timeout on attempt 3
2016-04-20_23:49:12.362234 <mbts:NOTE> TRXManager.cpp:88:sendCommandPacket: TRX link timeout on attempt 4
ALERT 1996394496 23:49:13.3 TRXManager.cpp:135:sendCommand: RESET failed with status -1
ALERT 1996394496 23:49:13.3 OpenBTS.cpp:250:main: Failed to reset transceiver2016-04-20_23:49:13.363544 <mbts:NOTE> TRXManager.cpp:88:sendCommandPacket: TRX link timeout on attempt 5

2016-04-20_23:49:13.363664 <mbts:MILD> TRXManager.cpp:101:sendCommandPacket: lost control link to transceiver
2016-04-20_23:49:13.363734 <mbts:WARN> TRXManager.cpp:135:sendCommand: RESET failed with status -1
2016-04-20_23:49:13.363804 <mbts:WARN> OpenBTS.cpp:250:main: Failed to reset transceiver
« Last Edit: May 07, 2016, 10:19:14 AM by wright3189 »

marian

  • Sr. Member
  • ****
  • Posts: 378
    • View Profile
Re: Tranceiver error: YateBTS + bladeRF + Raspbery Pi 3
« Reply #1 on: April 21, 2016, 01:08:10 AM »

andrew77

  • Newbie
  • *
  • Posts: 30
    • View Profile
Re: Tranceiver error: YateBTS + bladeRF + Raspbery Pi 3
« Reply #2 on: April 25, 2016, 01:36:41 PM »
i don't know if YateBts with bladeRF works well on USB2.0

according to my experience USB2.0 didn't work



wright3189

  • Newbie
  • *
  • Posts: 9
    • View Profile
Re: Tranceiver error: YateBTS + bladeRF + Raspbery Pi 3
« Reply #3 on: April 27, 2016, 01:07:57 PM »
Hey strcpy, very helpful article. Was able to get the transceiver working. Thanks :)

Would like to get GSM/3g USB dongle working via this yate-datacard module:
https://github.com/mbloody/yate-datacard

Anyone managed to get this working?

wright3189

  • Newbie
  • *
  • Posts: 9
    • View Profile
Re: Tranceiver error: YateBTS + bladeRF + Raspbery Pi 3
« Reply #4 on: May 01, 2016, 12:05:14 PM »
Trying to perform outbound calls through this SIP provider:
https://www.flowroute.com/
But calls are not going through and I'm getting the following error on my phone:
"Emergency calls restricted by access control"

I configured the settings in the NIB GUI for SIP with my credentials.

Monica Tepelus

  • Administrator
  • Full Member
  • *****
  • Posts: 149
    • View Profile
Re: Tranceiver error: YateBTS + bladeRF + Raspbery Pi 3
« Reply #5 on: May 03, 2016, 08:11:50 AM »
Hi,

Emergency calls are disabled by default and we STRONLY recommend you leave them disabled.

You can't make calls at all? Can you call between 2 phones registered on you network? Did you check that the phone is registered? Do you know if you really managed to connect an account to that provider?

wright3189

  • Newbie
  • *
  • Posts: 9
    • View Profile
Re: Tranceiver error: YateBTS + bladeRF + Raspbery Pi 3
« Reply #6 on: May 03, 2016, 04:04:18 PM »
I don't necessarily need to enable emergency calls, but I would eventually like the phone to stop warning me about it. Would this fix apply?:
http://forum.yate.ro/index.php?topic=481.0

The phone does register, as I can see IMSI's after I telnet and run "nib list registered." I did see a couple of active registrations on the SIP provider's proxy, sip-lv1.flowroute.com. Other then that, I haven't been able to test a call on the local network. I have two AT&T SIM cards, one prepaid, but only one phone that I can adjust down to 2G. I'll report back when I get another phone to test with.

wright3189

  • Newbie
  • *
  • Posts: 9
    • View Profile
Re: Tranceiver error: YateBTS + bladeRF + Raspbery Pi 3
« Reply #7 on: May 03, 2016, 11:46:46 PM »
So I got ahold of a Blackberry and was able to make calls and message between the two phones on a test network. So local calls are working, but outbound is not. Guess I should try a different SIP provider.

Monica Tepelus

  • Administrator
  • Full Member
  • *****
  • Posts: 149
    • View Profile
Re: Tranceiver error: YateBTS + bladeRF + Raspbery Pi 3
« Reply #8 on: May 04, 2016, 03:00:47 AM »
Try posting a log with debug SIP level 10 so we can see the answer from your provider.

wright3189

  • Newbie
  • *
  • Posts: 9
    • View Profile
Re: Tranceiver error: YateBTS + bladeRF + Raspbery Pi 3
« Reply #9 on: May 04, 2016, 07:03:00 PM »

Yate engine is initialized and starting up on loom
MBTS ready
Remote connection from 127.0.0.1:43617 to 127.0.0.1:5038
2016-05-05_00:45:42.007253 <sip:INFO> 'udp:0.0.0.0:5060' sending 'REGISTER sip:sip.flowroute.com' 0x7492e518 to 216.115.69.144:5060 [0xe18398]
------
REGISTER sip:sip.flowroute.com SIP/2.0
Contact: <sip:97007270@96.232.44.204:5060>
Expires: 149
To: <sip:97007270@sip.flowroute.com>
Call-ID: 380704645@sip.flowroute.com
Via: SIP/2.0/UDP 96.232.44.204:5060;rport;branch=z9hG4bK1042020320
From: <sip:97007270@sip.flowroute.com>;tag=1633376097
CSeq: 7 REGISTER
User-Agent: YATE/5.5.1
Max-Forwards: 70
Allow: ACK, INVITE, BYE, CANCEL, REGISTER, REFER, OPTIONS, INFO
Content-Length: 0

------
2016-05-05_00:45:42.078546 <sip:INFO> 'udp:0.0.0.0:5060' received 417 bytes SIP message from 216.115.69.144:5060 [0xe18398]
------
SIP/2.0 401 Unauthorized
To: <sip:97007270@sip.flowroute.com>;tag=aa681f9fdf30149b00040f579a1d99c4.61d1
Call-ID: 380704645@sip.flowroute.com
Via: SIP/2.0/UDP 96.232.44.204:5060;rport=5060;branch=z9hG4bK1042020320
From: <sip:97007270@sip.flowroute.com>;tag=1633376097
CSeq: 7 REGISTER
WWW-Authenticate: Digest realm="sip.flowroute.com", nonce="VyqY4Vcql7X4fR21elavuv27tT1EgkZo", qop="auth"
Content-Length: 0

------
2016-05-05_00:45:42.079705 <sip:INFO> 'udp:0.0.0.0:5060' sending 'REGISTER sip:sip.flowroute.com' 0x75b27d38 to 216.115.69.144:5060 [0xe18398]
------
REGISTER sip:sip.flowroute.com SIP/2.0
Contact: <sip:97007270@96.232.44.204:5060>
Expires: 149
To: <sip:97007270@sip.flowroute.com>
Call-ID: 380704645@sip.flowroute.com
Via: SIP/2.0/UDP 96.232.44.204:5060;rport;branch=z9hG4bK484455550
From: <sip:97007270@sip.flowroute.com>;tag=1633376097
User-Agent: YATE/5.5.1
Max-Forwards: 70
Allow: ACK, INVITE, BYE, CANCEL, REGISTER, REFER, OPTIONS, INFO
CSeq: 8 REGISTER
Authorization: Digest username="97007270", realm="sip.flowroute.com", nonce="VyqY4Vcql7X4fR21elavuv27tT1EgkZo", uri="sip:sip.flowroute.com", response="133e15282e5b3e9a356ee3d78a02a28c", algorithm=MD5, qop=auth, nc=00000004, cnonce="949aeaa0f06702631bba6255b9c85932"
Content-Length: 0

------
2016-05-05_00:45:42.154054 <sip:INFO> 'udp:0.0.0.0:5060' received 476 bytes SIP message from 216.115.69.144:5060 [0xe18398]
------
SIP/2.0 200 OK
To: <sip:97007270@sip.flowroute.com>;tag=aa681f9fdf30149b00040f579a1d99c4.2cb3
Call-ID: 380704645@sip.flowroute.com
Via: SIP/2.0/UDP 96.232.44.204:5060;rport=5060;branch=z9hG4bK484455550
From: <sip:97007270@sip.flowroute.com>;tag=1633376097
CSeq: 8 REGISTER
Contact: <sip:97007270@192.168.1.8:5060>;q=1;expires=37;received="sip:96.232.44.204:5060", <sip:97007270@96.232.44.204:5060>;q=1;expires=149;received="sip:96.232.44.204:5060"
Content-Length: 0

------
2016-05-05_00:45:42.156387 <sip:CALL> SIP line 'outbound' logon success to 216.115.69.144:5060
2016-05-05_00:45:44.486778 <sip:INFO> 'udp:0.0.0.0:5060' received 451 bytes SIP message from 216.115.69.144:5060 [0xe18398]
------
OPTIONS sip:96.232.44.204:5060 SIP/2.0
Max-Forwards: 10
Record-Route: <sip:216.115.69.144;lr>
Via: SIP/2.0/UDP 216.115.69.144;branch=z9hG4bK69b7.9096a5c90f6345f00de713afcf3abb15.0
Via: SIP/2.0/UDP 70.167.153.136:5060;branch=0
Route: <sip:216.115.69.144;lr;received='sip:96.232.44.204:5060'>
From: sip:ping@invalid;tag=e78d0e9b
To: sip:96.232.44.204:5060
Call-ID: efdc5dd3-a8dcf64e-491b313@70.167.153.136
CSeq: 1 OPTIONS
Content-Length: 0

------
2016-05-05_00:45:44.487620 <sip:INFO> 'udp:0.0.0.0:5060' received 451 bytes SIP message from 216.115.69.144:5060 [0xe18398]
------
OPTIONS sip:96.232.44.204:5060 SIP/2.0
Max-Forwards: 10
Record-Route: <sip:216.115.69.144;lr>
Via: SIP/2.0/UDP 216.115.69.144;branch=z9hG4bKdcbd.4051c43af623bdf8ae371b5d15c00fe5.0
Via: SIP/2.0/UDP 70.167.153.136:5060;branch=0
Route: <sip:216.115.69.144;lr;received='sip:96.232.44.204:5060'>
From: sip:ping@invalid;tag=f78d0e9b
To: sip:96.232.44.204:5060
Call-ID: efdc5dd3-b8dcf64e-491b313@70.167.153.136
CSeq: 1 OPTIONS
Content-Length: 0

------
2016-05-05_00:45:44.495951 <sip:INFO> 'udp:0.0.0.0:5060' sending code 100 0x74702748 to 216.115.69.144:5060 [0xe18398]
------
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 216.115.69.144;branch=z9hG4bK69b7.9096a5c90f6345f00de713afcf3abb15.0;received=216.115.69.144
Via: SIP/2.0/UDP 70.167.153.136:5060;branch=0
Record-Route: <sip:216.115.69.144;lr>
From: sip:ping@invalid;tag=e78d0e9b
To: sip:96.232.44.204:5060
Call-ID: efdc5dd3-a8dcf64e-491b313@70.167.153.136
CSeq: 1 OPTIONS
Server: YATE/5.5.1
Content-Length: 0

------
2016-05-05_00:45:44.496595 <sip:INFO> 'udp:0.0.0.0:5060' sending code 100 0x74702ad0 to 216.115.69.144:5060 [0xe18398]
------
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 216.115.69.144;branch=z9hG4bKdcbd.4051c43af623bdf8ae371b5d15c00fe5.0;received=216.115.69.144
Via: SIP/2.0/UDP 70.167.153.136:5060;branch=0
Record-Route: <sip:216.115.69.144;lr>
From: sip:ping@invalid;tag=f78d0e9b
To: sip:96.232.44.204:5060
Call-ID: efdc5dd3-b8dcf64e-491b313@70.167.153.136
CSeq: 1 OPTIONS
Server: YATE/5.5.1
Content-Length: 0

------
2016-05-05_00:45:44.497392 <sip:INFO> 'udp:0.0.0.0:5060' sending code 200 0x74703828 to 216.115.69.144:5060 [0xe18398]
------
SIP/2.0 200 OK
Via: SIP/2.0/UDP 216.115.69.144;branch=z9hG4bK69b7.9096a5c90f6345f00de713afcf3abb15.0;received=216.115.69.144
Via: SIP/2.0/UDP 70.167.153.136:5060;branch=0
Record-Route: <sip:216.115.69.144;lr>
From: sip:ping@invalid;tag=e78d0e9b
To: sip:96.232.44.204:5060;tag=1198162556
Call-ID: efdc5dd3-a8dcf64e-491b313@70.167.153.136
CSeq: 1 OPTIONS
Server: YATE/5.5.1
Allow: ACK, INVITE, BYE, CANCEL, REGISTER, REFER, OPTIONS, INFO
Content-Length: 0

------
2016-05-05_00:45:44.498051 <sip:INFO> 'udp:0.0.0.0:5060' sending code 200 0x74702748 to 216.115.69.144:5060 [0xe18398]
------
SIP/2.0 200 OK
Via: SIP/2.0/UDP 216.115.69.144;branch=z9hG4bKdcbd.4051c43af623bdf8ae371b5d15c00fe5.0;received=216.115.69.144
Via: SIP/2.0/UDP 70.167.153.136:5060;branch=0
Record-Route: <sip:216.115.69.144;lr>
From: sip:ping@invalid;tag=f78d0e9b
To: sip:96.232.44.204:5060;tag=1144814701
Call-ID: efdc5dd3-b8dcf64e-491b313@70.167.153.136
CSeq: 1 OPTIONS
Server: YATE/5.5.1
Allow: ACK, INVITE, BYE, CANCEL, REGISTER, REFER, OPTIONS, INFO
Content-Length: 0

------
2016-05-05_00:46:08.002224 <sip:ALL> Sending UDP keepalive to 216.115.69.144:5060 for 'outbound'
2016-05-05_00:46:14.480784 <INFO> Could not classify call from 'TMSI007b0001', wasted 10 usec
2016-05-05_00:46:14.489115 <sip/1:ALL> YateSIPConnection::YateSIPConnection(0x75301a68,'+19176511179') [0xfc98d8]
2016-05-05_00:46:14.490900 <sip/1:ALL> NAT address is '(null)' [0xfc98d8]
2016-05-05_00:46:14.492844 <sip/1:ALL> Set media: audio=mulaw,alaw,slin,ilbc20,ilbc30,isac/16000,isac/32000 [0xfc98d8]
2016-05-05_00:46:14.496089 <sip:INFO> 'udp:0.0.0.0:5060' sending 'INVITE sip:+19176511179@sip.flowroute.com' 0xfd0190 to 216.115.69.144:5060 [0xe18398]
------
INVITE sip:+19176511179@sip.flowroute.com SIP/2.0
Max-Forwards: 20
Via: SIP/2.0/UDP 96.232.44.204:5060;rport;branch=z9hG4bK1354670625
From: <sip:14157107@96.232.44.204>;tag=6468266
To: <sip:+19176511179@sip.flowroute.com>
Call-ID: 1399171416@96.232.44.204
CSeq: 2 INVITE
User-Agent: YATE/5.5.1
Contact: <sip:14157107@96.232.44.204:5060>
Allow: ACK, INVITE, BYE, CANCEL, REGISTER, REFER, OPTIONS, INFO
Content-Type: application/sdp
Content-Length: 394

v=0
o=yate 1462409174 1462409174 IN IP4 96.232.44.204
s=SIP Call
c=IN IP4 96.232.44.204
t=0 0
m=audio 19868 RTP/AVP 0 8 11 98 97 105 106 101
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:11 L16/8000
a=rtpmap:98 iLBC/8000
a=fmtp:98 mode=20
a=rtpmap:97 iLBC/8000
a=fmtp:97 mode=30
a=rtpmap:105 iSAC/16000
a=rtpmap:106 iSAC/32000
a=rtpmap:101 telephone-event/8000
a=ptime:30
------
2016-05-05_00:46:14.497243 <INFO> DataTranslator::attachChain [0xfd13d8] 'gsm' -> [0xfcda90] '(null)' not possible
2016-05-05_00:46:14.497455 <INFO> DataTranslator::attachChain [0xfce910] '(null)' -> [0xfd14e0] 'gsm' not possible
2016-05-05_00:46:14.568038 <sip:INFO> 'udp:0.0.0.0:5060' received 255 bytes SIP message from 216.115.69.144:5060 [0xe18398]
------
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 96.232.44.204:5060;rport=5060;branch=z9hG4bK1354670625
From: <sip:14157107@96.232.44.204>;tag=6468266
To: <sip:+19176511179@sip.flowroute.com>
Call-ID: 1399171416@96.232.44.204
CSeq: 2 INVITE
Content-Length: 0

------
2016-05-05_00:46:14.570797 <sip:INFO> 'udp:0.0.0.0:5060' received 428 bytes SIP message from 216.115.69.144:5060 [0xe18398]
------
SIP/2.0 407 Proxy Authentication Required
Via: SIP/2.0/UDP 96.232.44.204:5060;rport=5060;branch=z9hG4bK1354670625
From: <sip:14157107@96.232.44.204>;tag=6468266
To: <sip:+19176511179@sip.flowroute.com>;tag=a90f6ff38a5ea9aa0a4de2557847562b.a2cf
Call-ID: 1399171416@96.232.44.204
CSeq: 2 INVITE
Proxy-Authenticate: Digest realm="sip.flowroute.com", nonce="VyqZAVcql9UKZIAmNjGo/dD+i242LIPP", qop="auth"
Content-Length: 0

------
2016-05-05_00:46:14.573815 <sip:INFO> 'udp:0.0.0.0:5060' sending 'ACK sip:+19176511179@sip.flowroute.com' 0x75b2eb00 to 216.115.69.144:5060 [0xe18398]
------
ACK sip:+19176511179@sip.flowroute.com SIP/2.0
Via: SIP/2.0/UDP 96.232.44.204:5060;rport;branch=z9hG4bK1354670625
From: <sip:14157107@96.232.44.204>;tag=6468266
To: <sip:+19176511179@sip.flowroute.com>;tag=a90f6ff38a5ea9aa0a4de2557847562b.a2cf
Call-ID: 1399171416@96.232.44.204
CSeq: 2 ACK
Max-Forwards: 20
Contact: <sip:14157107@96.232.44.204:5060>
User-Agent: YATE/5.5.1
Content-Length: 0

------
2016-05-05_00:46:14.575146 <sip:INFO> 'udp:0.0.0.0:5060' sending 'INVITE sip:+19176511179@sip.flowroute.com' 0x75b08968 to 216.115.69.144:5060 [0xe18398]
------
INVITE sip:+19176511179@sip.flowroute.com SIP/2.0
Max-Forwards: 20
Via: SIP/2.0/UDP 96.232.44.204:5060;rport;branch=z9hG4bK1107183732
From: <sip:14157107@96.232.44.204>;tag=6468266
To: <sip:+19176511179@sip.flowroute.com>
Call-ID: 1399171416@96.232.44.204
User-Agent: YATE/5.5.1
Contact: <sip:14157107@96.232.44.204:5060>
Allow: ACK, INVITE, BYE, CANCEL, REGISTER, REFER, OPTIONS, INFO
CSeq: 3 INVITE
Proxy-Authorization: Digest username="97007270", realm="sip.flowroute.com", nonce="VyqZAVcql9UKZIAmNjGo/dD+i242LIPP", uri="sip:+19176511179@sip.flowroute.com", response="ffbcf28c9fdfce4eda70cd1fbce36ccf", algorithm=MD5, qop=auth, nc=00000005, cnonce="275b6000185c1cbe1d9458bb5eb07ef2"
Content-Type: application/sdp
Content-Length: 394

v=0
o=yate 1462409174 1462409174 IN IP4 96.232.44.204
s=SIP Call
c=IN IP4 96.232.44.204
t=0 0
m=audio 19868 RTP/AVP 0 8 11 98 97 105 106 101
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:11 L16/8000
a=rtpmap:98 iLBC/8000
a=fmtp:98 mode=20
a=rtpmap:97 iLBC/8000
a=fmtp:97 mode=30
a=rtpmap:105 iSAC/16000
a=rtpmap:106 iSAC/32000
a=rtpmap:101 telephone-event/8000
a=ptime:30
------
2016-05-05_00:46:14.646288 <sip:INFO> 'udp:0.0.0.0:5060' received 255 bytes SIP message from 216.115.69.144:5060 [0xe18398]
------
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 96.232.44.204:5060;rport=5060;branch=z9hG4bK1107183732
From: <sip:14157107@96.232.44.204>;tag=6468266
To: <sip:+19176511179@sip.flowroute.com>
Call-ID: 1399171416@96.232.44.204
CSeq: 3 INVITE
Content-Length: 0

------
2016-05-05_00:46:14.672719 <sip:INFO> 'udp:0.0.0.0:5060' received 347 bytes SIP message from 216.115.69.144:5060 [0xe18398]
------
SIP/2.0 403 IP Based Authentication Required - support@flowroute.com
Via: SIP/2.0/UDP 96.232.44.204:5060;rport=5060;branch=z9hG4bK1107183732
From: <sip:14157107@96.232.44.204>;tag=6468266
To: <sip:+19176511179@sip.flowroute.com>;tag=c93f6d6d336c15b2a78c29afa288a22f-c24d
Call-ID: 1399171416@96.232.44.204
CSeq: 3 INVITE
Content-Length: 0

------
2016-05-05_00:46:14.673777 <sip/1:ALL> YateSIPConnection::hangup() state=1 trans=0xecf828 error='forbidden' code=403 reason='IP Based Authentication Required - support@flowroute.com' [0xfc98d8]
2016-05-05_00:46:14.674231 >>> DataTranslator::detachChain(0xfce910,0xfd14e0)
2016-05-05_00:46:14.674387 <<< DataTranslator::detachChain
2016-05-05_00:46:14.674454 >>> DataTranslator::detachChain(0xfd13d8,0xfcda90)
2016-05-05_00:46:14.674666 <<< DataTranslator::detachChain
2016-05-05_00:46:14.674761 <ALL> Cleaning up RTP 0xfcf450 [0xfcafe0]
2016-05-05_00:46:14.675064 <sip/1:ALL> YateSIPConnection::~YateSIPConnection() [0xfc98d8]
2016-05-05_00:46:14.675472 <sip:INFO> 'udp:0.0.0.0:5060' sending 'ACK sip:+19176511179@sip.flowroute.com' 0x75b2f088 to 216.115.69.144:5060 [0xe18398]
------
ACK sip:+19176511179@sip.flowroute.com SIP/2.0
Via: SIP/2.0/UDP 96.232.44.204:5060;rport;branch=z9hG4bK1107183732
From: <sip:14157107@96.232.44.204>;tag=6468266
To: <sip:+19176511179@sip.flowroute.com>;tag=c93f6d6d336c15b2a78c29afa288a22f-c24d
Call-ID: 1399171416@96.232.44.204
CSeq: 3 ACK
Max-Forwards: 20
Contact: <sip:14157107@96.232.44.204:5060>
Proxy-Authorization: Digest username="97007270", realm="sip.flowroute.com", nonce="VyqZAVcql9UKZIAmNjGo/dD+i242LIPP", uri="sip:+19176511179@sip.flowroute.com", response="ffbcf28c9fdfce4eda70cd1fbce36ccf", algorithm=MD5, qop=auth, nc=00000005, cnonce="275b6000185c1cbe1d9458bb5eb07ef2"
User-Agent: YATE/5.5.1
Content-Length: 0

------
2016-05-05_00:46:17.857207 <sip:INFO> 'udp:0.0.0.0:5060' received 450 bytes SIP message from 216.115.69.144:5060 [0xe18398]
------
OPTIONS sip:96.232.44.204:5060 SIP/2.0
Max-Forwards: 10
Record-Route: <sip:216.115.69.144;lr>
Via: SIP/2.0/UDP 216.115.69.144;branch=z9hG4bK1bbf.e6ef6fac31a3b3bca3dc493d05ceb025.0
Via: SIP/2.0/UDP 216.115.69.131:5060;branch=0
Route: <sip:216.115.69.144;lr;received='sip:96.232.44.204:5060'>
From: sip:ping@invalid;tag=ad890c49
To: sip:96.232.44.204:5060
Call-ID: 597a8952-e890ad9-2008d33@216.115.69.131
CSeq: 1 OPTIONS
Content-Length: 0

------
2016-05-05_00:46:17.858105 <sip:INFO> 'udp:0.0.0.0:5060' received 450 bytes SIP message from 216.115.69.144:5060 [0xe18398]
------
OPTIONS sip:96.232.44.204:5060 SIP/2.0
Max-Forwards: 10
Record-Route: <sip:216.115.69.144;lr>
Via: SIP/2.0/UDP 216.115.69.144;branch=z9hG4bK8eb5.7811a372c989c2b2fd4e569e4b29bbd6.0
Via: SIP/2.0/UDP 216.115.69.131:5060;branch=0
Route: <sip:216.115.69.144;lr;received='sip:96.232.44.204:5060'>
From: sip:ping@invalid;tag=bd890c49
To: sip:96.232.44.204:5060
Call-ID: 597a8952-f890ad9-2008d33@216.115.69.131
CSeq: 1 OPTIONS
Content-Length: 0

------
2016-05-05_00:46:17.867717 <sip:INFO> 'udp:0.0.0.0:5060' sending code 100 0x74703060 to 216.115.69.144:5060 [0xe18398]
------
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 216.115.69.144;branch=z9hG4bK1bbf.e6ef6fac31a3b3bca3dc493d05ceb025.0;received=216.115.69.144
Via: SIP/2.0/UDP 216.115.69.131:5060;branch=0
Record-Route: <sip:216.115.69.144;lr>
From: sip:ping@invalid;tag=ad890c49
To: sip:96.232.44.204:5060
Call-ID: 597a8952-e890ad9-2008d33@216.115.69.131
CSeq: 1 OPTIONS
Server: YATE/5.5.1
Content-Length: 0

------
2016-05-05_00:46:17.868409 <sip:INFO> 'udp:0.0.0.0:5060' sending code 100 0x74701d30 to 216.115.69.144:5060 [0xe18398]
------
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 216.115.69.144;branch=z9hG4bK8eb5.7811a372c989c2b2fd4e569e4b29bbd6.0;received=216.115.69.144
Via: SIP/2.0/UDP 216.115.69.131:5060;branch=0
Record-Route: <sip:216.115.69.144;lr>
From: sip:ping@invalid;tag=bd890c49
To: sip:96.232.44.204:5060
Call-ID: 597a8952-f890ad9-2008d33@216.115.69.131
CSeq: 1 OPTIONS
Server: YATE/5.5.1
Content-Length: 0

------
2016-05-05_00:46:17.869152 <sip:INFO> 'udp:0.0.0.0:5060' sending code 200 0x74702f38 to 216.115.69.144:5060 [0xe18398]
------
SIP/2.0 200 OK
Via: SIP/2.0/UDP 216.115.69.144;branch=z9hG4bK1bbf.e6ef6fac31a3b3bca3dc493d05ceb025.0;received=216.115.69.144
Via: SIP/2.0/UDP 216.115.69.131:5060;branch=0
Record-Route: <sip:216.115.69.144;lr>
From: sip:ping@invalid;tag=ad890c49
To: sip:96.232.44.204:5060;tag=1257454149
Call-ID: 597a8952-e890ad9-2008d33@216.115.69.131
CSeq: 1 OPTIONS
Server: YATE/5.5.1
Allow: ACK, INVITE, BYE, CANCEL, REGISTER, REFER, OPTIONS, INFO
Content-Length: 0

------
2016-05-05_00:46:17.869871 <sip:INFO> 'udp:0.0.0.0:5060' sending code 200 0x74703060 to 216.115.69.144:5060 [0xe18398]
------
SIP/2.0 200 OK
Via: SIP/2.0/UDP 216.115.69.144;branch=z9hG4bK8eb5.7811a372c989c2b2fd4e569e4b29bbd6.0;received=216.115.69.144
Via: SIP/2.0/UDP 216.115.69.131:5060;branch=0
Record-Route: <sip:216.115.69.144;lr>
From: sip:ping@invalid;tag=bd890c49
To: sip:96.232.44.204:5060;tag=1525921625
Call-ID: 597a8952-f890ad9-2008d33@216.115.69.131
CSeq: 1 OPTIONS
Server: YATE/5.5.1
Allow: ACK, INVITE, BYE, CANCEL, REGISTER, REFER, OPTIONS, INFO
Content-Length: 0

------
2016-05-05_00:46:28.006272 <sip:INFO> 'udp:0.0.0.0:5060' sending 'REGISTER sip:sip.flowroute.com' 0x74986c70 to 216.115.69.144:5060 [0xe18398]
------
REGISTER sip:sip.flowroute.com SIP/2.0
Contact: <sip:97007270@96.232.44.204:5060>
Expires: 149
To: <sip:97007270@sip.flowroute.com>
Call-ID: 380704645@sip.flowroute.com
Via: SIP/2.0/UDP 96.232.44.204:5060;rport;branch=z9hG4bK2082274499
From: <sip:97007270@sip.flowroute.com>;tag=1560116176
CSeq: 9 REGISTER
User-Agent: YATE/5.5.1
Max-Forwards: 70
Allow: ACK, INVITE, BYE, CANCEL, REGISTER, REFER, OPTIONS, INFO
Content-Length: 0

------
2016-05-05_00:46:28.079713 <sip:INFO> 'udp:0.0.0.0:5060' received 417 bytes SIP message from 216.115.69.144:5060 [0xe18398]
------
SIP/2.0 401 Unauthorized
To: <sip:97007270@sip.flowroute.com>;tag=aa681f9fdf30149b00040f579a1d99c4.fe96
Call-ID: 380704645@sip.flowroute.com
Via: SIP/2.0/UDP 96.232.44.204:5060;rport=5060;branch=z9hG4bK2082274499
From: <sip:97007270@sip.flowroute.com>;tag=1560116176
CSeq: 9 REGISTER
WWW-Authenticate: Digest realm="sip.flowroute.com", nonce="VyqZD1cql+MSuGNfqqFugj9la2TXO4l1", qop="auth"
Content-Length: 0

------
2016-05-05_00:46:28.083302 <sip:INFO> 'udp:0.0.0.0:5060' sending 'REGISTER sip:sip.flowroute.com' 0x75b2fdf8 to 216.115.69.144:5060 [0xe18398]
------
REGISTER sip:sip.flowroute.com SIP/2.0
Contact: <sip:97007270@96.232.44.204:5060>
Expires: 149
To: <sip:97007270@sip.flowroute.com>
Call-ID: 380704645@sip.flowroute.com
Via: SIP/2.0/UDP 96.232.44.204:5060;rport;branch=z9hG4bK1362238293
From: <sip:97007270@sip.flowroute.com>;tag=1560116176
User-Agent: YATE/5.5.1
Max-Forwards: 70
Allow: ACK, INVITE, BYE, CANCEL, REGISTER, REFER, OPTIONS, INFO
CSeq: 10 REGISTER
Authorization: Digest username="97007270", realm="sip.flowroute.com", nonce="VyqZD1cql+MSuGNfqqFugj9la2TXO4l1", uri="sip:sip.flowroute.com", response="d7938aaab9d4452581b9ccc942d30683", algorithm=MD5, qop=auth, nc=00000006, cnonce="f6f3b544e784c418bf7b62cb3cdcfa77"
Content-Length: 0

------
2016-05-05_00:46:28.155207 <sip:INFO> 'udp:0.0.0.0:5060' received 396 bytes SIP message from 216.115.69.144:5060 [0xe18398]
------
SIP/2.0 200 OK
To: <sip:97007270@sip.flowroute.com>;tag=aa681f9fdf30149b00040f579a1d99c4.9fc8
Call-ID: 380704645@sip.flowroute.com
Via: SIP/2.0/UDP 96.232.44.204:5060;rport=5060;branch=z9hG4bK1362238293
From: <sip:97007270@sip.flowroute.com>;tag=1560116176
CSeq: 10 REGISTER
Contact: <sip:97007270@96.232.44.204:5060>;q=1;expires=149;received="sip:96.232.44.204:5060"
Content-Length: 0

------
2016-05-05_00:46:28.160125 <sip:CALL> SIP line 'outbound' logon success to 216.115.69.144:5060
2016-05-05_00:46:39.750517 <sip:INFO> 'udp:0.0.0.0:5060' received 451 bytes SIP message from 216.115.69.144:5060 [0xe18398]
------
OPTIONS sip:96.232.44.204:5060 SIP/2.0
Max-Forwards: 10
Record-Route: <sip:216.115.69.144;lr>
Via: SIP/2.0/UDP 216.115.69.144;branch=z9hG4bKc289.cebf963230588219e0647de6530762c7.0
Via: SIP/2.0/UDP 70.167.153.136:5060;branch=0
Route: <sip:216.115.69.144;lr;received='sip:96.232.44.204:5060'>
From: sip:ping@invalid;tag=3c501e9b
To: sip:96.232.44.204:5060
Call-ID: efdc5dd3-fcaff64e-cc1b313@70.167.153.136
CSeq: 1 OPTIONS
Content-Length: 0

marian

  • Sr. Member
  • ****
  • Posts: 378
    • View Profile
Re: Tranceiver error: YateBTS + bladeRF + Raspbery Pi 3
« Reply #10 on: May 05, 2016, 12:28:10 AM »
See response to INVITE:
SIP/2.0 403 IP Based Authentication Required - support@flowroute.com

Check with your provider.

wright3189

  • Newbie
  • *
  • Posts: 9
    • View Profile
Re: Tranceiver error: YateBTS + bladeRF + Raspbery Pi 3
« Reply #11 on: May 05, 2016, 09:01:33 PM »
Problem is that my primary ISP uses dynamic IP addressing and besides that the YateBTS I'm setting up needs to be portable, connecting via hotspots and WiFi. I would think SIP Credential Authentication would be ideal for that. I've contacted the SIP provider and am looking into alternatives.

wright3189

  • Newbie
  • *
  • Posts: 9
    • View Profile
Re: Tranceiver error: YateBTS + bladeRF + Raspbery Pi 3
« Reply #12 on: May 07, 2016, 10:16:53 AM »
So I enabled Outbound SIP Credentials through my SIP Provider. But when making out of network calls, it says that I'm connected, but I don't hear anything. I get the following log:

pi@loom:~ $ telnet 0 5038
Trying 0.0.0.0...
Connected to 0.
Escape character is '^]'.
YATE 5.5.1-devel1 r (http://YATE.null.ro) ready on loom.
debug on
Debug level: 10, objects: off, local: on, threshold: 10
debug level 10
Debug level: 10, objects: off, local: on, threshold: 10
debug sip level 10
Module sip debug on level 10 objects off
2016-05-07_16:11:56.313194 <INFO> Could not classify call from 'TMSI007b0001', wasted 11 usec
2016-05-07_16:11:56.320741 <sip/2:ALL> YateSIPConnection::YateSIPConnection(0x753011e8,'+19176511179') [0xc16fb8]
2016-05-07_16:11:56.321719 <sip/2:ALL> NAT address is '(null)' [0xc16fb8]
2016-05-07_16:11:56.322438 <sip/2:ALL> Set media: audio=mulaw,alaw,slin,ilbc20,ilbc30,isac/16000,isac/32000 [0xc16fb8]
2016-05-07_16:11:56.324218 <INFO> DataTranslator::attachChain [0xc16ac8] 'gsm' -> [0xc18668] '(null)' not possible
2016-05-07_16:11:56.324423 <INFO> DataTranslator::attachChain [0xc16120] '(null)' -> [0xc12b18] 'gsm' not possible
2016-05-07_16:11:56.324957 <sip:INFO> 'udp:0.0.0.0:5060' sending 'INVITE sip:+19176511179@sip.flowroute.com' 0xc18198 to 216.115.69.144:5060 [0xa603a0]
------
INVITE sip:+19176511179@sip.flowroute.com SIP/2.0
Max-Forwards: 20
Via: SIP/2.0/UDP 108.27.239.110:5060;rport;branch=z9hG4bK150264348
From: <sip:14157107@108.27.239.110>;tag=505328269
To: <sip:+19176511179@sip.flowroute.com>
Call-ID: 1729245378@108.27.239.110
CSeq: 4 INVITE
User-Agent: YATE/5.5.1
Contact: <sip:14157107@108.27.239.110:5060>
Allow: ACK, INVITE, BYE, CANCEL, REGISTER, REFER, OPTIONS, INFO
Content-Type: application/sdp
Content-Length: 396

v=0
o=yate 1462637516 1462637516 IN IP4 108.27.239.110
s=SIP Call
c=IN IP4 108.27.239.110
t=0 0
m=audio 22262 RTP/AVP 0 8 11 98 97 105 106 101
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:11 L16/8000
a=rtpmap:98 iLBC/8000
a=fmtp:98 mode=20
a=rtpmap:97 iLBC/8000
a=fmtp:97 mode=30
a=rtpmap:105 iSAC/16000
a=rtpmap:106 iSAC/32000
a=rtpmap:101 telephone-event/8000
a=ptime:30
------
2016-05-07_16:11:56.403495 <sip:INFO> 'udp:0.0.0.0:5060' received 259 bytes SIP message from 216.115.69.144:5060 [0xa603a0]
------
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 108.27.239.110:5060;rport=5060;branch=z9hG4bK150264348
From: <sip:14157107@108.27.239.110>;tag=505328269
To: <sip:+19176511179@sip.flowroute.com>
Call-ID: 1729245378@108.27.239.110
CSeq: 4 INVITE
Content-Length: 0

------
2016-05-07_16:11:56.405013 <sip:INFO> 'udp:0.0.0.0:5060' received 432 bytes SIP message from 216.115.69.144:5060 [0xa603a0]
------
SIP/2.0 407 Proxy Authentication Required
Via: SIP/2.0/UDP 108.27.239.110:5060;rport=5060;branch=z9hG4bK150264348
From: <sip:14157107@108.27.239.110>;tag=505328269
To: <sip:+19176511179@sip.flowroute.com>;tag=a90f6ff38a5ea9aa0a4de2557847562b.b56e
Call-ID: 1729245378@108.27.239.110
CSeq: 4 INVITE
Proxy-Authenticate: Digest realm="sip.flowroute.com", nonce="Vy4U91cuE8sp8jOF1pI/aiP2MG7+QJWC", qop="auth"
Content-Length: 0

------
2016-05-07_16:11:56.407554 <sip:INFO> 'udp:0.0.0.0:5060' sending 'ACK sip:+19176511179@sip.flowroute.com' 0x75b318c0 to 216.115.69.144:5060 [0xa603a0]
------
ACK sip:+19176511179@sip.flowroute.com SIP/2.0
Via: SIP/2.0/UDP 108.27.239.110:5060;rport;branch=z9hG4bK150264348
From: <sip:14157107@108.27.239.110>;tag=505328269
To: <sip:+19176511179@sip.flowroute.com>;tag=a90f6ff38a5ea9aa0a4de2557847562b.b56e
Call-ID: 1729245378@108.27.239.110
CSeq: 4 ACK
Max-Forwards: 20
Contact: <sip:14157107@108.27.239.110:5060>
User-Agent: YATE/5.5.1
Content-Length: 0

------
2016-05-07_16:11:56.408774 <sip:INFO> 'udp:0.0.0.0:5060' sending 'INVITE sip:+19176511179@sip.flowroute.com' 0x75b27d68 to 216.115.69.144:5060 [0xa603a0]
------
INVITE sip:+19176511179@sip.flowroute.com SIP/2.0
Max-Forwards: 20
Via: SIP/2.0/UDP 108.27.239.110:5060;rport;branch=z9hG4bK1940193854
From: <sip:14157107@108.27.239.110>;tag=505328269
To: <sip:+19176511179@sip.flowroute.com>
Call-ID: 1729245378@108.27.239.110
User-Agent: YATE/5.5.1
Contact: <sip:14157107@108.27.239.110:5060>
Allow: ACK, INVITE, BYE, CANCEL, REGISTER, REFER, OPTIONS, INFO
CSeq: 5 INVITE
Proxy-Authorization: Digest username="97007270", realm="sip.flowroute.com", nonce="Vy4U91cuE8sp8jOF1pI/aiP2MG7+QJWC", uri="sip:+19176511179@sip.flowroute.com", response="7e3c9500d5506322e7080d998c332759", algorithm=MD5, qop=auth, nc=00000004, cnonce="7c38e7ef161cc6574252dec9e89328de"
Content-Type: application/sdp
Content-Length: 396

v=0
o=yate 1462637516 1462637516 IN IP4 108.27.239.110
s=SIP Call
c=IN IP4 108.27.239.110
t=0 0
m=audio 22262 RTP/AVP 0 8 11 98 97 105 106 101
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:11 L16/8000
a=rtpmap:98 iLBC/8000
a=fmtp:98 mode=20
a=rtpmap:97 iLBC/8000
a=fmtp:97 mode=30
a=rtpmap:105 iSAC/16000
a=rtpmap:106 iSAC/32000
a=rtpmap:101 telephone-event/8000
a=ptime:30
------
2016-05-07_16:11:56.482780 <sip:INFO> 'udp:0.0.0.0:5060' received 260 bytes SIP message from 216.115.69.144:5060 [0xa603a0]
------
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 108.27.239.110:5060;rport=5060;branch=z9hG4bK1940193854
From: <sip:14157107@108.27.239.110>;tag=505328269
To: <sip:+19176511179@sip.flowroute.com>
Call-ID: 1729245378@108.27.239.110
CSeq: 5 INVITE
Content-Length: 0

------
2016-05-07_16:11:57.442223 <sip:INFO> 'udp:0.0.0.0:5060' received 642 bytes SIP message from 216.115.69.144:5060 [0xa603a0]
------
SIP/2.0 183 Session Progress
From: <sip:14157107@108.27.239.110>;tag=505328269
To: <sip:+19176511179@sip.flowroute.com>;tag=gK00821bf1
Via: SIP/2.0/UDP 108.27.239.110:5060;rport=5060;branch=z9hG4bK1940193854
Call-ID: 1729245378@108.27.239.110
CSeq: 5 INVITE
Record-Route: <sip:216.115.69.133:5060;lr>
Record-Route: <sip:216.115.69.144:5060;lr>
Contact: <sip:+19176511179@207.223.65.181:5060>
Content-Length:   185
Content-Type: application/sdp

v=0
o=- 658284292 691518277 IN IP4 207.223.65.164
s=-
c=IN IP4 207.223.65.164
t=0 0
m=audio 43548 RTP/AVP 0 101
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=maxptime:20
------
2016-05-07_16:11:57.446548 <INFO> Choosing offered 'audio' format 'mulaw' [0xc16428]
2016-05-07_16:11:57.446913 <sip/2:ALL> Set media: audio=mulaw [0xc16fb8]
2016-05-07_16:11:57.447568 >>> DataTranslator::detachChain(0xc16120,0xc12b18)
2016-05-07_16:11:57.447912 <<< DataTranslator::detachChain
2016-05-07_16:11:57.448220 <INFO> No DataTranslator created for 'mulaw' -> 'gsm'
2016-05-07_16:11:57.448386 <WARN> DataTranslator::attachChain [0xc16120] 'mulaw' -> [0xc12b18] 'gsm' failed
2016-05-07_16:11:57.448533 >>> DataTranslator::detachChain(0xc16ac8,0xc18668)
2016-05-07_16:11:57.448710 <<< DataTranslator::detachChain
2016-05-07_16:11:57.448874 <INFO> No DataTranslator created for 'gsm' -> 'mulaw'
2016-05-07_16:11:57.448956 <WARN> DataTranslator::attachChain [0xc16ac8] 'gsm' -> [0xc18668] 'mulaw' failed
2016-05-07_16:11:59.002771 <sip:ALL> Sending UDP keepalive to 216.115.69.144:5060 for 'outbound'
2016-05-07_16:12:00.454570 <yrtp:WARN> Initial timeout in channel sip/2 wrapper [0xc12fe8]
2016-05-07_16:12:02.960932 <sip:INFO> 'udp:0.0.0.0:5060' received 454 bytes SIP message from 216.115.69.144:5060 [0xa603a0]
------
OPTIONS sip:108.27.239.110:5060 SIP/2.0
Max-Forwards: 10
Record-Route: <sip:216.115.69.144;lr>
Via: SIP/2.0/UDP 216.115.69.144;branch=z9hG4bKb49b.1498ccd0585eaff19232b3c08650d4c1.0
Via: SIP/2.0/UDP 70.167.153.136:5060;branch=0
Route: <sip:216.115.69.144;lr;received='sip:108.27.239.110:5060'>
From: sip:ping@invalid;tag=9992dbcb
To: sip:108.27.239.110:5060
Call-ID: efdc5dd3-5ae1c47e-fad2713@70.167.153.136
CSeq: 1 OPTIONS
Content-Length: 0

------
2016-05-07_16:12:02.961977 <sip:INFO> 'udp:0.0.0.0:5060' received 454 bytes SIP message from 216.115.69.144:5060 [0xa603a0]
------
OPTIONS sip:108.27.239.110:5060 SIP/2.0
Max-Forwards: 10
Record-Route: <sip:216.115.69.144;lr>
Via: SIP/2.0/UDP 216.115.69.144;branch=z9hG4bKec89.bb70f0c0c4dd2ad12c3352547bd12d6f.0
Via: SIP/2.0/UDP 70.167.153.136:5060;branch=0
Route: <sip:216.115.69.144;lr;received='sip:108.27.239.110:5060'>
From: sip:ping@invalid;tag=a992dbcb
To: sip:108.27.239.110:5060
Call-ID: efdc5dd3-6ae1c47e-fad2713@70.167.153.136
CSeq: 1 OPTIONS
Content-Length: 0

------
2016-05-07_16:12:02.969365 <sip:INFO> 'udp:0.0.0.0:5060' sending code 100 0x74704a78 to 216.115.69.144:5060 [0xa603a0]
------
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 216.115.69.144;branch=z9hG4bKb49b.1498ccd0585eaff19232b3c08650d4c1.0;received=216.115.69.144
Via: SIP/2.0/UDP 70.167.153.136:5060;branch=0
Record-Route: <sip:216.115.69.144;lr>
From: sip:ping@invalid;tag=9992dbcb
To: sip:108.27.239.110:5060
Call-ID: efdc5dd3-5ae1c47e-fad2713@70.167.153.136
CSeq: 1 OPTIONS
Server: YATE/5.5.1
Content-Length: 0

------
2016-05-07_16:12:02.970365 <sip:INFO> 'udp:0.0.0.0:5060' sending code 100 0x747009b0 to 216.115.69.144:5060 [0xa603a0]
------
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 216.115.69.144;branch=z9hG4bKec89.bb70f0c0c4dd2ad12c3352547bd12d6f.0;received=216.115.69.144
Via: SIP/2.0/UDP 70.167.153.136:5060;branch=0
Record-Route: <sip:216.115.69.144;lr>
From: sip:ping@invalid;tag=a992dbcb
To: sip:108.27.239.110:5060
Call-ID: efdc5dd3-6ae1c47e-fad2713@70.167.153.136
CSeq: 1 OPTIONS
Server: YATE/5.5.1
Content-Length: 0

------
2016-05-07_16:12:02.971606 <sip:INFO> 'udp:0.0.0.0:5060' sending code 200 0x747022e0 to 216.115.69.144:5060 [0xa603a0]
------
SIP/2.0 200 OK
Via: SIP/2.0/UDP 216.115.69.144;branch=z9hG4bKb49b.1498ccd0585eaff19232b3c08650d4c1.0;received=216.115.69.144
Via: SIP/2.0/UDP 70.167.153.136:5060;branch=0
Record-Route: <sip:216.115.69.144;lr>
From: sip:ping@invalid;tag=9992dbcb
To: sip:108.27.239.110:5060;tag=2043097593
Call-ID: efdc5dd3-5ae1c47e-fad2713@70.167.153.136
CSeq: 1 OPTIONS
Server: YATE/5.5.1
Allow: ACK, INVITE, BYE, CANCEL, REGISTER, REFER, OPTIONS, INFO
Content-Length: 0

------
2016-05-07_16:12:02.972923 <sip:INFO> 'udp:0.0.0.0:5060' sending code 200 0x74704a78 to 216.115.69.144:5060 [0xa603a0]
------
SIP/2.0 200 OK
Via: SIP/2.0/UDP 216.115.69.144;branch=z9hG4bKec89.bb70f0c0c4dd2ad12c3352547bd12d6f.0;received=216.115.69.144
Via: SIP/2.0/UDP 70.167.153.136:5060;branch=0
Record-Route: <sip:216.115.69.144;lr>
From: sip:ping@invalid;tag=a992dbcb
To: sip:108.27.239.110:5060;tag=1987633634
Call-ID: efdc5dd3-6ae1c47e-fad2713@70.167.153.136
CSeq: 1 OPTIONS
Server: YATE/5.5.1
Allow: ACK, INVITE, BYE, CANCEL, REGISTER, REFER, OPTIONS, INFO
Content-Length: 0

------
2016-05-07_16:12:10.798075 <sip:INFO> 'udp:0.0.0.0:5060' received 683 bytes SIP message from 216.115.69.144:5060 [0xa603a0]
------
SIP/2.0 200 OK
From: <sip:14157107@108.27.239.110>;tag=505328269
To: <sip:+19176511179@sip.flowroute.com>;tag=gK00821bf1
Via: SIP/2.0/UDP 108.27.239.110:5060;rport=5060;branch=z9hG4bK1940193854
Call-ID: 1729245378@108.27.239.110
CSeq: 5 INVITE
Record-Route: <sip:216.115.69.133:5060;lr>
Record-Route: <sip:216.115.69.144:5060;lr>
Contact: <sip:+19176511179@207.223.65.181:5060>
Session-Expires: 1800;refresher=uas
Content-Length:   185
Content-Type: application/sdp
Supported: timer

v=0
o=- 658284292 691518277 IN IP4 207.223.65.164
s=-
c=IN IP4 207.223.65.164
t=0 0
m=audio 43548 RTP/AVP 0 101
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=maxptime:20
------
2016-05-07_16:12:10.799670 <sip/2:ALL> Set media: audio=mulaw [0xc16fb8]
2016-05-07_16:12:10.803504 <sip:INFO> 'udp:0.0.0.0:5060' sending 'ACK sip:+19176511179@207.223.65.181:5060' 0x75b36760 to 216.115.69.144:5060 [0xa603a0]
------
ACK sip:+19176511179@207.223.65.181:5060 SIP/2.0
Via: SIP/2.0/UDP 108.27.239.110:5060;rport;branch=z9hG4bK1273853296
Route: <sip:216.115.69.144:5060;lr>
Route: <sip:216.115.69.133:5060;lr>
From: <sip:14157107@108.27.239.110>;tag=505328269
To: <sip:+19176511179@sip.flowroute.com>;tag=gK00821bf1
Call-ID: 1729245378@108.27.239.110
CSeq: 5 ACK
Max-Forwards: 20
Contact: <sip:14157107@108.27.239.110:5060>
Proxy-Authorization: Digest username="97007270", realm="sip.flowroute.com", nonce="Vy4U91cuE8sp8jOF1pI/aiP2MG7+QJWC", uri="sip:+19176511179@sip.flowroute.com", response="7e3c9500d5506322e7080d998c332759", algorithm=MD5, qop=auth, nc=00000004, cnonce="7c38e7ef161cc6574252dec9e89328de"
User-Agent: YATE/5.5.1
Content-Length: 0

------
2016-05-07_16:12:19.154593 <sip:INFO> 'udp:0.0.0.0:5060' received 453 bytes SIP message from 216.115.69.144:5060 [0xa603a0]
------
OPTIONS sip:108.27.239.110:5060 SIP/2.0
Max-Forwards: 10
Record-Route: <sip:216.115.69.144;lr>
Via: SIP/2.0/UDP 216.115.69.144;branch=z9hG4bK096b.5f36199602ba8b6f6bd52dcc983d3f90.0
Via: SIP/2.0/UDP 216.115.69.131:5060;branch=0
Route: <sip:216.115.69.144;lr;received='sip:108.27.239.110:5060'>
From: sip:ping@invalid;tag=488be979
To: sip:108.27.239.110:5060
Call-ID: 597a8952-83928bc-b0cf043@216.115.69.131
CSeq: 1 OPTIONS
Content-Length: 0

------
2016-05-07_16:12:19.155637 <sip:INFO> 'udp:0.0.0.0:5060' received 453 bytes SIP message from 216.115.69.144:5060 [0xa603a0]
------
OPTIONS sip:108.27.239.110:5060 SIP/2.0
Max-Forwards: 10
Record-Route: <sip:216.115.69.144;lr>
Via: SIP/2.0/UDP 216.115.69.144;branch=z9hG4bK9745.3e5564feb4ad0d41501394614ced41a5.0
Via: SIP/2.0/UDP 216.115.69.131:5060;branch=0
Route: <sip:216.115.69.144;lr;received='sip:108.27.239.110:5060'>
From: sip:ping@invalid;tag=388be979
To: sip:108.27.239.110:5060
Call-ID: 597a8952-73928bc-b0cf043@216.115.69.131
CSeq: 1 OPTIONS
Content-Length: 0

------
2016-05-07_16:12:19.163949 <sip:INFO> 'udp:0.0.0.0:5060' sending code 100 0x747009b0 to 216.115.69.144:5060 [0xa603a0]
------
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 216.115.69.144;branch=z9hG4bK096b.5f36199602ba8b6f6bd52dcc983d3f90.0;received=216.115.69.144
Via: SIP/2.0/UDP 216.115.69.131:5060;branch=0
Record-Route: <sip:216.115.69.144;lr>
From: sip:ping@invalid;tag=488be979
To: sip:108.27.239.110:5060
Call-ID: 597a8952-83928bc-b0cf043@216.115.69.131
CSeq: 1 OPTIONS
Server: YATE/5.5.1
Content-Length: 0

------
2016-05-07_16:12:19.165449 <sip:INFO> 'udp:0.0.0.0:5060' sending code 100 0x74702c98 to 216.115.69.144:5060 [0xa603a0]
------
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 216.115.69.144;branch=z9hG4bK9745.3e5564feb4ad0d41501394614ced41a5.0;received=216.115.69.144
Via: SIP/2.0/UDP 216.115.69.131:5060;branch=0
Record-Route: <sip:216.115.69.144;lr>
From: sip:ping@invalid;tag=388be979
To: sip:108.27.239.110:5060
Call-ID: 597a8952-73928bc-b0cf043@216.115.69.131
CSeq: 1 OPTIONS
Server: YATE/5.5.1
Content-Length: 0

------
2016-05-07_16:12:19.167035 <sip:INFO> 'udp:0.0.0.0:5060' sending code 200 0x74706338 to 216.115.69.144:5060 [0xa603a0]
------
SIP/2.0 200 OK
Via: SIP/2.0/UDP 216.115.69.144;branch=z9hG4bK096b.5f36199602ba8b6f6bd52dcc983d3f90.0;received=216.115.69.144
Via: SIP/2.0/UDP 216.115.69.131:5060;branch=0
Record-Route: <sip:216.115.69.144;lr>
From: sip:ping@invalid;tag=488be979
To: sip:108.27.239.110:5060;tag=397478705
Call-ID: 597a8952-83928bc-b0cf043@216.115.69.131
CSeq: 1 OPTIONS
Server: YATE/5.5.1
Allow: ACK, INVITE, BYE, CANCEL, REGISTER, REFER, OPTIONS, INFO
Content-Length: 0

------
2016-05-07_16:12:19.168573 <sip:INFO> 'udp:0.0.0.0:5060' sending code 200 0x747009b0 to 216.115.69.144:5060 [0xa603a0]
------
SIP/2.0 200 OK
Via: SIP/2.0/UDP 216.115.69.144;branch=z9hG4bK9745.3e5564feb4ad0d41501394614ced41a5.0;received=216.115.69.144
Via: SIP/2.0/UDP 216.115.69.131:5060;branch=0
Record-Route: <sip:216.115.69.144;lr>
From: sip:ping@invalid;tag=388be979
To: sip:108.27.239.110:5060;tag=566393845
Call-ID: 597a8952-73928bc-b0cf043@216.115.69.131
CSeq: 1 OPTIONS
Server: YATE/5.5.1
Allow: ACK, INVITE, BYE, CANCEL, REGISTER, REFER, OPTIONS, INFO
Content-Length: 0

------
2016-05-07_16:12:25.000571 <sip:ALL> Sending UDP keepalive to 216.115.69.144:5060 for 'outbound'
2016-05-07_16:12:27.411778 >>> DataTranslator::detachChain(0xc16ac8,0xc18668)
2016-05-07_16:12:27.412075 <<< DataTranslator::detachChain
2016-05-07_16:12:27.412558 >>> DataTranslator::detachChain(0xc16120,0xc12b18)
2016-05-07_16:12:27.412748 <<< DataTranslator::detachChain
2016-05-07_16:12:27.412954 <sip/2:ALL> YateSIPConnection::disconnected() 'normal-clearing' [0xc16fb8]
2016-05-07_16:12:27.418462 <sip/2:ALL> YateSIPConnection::hangup() state=3 trans=(nil) error='noanswer' code=487 reason='normal-clearing' [0xc16fb8]
2016-05-07_16:12:27.419358 <ALL> Cleaning up RTP 0xc16c58 [0xc12fe8]
2016-05-07_16:12:27.420586 <sip/2:ALL> YateSIPConnection::~YateSIPConnection() [0xc16fb8]
2016-05-07_16:12:27.425020 <sip:INFO> 'udp:0.0.0.0:5060' sending 'BYE sip:+19176511179@207.223.65.181:5060' 0x74923410 to 216.115.69.144:5060 [0xa603a0]
------
BYE sip:+19176511179@207.223.65.181:5060 SIP/2.0
Route: <sip:216.115.69.144:5060;lr>
Route: <sip:216.115.69.133:5060;lr>
Call-ID: 1729245378@108.27.239.110
From: <sip:14157107@108.27.239.110>;tag=505328269
To: <sip:+19176511179@sip.flowroute.com>;tag=gK00821bf1
Reason: SIP;text="normal-clearing"
P-RTP-Stat: PS=0,OS=0,PR=0,OR=0,PL=0
Via: SIP/2.0/UDP 108.27.239.110:5060;rport;branch=z9hG4bK6767567
CSeq: 5 BYE
User-Agent: YATE/5.5.1
Max-Forwards: 70
Allow: ACK, INVITE, BYE, CANCEL, REGISTER, REFER, OPTIONS, INFO
Content-Length: 0

------
2016-05-07_16:12:27.513078 <sip:INFO> 'udp:0.0.0.0:5060' received 353 bytes SIP message from 216.115.69.144:5060 [0xa603a0]
------
SIP/2.0 200 OK
From: <sip:14157107@108.27.239.110>;tag=505328269
To: <sip:+19176511179@sip.flowroute.com>;tag=gK00821bf1
Via: SIP/2.0/UDP 108.27.239.110:5060;rport=5060;branch=z9hG4bK6767567
Call-ID: 1729245378@108.27.239.110
CSeq: 5 BYE
Record-Route: <sip:216.115.69.133:5060;lr>
Record-Route: <sip:216.115.69.144:5060;lr>
Content-Length: 0

------

wright3189

  • Newbie
  • *
  • Posts: 9
    • View Profile
Re: Troubleshooting: YateBTS + bladeRF + Raspbery Pi 3
« Reply #13 on: May 07, 2016, 10:46:02 AM »
This is what stands out while skimming:

2016-05-07_16:08:15.347121 <INFO> Choosing offered 'audio' format 'mulaw' [0x75b2f9e0]
2016-05-07_16:08:15.348230 <sip/1:ALL> Set media: audio=mulaw [0x75b2c668]
2016-05-07_16:08:15.349195 >>> DataTranslator::detachChain(0x75b30768,0x75b322b8)
2016-05-07_16:08:15.349822 <<< DataTranslator::detachChain
2016-05-07_16:08:15.350375 <INFO> No DataTranslator created for 'mulaw' -> 'gsm'
2016-05-07_16:08:15.350911 <WARN> DataTranslator::attachChain [0x75b30768] 'mulaw' -> [0x75b322b8] 'gsm' failed
2016-05-07_16:08:15.351296 >>> DataTranslator::detachChain(0x75b32190,0x75b30870)
2016-05-07_16:08:15.351760 <<< DataTranslator::detachChain
2016-05-07_16:08:15.352175 <INFO> No DataTranslator created for 'gsm' -> 'mulaw'
2016-05-07_16:08:15.353046 <WARN> DataTranslator::attachChain [0x75b32190] 'gsm' -> [0x75b30870] 'mulaw' failed
2016-05-07_16:08:17.901926 <sip:INFO> 'udp:0.0.0.0:5060' received 682 bytes SIP message from 216.115.69.144:5060 [0xa603a0]

Looks like I'm missing a dependency: libgsm1-dev
http://wiki.yatebts.com/index.php/You_don't_hear_anything
« Last Edit: May 07, 2016, 10:52:18 AM by wright3189 »

marian

  • Sr. Member
  • ****
  • Posts: 378
    • View Profile
Re: Troubleshooting: YateBTS + bladeRF + Raspbery Pi 3
« Reply #14 on: May 09, 2016, 01:13:40 AM »
Indeed, you are missing the gsmcodec module.