Displaying 9 results from an estimated 9 matches for "sip_endpoint".
2017 Jun 15
2
asterisk 13.16 / pjsip / t.38: res_pjsip_t38.c:207 t38_automatic_reject: Automatically rejecting T.38 request on channel 'PJSIP/91-00000007'
...o you have an idea?
>
> Not without setting up the scenario and digging deep into it. Nothing
> immediately springs to mind.
>
After enabling pjsip specific debug log in asterisk, I can see, the
following behavior:
Incoming packages from network are always signaled like this (e.g.):
sip_endpoint.c Processing incoming message: Request msg INVITE/cseq=10 (rdata0x7f5f1801a758)
<--- Received SIP request (918 bytes) from UDP:195.185.37.60:5060
...
The path of the critical not existing package is like this and can't
be seen elsewhere (there wasn't any corresponding incoming
messag...
2017 Jun 14
2
asterisk 13.16 / pjsip / t.38: res_pjsip_t38.c:207 t38_automatic_reject: Automatically rejecting T.38 request on channel 'PJSIP/91-00000007'
...t;> +++ a/res/res_pjsip/pjsip_distributor.c 2017-06-13 20:25:27.233000000
>> +0200
>> @@ -407,6 +407,7 @@
>> /* We have a BYE or CANCEL request without a serializer.
>> */
>> pjsip_endpt_respond_stateless(ast_sip_get_pjsip_endpoint(),
>> rdata,
>> PJSIP_SC_CALL_TSX_DOES_NOT_EXIST, NULL, NULL,
>> NULL);
>> + ast_debug(3, "PJ_TRUE 1\n");
>> return PJ_TRUE;
>> } else {
>>...
2013 Sep 02
2
Asterisk 12 issue
hello,
I' trying to use Asterisk 12 Alpha.
Compilation and instalation without issues.
When I try to start asterisk with:
asterisk -cvvvvvvvvvvvvvvv
i see this error on the console:
17:09:43.559 sip_endpoint.c !Module "mod-refer" registered
asterisk: ../src/pjsip-simple/evsub.c:415: pjsip_evsub_register_pkg:
Assertion `mod_evsub.mod.id != -1' failed.
Any hints?
Thank you
Regards
2016 Mar 07
2
Asterisk now available with bundled pjproject!
On Mon, Mar 7, 2016 at 2:53 PM, Jean-Denis Girard <jd.girard at sysnux.pf>
wrote:
> Hi,
>
> Le 07/03/2016 09:28, George Joseph a ?crit :
> > PLEASE TRY THIS!! I'd love some feedback BEFORE 13.8.0 is released.
>
> I have tried GIT-master-ee5a944M on my Fedora 23 test server, and got:
>
> [pjproject] Unpacking /tmp/pjproject-2.4.5.tar.bz2
> [pjproject]
2017 May 09
2
asterisk 13.15.0 stopping/crashing
hi,
i have strange problem with asterisk 13.15.0+pjsip bundled/centos
7/systemd start script
we are using chan_pjsip only for webrtc endpoints . switched from sipml5
to jssip with upgrade to 13.15.0(from 13.9.0) few days ago
today i have problems with stopping/crashing asterisk
/var/log/asterisk/messages dont show any clues
[May 9 12:10:52] WARNING[25762] pjproject: tsx0x7fbb28024088
2015 Jul 14
2
pjsip.conf question
...rks fine with a 3rd party. Third party does not use authentication or registration, it's ip based authentication...
When I try switching to PJSIP.conf, I seeing 488 responses from the Asterisk side.
What has me really baffled is the debugging indicates
[Jul 14 17:28:24] DEBUG[3620] pjsip: sip_endpoint.c Processing incoming message: Request msg INVITE/cseq=222 (rdata0x7f9e98129f38)
[Jul 14 17:28:24] DEBUG[3620] netsock2.c: Splitting 'xxx.xxx.xxx.xxx:1662' into...
[Jul 14 17:28:24] DEBUG[3620] netsock2.c: ...host 'xxx.xxx.xxx.xxx' and port '1662'.
[Jul 14 17:28:24] DEBUG[36...
2023 Aug 09
1
[External] Encountered a crash, what is best way to tell if it has been fixed or now
...nat") at astobj2_container.c:414
#6 0x00007f7738019ddf in process_nat (tdata=0x7f773c633ac8) at res_pjsip_nat.c:470
#7 nat_on_tx_message (tdata=0x7f773c633ac8) at res_pjsip_nat.c:479
#8 0x00007f777bc6fc66 in endpt_on_tx_msg (endpt=<optimized out>, tdata=0x7f773c633ac8) at ../src/pjsip/sip_endpoint.c:1115
#9 0x00007f777bc77c69 in pjsip_transport_send (tr=0x55e7c1ac7708, tdata=tdata at entry=0x7f773c633ac8, addr=addr at entry=0x7f773c633cb8, addr_len=addr_len at entry=16, token=token at entry=0x7f773c635950,
cb=cb at entry=0x7f777bc71610 <stateless_send_transport_cb>) at ../src/pjsi...
2017 Jun 18
2
asterisk 13.16. - sigseg during negotiation
...b00a8) at ../src/pjsip/sip_dialog.c:1711
#13 0x00007fba44b65bde in mod_ua_on_rx_request (rdata=0x7fba3c0b00a8) at ../src/pjsip/sip_ua_layer.c:704
#14 0x00007fba44b42b1e in pjsip_endpt_process_rx_data (endpt=0x36cc2a8, rdata=0x7fba3c0b00a8, p=0x7fba05c8d0a0, p_handled=0x7fb9f5901b7c) at ../src/pjsip/sip_endpoint.c:887
#15 0x00007fba05a72c59 in distribute (data=0x7fba3c0b00a8) at res_pjsip/pjsip_distributor.c:770
#16 0x00000000005ed6d1 in ast_taskprocessor_execute (tps=0x7fba3c0400a0) at taskprocessor.c:965
#17 0x00000000005f7056 in execute_tasks (data=0x7fba3c0400a0) at threadpool.c:1322
#18 0x00000000005e...
2023 Aug 09
2
Encountered a crash, what is best way to tell if it has been fixed or now
On Wed, Aug 9, 2023 at 3:20 PM Dan Cropp <dcropp at amtelco.com> wrote:
> I have a customer who just encountered a crash while running Asterisk
> 18.17.1 version.
>
>
>
> I’m trying to adapt to the changes so not sure where best to look or how
> to possibly report this.
>
>
>
> I started by going through
>