On 06/12/2015 02:59 PM, Roberto Fichera wrote: > On 06/12/2015 02:50 PM, AJ NOURI wrote: >> This time Trixbox (192.168.22.10) a linux desktop host (192.168.10.2) and a linux cli host (192.168.10.3) are in the >> same subnet, no routing. >> >> Linphone from the desktop host (192.168.10.2) successfully register to Trixbox, but not pjsua (with same extension): >> >> *./pjsua-x86_64-unknown-linux-gnu --id sip:101 at f192.168.22.10 --registrar sip:192.168.22.10 --realm * --username 101 >> --password user101* > > The --realm * get expanded as --realm *pjsua-x86_64-unknown-linux-gnu* because you have it in your current directory I meant expanded as --realm *pjsystest-x86_64-unknown-linux-gnu* > > try with --realm "*" > >> >> 12:41:07.745 os_core_unix.c !pjlib 2.3 for POSIX initialized >> 12:41:07.746 sip_endpoint.c .Creating endpoint instance... >> 12:41:07.746 pjlib .select() I/O Queue created (0x1e000f0) >> 12:41:07.746 sip_endpoint.c .Module "mod-msg-print" registered >> 12:41:07.746 sip_transport. .Transport manager created. >> 12:41:07.746 pjsua_core.c .PJSUA state changed: NULL --> CREATED >> *12:41:07.746 pjsua_app_conf Invalid SIP URI pjsystest-x86_64-unknown-linux-gnu* >> 12:41:07.746 pjsua_core.c Shutting down, flags=0... >> 12:41:07.746 pjsua_core.c PJSUA state changed: CREATED --> CLOSING >> 12:41:07.746 pjsua_call.c .Hangup all calls.. >> 12:41:07.746 pjsua_media.c .Call 0: deinitializing media.. >> 12:41:07.746 pjsua_media.c .Call 1: deinitializing media.. >> 12:41:07.746 pjsua_media.c .Call 2: deinitializing media.. >> 12:41:07.746 pjsua_media.c .Call 3: deinitializing media.. >> 12:41:07.746 pjsua_pres.c .Shutting down presence.. >> 12:41:08.752 pjsua_core.c .Destroying... >> 12:41:08.752 pjsua_media.c .Shutting down media.. >> 12:41:08.752 sip_endpoint.c .Destroying endpoing instance.. >> 12:41:08.752 sip_endpoint.c .Module "mod-msg-print" unregistered >> 12:41:08.752 sip_transport. .Destroying transport manager >> 12:41:08.752 sip_endpoint.c .Endpoint 0x1df5358 destroyed >> 12:41:08.752 pjsua_core.c .PJSUA state changed: CLOSING --> NULL >> 12:41:08.752 pjsua_core.c .PJSUA destroyed... >> >> >> On Thu, May 21, 2015 at 2:56 AM, AJ NOURI <ajn.bin at gmail.com <mailto:ajn.bin at gmail.com>> wrote: >> >> Connectivity is OK. >> >> linux1(pjsua), linux2(pjsua), Desktop linux(linphone) and Trixbox can ping/trace/ssh/http to each other . >> >> On Thu, May 21, 2015 at 2:32 AM, ?? <sanfarloth at gmail.com <mailto:sanfarloth at gmail.com>> wrote: >> >> Hello, >> >> What's your router setting? It seems like your packets are being blocked by router. >> >> 2015-05-21 8:03 GMT+08:00 David Villasmil Govea <david.villasmil at gmail.com <mailto:david.villasmil at gmail.com>>: >> >> Hello, >> >> Did you run a trace on the asterisk side? >> >> On Thu 21 May 2015 at 01:59 AJ NOURI <ajn.bin at gmail.com <mailto:ajn.bin at gmail.com>> wrote: >> >> Hi everyone, >> >> I have a hard time registering to trixbox using pjsua from Linux machines (192.168.22.1 and 192.168.33.1) >> topology: >> https://drive.google.com/file/d/0BzYXUSsUVFR_UkUtMkk4b18xNzQ/view?usp=sharing >> >> I have configured 3 extensions on the Asterisk call manager (192.168.0.125), here is an example of >> Asterisk configuration: >> https://drive.google.com/file/d/0BzYXUSsUVFR_ZnpkMjFWbURwWnM/view?usp=sharing >> >> I can register with any extension using Linphone (GUI SIP Phone) , located in 192.168.0.121 >> >> Here is how I try to register from pjsua: >> >> >>> +a >> Your SIP URL: (empty to cancel): sip:101 at 192.168.0.125 <mailto:sip%3A101 at 192.168.0.125> >> URL of the registrar: (empty to cancel): sip:192.168.0.125 >> Auth Realm: (empty to cancel): * >> Auth Username: (empty to cancel): 101 >> Auth Password: (empty to cancel): user101 >> 07:54:42.539 pjsua_acc.c Adding account: id=sip:101 at 192.168.0.125 <mailto:sip%3A101 at 192.168.0.125> >> 07:54:42.539 pjsua_acc.c .Account sip:101 at 192.168.0.125 <mailto:sip%3A101 at 192.168.0.125> added >> with id 0 >> 07:54:42.540 pjsua_acc.c .Acc 0: setting registration.. >> 07:54:42.540 pjsua_core.c ...TX 538 bytes Request msg REGISTER/cseq=317 (tdta0x2130d20) to UDP >> *MailScanner has detected a possible fraud attempt from "192.168.0.125:5060" claiming to be* >> *MailScanner warning: numerical links are often malicious:* 192.168.0.125:5060 >> <http://192.168.0.125:5060>: >> REGISTER sip:192.168.0.125 SIP/2.0 >> Via: SIP/2.0/UDP 192.168.33.1:5060;rport;branch=z9hG4bKPj.yCkzLqEWHrpvyKuN4P35HKwfpfWcgz8 >> Max-Forwards: 70 >> From: <sip:101@192.168.0.125 <mailto:sip%3A101 at 192.168.0.125>>;tag=01KRw5An8aWhj7N3tQLsxVdSNR-rxTOS >> To: <sip:101 at 192.168.0.125 <mailto:sip%3A101 at 192.168.0.125>> >> Call-ID: A9IR4N9vlT5KiqNc.bNVf2XTWq8OyOsu >> CSeq: 317 REGISTER >> User-Agent: PJSUA v2.3 Linux-3.13.0.52/x86_64/glibc-2.19 >> Contact: <sip:101 at 192.168.33.1:5060;ob> >> Expires: 300 >> Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS >> Content-Length: 0 >> >> >> --end msg-- >> >> *<...> After multiple tries* >> >> --end msg-- >> 07:55:51.544 pjsua_acc.c ...SIP registration failed, status=408 (Request Timeout) >> 07:55:51.544 pjsua_acc.c ...Scheduling re-registration retry for acc 0 in 294 seconds.. >> >> And here is the tcpdump showing pjsua registering without response from the server: >> https://drive.google.com/file/d/0BzYXUSsUVFR_eE1NRjRRS3psOUE/view?usp=sharing >> >> Note that point-to-point SIP test between 2 pjsua works perfectly. >> >> _______________________________________________ >> Visit our blog: http://blog.pjsip.org >> >> pjsip mailing list >> pjsip at lists.pjsip.org <mailto:pjsip at lists.pjsip.org> >> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org >> >> >> _______________________________________________ >> Visit our blog: http://blog.pjsip.org >> >> pjsip mailing list >> pjsip at lists.pjsip.org <mailto:pjsip at lists.pjsip.org> >> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org >> >> >> >> _______________________________________________ >> Visit our blog: http://blog.pjsip.org >> >> pjsip mailing list >> pjsip at lists.pjsip.org <mailto:pjsip at lists.pjsip.org> >> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org >> >> >> >> >> >> _______________________________________________ >> Visit our blog: http://blog.pjsip.org >> >> pjsip mailing list >> pjsip at lists.pjsip.org >> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org > > > > _______________________________________________ > Visit our blog: http://blog.pjsip.org > > pjsip mailing list > pjsip at lists.pjsip.org > http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/attachments/20150612/66316bd9/attachment.html>
