search for: send_rpid

...tive. The trunk between AST-A and AST-B is configured like this in pjsip.conf and is identical on both machines: [transport-lan] type=transport protocol=udp bind=0.0.0.0 tos=af31 [pbxbeta] type=endpoint disallow=all allow=g722 allow=ulaw transport=transport-lan context=phone-level3 aors=pbxbeta send_rpid=no send_pai=yes trust_id_inbound=yes trust_id_outbound=yes direct_media=yes direct_media_glare_mitigation=outgoing ;direct_media_method=update tos_audio=46 tos_video=34 t38_udptl=no t38_udptl_nat=no [pbxbeta] type=aor contact=sip:{remote IP address}:5060 [pbxbeta] type=identify endpoint=pbxbeta m...

...g=true [DEADDEADBEEF] type=auth md5_cred= realm= auth_type=userpass password=4D7D9A7F1822 nonce_lifetime=32 username=507B495E565B [DEADDEADBEEF] type=endpoint timers_sess_expires=1800 device_state_busy_at=0 dtls_cipher= from_domain= dtls_rekey=0 dtls_fingerprint=SHA-256 direct_media_method=invite send_rpid=false pickup_group= sdp_session=Asterisk dtls_verify=No message_context= mailboxes= named_pickup_group= record_on_feature=automixmon dtls_private_key= named_call_group= t38_udptl_maxdatagram=0 media_encryption_optimistic=false aors=DEADDEADBEEF rpid_immediate=false outbound_proxy= identify_by=usern...

...;* [outbound.vitelity.net] type = aor remove_existing = yes qualify_frequency = 60 contact = sip:64.2.142.93 [outbound.vitelity.net] type = endpoint context = TestApp transport = transport1 aors = outbound.vitelity.net dtmf_mode = rfc4733 force_rport = yes rtp_symmetric = yes rewrite_contact = yes send_rpid = yes trust_id_inbound = yes disallow = all allow = ulaw direct_media = no *from_user=<your main vitelity account name> ; Not subaccount* [outbound.vitelity.net] type = identify endpoint = outbound.vitelity.net match = 64.2.142.93 -------------- next part -------------- An HTML attachment w...

...nd.vitelity.net] type = aor remove_existing = yes qualify_frequency = 60 contact = sip:outbound.vitelity.net [outbound.vitelity.net] type = endpoint context = TestApp transport = transport1 aors = outbound.vitelity.net dtmf_mode = rfc4733 force_rport = yes rtp_symmetric = yes rewrite_contact = yes send_rpid = yes trust_id_inbound = yes disallow = all allow = ulaw direct_media = no [outbound.vitelity.net] type = identify endpoint = outbound.vitelity.net match = 64.2.142.93 Have a great day! Dan

We've been using Asterisk 16 for a while now, and tried turning on send_rpid = yes in my pjsip config for end points.  This solves a problem we're having where attended transfers aren't updating the CallerID when the transfer is complete (it would show the callerID of the party attempting the transfer, and never update after the transfer happened). The side ef...

...> > > > [outbound.vitelity.net] > > type = endpoint > > context = TestApp > > transport = transport1 > > aors = outbound.vitelity.net > > dtmf_mode = rfc4733 > > force_rport = yes > > rtp_symmetric = yes > > rewrite_contact = yes > > send_rpid = yes > > trust_id_inbound = yes > > disallow = all > > allow = ulaw > > direct_media = no > > > > [outbound.vitelity.net] > > type = identify > > endpoint = outbound.vitelity.net > > match = 64.2.142.93 > > > > Have a great day! &gt...

...> > > > [outbound.vitelity.net] > > type = endpoint > > context = TestApp > > transport = transport1 > > aors = outbound.vitelity.net > > dtmf_mode = rfc4733 > > force_rport = yes > > rtp_symmetric = yes > > rewrite_contact = yes > > send_rpid = yes > > trust_id_inbound = yes > > disallow = all > > allow = ulaw > > direct_media = no > > > > [outbound.vitelity.net] > > type = identify > > endpoint = outbound.vitelity.net > > match = 64.2.142.93 > > > > Have a great day! &gt...

...qualify_frequency = 60 > contact = sip:64.2.142.93 > > [outbound.vitelity.net] > type = endpoint > context = TestApp > transport = transport1 > aors = outbound.vitelity.net > dtmf_mode = rfc4733 > force_rport = yes > rtp_symmetric = yes > rewrite_contact = yes > send_rpid = yes > trust_id_inbound = yes > disallow = all > allow = ulaw > direct_media = no > > *from_user=<your main vitelity account name> ; Not subaccount* > > [outbound.vitelity.net] > type = identify > endpoint = outbound.vitelity.net > match = 64.2.142.93 > &...

...0 protocol = udp [outbound.vitelity.net] type = aor remove_existing = yes contact = sip:64.2.142.93 at 5060 [outbound.vitelity.net] type = endpoint context = TestApp transport = transport1 aors = outbound.vitelity.net dtmf_mode = rfc4733 force_rport = yes rtp_symmetric = yes rewrite_contact = yes send_rpid = yes trust_id_inbound = yes allow = all direct_media = no [identify1] type = identify endpoint = outbound.vitelity.net match = 64.2.142.93 When I attempt to use AMI Originate, it's failing. I am not seeing anything with pjsip logging turned on, so it seems to be something with the settings....

On Mon, Dec 15, 2014 at 2:08 PM, Dan Cropp <dan at amtelco.com> wrote: > > Today, I tried the same behavior on Asterisk 13.1.0 and Asterisk 12.2.0. > > > > Same problem is happening with both of them. > > > > Could this be caused by PJPROJECT 2.3? > > > > Anyone have any suggestions for what I can try? > > > > My boss is giving me until

...from phonetype allow=alaw ; from phonetype (G.729 replaced with alaw) direct_media=no context=phone rtp_timeout=120 set_var=__phoneid=12 set_var=__contacttypeid=4 set_var=__phonelineid=78 callerid="Steve Murphy" <101> call_group=2 pickup_group=2 mailboxes=101 at murftest language=en send_rpid=yes send_pai=yes ?OK, that completes the config (I hope). Now, when I run "pjsip show endpoints, I get:? SFO02-HostedPBXPJSip-Dev03*CLI> pjsip show endpoints Endpoint: <Endpoint/CID.....................................> <State.....> <Channels.> I/OAuth: <Aut...

...= 3600 [Biv_Sortie] type = identify endpoint = Biv_Sortie match = orange-obs.fr [Biv_Sortie] type=auth username = Biv_Sortie password=3314C9BA9688C2AA [Biv_Sortie] type=endpoint context = Isdn_Inbound dtmf_mode=rfc4733 disallow=all allow = g722, alaw, g729 direct_media=no trust_id_inbound = yes send_rpid=yes from_user = 75B55BTQUHSG at orange-obs.fr from_domain = orange-obs.fr language = en allow_subscribe = yes auth = Biv_Exit outbound_auth = Biv_Sortie aors = Biv_Sortie Question how can I solve this character problem "@"? 2) resolution of the orange-obs.fr DNS.  I am attaching an extr...

...lpc10,g729,speex,g726aal2,g722 endpoint/allow = ulaw,alaw,adpcm,gsm endpoint/direct_media = no endpoint/force_rport = yes endpoint/rewrite_contact = yes endpoint/rtp_keepalive = 30 endpoint/rtp_symmetric = yes endpoint/rtp_timeout = 60 endpoint/rtp_timeout_hold = 60 endpoint/send_pai = yes endpoint/send_rpid = yes endpoint/trust_id_inbound = yes endpoint/trust_id_outbound = yes endpoint/trust_connected_line = no endpoint/send_connected_line = no endpoint/context = trunkhandler_pbx-sip-t1 Attached sip sessions and debug log... the only thing I found interesting was finding a lack of a log item We SHO...

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)

...4.2.142.93 >> >> [outbound.vitelity.net] >> type = endpoint >> context = TestApp >> transport = transport1 >> aors = outbound.vitelity.net >> dtmf_mode = rfc4733 >> force_rport = yes >> rtp_symmetric = yes >> rewrite_contact = yes >> send_rpid = yes >> trust_id_inbound = yes >> disallow = all >> allow = ulaw >> direct_media = no >> >> *from_user=<your main vitelity account name> ; Not subaccount* >> >> [outbound.vitelity.net] >> type = identify >> endpoint = outbound.vite...

...? IIRC unless you ask them, they don't allow it. > > [outbound.vitelity.net] > type = endpoint > context = TestApp > transport = transport1 > aors = outbound.vitelity.net > dtmf_mode = rfc4733 > force_rport = yes > rtp_symmetric = yes > rewrite_contact = yes > send_rpid = yes > trust_id_inbound = yes > allow = all > direct_media = no > > [identify1] > type = identify > endpoint = outbound.vitelity.net > match = 64.2.142.93 > > When I attempt to use AMI Originate, it's failing. I am not seeing > anything with pjsip logging turn...

...p [outbound.vitelity.net] type = aor remove_existing = yes qualify_frequency = 60 contact = sip:64.2.142.93 [outbound.vitelity.net] type = endpoint context = TestApp transport = transport1 aors = outbound.vitelity.net dtmf_mode = rfc4733 force_rport = yes rtp_symmetric = yes rewrite_contact = yes send_rpid = yes trust_id_inbound = yes disallow = all allow = ulaw direct_media = no [outbound.vitelity.net] type = identify endpoint = outbound.vitelity.net match = 64.2.142.93 Have a great day! Dan From: asterisk-users-bounces at lists.digium.com [mailto:asterisk-users-bounces at lists.digium.com] On B...

...quency = 60 contact = sip:64.2.142.93 [outbound.vitelity.net<http://outbound.vitelity.net>] type = endpoint context = TestApp transport = transport1 aors = outbound.vitelity.net<http://outbound.vitelity.net> dtmf_mode = rfc4733 force_rport = yes rtp_symmetric = yes rewrite_contact = yes send_rpid = yes trust_id_inbound = yes disallow = all allow = ulaw direct_media = no from_user=<your main vitelity account name> ; Not subaccount [outbound.vitelity.net<http://outbound.vitelity.net>] type = identify endpoint = outbound.vitelity.net<http://outbound.vitelity.net> match = 64....

Dan Cropp wrote: > I corrected my local_net setting (based on advice from network admin). > > I have tried several different values for the from_user and still have > the same problem. > > Asterisk receives the OK from Vitelity. > > Asterisk sends the ACK (without a Contact header). A Contact header is not required to be in the ACK. > > Vitelity doesn?t seem to

.../allow_subscribe = no endpoint/allow = !all,g729 aor/qualify_frequency = 30 registration/expiration = 1800 contact_pattern=xxx [xxx](trunk_defaults) sends_auth = yes sends_registrations = yes endpoint/context = extensions remote_hosts = xxx.xx.xx.xx accepts_registrations = no endpoint/send_rpid = yes endpoint/send_pai = yes outbound_auth/username = xxx outbound_auth/password = xxx contact_pattern=xxx -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20151019/1dcc4b09/attachment.html>