[Spce-user] Audiocodes device workaround and permanent registrations
dgrotti at sipwise.com
Tue Jun 11 08:08:57 EDT 2019
mmm, what version are you using?
The path should be set with the proper dummy0 interface. We have other
customers using permanent registration and dummy0 interfaces for Audiocosed.
Make sure to run latest mr6.5.3, as we fixed some problems with
permanent registration and wrong path, in case the Outbound_socket was
selected during the permanent registration creation.
In that case path was wrongly created as:
<sip:lb at DUMMY0_IP:5060;lr;received=sip:sip:RECEIVED_IP;socket=sip:22.214.171.124:5060>
Please notice the double "sip:sip" string.
Make sure to have ngcp-panel with version mr126.96.36.199 or greater.
Head of Customer Support Sipwise GmbH
e: dgrotti at sipwise.com Europaring F15
t: +43(0)130120332 A-2345 Brunn Am Gebirge
w: www.sipwise.com FN: 305595f FG: LG Wiener Neustadt
On 5/31/19 8:14 PM, Jon Bonilla (Manwe) wrote:
> Hi all
> I've changed sip_int in a production system to test the audiocodes workaround.
> Incoming calls stopped working as sems tried to send the calls to the lb to
> I guess that's because permanent registrations have 127.0.0.1 in the path.
> Any other ideas? Should I just change the path in the location table and
> restart the proxy or is there any helper for that scenario?
> Spce-user mailing list
> Spce-user at lists.sipwise.com
More information about the Spce-user