search for: match_headers

Thank you George. I will pass along the rfc information to those responsible for the other switch. I missed the match_header addition to Asterisk. Unfortunately, the only header field that seems appropriate is the To header. On a separate box I am now trying to configure the endpoint recognition. Planning on multiple endpoints to the same switch, so I am trying to use the match_header field.

Thanks George I originally didn?t have the 1002@ for the identify. Changed that when things were not working. I changed it back. Unfortunately, the system I am connecting with doesn?t seem to support the line support. Looking at the SIP packets, I see Asterisk send it. Unfortunately, they do not send the line information as part of the INVITE. I checked with some developers of that system

...ssword, 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 scenario, but it does not work... Is there any way to make it working ? ----------...

??? I am having a really bad day trying to get incoming calls to work on Asterisk 13 with PJSIP.? We just migrated from Asterisk 1.8 where everything was working but there seems that something got lost in translation.? No matter what I try I always get a 401 Unauthorized message when receiving a call from the PSTN provider.? I can make calls and the registration is working.? I have tried to

Hi Gang Mitel PBX use 'options' without username to monitor the connection. Therefore Asterisk PJSIP cannot match an unsername against an endpoint and prints a notice on the console. Is there a way to silence this kind of notice? I wonder if identify_by 'header' could solve the issue to match method 'options', but I was not able to find any documentation about this.

...VITE'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 scenario, but it does not work... &...