Hi Guys, After Bob and Mark information about SIP aware (SIP ALG) device, I search the information about Cisco IOS version and I found that the IOS version for the Cisco we use is already support NAT for SIP and by default is running. After playing and searching around the configuration I managed to disable NAT for SIP support on the router. And now the remote worker support is running good.
For others who have the Cisco router doing NAT and had the same problem with me, here are the command to disable NAT for SIP support: no ip nat service sip tcp port 5060 no ip nat service sip udp port 5060 Thanks all, B. Aidil Sjam > -----Original Message----- > From: Mark Gertsvolf [mailto:[email protected]] > Sent: Monday, May 25, 2009 5:34 AM > To: Boy Aidil Sjam; Robert Joly; [email protected] > Subject: RE: [sipx-users] Media Relay Service Failed > > I am sorry, I did not have time to respond earlier. > The two traces in your email do not match, i.e. they do not correspond > to the same call. > Having said that, I think Bob has identified the problem correctly. > Your Cisco router at the remote worker's site is SIP aware and has a > SIP ALG turned on, which interferes with sipX remote worker logic. The > problem is NOT incompatibility between the remote worker logic and the > SIP ALG, but the fact that The SIP ALG is doing a poor job and hence > your speech path issues and disconnect issues. > The only way forward in this deployment is to disable the SIP > capabilities on the Cisco router and let sipXecs remote worker do the > work uninterrupted. > > Thanks, > Mark. > > > > > > > -----Original Message----- > > From: Boy Aidil Sjam [mailto:[email protected]] > > Sent: May 19, 2009 6:50 AM > > To: Joly, Robert (CAR:9D30); [email protected]; > > Gertsvolf, Mark (CAR:9D30) > > Subject: RE: [sipx-users] Media Relay Service Failed > > > > Additional Trace files. > > All trace files captured at the end-user > > > > > > > > > -----Original Message----- > > > From: Robert Joly [mailto:[email protected]] > > > Sent: Saturday, May 16, 2009 2:26 AM > > > To: [email protected]; [email protected]; Mark > > > Gertsvolf > > > Cc: [email protected] > > > Subject: RE: [sipx-users] Media Relay Service Failed > > > > > > Boy, > > > Please be sure to also capture the registration of the > > remote x-lite. > > > I took a second look at the traces and all signs point to > > some kind of > > > SIP-aware device at the remote site. Please double-check that you > > > have used 'Use local address' as opposed to 'discover > > global address' > > > and that ICE is disabled. If that is the case then your router is > > > likely doing some SIP manipulations. What is your router > > brand & model? > > > > > > Actually, what would prove this without the shadow of a > > doubt would be > > > if you have a simultaneous trace going on the x-lite and on > > the public > > > network. > > > > > > Cheers, > > > bob > > > > > > > -----Original Message----- > > > > From: Boy Aidil Sjam [mailto:[email protected]] > > > > Sent: Friday, May 15, 2009 3:20 PM > > > > To: [email protected]; [email protected]; > > > > Gertsvolf, Mark (CAR:9D30); Joly, Robert (CAR:9D30) > > > > Cc: [email protected] > > > > Subject: RE: [sipx-users] Media Relay Service Failed > > > > > > > > > > > > Robert, > > > > I will tried to capture the packet again as you suggested > > > > > > > > -----Original Message----- > > > > From: Robert Joly > > > > Sent: 16/05/2009 02:11:19 > > > > To: [email protected]; > > [email protected]; Mark > > > > Gertsvolf > > > > Cc: [email protected] > > > > Subject: RE: [sipx-users] Media Relay Service Failed > > > > > > > > Mark, > > > > Thank you for jumping in and looking at this trace. I > > arrive at the > > > > same conclusion. > > > > > > > > Boy, > > > > Although x-lite sends RTP packets exactly at the right > > IP:port, the > > > > audio content of those RTP packets is dead silence. So, at the > > > > packet level, you have bidirectional speech... If you do > > not have > > > > microphone issues, I cannot guess at this point why > > x-lite elects to > > > > mute its transmit for that call. Could you please > > provide a capture > > > > taken directly at PC that it running x-lite? Who knows perhaps, > > > > there's a clue there... > > > > > > > > Cheers, > > > > bob > > > > > > > > > -----Original Message----- > > > > > From: Boy Aidil Sjam [mailto:[email protected]] > > > > > Sent: Friday, May 15, 2009 2:55 PM > > > > > To: Boy Aidil Sjam; Joly, Robert (CAR:9D30); > > > > > [email protected]; Gertsvolf, Mark (CAR:9D30) > > > > > Cc: [email protected] > > > > > Subject: RE: [sipx-users] Media Relay Service Failed > > > > > > > > > > > > > > > nope, the mic is ok, i've tested both as local user, > > and it worked > > > > > correctly. > > > > > > > > > > when the remote worker disconnected first, it took a > > little while > > > > > until the local user status hung up, even I tried to > > > > manually hung up > > > > > > > > > > thanks > > > > > > > > > > -----Original Message----- > > > > > From: Mark Gertsvolf > > > > > Sent: 16/05/2009 01:32:56 > > > > > To: Boy Aidil Sjam; Robert Joly; [email protected] > > > > > Subject: RE: [sipx-users] Media Relay Service Failed > > > > > > > > > > > > > > > Boy Aidil Sjam wrote: > > > > > > Sent: May 15, 2009 2:04 PM > > > > > > To: Joly, Robert (CAR:9D30); Gertsvolf, Mark (CAR:9D30); > > > > > > [email protected] > > > > > > Subject: RE: [sipx-users] Media Relay Service Failed > > > > > > > > > > > > > > > The call seems to be working as expected. The media is > > > > being properly > > > > > relayed in both direction. However, the RTP stream in the > > > > > direction from the remote worker to the internal user contains > > > > > dead > > > > silence. I > > > > > suspect that your microphone is not properly set. > > > > > > > > > > One strange thing I am seeing regarding call disconnect > > sequence. > > > > > For some unknown reason remote X-lite decides to send 200OK > > > > response > > > > > for the BYE transaction in frame 1448 to UDP port 1025. > > There is > > > > > no indication why it would make this choice. > > > > > This causes unclean call disconnect sequence, but it does > > > > not seem to > > > > > be causing any real issues. > > > > > I wonder what happens if you disconnect the call from > > the remote > > > > > worker side. > > > > > > > > > > In any case your main issue might simply be microphone > > > > config at the > > > > > remote worker end. > > > > > > > > > > Cheers, > > > > > Mark. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > =2ÿ > > > > > > > > > > > > > > > > > > > > DISCLAIMER: > > > > > Information in this message is confidential and may be legally > > > > > privileged. It is intended solely for the addressees. > > > > > Access to this message by anyone else is unauthorised. If > > > > you are not > > > > > the intended recipient, any disclosure, copying, or > > distribution > > > > > of the message, or any action or omission taken by you in > > > > reliance on it, > > > > > is prohibited and may be unlawful. > > > > > Please immediately contact the sender if you have received this > > > > > message in error. > > > > > > > > > >=2ÿ > > > > > > > > > > > > > > > > DISCLAIMER: > > > > Information in this message is confidential and may be legally > > > > privileged. It is intended solely for the addressees. > > > > Access to this message by anyone else is unauthorised. If you are > > > > not the intended recipient, any disclosure, copying, or > > distribution > > > > of the message, or any action or omission taken by you in > > reliance > > > > on it, is prohibited and may be unlawful. > > > > Please immediately contact the sender if you have received this > > > > message in error. > > > > > > > > > > > No virus found in this incoming message. > > > Checked by AVG - www.avg.com > > > Version: 8.5.329 / Virus Database: 270.12.30/2115 - Release Date: > > > 05/14/09 17:54:00 > > > > > > > > DISCLAIMER: > > Information in this message is confidential and may be > > legally privileged. It is intended solely for the addressees. > > Access to this message by anyone else is unauthorised. If you > > are not the intended recipient, any disclosure, copying, or > > distribution of the message, or any action or omission taken > > by you in reliance on it, is prohibited and may be unlawful. > > Please immediately contact the sender if you have received > > this message in error. > > > No virus found in this incoming message. > Checked by AVG - www.avg.com > Version: 8.5.339 / Virus Database: 270.12.37/2131 - Release Date: > 05/24/09 07:09:00 DISCLAIMER: Information in this message is confidential and may be legally privileged. It is intended solely for the addressees. Access to this message by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, or distribution of the message, or any action or omission taken by you in reliance on it, is prohibited and may be unlawful. Please immediately contact the sender if you have received this message in error. _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
