[Spce-user] Interoperability problem with audiocodes cpe devices

[Thilo Bangert]

On Tuesday, June 19, 2012 12:21:46 PM Andrew Pogrebennyk 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.

hhm, do you know more specifics of which audiocodes are affected? we have a 
couple hundred MP-124D in different hardware revisions and firmware versions 
as well as a few MP-118 that we like to hook up to spce/sppro....

i guess we better implement the workaround from the start. care to share the 
details? on the wiki perhaps ;-)

thanks

kind regards
Thilo


> 
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> http://lists.sipwise.com/listinfo/spce-user