[Users] 200 ok not cought in ONREPLY

Dan-Cristian Bogos dan.bogos at gmail.com
Thu Feb 1 14:48:06 CET 2007


Hi Guys,

By receiving incoming traffic from some other sip server (configured
for different domain than mines) I will not be able to catch in the
routing, onreply section, the 200 OK for the INVITE , OK which my
client, behind my server, is sending to remote side, therefore not
beeing able to modify sdp to use mediaproxy. Bellow is a level8 of
debug of the OK.
Is there any other way of catching this message in the routing? Any
help will be appreciated.

Thxs in advance,
Dan

Feb  1 13:33:48 localhost /usr/local/sbin/openser[17816]: SIP Reply  (status):
Feb  1 13:33:48 localhost /usr/local/sbin/openser[17816]:  version: <SIP/2.0>
Feb  1 13:33:48 localhost /usr/local/sbin/openser[17816]:  status:  <200>
Feb  1 13:33:48 localhost /usr/local/sbin/openser[17816]:  reason:  <OK>
Feb  1 13:33:48 localhost /usr/local/sbin/openser[17816]:
parse_headers: flags=2
Feb  1 13:33:48 localhost /usr/local/sbin/openser[17816]: Found param
type 232, <branch> = <z9hG4bKeaa9.11b641a2.0>; state=16
Feb  1 13:33:48 localhost /usr/local/sbin/openser[17816]: end of
header reached, state=5
Feb  1 13:33:48 localhost /usr/local/sbin/openser[17816]:
parse_headers: Via found, flags=2
Feb  1 13:33:48 localhost /usr/local/sbin/openser[17816]:
parse_headers: this is the first via
Feb  1 13:33:48 localhost /usr/local/sbin/openser[17816]: After parse_msg...
Feb  1 13:33:48 localhost /usr/local/sbin/openser[17816]:
forward_reply: found module nathelper, passing reply to it
Feb  1 13:33:48 localhost /usr/local/sbin/openser[17816]:
parse_headers: flags=20
Feb  1 13:33:48 localhost /usr/local/sbin/openser[17816]: Found param
type 232, <branch> = <z9hG4bKeaa9.2ffc88b3.0>; state=16
Feb  1 13:33:48 localhost /usr/local/sbin/openser[17816]: end of
header reached, state=5
Feb  1 13:33:48 localhost /usr/local/sbin/openser[17816]:
parse_headers: Via found, flags=20
Feb  1 13:33:48 localhost /usr/local/sbin/openser[17816]:
parse_headers: this is the second via
Feb  1 13:33:48 localhost /usr/local/sbin/openser[17816]: Found param
type 234, <received> = <87.139.12.167>; state=6
Feb  1 13:33:48 localhost /usr/local/sbin/openser[17816]: Found param
type 235, <rport> = <5096>; state=6
Feb  1 13:33:48 localhost /usr/local/sbin/openser[17816]: Found param
type 232, <branch> = <z9hG4bK521554023>; state=16
Feb  1 13:33:48 localhost /usr/local/sbin/openser[17816]: end of
header reached, state=5
Feb  1 13:33:48 localhost /usr/local/sbin/openser[17816]:
parse_headers: Via found, flags=20
Feb  1 13:33:48 localhost /usr/local/sbin/openser[17816]: DEBUG:
add_param: tag=8b2d7e45
Feb  1 13:33:48 localhost /usr/local/sbin/openser[17816]:
DEBUG:parse_to:end of header reached, state=29
Feb  1 13:33:48 localhost /usr/local/sbin/openser[17816]:
DBUG:parse_to: display={}, ruri={sip:dan at de.babble.net}
Feb  1 13:33:48 localhost /usr/local/sbin/openser[17816]: DEBUG:
get_hdr_field: <To> [38]; uri=[sip:dan at de.babble.net]
Feb  1 13:33:48 localhost /usr/local/sbin/openser[17816]: DEBUG: to
body [<sip:dan at de.babble.net>]
Feb  1 13:33:48 localhost /usr/local/sbin/openser[17816]:
get_hdr_field: cseq <CSeq>: <20> <INVITE>
Feb  1 13:33:48 localhost /usr/local/sbin/openser[17816]:
forward_reply: found module tm, passing reply to it
Feb  1 13:33:48 localhost /usr/local/sbin/openser[17816]: DEBUG:
t_check: msg id=1 global id=0 T start=0xffffffff
Feb  1 13:33:48 localhost /usr/local/sbin/openser[17816]:
parse_headers: flags=22
Feb  1 13:33:48 localhost /usr/local/sbin/openser[17816]:
parse_headers: flags=8
Feb  1 13:33:48 localhost /usr/local/sbin/openser[17816]: DEBUG:
t_reply_matching: hash 39598 label 705981201 branch 0
Feb  1 13:33:48 localhost /usr/local/sbin/openser[17816]:
DEBUG:tm:REF_UNSAFE: after is 1
Feb  1 13:33:48 localhost /usr/local/sbin/openser[17816]: DEBUG:
t_reply_matching: reply matched (T=0x4081f430)!
Feb  1 13:33:48 localhost /usr/local/sbin/openser[17816]: DEBUG:
t_check: msg id=1 global id=1 T end=0x4081f430
Feb  1 13:33:48 localhost /usr/local/sbin/openser[17816]:
DEBUG:tm:reply_received: org. status uas=180, uac[0]=180 local=0
is_invite=1)
Feb  1 13:33:48 localhost /usr/local/sbin/openser[17816]:
DEBUG:tm:t_should_relay_response: T_code=180, new_code=200
Feb  1 13:33:48 localhost /usr/local/sbin/openser[17816]:
DEBUG:tm:relay_reply: branch=0, save=0, relay=0
Feb  1 13:33:48 localhost /usr/local/sbin/openser[17816]:  old size:
911, new size: 850
Feb  1 13:33:48 localhost /usr/local/sbin/openser[17816]:
build_res_from_sip_res: copied size: orig:77, new: 16, rest: 834 msg=
SIP/2.0 200 OK^M Via: SIP/2.0/UDP
87.102.50.17;branch=z9hG4bKeaa9.2ffc88b3.0^M Via: SIP/2.0/UDP
10.10.10.132:5096;received=87.139.12.167;rport=5096;branch=z9hG4bK521554023^M
Record-Route: <sip:87.102.50.13;lr=on;ftag=2240571840>^M Record-Route:
<sip:87.102.50.17;lr;ftag=2240571840>^M Contact:
<sip:dan at 87.139.12.167:7472;rinstance=37d0f83d79f3ede2>^M To:
<sip:dan at de.babble.net>;tag=8b2d7e45^M From:
<sip:dan at babble.net>;tag=2240571840^M Call-ID:
1174762859 at 10.10.10.132^M CSeq: 20 INVITE^M Allow: INVITE, ACK,
CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO^M
Content-Type: application/sdp^M User-Agent: X-Lite release 1006e stamp
34025^M Content-Length: 185^M ^M v=0^M o=- 5 2 IN IP4 87.139.12.167^M
s=CounterPath X-Lite 3.0^M c=IN IP4 87.139.12.167^M t=0 0^M m=audio
34556 RTP/AVP 0 101^M a=fmtp:101 0-15^M a=rtpmap:101
telephone-event/8000^M a=sendrecv^M
Feb  1 13:33:48 localhost /usr/local/sbin/openser[17816]: DEBUG:
add_to_tail_of_timer[2]: 0x4081f478
Feb  1 13:33:48 localhost /usr/local/sbin/openser[17816]:
DEBUG:tm:relay_reply: sent buf=0x814a048: SIP/2.0 2...,
shmem=0x40821528: SIP/2.0 2
Feb  1 13:33:48 localhost /usr/local/sbin/openser[17816]: DEBUG:
cleanup_uac_timers: RETR/FR timers reset
Feb  1 13:33:48 localhost /usr/local/sbin/openser[17816]:
DEBUG:tm:UNREF_UNSAFE: after is 0
Feb  1 13:33:48 localhost /usr/local/sbin/openser[17816]:
DEBUG:destroy_avp_list: destroying list (nil)
Feb  1 13:33:48 localhost /usr/local/sbin/openser[17816]: receive_msg:
cleaning up




More information about the Users mailing list