similar to: Is 100 trying mandatory? Can asterisk answer with 180 without prior 100 trying?

Hello List Asterisk 13.14.1 in use with pjsip stack. On the remote side is a SBC which performs some 'nat' detection. I suppose this means the SBC listens from where it is getting RTP data and then replies to that ip. As long as the asterisk is initiating the call this is fine, the asterisk start sending RTP to the media IP of the SBC and the SBC is sending media back. Now I want to do

Hi List I have been pondering over a problem to use an asterisk server behind an SBC unable to successfully handle registrations. Now I observed something strange which I suspect might be a bug on the asterisk side. The SBC originates is register from Port 6011 to Port 5060 on the Asterisk. The Contact Header of the REGISTER contains: Contact: user at SBC-IP:6011 The Asterisk is sending the

Hello List I work at an SIP Provider and we have added and SBC in front of our Voice Switch to protect it. This requires all our SIP Trunk customers to register via a 'proxy'. I struggle with Asterisk to work over a proxy. This is what I have done so far. register => username at sip.example.com:password at sbc.example.com This works fine, asterisk is sending registrations via the

Hi Joshua Thank you for your reply. Indeed, Ubuntu only ships with this old version. Upgraded to 16.2. via PPA. Problem persisted. Well, I already mentioned that this is a machine with two physical interfaces with different routes which on the 'external' side handles SIP customer registrations and has an 'internal' IC Trunk to a commercial Voice Switch via private IP Range. I

Hi List I wonder how SIP via TCP is supposed to work. Not realy Asterisk related, but I hope you experts might be able to help out :-) One of our customers has a SIP device registering via a complex NAT. To benefit from TCP Connection Tracking, he choose TCP instead of UDP. So he expected, that an incoming call would be sent back to him on the already open TCP connection, making it easy to get

Hi Richard > That could be possible and would be a bug in chan_sip. Ok, so I switched to PJSIP to see if this behaves differently So ip do a Transfer(PJSIP/${DESTNUMBER}@trunk) And this results in: Failed to parse destination URI '[destnumber scrubber]' for channel PJSIP/trunk-00000011 Do I have to specify the destination number differently when using Transfer with pjsip that I

So long as the tcp socket is open your SBC should send the call back over the same socket. Now it can be that your SBC is seeing the socket as timing out. If you are using Kamailio you can have it send tcp keep alives every so often so that the socket stays up. On Fri, Dec 27, 2019 at 10:41 AM Benoit Panizzon <benoit.panizzon at imp.ch> wrote: > Hi List > > I wonder how SIP via

Hi Joshua > The "rtp_keepalive" option can be used to have the RTP stack send an > RTP packet out. Try that and see what happens. Once again 'bullseye' that fixed the problem. Thank you! Mit freundlichen Gr?ssen -Beno?t Panizzon- -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29

Dear fellow list readers This is the situation: ISDN Devices => Patton ISDN to SIP GW => Asterisk PJSIP The Patton GW resides on a dynamic IP address, so I cannot really use match=ip in the identify section. The Patton does not send a line parameter. The ISDN Devices behind the patton have different MSN and should be able to send them in the From: Header, so the default endpoint

Hi Gang According to: https://wiki.asterisk.org/wiki/display/AST/Asterisk+13+Configuration_res_pjsip#Asterisk12Configuration_res_pjsip-endpoint_device_state_busy_at And endpoint should return busy if this number is reached. We have PBX Trunks registering to the Asterisk. So we want to limit the number of concurrent calls to a PBX and return busy, if more than the configured number of channels

Hi Gang Server, two interfaces, routing to two different networks. Two transports defined, each bound to the corresponding ip assigned to the interface. But still, especially when an 183 message is sent, the Contact header does contain the wrong IP Address. Is this a known issue 13.18.3? Or is there a way to make absolutely sure the IP addresses within the Contact header is corresponding 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.

Hi Richard Thank you > You need to set more redirecting information [1]. > > In sip.conf send_diversion=yes needs to be in effect. You also need > to setup > the from party id information (at least the from number) to indicate > where you > are redirecting from. You should also increment the redirecting > count. > > Richard > > [1] >

Hi Gang To get our customers more information on how they registered I am looking for a elegant way to get an information like the CLI command: pjsip show endpoint [endpoint] I had a got on ARI, but that basically only returns the information if an endpoint is online or not. Is there a API to get similar detailed information as the cli command? Mit freundlichen Grüssen -Benoît Panizzon- --

Hello List Next question where google did not spit out an unsable answer. When redirecting a call with Transfer, I would like to correctly indicate the reason. I did try this: exten => XX,1,NoOp(Call to ${EXTEN} from ${CALLERID(all)}) exten => XX,n,Dial(SIP/ZZ) exten => XX,n,set(REDIRECTING(reason)=cfb) exten => XX,n,Transfer(SIP/YY) I did try with 'reason'

Hi List We have some CPE which run an embedded asterisk 13 with chan_sip. Unfortunately, when a registration is rejected, those stop trying. I am familiar with pjsip which allows to configure: auth_rejection_permanent=no How do I achieve the same with chan_sip? Mit freundlichen Grüssen -Benoît Panizzon- -- I m p r o W a r e A G - Leiter Commerce Kunden

Hi List Asterisk 16.28.0 in use. PJSIP in use Two endpoints Both using IPv6 One Endpoint on UDP, the other via TLS. Both with: t38_udptl=yes ;fax_detect=yes ;fax_detect_timeout=30 rtp_ipv6=yes Both sides are T.38 capable and detect fax tone so no need for fax detection on asterisk. Voice calls between the two work fine. But on a Fax call, I see this situation: A <=> Asterisk

Hi Gang To increase security against phished passwords and similar attacks, we consider offering customers to define IP ranges (or GeoIP locations) from which their dynamic registrations are being accepted. I can already look at the source IP in the dial plan, so no issue with validate an INVITE against a source IP. But I would also like to prevent registrations from outside of this

Hi Gang I gave up on running asterisk with two interfaces without it mixing up the ip addresses. So I have removed one transport definition from pjsip.conf Now * keeps complaining: res_pjsip.c:3461 ast_sip_set_tpselector_from_transport_name: Unable to retrieve PJSIP transport 'transport-name' I did a grep on /etc/asterisk for that transport name. It's in any file anymore.

Dear List I fear I stumbled over a bug in asterisk 13.14.1. My 'phones' are roaming around, sometimes some are connecting from ipv6 enabled networks, another time they are not. If a connection is ipv6 I would prefer to use ipv6 to avoid ipv4-nat problems. I have not specified a transport in the endpoint section, so that the appropriate transport which corresponds to the registration