similar to: pjsip.conf question

I am running asterisk 13.1.0 In pjsip.conf, the endpoint section has an aors and an auth field. I can name the auth field anything I want. The key is to set the auth=field accordingly. However, when I try this with the aors field, it never works. It seems I have to name the aors=field to match the name of the endpoint section. Is this correct? Would there ever be a need for multiple aors to

Currently using PJSIP. First, they want me to get this working with the existing PJSIP configuration, but then setup a second box using chan_sip performing similar work. For PJSIP... I currently have an endpoint configured to a system using IP based authentication. It is configured with a match setting in the endpoint section. All channels coming from that IP address go to this endpoint. They

Ok Dan, try this... I was able to get this to work behind a NAT and with ip address authentication. [global] type = global debug = yes [transport1] type = transport bind = 0.0.0.0 protocol = udp *local_net=<yourlocalnet I.E. 10.10.10.10/24 <http://10.10.10.10/24>>external_media_address=<your public ip address>external_signaling_address=<your public address>*

Hi All, I'm trying to upgrade asterisk server to 1.8.x from my asterisk 1.6, But when making A Call from SIP Client, I got cli Warning ... and no call has been made. My Sip Client is using lib java peers client http://peers.sourceforge.net/ with standard codec PCMU/PCMA [Jan 28 23:03:32] WARNING[1654]: chan_sip.c:8942 process_sdp: Unsupported SDP media type in offer: audio 0 RTP/AVP 0 8

Hi, I created an IAX2 trunk between my old Asterisk 1.4 server (A) and my new one with v. 16.10.0 (B). The trunk seems to be up, and the calls are initiated, eg. an extension from A can dial an extension in B which rings. However, as soon as the extension in B answers, the call is terminated. This is what I see in the console of B: -- Called PJSIP/4053 -- PJSIP/4053-00000002 is ringing

Please help find the cause of strange behavior res_pjsip. Making outgoint call to other sip server (CommuniGatePro), my asterisk suddenly sends BYE after picking up! Partial log of an outgoing call with full debug is attached and on web: http://pastebin.com/tLNCpx4d No diagnostic messages why asterisk suddenly decided to hangup i don't found :( There are suggestions or strong belief

I just realized that you are asking about dynamic AORs, not static Contacts in an AOR. That may be the difference. I have never actually tried giving a dynamic AOR a different name. And you wouldn't want more than one dynamic AOR, you'd just use an AOR that allowed more than 1 contact. On Wed, Apr 1, 2015 at 2:59 PM Trey Hilyard <kctrey at gmail.com> wrote: > I don't know

Not sure why, but Vitelity changed the settings to IP based authentication on me. Here's the new sip.conf settings they sent me. type=friend dtmfmode=auto host=64.2.142.93 allow=all nat=yes canreinvite=no trustrpid=yes sendrpid=yes When I use these settings to originate calls using the sip.conf they sent me, everything works. Action: Originate ActionID: S8 Channel:

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

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

Hi, my log is full of errors from this mobile user: -- Registered SIP '0010106' at 212.93.97.135:7759 [2011-05-17 17:44:05] NOTICE[21456]: chan_sip.c:19804 handle_response_peerpoke: Peer '0010106' is now Reachable. (381ms / 10000ms) [2011-05-17 17:44:06] ERROR[21456]: netsock2.c:245 ast_sockaddr_resolve: getaddrinfo("212.93.97.135:7759", "7759", ...): Name

On Mon, Dec 15, 2014 at 3:54 PM, Dan Cropp <dan at amtelco.com> wrote: > > Yes, everything is behind the same NAT. > > > > For the application I?m working on, the only endpoint is the endpoint to > Vitelity. > > We use AMI to Originate calls from Asterisk endpoint through Vitelity to > phones. > > After that, we control the call through AMI to perform the

Here's an update... My network admin would not turn off the ALG because it would cause several other problems to other phone systems we have. He looked at the sip trace. What he found is the PJSIP trace showed a different IP address than the older chan_sip so he had me change the aor contact to outbound.vitelity.net At this point, it seems to be working (and this is going through a Cisco

On Mon, Dec 15, 2014 at 3:33 PM, Dan Cropp <dan at amtelco.com> wrote: > > Hi George, > > > > Thank you for looking into this. > > This is behind a nat? > > > Just to be clear...both the pbx and local endpoints are behind the same NAT? > [global] > > type = global > > debug = yes > > > > [transport1] > > type = transport

On Mon, Dec 15, 2014 at 7:34 PM, Dan Cropp <dan at amtelco.com> wrote: > > I am not sure if I entered the correct settings for the transport > information. > > For the local_net, I entered my local ip address, but no mask. I will > check with the network admin so he can verify the settings I entered. > > > You need the network and mask. For example if the ip

3rd attempt to post it to the list, please ignore if it is duplicate I have the following problem When trying to setup asterisk 13.1 with PJSIP to connect to my IPV6 capable SIP provider the registration fails. [code][Dec 22 19:24:24] DEBUG[25247] pjsip: tsx0x110736c .Transaction created for Request msg REGISTER/cseq=36181 (tdta0x721d90) [Dec 22 19:24:24] DEBUG[25247] pjsip:

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.

Hello! We recently upgraded one of our customers from 1.4.44 to 1.8.15-cert1. We have several other customers running both versions. The customer in question does not use us as their provider as they?re located in a different country. When they make outgoing calls, there is a 3 second delay between answering the call and the call being established. When debugging this, I found that Asterisk

OK, I need a bit of help here. I'm configuring a new Asterisk 11 system and I accidentally let my firewall rules drop for a day or so. When I logged in today, I found messages like the ones below on my asterisk console. Obviously somebody was trying to take advantage of my carelessness. So can someone explain what would cause these types of messages to show up on my console? I understand

I am having an issue that prevents WebSockets over SSL/TLS (or any kind of encrypted HTTP traffic to Asterisk) from working after an openssl library update. My setup is CentOS 6 x86_64, and initially, with openssl[-devel]-1.0.0-20.el6_2.5.x86_64 . With this openssl versions, https over TCP port 8089 initializes correctly with asterisk-11.7.0. After an upgrade to