[Spce-user] Interoperability problem with audiocodes cpe devices

[Vladimir Grujic]

Found it. Dispatcher file in the db dir still holds the old data. This is
must be addedd to ngcpcfg apply procedure on interface change

Vladimir


On Tue, Jun 19, 2012 at 12:54 PM, Vladimir Grujic <hyperbabac at gmail.com>wrote:

> I have changed the iaddress to private network (existing interface) but
> now subscribers can not login . LB trying to relay request to
> 127.0.0.1:5062 and proxy is listening on private address
>
>
> Vladimir
>
>
> On Tue, Jun 19, 2012 at 12:21 PM, Andrew Pogrebennyk <
> apogrebennyk at sipwise.com> wrote:
>
>> On 06/19/2012 11:57 AM, Andrew Pogrebennyk wrote:
>> > Vladimir,
>> >
>> > we've had a problem like this before when mp202 was replacing 127.0.0.1
>> > address in Record-Route headers (added by spce internal components) with
>> > its own IP address. Could you run 'ngrep-sip b' and send us the trace to
>> > know if that is the case? You can send it to me privately to not
>> > disclose any IP addresses.
>>
>> A follow-up from discussion in private: this is indeed a known bug in
>> Audiocodes.  SPCE is routing calls via a SIP loadbalancer, a SIP proxy
>> and an SBC internally, and we have two record routes via 127.0.0.1 which
>> are wrongly rewritten by the MP252 to its public IP address. An ACK
>> message then can't reach the UAS. In case somebody wonders there is
>> workaround to setup dummy network interface and change iaddress to that.
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20120619/0c92d390/attachment-0001.html>