New subject: [BULK] [Serusers] Mediaproxy sip-asymmetric-clients

22 Apr 2007


      Hi,
I have been using ser with mediaproxy for more than a year without any major
issue.
I have couple of asymmetric UAs, and i'm not able to call them most of the
time. i noticed in my ser.cfg  following lines.
My ser.cfg
===========================
modparam("mediaproxy","sip_asymmetrics","/usr/local/etc/ser/sip-clients")
modparam("mediaproxy","rtp_asymmetrics","/usr/local/etc/ser/rtp-clients")
#
modparam("mediaproxy","sip_asymmetrics","/usr/local/etc/ser/sip-asymmetric-clients")
#
modparam("mediaproxy","rtp_asymmetrics","/usr/local/etc/ser/rtp-asymmetric-clients")
===========================
I have above files in ser folder, and i tried to put user agent in
sip-clients file, i don't know if i'm doing it right.
Ii'm still trying to figure it out, what should i put in these sip-clients
and rtp-clients files (username? URI ), and how do i know if they are
working. I just put UA 5007860215 and restarted ser and mediaproxy but ngrep
are same.
my sip-clients file is as follows:
########### START ##################
# Lines starting with a '#' character or empty lines are ignored.
# Put a User-Agent name or regular expression per line.
# Check is case insensitive.
#
# This file should only list SIP clients that are asymmetric regarding
# the SIP signaling. For clients that are asymmetric regarding the RTP
# media streams, use the equivalent RTP version of this file.
# Clients that are asymmetric for both SIP signaling as well as RTP media
# streams should go in both files.
#
ipDialog SipTone.*  #<== what is it?
5007860215
########### END OF FILE############
client sending keep alive message, reason i setup keep alive on my client is
becouse they were keep loosing registration, so that problem is solved.
Following asymentric client coming through port 50005 and SER sending reply
at port 5060.
#################
U XX.XX.55.170:50005 -> XX.XX.66.231:5060
  NOTIFY sip:ser.mydomain.com SIP/2.0..Via: SIP/2.0/UDP
192.168.1.25:5060;branch=z9hG4bK-2173a014..From: Tony <
sip:5007860215@ser.mydomain.com>;tag=a11c95e2a205caa8o0..To: sip:
ser.mydomain.com..Call-ID: 9b70d42-e62ebac8@192.168.1. 25..CSeq: 4043
NOTIFY..Max-Forwards: 70..Event: keep-alive..User-Agent: Sipura/SPA1001-
3.1.8(SEc)..Content-Length: 0. ...
#
U XX.XX.66.231:5060 -> XX.XX.55.170:5060
  SIP/2.0 404 User Not Found..Via: SIP/2.0/UDP 192.168.1.25:5060
;branch=z9hG4bK-ceived=XX.XX.55.170..From: Tony
sip:5007860215@ser.mydomain.com;tag=a11c95e2a205caa8o0..To:
sip:ser.mydomain.com;tag=e4b88024d5465a32af4d4d872ac6bb61.0ce2..Call-ID:
9b70d42-e62ebac8@192.168.1.25..CSeq: 4043 NOTIFY..Server: Sip EXpress router
(0.9.5-pre4
   (i386/linux))..Content-Length: 0..Warning: 392
ser.mydomain.com:5060"Noisy feedback tells:  pid=14718 req_src_ip=
70.18.55.170 req_src_port=50005 in_uri=sip:ser.mydomain.com out_uri=sip:
ser.mydomain.com via_cnt==1"....
################
If i ping my UA with (serctl ping sip:5007860208@ser.mydomain.com) i get
following ngrep. It appears that SER has no problem reaching UA at port
50005.
###################
U XX.XX.66.231:5060 -> XX.XX.55.170:50005
  OPTIONS sip:5007860215@192.168.1.25:5060 SIP/2.0..Max-Forwards:
10..Record-Route:
sip:XX.XX.66.231;ftag=887df13cdb9661be5c6769ac08d69940-385f;lr=on..Via:
SIP/2.0/UDP XX.XX.66.231;branch=z9hG4bK88b5.16ac1512.0..Via: SIP/2.0/UDP
67.83.66.231;branch=z9hG4bK88b5.06ac1512.0..To: <sip:5007860215@ser.igranet.com
...
..From: sip:daemon@ool-435342e7.covad.net;tag=887df13cdb9661be5c6769ac08d69940-385f..CSeq:
10 OPTIONS..Call-ID: 7effbd40-0@XX.XX.66.231..Content-Length: 0..User-Agent:
Sip EXpress router(0.9.5-pre4 (i386/linux))..Contact:<
sip:daemon@XX.XX.66.231:5060>....
#
U XX.XX.55.170:50005 -> XX.XX.66.231:5060
  SIP/2.0 200 OK..To: <
sip:5007860215@ser.igranet.com>;tag=8b659eab4f39640i0..From:
sip:daemon@ool-435342e7.covad.net;tag=887df13cdb9661be5c6769ac08d69940-385f..Call-ID:
7effbd40-0@XX.XX.66.231..CSeq: 10 OPTIONS..Via: SIP/2.0/UD
  P XX.XX.66.231;branch=z9hG4bK88b5.16ac1512.0..Via: SIP/2.0/UDP
XX.XX.66.231;branch=z9hG4bK88b5.06ac1512.0..Record-Rou
  te: sip:XX.XX.66.231;ftag=887df13cdb9661be5c6769ac08d69940-385f;lr=on..Server:
Sipura/SPA1001-3.1.8(SEc)..Content-L
  ength: 0..Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS,
REFER..Supported: x-sipura....
##################
please help...
Ali....