Hi, I'm experimenting a annoying problem since it seems that my OpenSer, sometimes, doesn't match correct replies from my gateway to client transactions initiated by OpenSer. AFAIK all is correct but OpenSer doesn't match the "100 Trying", neither the "183" and ends the transactoion after "fr_timer" (and before it OpenSer sends INVITE retransmissions).
The following is n example of non mathed response. I can't understand why, the top branch matches and also the CSeq (as RFC 3261 17.1.3 indicates):
INVITE from OpenSer to gateway:
--------------------------- INVITE sip:0034687105267@66.44.0.144 SIP/2.0 Record-Route: sip:88.99.3.10;lr=on;ftag=as5fc7617f Via: SIP/2.0/UDP 88.99.3.10;branch=z9hG4bK87ab.47b6f072.0 Via: SIP/2.0/UDP 192.168.1.203:5060;received=88.99.1.192;branch=z9hG4bK20b50ef9;rport=10000 From: sip:202@sip.domain.net;tag=as5fc7617f To: sip:XXXXXXXXX@sip.domain.net Contact: sip:202@88.99.1.192:10000 Call-ID: 70af31e43126fa0917146b5523ea4add@sip.domain.net CSeq: 103 INVITE User-Agent: domain - Asterisk PBX Max-Forwards: 69 Date: Thu, 19 Jun 2008 10:45:03 GMT Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY Supported: replaces Content-Type: application/sdp Content-Length: 284 X-Called-E164: +34XXXXXXXXX P-Asserted-Identity: sip:XXXXXXXXX@88.99.3.10
v=0 o=root 1468 1469 IN IP4 192.168.1.203 s=session c=IN IP4 88.99.3.10 t=0 0 m=audio 60884 RTP/AVP 8 18 101 a=rtpmap:8 PCMA/8000 a=rtpmap:18 G729/8000 a=fmtp:18 annexb=no a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=silenceSupp:off - - - - a=ptime:20 a=sendrecv -----------------------------------------------
"100 Trying" from gateway
----------------------------------------------- SIP/2.0 100 Trying From: sip:202@sip.domain.net;tag=as5fc7617f To: sip:XXXXXXXXX@sip.domain.net;tag=5ad3254683132008619125120 Call-ID: 70af31e43126fa0917146b5523ea4add@sip.domain.net CSeq: 103 INVITE Allow: ACK,BYE,CANCEL,INVITE,OPTIONS,INFO,SUBSCRIBE,REFER,NOTIFY,PRACK Via: SIP/2.0/UDP 88.99.3.10;branch=z9hG4bK87ab.47b6f072.0 Via: SIP/2.0/UDP 192.168.1.203:5060;received=88.99.1.192;rport=10000;branch=z9hG4bK20b50ef9 Contact: sip:66.44.0.144:5060;transport=UDP Content-Length: 0 -----------------------------------------------
This just occurs some times (3% of outgoing calls, that's really enough).
I'm using OpenSer 1.3.2 complied in Debian Etch as deb package and of course use t_relay().
Any idea? IMHO this error doesn't make sense :(
El Thursday 19 June 2008 17:47:30 Iñaki Baz Castillo escribió:
Hi, I'm experimenting a annoying problem since it seems that my OpenSer, sometimes, doesn't match correct replies from my gateway to client transactions initiated by OpenSer. AFAIK all is correct but OpenSer doesn't match the "100 Trying", neither the "183" and ends the transactoion after "fr_timer" (and before it OpenSer sends INVITE retransmissions).
The following is n example of non mathed response. I can't understand why, the top branch matches and also the CSeq (as RFC 3261 17.1.3 indicates):
Oh my god!!!! I didn't realize that the FU**ING gateway is sending replies to OpenSer port 5061 instead of 5060 !!!!!!!!!!!!!!!!!!!!!!
El Viernes, 20 de Junio de 2008, Iñaki Baz Castillo escribió:
El Thursday 19 June 2008 17:47:30 Iñaki Baz Castillo escribió:
Hi, I'm experimenting a annoying problem since it seems that my OpenSer, sometimes, doesn't match correct replies from my gateway to client transactions initiated by OpenSer. AFAIK all is correct but OpenSer doesn't match the "100 Trying", neither the "183" and ends the transactoion after "fr_timer" (and before it OpenSer sends INVITE retransmissions).
The following is n example of non mathed response. I can't understand why, the top branch matches and also the CSeq (as RFC 3261 17.1.3 indicates):
Oh my god!!!! I didn't realize that the FU**ING gateway is sending replies to OpenSer port 5061 instead of 5060 !!!!!!!!!!!!!!!!!!!!!!
So, of course it's not an OpenSer issue, but my carrier softswitch's bug. OpenSer does transaction matching perfectly :)
What gw is it?
On Sun, Jun 22, 2008 at 12:17 AM, Iñaki Baz Castillo ibc@aliax.net wrote:
El Viernes, 20 de Junio de 2008, Iñaki Baz Castillo escribió:
El Thursday 19 June 2008 17:47:30 Iñaki Baz Castillo escribió:
Hi, I'm experimenting a annoying problem since it seems that my
OpenSer,
sometimes, doesn't match correct replies from my gateway to client transactions initiated by OpenSer. AFAIK all is correct but OpenSer doesn't match the "100 Trying",
neither
the "183" and ends the transactoion after "fr_timer" (and before it OpenSer sends INVITE retransmissions).
The following is n example of non mathed response. I can't understand why, the top branch matches and also the CSeq (as RFC 3261 17.1.3 indicates):
Oh my god!!!! I didn't realize that the FU**ING gateway is sending
replies
to OpenSer port 5061 instead of 5060 !!!!!!!!!!!!!!!!!!!!!!
So, of course it's not an OpenSer issue, but my carrier softswitch's bug. OpenSer does transaction matching perfectly :)
-- Iñaki Baz Castillo
Users mailing list Users@lists.openser.org http://lists.openser.org/cgi-bin/mailman/listinfo/users
El Sábado, 21 de Junio de 2008 23:17, Iñaki Baz Castillo escribió:
El Viernes, 20 de Junio de 2008, Iñaki Baz Castillo escribió:
El Thursday 19 June 2008 17:47:30 Iñaki Baz Castillo escribió:
Hi, I'm experimenting a annoying problem since it seems that my OpenSer, sometimes, doesn't match correct replies from my gateway to client transactions initiated by OpenSer. AFAIK all is correct but OpenSer doesn't match the "100 Trying", neither the "183" and ends the transactoion after "fr_timer" (and before it OpenSer sends INVITE retransmissions).
The following is n example of non mathed response. I can't understand why, the top branch matches and also the CSeq (as RFC 3261 17.1.3 indicates):
Oh my god!!!! I didn't realize that the FU**ING gateway is sending replies to OpenSer port 5061 instead of 5060 !!!!!!!!!!!!!!!!!!!!!!
So, of course it's not an OpenSer issue, but my carrier softswitch's bug. OpenSer does transaction matching perfectly :)
Iñaki ... you should dessit with then ... that will never end .. I promiss you :-(