search for: sub_min_expiry

...Description A remotely exploitable crash vulnerability exists in the PJSIP channel driver's pub/sub framework. If an attempt is made to unsubscribe when not currently subscribed and the endpoint's "sub_min_expiry" is set to zero, Asterisk tries to create an expiration timer with zero seconds, which is not allowed, so an assertion raised. Resolution Upgrade to a version with the patch integrated, apply the patch...

...Description A remotely exploitable crash vulnerability exists in the PJSIP channel driver's pub/sub framework. If an attempt is made to unsubscribe when not currently subscribed and the endpoint's "sub_min_expiry" is set to zero, Asterisk tries to create an expiration timer with zero seconds, which is not allowed, so an assertion raised. Resolution Upgrade to a version with the patch integrated, apply the patch...

...2014-005: Remote Crash in PJSIP Channel Driver's Publish/Subscribe Framework A remotely exploitable crash vulnerability exists in the PJSIP channel driver's pub/sub framework. If an attempt is made to unsubscribe when not currently subscribed and the endpoint's ???sub_min_expiry??? is set to zero, Asterisk tries to create an expiration timer with zero seconds, which is not allowed, so an assertion raised. * AST-2014-008: Denial of Service in PJSIP Channel Driver Subscriptions When a SIP transaction timeout caused a subscription to be terminated, the action taken...

...2014-005: Remote Crash in PJSIP Channel Driver's Publish/Subscribe Framework A remotely exploitable crash vulnerability exists in the PJSIP channel driver's pub/sub framework. If an attempt is made to unsubscribe when not currently subscribed and the endpoint's ???sub_min_expiry??? is set to zero, Asterisk tries to create an expiration timer with zero seconds, which is not allowed, so an assertion raised. * AST-2014-008: Denial of Service in PJSIP Channel Driver Subscriptions When a SIP transaction timeout caused a subscription to be terminated, the action taken...

Asterisk 13.8 Is CALLERID(all) supposed to wok for pjsip? When I do this: exten => 1234,Set(CALLERID(all)="Jon Doe" <+123456789>) same => n,Dial(PJSIP/phone123, 30) I expect the callerid to be as set, but is always seems to be "phone123", the name of the endpoint. Andrew -------------- next part -------------- An HTML attachment was scrubbed... URL:

...otocol=udp bind=0.0.0.0:5160 local_net=192.0.0.0/24 external_media_address=192.168.0.196 external_signaling_address=192.168.0.196 [6001] type=endpoint context=callcenter disallow=all allow=g729 allow=ulaw allow=gsm auth=6001 aors=6001 transport=transport-udp-nat direct_media=no allow_subscribe=yes sub_min_expiry=30 [6001] type=auth auth_type=userpass password=6001 username=6001 [6001] type=aor max_contacts=99 Has anyone experienced the same problem? I upgraded my asterisk to 17 and the problem still persists. Thanks! -------------- next part -------------- An HTML attachment was scrubbed... URL: &lt...

...c=false aors=DEADDEADBEEF rpid_immediate=false outbound_proxy= identify_by=username inband_progress=false rtp_symmetric=false transport=transport-udp rtp_keepalive=0 t38_udptl_ec=none fax_detect=false t38_udptl_nat=false allow_transfer=true tos_video=0 srtp_tag_32=false timers_min_se=90 call_group= sub_min_expiry=0 100rel=yes direct_media=true rtp_timeout_hold=0 g726_non_standard=false dtmf_mode=rfc4733 voicemail_extension= rtp_timeout=0 dtls_cert_file= media_encryption=no media_use_received_transport=false direct_media_glare_mitigation=none trust_id_inbound=false force_avp=false record_off_feature=automixm...

On 06/05/2017 at 11:30 AM, Joshua Colp wrote: > On Sun, Jun 4, 2017, at 10:40 AM, Michael Maier wrote: >> On 06/04/2017 at 01:41 PM Telium Technical Support wrote: >>> Just a guess (without knowing about your network), but are the two ends >>> points on public networks and visible to one another? If not the reinvite >>> may be passing an internal (nat'ed)