Displaying 9 results from an estimated 9 matches for "res_pjsip_endpoint_identifier_user".
2016 Aug 15
2
pjproject 2.5.5 + asterisk-certified-13.8-cert1 : many Error loading module...undefined symbol
...point.so
res_pjsip_acl.so
res_pjsip_authenticator_digest.so
res_pjsip_caller_id.so
res_pjsip_config_wizard.so
res_pjsip_dialog_info_body_generator.so
res_pjsip_diversion.so
res_pjsip_dlg_options.so
res_pjsip_dtmf_info.so
res_pjsip_endpoint_identifier_anonymous.so
res_pjsip_endpoint_identifier_ip.so
res_pjsip_endpoint_identifier_user.so
res_pjsip_exten_state.so
res_pjsip_header_funcs.so
res_pjsip_logger.so
res_pjsip_messaging.so
res_pjsip_multihomed.so
res_pjsip_mwi_body_generator.so
res_pjsip_mwi.so
res_pjsip_nat.so
res_pjsip_notify.so
res_pjsip_one_touch_record_info.so
res_pjsip_outbound_authenticator_digest.so
res_pjsip_outb...
2019 Apr 22
2
Incoming SIP call, outgoing SIP registration. PJSIP.
...ith SIP ID 1121.
Registration is OK.
Server2 outgoing calls are OK.
INVITE, unauthorized, INVITE with password, OK, RINGING,...
Troubles with incoming calls / incoming INVITE's .
I can not identify endpoint by IP, I have multiple registrations on the
same Server1.
As far as I understood, res_pjsip_endpoint_identifier_user match
endpoint by "From" header, so it will not match also.
match_headers also seems useless (not able to match "INVITE" string,
just headers like "TO:").
Is there any way to match incoming INVITE calls ? (also OPTIONS, NOTIFY,
... packets)
It should be a typical...
2015 Mar 06
2
res_pjsip endpoint config object's 'identify_by' option needs new value "uri".
...ptrunk-in]
type=endpoint
transport=udp-transport
context=from-trunk
disallow=all
allow=ulaw
outbound_auth=siptrunk
aors=siptrunk
identify_by=uri
Registration section has option "contact_user". Incoming call from this
registration will be INVITE sip:siptrunk-in at ....
I offer to change res_pjsip_endpoint_identifier_user to realize endpoint
identification by sip uri.
I think it will be usefull.
P.S. i hope issues will be rejected:
https://issues.asterisk.org/jira/browse/ASTERISK-22306 and SWP-6069
Dmitriy Serov
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.di...
2015 Mar 06
2
res_pjsip endpoint config object's 'identify_by' option needs new value "uri".
...sallow=all
> allow=ulaw
> outbound_auth=siptrunk
> aors=siptrunk
> identify_by=uri
>
>
> Registration section has option "contact_user". Incoming call from
> this registration will be INVITE sip:siptrunk-in at ....
> I offer to change res_pjsip_endpoint_identifier_user to realize
> endpoint identification by sip uri.
>
> I think it will be usefull.
>
> P.S. i hope issues will be rejected:
> https://issues.asterisk.org/jira/browse/ASTERISK-22306 and SWP-6069
>
>
> Dmitriy Serov
>
> -
>
>
> I believe...
2015 Mar 06
0
res_pjsip endpoint config object's 'identify_by' option needs new value "uri".
...; context=from-trunk
> disallow=all
> allow=ulaw
> outbound_auth=siptrunk
> aors=siptrunk
> identify_by=uri
>
>
> Registration section has option "contact_user". Incoming call from this
> registration will be INVITE sip:siptrunk-in at ....
> I offer to change res_pjsip_endpoint_identifier_user to realize endpoint
> identification by sip uri.
>
> I think it will be usefull.
>
> P.S. i hope issues will be rejected:
> https://issues.asterisk.org/jira/browse/ASTERISK-22306 and SWP-6069
>
>
> Dmitriy Serov
>
> -
>
I believe what you are looking for is alre...
2013 Sep 24
2
PJSIP Authrentication by IP fails
...sip.so
load => res_pjsip_acl.so
noload => res_pjsip_authenticator_digest.so
load => res_pjsip_caller_id.so
load => res_pjsip_diversion.so
load => res_pjsip_dtmf_info.so
noload => res_pjsip_endpoint_identifier_anonymous.so
load => res_pjsip_endpoint_identifier_ip.so
noload => res_pjsip_endpoint_identifier_user.so
load => res_pjsip_exten_state.so
load => res_pjsip_log_forwarder.so
load => res_pjsip_logger.so
noload => res_pjsip_messaging.so
noload => res_pjsip_mwi.so
load => res_pjsip_nat.so
load => res_pjsip_notify.so
noload => res_pjsip_one_touch_record_info.so
noload => res_p...
2015 Mar 06
0
res_pjsip endpoint config object's 'identify_by' option needs new value "uri".
...ll
>> allow=ulaw
>> outbound_auth=siptrunk
>> aors=siptrunk
>> identify_by=uri
>>
>>
>> Registration section has option "contact_user". Incoming call from this
>> registration will be INVITE sip:siptrunk-in at ....
>> I offer to change res_pjsip_endpoint_identifier_user to realize endpoint
>> identification by sip uri.
>>
>> I think it will be usefull.
>>
>> P.S. i hope issues will be rejected:
>> https://issues.asterisk.org/jira/browse/ASTERISK-22306 and SWP-6069
>>
>>
>> Dmitriy Serov
>>
>> -
>...
2019 Apr 22
2
Incoming SIP call, outgoing SIP registration. PJSIP.
...t;
>> INVITE, unauthorized, INVITE with password, OK, RINGING,...
>>
>> Troubles with incoming calls / incoming INVITE's .
>>
>> I can not identify endpoint by IP, I have multiple registrations on the
>> same Server1.
>>
>> As far as I understood, res_pjsip_endpoint_identifier_user match
>> endpoint by "From" header, so it will not match also.
>>
>> match_headers also seems useless (not able to match "INVITE" string,
>> just headers like "TO:").
>>
>> Is there any way to match incoming INVITE calls ? (also OPTI...
2015 Jul 14
2
pjsip.conf question
...'xxx.xxx.xxx.xxx' and port ''.
[Jul 14 17:28:24] DEBUG[3614] threadpool.c: Increasing threadpool SIP's size by 5
[Jul 14 17:28:24] DEBUG[3689] pjsip: sip_endpoint.c Distributing rdata to modules: Request msg INVITE/cseq=222 (rdata0x7f9e98085848)
[Jul 14 17:28:24] DEBUG[3689] res_pjsip_endpoint_identifier_user.c: Retrieved endpoint 3400
[Jul 14 17:28:24] DEBUG[3689] pjsip: tsx0x25e0538 ..Transaction created for Request msg INVITE/cseq=222 (rdata0x7f9e98085848)
[Jul 14 17:28:24] DEBUG[3689] pjsip: tsx0x25e0538 .Incoming Request msg INVITE/cseq=222 (rdata0x7f9e98085848) in state Null
[Jul 14 17:2...