Hi, I have noticed, according to wireshark packet capture that when it doesn't work, comparing to linphone for example, the REGISTER packet sent by pjsua doesn't contain the authorization header. here is the packet capture comparison: https://drive.google.com/file/d/0BzYXUSsUVFR_ZjIxZVN1OUExWms/view?usp=sharing Is there specific cases where authorization header is not included? On Fri, Jun 12, 2015 at 3:53 PM, Roberto Fichera <kernel at tekno-soft.it> wrote: > On 06/12/2015 03:47 PM, AJ NOURI wrote: > > Thanks Riberto, > Corrected, but still the same outcome: > > > I think is better you check the asterisk configuration. > > > *408 (Request Timeout)* > > ./pjsua-x86_64-unknown-linux-gnu --id sip:101 at 192.168.22.10 --registrar > sip:192.168.22.10 --realm "*" --username 101 --password user101 > > --end msg-- > 13:42:42.763 pjsua_core.c .TX 540 bytes Request msg REGISTER/cseq=61089 > (tdta0x7f7bc0001d40) to UDP *MailScanner has detected a possible fraud > attempt from "192.168.22.10:5060" claiming to be* *MailScanner warning: > numerical links are often malicious:* 192.168.22.10:5060 > <http://192.168.22.10:5060>: > REGISTER sip:192.168.22.10 SIP/2.0 > Via: SIP/2.0/UDP 192.168.22.1:5060 > ;rport;branch=z9hG4bKPj3t..o84FfxnPB.0zJMZVj0.XX8W.2uyS > Max-Forwards: 70 > From: <sip:101@192.168.22.10>;tag=484sAHDsFM9zT8.j9Oyfjl-ACl37ri71 > To: <sip:101 at 192.168.22.10> > Call-ID: d8LSfvCMCGNQiqMAFjAdqgEesyz3i7GO > CSeq: 61089 REGISTER > User-Agent: PJSUA v2.3 Linux-3.13.0.52/x86_64/glibc-2.19 > Contact: <sip:101 at 192.168.22.1:5060;ob> <sip:101 at 192.168.22.1:5060;ob> > Expires: 300 > Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, SUBSCRIBE, NOTIFY, > REFER, MESSAGE, OPTIONS > Content-Length: 0 > > > --end msg-- > 13:42:43.260 pjsua_acc.c ...SIP registration failed, status=408 > (Request Timeout) > 13:42:43.260 pjsua_acc.c ...Scheduling re-registration retry for acc 2 > in 295 seconds.. > > > The server is perfectly reachable: > > ping 192.168.22.10 > PING 192.168.22.10 (192.168.22.10) 56(84) bytes of data. > 64 bytes from *MailScanner has detected a possible fraud attempt from > "192.168.22.10" claiming to be* *MailScanner warning: numerical links are > often malicious:* 192.168.22.10 <http://192.168.22.10>: icmp_seq=1 ttl=64 > time=1.34 ms > 64 bytes from *MailScanner has detected a possible fraud attempt from > "192.168.22.10" claiming to be* *MailScanner warning: numerical links are > often malicious:* 192.168.22.10 <http://192.168.22.10>: icmp_seq=2 ttl=64 > time=0.336 ms > 64 bytes from *MailScanner has detected a possible fraud attempt from > "192.168.22.10" claiming to be* *MailScanner warning: numerical links are > often malicious:* 192.168.22.10 <http://192.168.22.10>: icmp_seq=3 ttl=64 > time=0.375 ms > ^C > --- 192.168.22.10 ping statistics --- > 3 packets transmitted, 3 received, 0% packet loss, time 2000ms > rtt min/avg/max/mdev = 0.336/0.684/1.342/0.465 ms > > > > > On Fri, Jun 12, 2015 at 3:39 PM, Roberto Fichera <kernel at tekno-soft.it> > wrote: > >> On 06/12/2015 03:26 PM, AJ NOURI wrote: >> >> Hi, >> >> Hi Roberto, >> Tried with --realm "*" >> >> ./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 >> >> >> there is an 'f' in you sip id, see below: >> >> --id sip:101@*f*192.168.22.10 >> >> >> >> --end msg-- >> 13:18:28.617 pjsua_core.c .TX 542 bytes Request msg >> REGISTER/cseq=19598 (tdta0x18ed770) to UDP *MailScanner has detected a >> possible fraud attempt from "192.168.22.10:5060" claiming to be* *MailScanner >> warning: numerical links are often malicious:* 192.168.22.10:5060 >> <http://192.168.22.10:5060>: >> REGISTER sip:192.168.22.10 SIP/2.0 >> Via: SIP/2.0/UDP 192.168.22.1:5060 >> ;rport;branch=z9hG4bKPj4SepQ9O-akxHk3dFrqqB.bNPZjDMy4fe >> Max-Forwards: 70 >> From: <sip:101@f192.168.22.10> <sip:101 at f192.168.22.10> >> ;tag=wnKcrBK8.2LFrTomN82Df149IIWUrQsh >> To: <sip:101 at f192.168.22.10> <sip:101 at f192.168.22.10> >> Call-ID: QH4lxZczkk89C3AVZOyNMqKxKPS89sQD >> CSeq: 19598 REGISTER >> User-Agent: PJSUA v2.3 Linux-3.13.0.52/x86_64/glibc-2.19 >> Contact: <sip:101 at 192.168.22.1:5060;ob> <sip:101 at 192.168.22.1:5060;ob> >> Expires: 300 >> Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, SUBSCRIBE, NOTIFY, >> REFER, MESSAGE, OPTIONS >> Content-Length: 0 >> >> >> --end msg-- >> 13:18:29.117 pjsua_acc.c ...*SIP registration failed, status=408 >> (Request Timeout)* >> 13:18:29.117 pjsua_acc.c ...Scheduling re-registration retry for acc >> 2 in 57 seconds.. >> >> This is the code observed, still doesn't help to explain the issue: >> >> 408 Request Timeout Couldn't find the user in time. The server could >> not produce a response within a suitable amount of time, for example, if it >> could not determine the location of the user in time. The client MAY repeat >> the request without modifications at any later time. >> >> >> >> On Fri, Jun 12, 2015 at 3:09 PM, Roberto Fichera <kernel at tekno-soft.it> >> wrote: >> >>> 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 >>> <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> 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> 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>: >>>>> >>>>>> 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> 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 >>>>>>> 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 >>>>>>> 07:54:42.539 pjsua_acc.c .Account sip:101 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>;tag=01KRw5An8aWhj7N3tQLsxVdSNR-rxTOS >>>>>>> To: <sip:101 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> >>>>>>> <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 >>>>>>> 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 >>>>> >>>>> >>>> >>> >>> >>> _______________________________________________ >>> Visit our blog: http://blog.pjsip.org >>> >>> pjsip mailing listpjsip at lists.pjsip.orghttp://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org >>> >>> >>> >>> >>> _______________________________________________ >>> Visit our blog: http://blog.pjsip.org >>> >>> pjsip mailing listpjsip at lists.pjsip.orghttp://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 listpjsip at lists.pjsip.orghttp://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 listpjsip at lists.pjsip.orghttp://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/20150614/08ad2a10/attachment.html>
