Hello. Asterisk 13.2, PJSIP. Problem: I do not get any AMI events when changing the status of the contact. When using chan_sip I got "peerstatus" event. When using res_pjsip and devices (endpoint configuration) I got "peerstatus" event. When using res_pjsip.so and OUTBOUND REGISTRATION WITH OUTBOUND AUTHENTICATION i got "registry" event. When using "ENDPOINT CONFIGURED AS A TRUNK, OUTBOUND AUTHENTICATION" and status on contact changed I do not get any AMI event. I missed something? Tell me how to determine the change in the status of the contact (or endpoint/trunk) through AMI? Simple config: [srv_dev] type=auth auth_type=userpass username=login password=secret [srv_dev] type=aor contact=sip:sip.example.com:5060 qualify_frequency=5 default_expiration=10 max_contacts=1 remove_existing=yes [srv_dev] type=endpoint from_domain=example.com aors=srv_dev outbound_auth=srv_dev rewrite_contact=yes allow=!all,alaw Dmitriy Serov
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I made some tests with asterisk-13.2.0 and chan_pjsip this weekend myself, and came to the same conclusion: some peerstatus events are missing (eg. when contacts become unreachable / unavailable, IIRC), and I could not find a way to get contacts status through AMI. It looks a bit similar to issues 23172, 23173: PJSip missing functionalities. Thanks, - -- Jean-Denis Girard SysNux Syst?mes Linux en Polyn?sie fran?aise http://www.sysnux.pf/ T?l: +689 40.50.10.40 / GSM: +689 87.79.75.27 Le 10/03/2015 21:27, Dmitriy Serov a ?crit :> Hello. > > Asterisk 13.2, PJSIP. > > Problem: I do not get any AMI events when changing the status of the > contact. > > When using chan_sip I got "peerstatus" event. > When using res_pjsip and devices (endpoint configuration) I got > "peerstatus" event. > When using res_pjsip.so and OUTBOUND REGISTRATION WITH OUTBOUND > AUTHENTICATION i got "registry" event. > > When using "ENDPOINT CONFIGURED AS A TRUNK, OUTBOUND AUTHENTICATION" and > status on contact changed I do not get any AMI event. > I missed something? > Tell me how to determine the change in the status of the contact (or > endpoint/trunk) through AMI? > > > Simple config: > [srv_dev] > type=auth > auth_type=userpass > username=login > password=secret > > [srv_dev] > type=aor > contact=sip:sip.example.com:5060 > qualify_frequency=5 > default_expiration=10 > max_contacts=1 > remove_existing=yes > > [srv_dev] > type=endpoint > from_domain=example.com > aors=srv_dev > outbound_auth=srv_dev > rewrite_contact=yes > allow=!all,alaw > > Dmitriy Serov >-----BEGIN PGP SIGNATURE----- iEYEARECAAYFAlUA2aoACgkQuu7Rv+oOo/g8VgCfejBsC/X/47QnKrsoNjl3pewn YRIAnA/IzoxGm/2sQgKEI4gFv6TpwN9Q =Db9Z -----END PGP SIGNATURE-----
On Wed, Mar 11, 2015 at 7:11 PM, Jean-Denis Girard <jd.girard at sysnux.pf> wrote:> -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi, > > I made some tests with asterisk-13.2.0 and chan_pjsip this weekend > myself, and came to the same conclusion: some peerstatus events are > missing (eg. when contacts become unreachable / unavailable, IIRC), and > I could not find a way to get contacts status through AMI. > > It looks a bit similar to issues 23172, 23173: PJSip missing > functionalities. >Yup, it was an oversight in the implementation of 'qualify' for PJSIP endpoints. Dmitriy was kind enough to open an issue for it: https://issues.asterisk.org/jira/browse/ASTERISK-24863 -- Matthew Jordan Digium, Inc. | Director of Technology 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA Check us out at: http://digium.com & http://asterisk.org