Hi, Jerome Here is a better picture.
The system has wengophone, SER , asterisk and linksys SPA3000. SER is a proxy in between. case 1: wengophone to US DID (through asterisk). wengophone--INVITE--> <---TRYING SER(RTPProxy) INVITE ---> <---OK -- -- ACK --> asterisk wengophone hears the rings. case 2: wengophone to SPA3000 (through asterisk). not picking up the SPA3000 wengophone--INVITE--> <---TRYING SER(RTPProxy) INVITE ---> <-- RING -- RING -- SPA3000 RING is received by wengophone, but it doesn't generate the rings. case 3: wengophone to SPA3000 (through asterisk). picking up the SPA3000 wengophone--INVITE--> <---TRYING SER(RTPProxy) INVITE ---> <-- RING --- SPA3000 After picking up the SPA3000, SPA--OK -- OK --> SER(RTPProxy) OK ---> <-- ACK --- wengophone SER doesn't pass ACK to SPA, SPA keeps sending OK. Then wengo crashes. Here is the piece of OK and ACK traces from wengo. Hope it is clearer. I suspect that it is the differences in using "VIA" and "ROUTE" fields that is the root of issue. Thanks Steven | INFO1 | <wifo\eXosip\src\jcallback.c: 1332> cb_rcv2xx (id=11) | INFO1 | <wifo\eXosip\src\jcallback.c: 1363> cb_rcv2xx (id=11) Error: no call or transaction info for OPTIONS transaction | INFO1 | <wifo\eXosip\src\eXosip.c: 402> eXosip: timer sec:15 usec:578000! | INFO1 | <wifo\eXosip\src\udp.c: 2327> Received message: SIP/2.0 200 OK To: <sip:[EMAIL PROTECTED]>;tag=79f03096b7ac56c4i0 From: 8011143 <sip:[EMAIL PROTECTED]>;tag=4117659422 Call-ID: [EMAIL PROTECTED] CSeq: 20 INVITE Via: SIP/2.0/UDP 192.168.1.105:5060;received=71.245.97.42;rport=1026;branch=z9hG4bK390934550 Record-Route: <sip:209.97.198.24;ftag=4117659422;lr=on> Contact: Steven Wang <sip:[EMAIL PROTECTED]:5060> Server: Linksys/SPA3000-3.1.10(GWd) Content-Length: 221 Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER Supported: x-sipura Content-Type: application/sdp P-hint: fixed NAT contact for response P-hint: response forced to rtp proxy v=0 o=- 38702051 38702051 IN IP4 192.168.1.101 s=- c=IN IP4 209.97.198.24 t=0 0 m=audio 38584 RTP/AVP 0 100 a=rtpmap:0 PCMU/8000 a=rtpmap:100 NSE/8000 a=fmtp:100 192-193 a=ptime:30 a=sendrecv a=nortpproxy:yes | INFO1 | <wifo\eXosip\src\udp.c: 2332> Message suite: PA3000-3.1.10(GWd) Content-Length: 221 Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER Supported: x-sipura Content-Type: application/sdp P-hint: fixed NAT contact for response P-hint: response forced to rtp proxy v=0 o=- 38702051 38702051 IN IP4 192.168.1.101 s=- c=IN IP4 209.97.198.24 t=0 0 m=audio 38584 RTP/AVP 0 100 a=rtpmap:0 PCMU/8000 a=rtpmap:100 NSE/8000 a=fmtp:100 192-193 a=ptime:30 a=sendrecv a=nortpproxy:yes | INFO1 | <wifo\eXosip\src\jcallback.c: 1332> cb_rcv2xx (id=10) |WARNING| <wifo\eXosip\src\jcallback.c: 1150> The dialog has been replaced with the new one fro 200ok. | INFO1 | <wifo\eXosip\src\jcallback.c: 193> Message sent: ACK sip:[EMAIL PROTECTED]:5060 SIP/2.0 Via: SIP/2.0/UDP 192.168.1.105:5060;rport;branch=z9hG4bK3235694063 Route: <sip:209.97.198.24;ftag=4117659422;lr=on> From: 8011143 <sip:[EMAIL PROTECTED]>;tag=4117659422 To: <sip:[EMAIL PROTECTED]>;tag=79f03096b7ac56c4i0 Call-ID: [EMAIL PROTECTED] CSeq: 20 ACK Contact: <sip:[EMAIL PROTECTED]:5060> Max-Forwards: 70 User-Agent: phapi/eXosip/0.2.0 Content-Length: 0 -----Original Message----- From: Jérôme WAGNER [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 19, 2006 2:34 AM To: 'xu w'; 'Steven Wang'; [email protected] Subject: RE: [Wengophone-devel] wengo sip compliant questions Hello, Could you draw you diagram like Wengo --INVITE--> <--TRYING-- <--OK-- --ACK--> Asterisk It might help us read what you explain in you email. I could not understand whether the messages was received or not on the PC where Wengo is installed. Does this problem exist also with another softphone ? Jerome -----Message d'origine----- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] De la part de xu w Envoyé : mardi 19 septembre 2006 06:05 À : Steven Wang; [email protected] Objet : [Wengophone-devel] wengo sip compliant questions Hello I have limit knowledge of SIP, I am puzzled by the different implementation of SIP protocols in different products. Hope someone can shed some lights on it. I did some traces to use wengo call Asterisk, compared them to the traces from wengo to another sip UAC. Here is what a rough diagram: Wengo --- Asterisk invite try SIP OK ack (rings happen) Wengo --- UAC invite try SIP OK (not received) ring (receive ring message, but silient) So dialing to Asterisk works fine. But to UAC fails. What might be the problems? thanks! Steven _______________________________________________ Wengophone-devel mailing list [email protected] http://dev.openwengo.com/mailman/listinfo/wengophone-devel _______________________________________________ Wengophone-devel mailing list [email protected] http://dev.openwengo.com/mailman/listinfo/wengophone-devel
