similar to: SIP topology hiding

On Tue, Apr 9, 2013 at 1:22 PM, Bogdan-Andrei Iancu <bogdan at opensips.org>wrote: > ** > Hi Nick, > > The BYE is not properly formed and rejected by script - in the 200 OK of > the INVITE, you can see that your opensips is doing Record-Routing, but the > BYE does not contain the corresponding Route hdr, so SIP routing is > impossible. > > Regards, > >

does anyone use OpenSBC , or know if it is mature stable opensource for a production enviroment http://rpm.pbone.net/index.php3/stat/4/idpl/10795970/com/opensbc-1.1.4-3.el5.pp.i386.rpm.html -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20091201/67c95aac/attachment.htm

I have a problem where SIP calls from some providers are dropping at 15 minutes. The topology is: Client sends calls to a host running OpenSIPS, OpenSIPS sends calls to an Asterisk server. Below, 'Client' is the IP address of the client's host (running FPBX-2.8.1(1.8.20.0) 'OpenSIPS' is the IP address of my host running OpenSIPS 1.7.2-tls 'Asterisk' is the IP

Hello, I have a question about best practice (or recommended practice) for allowing SIP registrations from the Internet. This is what I was thinking of implementing: 1. Use OpenSips for the SBC, enable SRTP and TLS 2. Allow limited access to the actual Asterisk PBX (behind firewall) via OpenSips Is there anything that I am missing that probably should be implemented? Thanks, Richard

Hello all, ? I have some issues with the MeetMe application. ? The working topology is as follows. The Asterisk (1.4.22-rc5) is connected through SIP trunk to a Call Manager (6.1.2) which is connected to a Cisco Voice Gateway. The Gateway is connected to PSTN through a PRI. The calls are forwarded to Asterisk by the CM. ? The problem is that some users who are calling in from PSTN are getting

One of the above is frequently used to front-end Asterisk. I used OpenSER to front-end a farm of Asterisk servers and was very happy with it. The ability to take a box out of service or to route a specific DNIS to a box for testing rocks. Since OpenSER has died (I don't care about the politics/personalities/trademarks), Kamailio and OpenSIPS have risen from the ashes. What are you using?

*Hi All, I have starting to reading About SBC and found one artical reagding SBC and they gives a solutions like this. i want to know is this true in realtime sceanario while we think of an big implementation and is it possible with cloud computing. i have found from http://www.smartvox.co.uk/products_gateways_explained.htm Asterisk as a Session Border Controller* Equip the Asterisk server

Hey John, In one installation I have, we use several monitoring tools (nagios based and custom scripts based) and we have the following: ; Reply OK to SIP:OPTIONS [public] exten => s,1,Wait(1) same => n,Hangup : For Nagios exten => nagios,1,Wait(1) same => n,Hangup NOTES: 1- We have context=public in sip.conf, if you have anything else, you must update the dialplan above

Finally! For a very long time, our MST helpers have had one very annoying issue: They don't know how to reprobe the topology state when coming out of suspend. This means that if a user has a machine connected to an MST topology and decides to suspend their machine, we lose all topology changes that happened during that period. That can be a big problem if the machine was connected to a

I've got this setup in a test context. [test] exten => s,hint,SIP/7124 exten => s,1,NoOP(Options to $EXTEN) same => n,Hangup() exten => _x.,hint,SIP/7124 exten => _X.,1,NoOP(Options to $EXTEN) same => n,Hangup() exten => Anonymous,hint,SIP/7124 exten => Anonymous,1,NoOP(Options to $EXTEN) same => n,Hangup() I added hints to see if that would make a difference

On Tue, Sep 03, 2019 at 04:46:03PM -0400, Lyude Paul wrote: > Finally! For a very long time, our MST helpers have had one very > annoying issue: They don't know how to reprobe the topology state when > coming out of suspend. This means that if a user has a machine connected > to an MST topology and decides to suspend their machine, we lose all > topology changes that happened

On Fri, Aug 21, 2020 at 03:15:34PM +0200, Jean-Philippe Brucker wrote: > Add a topology description to the virtio-iommu driver and enable x86 > platforms. > > Since [v2] we have made some progress on adding ACPI support for > virtio-iommu, which is the preferred boot method on x86. It will be a > new vendor-agnostic table describing para-virtual topologies in a > minimal

Hi, On 8/21/20 3:15 PM, Jean-Philippe Brucker wrote: > Add a topology description to the virtio-iommu driver and enable x86 > platforms. > > Since [v2] we have made some progress on adding ACPI support for > virtio-iommu, which is the preferred boot method on x86. It will be a > new vendor-agnostic table describing para-virtual topologies in a > minimal format. However some

On Tue, Sep 17, 2013 at 05:41:12PM +0800, Peeyush Gupta wrote: > Hi all, > > I have been trying to find out cpu topology using libvirt. When > I do 'virsh capabilites', I find this inside <topology> tag: > > > <topology> >       <cells num='1'> >         <cell id='0'> >           <memory

While this isn't a complete fix, this will improve the reliability of drm_dp_get_last_connected_port_and_mstb() pretty significantly during hotplug events, since there's a chance that the in-memory topology tree may not be fully updated when drm_dp_get_last_connected_port_and_mstb() is called and thus might end up causing our search to fail on an mstb whose topology refcount has reached 0,

While this isn't a complete fix, this will improve the reliability of drm_dp_get_last_connected_port_and_mstb() pretty significantly during hotplug events, since there's a chance that the in-memory topology tree may not be fully updated when drm_dp_get_last_connected_port_and_mstb() is called and thus might end up causing our search to fail on an mstb whose topology refcount has reached 0,

Hi When I create a domain from xml file, the vcpu number point in <vcpu/>, I not point <cpu><topology> in xml file, when allocate more than 2 vpcus, some(windows) system can't use all vcpu. But I point <cpu><topology sockets='1' cores='num' threads='1'/></cpu>. num is <vcpu>'num'</vcpu>. then whindows can

Add a lightweight method to describe the IOMMU topology in the config space, guarded by a new feature bit. A list of capabilities in the config space describes the devices managed by the IOMMU and their endpoint IDs. Signed-off-by: Jean-Philippe Brucker <jean-philippe at linaro.org> --- virtio-iommu.tex | 88 ++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 88 insertions(+)

On Fri, Sep 04, 2020 at 06:24:12PM +0200, Auger Eric wrote: > Hi, > > On 8/21/20 3:15 PM, Jean-Philippe Brucker wrote: > > Add a topology description to the virtio-iommu driver and enable x86 > > platforms. > > > > Since [v2] we have made some progress on adding ACPI support for > > virtio-iommu, which is the preferred boot method on x86. It will be a >

On Fri, Sep 04, 2020 at 06:24:12PM +0200, Auger Eric wrote: > Hi, > > On 8/21/20 3:15 PM, Jean-Philippe Brucker wrote: > > Add a topology description to the virtio-iommu driver and enable x86 > > platforms. > > > > Since [v2] we have made some progress on adding ACPI support for > > virtio-iommu, which is the preferred boot method on x86. It will be a >