ansaurus

Question

Answer 1

+2 A:

AlexKR 2009-10-27 19:13:48

Using a packet sniffer would've actually solved my problem, I was sending data past the \0 which wasn't being printed because I'm using C strings. I solved it before trying a packet sniffer, but that's not your fault.

Ramónster 2009-11-04 19:12:44

Answer 2

A:

"via_cnt==1092" is also very suspicious.

BTW, you appear to building a B2BUA, in that you accept the call from the outside before even sending an invite to local phone (1234). If the local phone were to accept with different parameters, accept a different codec, etc you'd be screwed since you told the local phone to send media directly to the original caller. They really should both be sending their media to your server, which would relay (or if needed transcode).

If you don't want to do that (i.e. you don't want to act as media relay and possible transcoder), you need to forward the INVITE to the local phone, then forward any response, etc. Basically act more as a SIP proxy server and not a SIP B2BUA.

jesup 2009-10-29 18:38:13

My server actually does act as a media relay

Ramónster 2009-11-04 19:10:42

Answer 3

A:

I'd recommend to check if calling leg accepts BYE request (looks it accepts but...) and how it handles this request. What you really need is similar log from 174.37.45.134. It seems problem is behind .134 (timeout was generated by .134).

BTW as for first look I see you are breaking several basic call processing rules which could get you in such trouble: - You are missing Trying response for originating call leg. If originator's SIP stack really waits for this it could lead to call ID not really recorded. Yes, this is buggy behavior but we are living in real world. Standards say to respond with Trying ASAP (even before you are doing routing, just after call authentication - You are fully establishing call session with calling party before even initiating outgoing INVITE to called party. This is wrong logics. At least because in case of failed outgoing call originator will be billed.

If you can do this quick I'd recommend to fix call setup sequence first. You anyway will need this and there is possibility this will fix call termination:

INVITE  ->
TRYING  <-
        -> INVITE
        <- TRYING
        <- RINGING
RINGING <-
        <- OK
OK      <-
ACK     ->
        -> ACK

Roman Nikitchenko 2009-11-06 10:31:03

ansaurus

tags:

views:

answers:

Problem with SIP BYE message

related questions