I have one single endpoint [inhouse](endpoint-basic) type=endpoint and one section like this [indentify] endpoint=inhouse match=X.Z.Y.X But when I call in from IP X.Z.Y.X, it does not match my peer. It tries to send the call the "default" context, and the number is not found. I know that I should have loaded this module, res_pjsip_endpoint_identifier_ip.so and it is loaded. In fact, all others authentitcation modules are not, since I only identify via IP. I did not load all the methods I will never use. load => res_pjsip.so load => chan_pjsip.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_pjsip_outbound_authenticator_digest.so noload => res_pjsip_outbound_registration.so load => res_pjsip_pidf.so load => res_pjsip_pubsub.so noload => res_pjsip_refer.so noload => res_pjsip_registrar_expire.so noload => res_pjsip_registrar.so load => res_pjsip_rfc3326.so load => res_pjsip_sdp_rtp.so load => res_pjsip_session.so noload => res_pjsip_t38.so noload => res_pjsip_transport_websocket.so load => res_pjsip_acl.so I need to identify the caller, and since there is no way to see the IP address of the caller in the dial plan, at least I need to force Asterisk to match it to a peer. Any ideas?
CDR wrote:> I have one single endpoint > > [inhouse](endpoint-basic) > type=endpoint > > and one section like this > > [indentify] > endpoint=inhouse > match=X.Z.Y.XYou have not provided the complete configuration or console output so it is impossible to know exactly what is going on.> But when I call in from IP X.Z.Y.X, it does not match my peer. It > tries to send the call the "default" context, and the number is not > found. > I know that I should have loaded this module, > res_pjsip_endpoint_identifier_ip.soThe PJSIP functionality has no default endpoint, unless the anonymous module is loaded. Since you have not loaded it either the endpoint IS being used or you are actually using chan_sip. Providing the configuration and console output would illuminate the situation. -- Joshua Colp Digium, Inc. | Senior Software Developer 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA Check us out at: www.digium.com & www.asterisk.org
On 09/24/2013 02:15 AM, CDR wrote:> I have one single endpoint > > [inhouse](endpoint-basic) > type=endpoint > > and one section like this > > [indentify] > endpoint=inhouse > match=X.Z.Y.XYou are missing "type=identify" from this section. The common model of configuration sections in pjsip.conf is that you can name them whatever you wish. The important piece of information when determining what type of configuration section it is is the "type=" option for the section. With no "type=" option set, the configuration section is completely ignored. Mark Michelson
Apparently Analagous Threads
- pjproject 2.5.5 + asterisk-certified-13.8-cert1 : many Error loading module...undefined symbol
- cannot boot domU
- AST-2014-013: PJSIP ACLs are not loaded on startup
- AST-2014-013: PJSIP ACLs are not loaded on startup
- DNS is confusing! (I really need some help understanding!)