IRC log for #asterisk on 20190217

18:57.44*** join/#asterisk infobot (ibot@rikers.org)
18:57.44*** topic/#asterisk is #asterisk The Open Source PBX and Telephony Platform (asterisk.org) -=- LTS: 13.25.0 (2019/2/15) 16.2.0 (2019/2/15), Security Only: 15.7.1 (2018/12/26); DAHDI: DAHDI-linux 2.11.1 (2016/03/01), DAHDI-tools 2.11.1 (2016/03/01); libpri 1.6.0 (2017/01/27) -=- Wiki: wiki.asterisk.org -=- Code of Conduct: bit.ly/1hH6P22
19:02.48*** join/#asterisk bbt (~dbag@unaffiliated/bbt)
19:10.32bbtrunning pjsip with asterisk13 and having troubles getting sip phone to register
19:11.20bbtgetting that no endpoints found error
19:12.58SamotThat means it can't find an endpoint with that name
19:13.08SamotWhat port is PJSIP listening on?
19:13.29bbthow do i check?
19:13.37SamotYou set it up.
19:13.41SamotYou don't know?
19:14.08bbti am trying to do this via cli
19:15.13bbttrunks were registering via 5060 fine but havent done them again, trying to get sip phones working first after wipe
19:15.48SamotOK
19:15.56SamotSo what port did you bind PJSIP for this transport?
19:16.13SamotDoing by the CLI still means you had to enter this information into the configs.
19:17.19bbtthis is what i have used based on the asterisk wiki
19:17.21bbthttps://pastebin.com/Wez26dJG
19:18.09[TK]D-Fendershow us the registration attempt
19:18.12SamotUhm. No.
19:18.15[TK]D-Fender"pjsip set logger on"
19:18.19SamotNo.
19:18.24SamotThis isn't configured properly.
19:18.44[TK]D-Fenderobviously
19:18.52SamotSo I don't need a call.
19:18.59SamotWhy would you need a call. I just saw the configs.
19:19.02[TK]D-FenderI didn't ask for a call
19:19.02SamotThey are not correct.
19:19.09SamotOr the Registration attempt.
19:19.13SamotThe endpoint is configured wrong.
19:19.15[TK]D-FenderBecause?
19:19.20SamotThe endpoint is missing vital settings.
19:19.25SamotSo is the transport config
19:19.26[TK]D-FenderWe should see what it is trying to auth as
19:19.36[TK]D-Fenderso he can better match the setting that is wrong
19:19.37SamotThere is NO TRANSPORT
19:19.45SamotFor the endpoint.
19:19.52SamotIt doesn't know what port to use or what to listen on
19:20.04SamotMisconfigured endpoints do _not load_ in PJSIP
19:20.10bbtok so what do i need to add?
19:20.31[TK]D-Fenderyou need to define the transport in your endpoint
19:20.47SamotWell  is this behind NAT?
19:20.58bbtyes, behind nat
19:21.11[TK]D-Fenderbehind a different NAT than your server?
19:21.21SamotStop. PLEASE
19:21.27SamotIs the PBX behind NAT?
19:21.35bbtyes
19:21.43SamotOK so your transport section needs more settings.
19:21.46Samotexternal_address
19:21.46[TK]D-FenderI cxan have my server behind nat, and my phone behind NAT and it's the SAME NAT router and doesn't affect anything
19:21.50Samotlocal_network
19:22.09Samotexternal_address= <-- That is your WAN IP
19:22.21Samotlocal_network= <-- The local subnets for the PBX.
19:23.16bbtok, what else?
19:23.22SamotThen in the endpoint section you need to add transport=simpletrans
19:23.33SamotSo the endpoint knows what transport it should be using.
19:24.11*** join/#asterisk adnidor (~adnidor@p200300E59742E8000000000000000001.dip0.t-ipconnect.de)
19:24.46bbtok
19:26.20bbtanything else needed?
19:26.39SamotNo. Reload Asterisk..
19:26.42Samotcore reload
19:27.06SamotI mean you probably could do with some refinement on the endpoint..
19:27.28SamotBut the core settings are there now.
19:30.42bbtnot registering
19:31.36SamotNow you show attempts.
19:31.40Samotpjsip set logger on
19:31.54SamotEven before that...
19:32.00Samotpjsip show endpoints
19:32.13SamotWhat is the output of that ^^
19:32.16Samotpjsip show endpoints
19:32.21bbt<PROTECTED>
19:32.22bbt<PROTECTED>
19:32.22bbt<PROTECTED>
19:32.36SamotOK so that's a positive. The endpoint loaded.
19:32.42SamotNow show the register attempt.
19:48.18bbtdont see anything in log, and i have nothing coming up in console
19:51.44SamotAnd what does the phone do?
19:51.56SamotWhat is the failure reason?
19:53.21bbtphone says connection lost, phone page says: Registration failed.
19:54.01SamotWell then you need a tcpdump to see if it is even hitting your server.
19:54.08SamotBecause it doesn't appear to be hitting Asterisk.
19:54.55Samottcpdump -nttv -s 0 -i eth0 port 5060 <-- Replace eth0 with your interface name if it is different.
19:55.10SamotThen make the phone register again
19:56.57bbthttps://pastebin.com/niSHQz5v
19:57.34SamotNeed more then _a_ packet.
19:57.37SamotThis is a transaction.
19:57.42SamotSo what happens..
19:57.53SamotIs there a reply to follow?
19:58.06SamotDoes the phone re-attempt the registration more than once?
19:59.02bbtno reply and three register atemmpts
19:59.22SamotShow your pjsip.conf with all the changes you made.
20:01.13bbthttps://pastebin.com/ApcWcZsV
20:03.34Samotpjsip show transports
20:04.01bbtNo objects found.
20:04.09SamotThen your transport didn't load.
20:04.15SamotYou running Chan_SIP as well?
20:04.21SamotOr did you disable it?
20:04.21bbtno
20:04.34bbthow do i disable it?
20:04.56SamotWell first do: sip show settings
20:05.13bbtNo such command 'sip show settings'
20:05.36Samotmodule show like sip
20:06.18SamotOh damn. This is on me.
20:06.21SamotSomewhat.
20:06.29Samotexternal_media_address
20:06.59Samotexternal_signaling_address
20:07.05bbtall shows pjsip and loaded except this one: res_pjsip_transport_websocket.so PJSIP WebSocket Transport Support        0          Not Running          core
20:07.22SamotReplace external_address with those two
20:07.25SamotSame setting.
20:07.29SamotYour WAN IP.
20:07.59SamotAnd local_net=
20:08.47Samotlocal_network= should be local_net=
20:09.14SamotI don't have to use them generally for my setups so I had a brain fart on the proper setting name.
20:12.04bbtconfused what i need to add
20:12.20Samotmedia_address and local_network are wrong.
20:12.32Samotexternal_media_address=WANIP
20:12.41Samotexternal_signaling_address=WANIP
20:12.50Samotlocal_net=LANSUBNET
20:13.22bbtok
20:13.59Samotupdate it, save it, core reload, pjsip show transports
20:14.04SamotIt should be there now after all that.
20:14.46bbtnope
20:14.54SamotShow what you updated to for the transport
20:14.59bbtlike i said res_pjsip_transport_websocket.so is not loaded all other modules are
20:15.00SamotJust the transport section
20:15.10SamotYou're not using a websocket.
20:15.12SamotSo...
20:17.52bbtnot registering is this cvorrect? https://pastebin.com/sgqAJ6S4
20:18.24SamotSo it show up when you do "pjsip show transports"?
20:18.46bbtNo objects found.
20:19.11Samotcore restart
20:19.39SamotAfter everything is restarted/reloaded
20:19.42Samotpjsip show transports
20:22.16bbtsame again
20:22.32SamotComment out those last three lines in the transport section.
20:22.47bbtoh oh its there
20:23.00bbtTransport:  simpletrans               udp      0      0  0.0.0.0:5060
20:23.15*** join/#asterisk TheHonorableKitt (~TheHonora@gateway/tor-sasl/thehonorablekitt)
20:23.45bbtbut sip phone still not registered
20:25.02SamotOK so now do you see the attempts in Asterisk?
20:26.46bbtregistered
20:26.50bbtthank you!
20:30.17SamotYeah, so you had two issues.
20:30.29Samot1) You didn't have a transport defined in your endpoint.
20:30.45Samot2) Your transport wasn't set up for being behind NAT.
20:30.57SamotJust took a little longer because I gave bad setting names at first.
20:31.29SamotBut "pjsip show endpoints/contacts/aors/transports"
20:31.35[TK]D-Fender<Samot> Comment out those last three lines in the transport section. <-
20:31.45[TK]D-FenderIf he commented them out how as that "fixed"?
20:31.46SamotOh did you do that?
20:31.51SamotHe actually didn't confirm he did
20:32.13SamotJust like he said the transport wasn't there and then it was.
20:32.39[TK]D-FenderSo was it there following undoing what you spent all that time on.
20:32.47SamotI don't know.
20:32.48[TK]D-FenderAnd NAT isn't a factor for him yet
20:32.50[TK]D-Fendereverything is local
20:32.58[TK]D-FenderMaybe soon it would be
20:33.04Samotbbt: Did you comment out those three lines?
20:33.06[TK]D-Fenderbut that would be a separate issue
20:33.10SamotOr did you just do the core restart?
20:34.03Samot[TK]D-Fender: I don't believe the transport was fully reloading itself with just a "core reload"
20:34.33SamotI had him to a "core restart" he said it wasn't there and as soon as I told him to comment out those three lines, he said they were.
20:34.41SamotSo not enough time to comment and do another core restart.
20:34.51bbtcore restart now
20:35.05SamotSo you didn't comment out those three lines?
20:35.05[TK]D-Fenderbbt, that was not what was just asked
20:35.09bbtcore reload didnt do it
20:35.14SamotSo you didn't comment out those three lines?
20:35.20bbtso i did
20:35.24SamotOK
20:35.25bbtyes i did
20:35.28SamotNo uncomment them.
20:35.32SamotSAve and do another core restart
20:35.38SamotNow*
20:36.48filetransports require an explicit option to be enabled to do reloads, because PJSIP doesn't support such things so it uses a hackish mechanism to do so - which can and does fail in certain circumstances
20:36.54SamotYeah
20:37.05SamotThat's what I changed it to core restart
20:37.11bbtstill works with uncomment
20:37.23bbtas i said core reload didnt work, core restart now did
20:37.31SamotYes, because as file mentioned, there is another setting to allow transports to be reloaded
20:38.01Samothttps://github.com/asterisk/asterisk/blob/master/configs/samples/pjsip.conf.sample
20:38.13Samot^^ Should really review this so you can refine your config.
20:38.36bbtok thanks
20:38.40Samotallow_reload=yes <-- This would allow "core reload" to reload transport changes on the specific transport.
20:46.13bbtEndpoint 1002 is now Reachable :)
21:14.43*** join/#asterisk sh_smith (~sh_smith@cpe-76-174-26-91.socal.res.rr.com)
21:21.36*** join/#asterisk rpifan (~rpifan@ipb218f100.dynamic.kabel-deutschland.de)
21:25.45*** join/#asterisk miralin (~Thunderbi@81.177.57.153)
21:26.47*** join/#asterisk rpifan (~rpifan@ipb218f100.dynamic.kabel-deutschland.de)
22:14.41*** join/#asterisk Typhon (~Typhon@dslb-084-056-163-061.084.056.pools.vodafone-ip.de)
22:18.54*** join/#asterisk pvoigt (~Linux@unaffiliated/pvoigt)
22:20.58*** join/#asterisk Ron9 (~rp@185.9.7.216)
22:26.21Ron9I'm struggling to find any information on how to set CallerID Name to local letters like æøåöß. Can anyone help me on how to set these letters in Asterisk CallerID name so it would be showen correctly?
23:09.56*** join/#asterisk tomaluca95 (~quassel@kde/developer/tomaluca)
23:13.50*** join/#asterisk AndChat|620489 (~AndChat62@67-130-74-235.dia.static.qwest.net)
23:14.46*** join/#asterisk ih8wndz (jwpierce3@001.srv.trnkmstr.com)
23:54.47*** join/#asterisk rpifan (~rpifan@ipb218f0f6.dynamic.kabel-deutschland.de)
23:59.27bbtwhat file do i need to edit via cli for incoming and outgoing routes?

Generated by irclog2html.pl Modified by Tim Riker to work with infobot.