Hi all, I was enabling features like call forwarding and voicemail in my openser script. I also took some idea from the call forward configuration available at Onsip.org. But I find a strange problem: When the user has set his call forwarding to forwarding on no answer and if someone calls this user it rings for the request timeout period but after request timeout the invite goes again to the same user instead of the forwarded number and the phone keeps on ringing. Then I jus used the onsip.org configuration and again I face the same problem. Can someone help me on this please. I remember that this script worked well in the 0.9.5 version of openser but now I am using 1.1.x from the cvs and I am facing this problem. The problem somewhere seems to be with the append_branch function. I inserted the log function at different places in the script to check the flow, it behaves as needed but after the append_branch() I dont know what goes wrong but the call is not forwarded somehow. The blind forwarding concept works fine as it does not need any append_branch() in it. The ngrep after request timeout happens is given below:

202.XXX.60.XXX:5060 -> 202.80.XXX.XXX:1443 CANCEL sip:6468621545@192.168.2.18:8469 SIP/2.0..Via: SIP/2.0/UDP 202.XXX.60.XXX;branch=z9hG4bK39ec.b7193062.0..From: "jaye sh"sip:6468621547@202.XXX.60.XXX;tag=1b0d5617..Call-ID: 83236e2f50004a44@SkFZRVNI..To: sip:6468621545@202.XXX.60.XXX..CSe q: 2 CANCEL..User-Agent: OpenSer (1.1.0-dev16 -notls (i386/linux))..Content-Length: 0.... # U 202.XXX.60.XXX:5060 -> 202.80.XXX.XXX:2650 SIP/2.0 407 Proxy Authentication Required..Via: SIP/2.0/UDP 192.168.2.18:8466;received=202.80.XXX.XXX;branch=z9hG4bK-d8754 3-c63a9f56aa2b013d-1--d87543-;rport=2650..To: sip:6468621545@202.XXX.60.XXX;tag=71ff39c351286642530928b88b3f93ba.d71b..Fr om: "jayesh"sip:6468621547@202.XXX.60.XXX;tag=1b0d5617..Call-ID: 83236e2f50004a44@SkFZRVNI..CSeq: 2 INVITE..Proxy-Authent icate: Digest realm="202.XXX.60.XXX", nonce="4444ecd2d1559130637b185152e48a75efecca04"..Server: OpenSer (1.1.0-dev16 -notls (i386/linux))..Content-Length: 0..Warning: 392 202.XXX.60.XXX:5060 "Noisy feedback tells: pid=11598 req_src_ip=202.80.61. 10 req_src_port=5060 in_uri=sip:00919833171405@202.XXX.60.XXX out_uri=sip:00919833171405@202.XXX.60.XXX via_cnt==2".... # U 202.80.XXX.XXX:2650 -> 202.XXX.60.XXX:5060 ACK sip:6468621545@202.XXX.60.XXX SIP/2.0..Via: SIP/2.0/UDP 192.168.2.18:8466;branch=z9hG4bK-d87543-c63a9f56aa2b013d-1--d87 543-;rport..To: sip:6468621545@202.XXX.60.XXX;tag=71ff39c351286642530928b88b3f93ba.d71b..From: "jayesh"<sip:6468621547@20 2.80.61.10>;tag=1b0d5617..Call-ID: 83236e2f50004a44@SkFZRVNI..CSeq: 2 ACK..Content-Length: 0.... # U 202.80.XXX.XXX:2650 -> 202.XXX.60.XXX:5060 INVITE sip:6468621545@202.XXX.60.XXX SIP/2.0..Via: SIP/2.0/UDP 192.168.2.18:8466;branch=z9hG4bK-d87543-1b1c6b50b550ef43-1-- d87543-;rport..Max-Forwards: 70..Contact: sip:6468621547@192.168.2.18:8466..To: sip:6468621545@202.XXX.60.XXX..From: "jayesh"sip:6468621547@202.XXX.60.XXX;tag=1b0d5617..Call-ID: 83236e2f50004a44@SkFZRVNI..CSeq: 3 INVITE..Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO..Content-Type: application/sdp..Proxy-Authorization: Diges t username="6468621547",realm="202.XXX.60.XXX",nonce="4444ecd2d1559130637b185152e48a75efecca04",uri="sip:6468621545@202.80. 61.10",response="752c0923d00e9a7a4a8611835ea0c649",algorithm=MD5..Supported: eventlist..User-Agent: eyeBeam release 3010n stamp 19039..Content-Length: 235....v=0..o=- 18498030 18498049 IN IP4 192.168.2.18..s=eyeBeam..c=IN IP4 192.168.2.18..t= 0 0..m=audio 8470 RTP/AVP 8 18 5 101..a=alt:1 1 : 3E35CA80 000000D3 192.168.2.18 8470..a=fmtp:101 0-15..a=rtpmap:101 tele phone-event/8000..a=sendrecv.. # U 202.XXX.60.XXX:5060 -> 202.80.XXX.XXX:2650 SIP/2.0 100 trying -- your call is important to us..Via: SIP/2.0/UDP 192.168.2.18:8466;branch=z9hG4bK-d87543-1b1c6b50b550 ef43-1--d87543-;rport=2650;received=202.80.XXX.XXX..To: sip:6468621545@202.XXX.60.XXX..From: "jayesh"<sip:6468621547@202.8 0.61.10>;tag=1b0d5617..Call-ID: 83236e2f50004a44@SkFZRVNI..CSeq: 3 INVITE..Server: OpenSer (1.1.0-dev16 -notls (i386/linu x))..Content-Length: 0..Warning: 392 202.XXX.60.XXX:5060 "Noisy feedback tells: pid=11594 req_src_ip=202.80.XXX.XXX req_src _port=2650 in_uri=sip:6468621545@202.XXX.60.XXX out_uri=sip:6468621545@192.168.2.18:8469 via_cnt==1".... # U 202.XXX.60.XXX:5060 -> 202.80.XXX.XXX:1443 INVITE sip:6468621545@192.168.2.18:8469 SIP/2.0..Record-Route: sip:202.XXX.60.XXX:5060;nat=yes;ftag=1b0d5617;lr=on..Via: SIP/2.0/UDP 202.XXX.60.XXX;branch=z9hG4bK49ec.e5a8534.0..Via: SIP/2.0/UDP 192.168.2.18:8466;received=202.80.XXX.XXX;branch=z 9hG4bK-d87543-1b1c6b50b550ef43-1--d87543-;rport=2650..Max-Forwards: 69..Contact: sip:6468621547@202.80.XXX.XXX:2650..To: sip:6468621545@202.XXX.60.XXX..From: "jayesh"sip:6468621547@202.XXX.60.XXX;tag=1b0d5617..Call-ID: 83236e2f50004a44@SkFZR VNI..CSeq: 3 INVITE..Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO..Content-Type: app lication/sdp..Supported: eventlist..User-Agent: eyeBeam release 3010n stamp 19039..Content-Length: 236....v=0..o=- 184980 30 18498049 IN IP4 192.168.2.18..s=eyeBeam..c=IN IP4 202.XXX.60.XXX..t=0 0..m=audio 10108 RTP/AVP 8 18 5 101..a=alt:1 1 : 3 E35CA80 000000D3 192.168.2.18 8470..a=fmtp:101 0-15..a=rtpmap:101 telephone-event/8000..a=sendrecv.. # U 202.80.XXX.XXX:1443 -> 202.XXX.60.XXX:5060 SIP/2.0 200 OK..Via: SIP/2.0/UDP 202.XXX.60.XXX;branch=z9hG4bK39ec.b7193062.0..Contact: sip:6468621545@192.168.2.18:8469. .To: sip:6468621545@202.XXX.60.XXX;tag=023e0170..From: "jayesh"sip:6468621547@202.XXX.60.XXX;tag=1b0d5617..Call-ID: 83236 e2f50004a44@SkFZRVNI..CSeq: 2 CANCEL..User-Agent: eyeBeam release 3010n stamp 19039..Content-Length: 0.... # U 202.80.XXX.XXX:1443 -> 202.XXX.60.XXX:5060 SIP/2.0 487 Request Terminated..Via: SIP/2.0/UDP 202.XXX.60.XXX;branch=z9hG4bK39ec.b7193062.0..Via: SIP/2.0/UDP 192.168.2.1 8:8466;received=202.80.XXX.XXX;branch=z9hG4bK-d87543-c63a9f56aa2b013d-1--d87543-;rport=2650..To: <sip:6468621545@202.80.61 .10>;tag=023e0170..From: "jayesh"sip:6468621547@202.XXX.60.XXX;tag=1b0d5617..Call-ID: 83236e2f50004a44@SkFZRVNI..CSeq: 2 INVITE..User-Agent: eyeBeam release 3010n stamp 19039..Content-Length: 0.... # U 202.XXX.60.XXX:5060 -> 202.80.XXX.XXX:1443 ACK sip:6468621545@192.168.2.18:8469 SIP/2.0..Via: SIP/2.0/UDP 202.XXX.60.XXX;branch=z9hG4bK39ec.b7193062.0..From: "jayesh" sip:6468621547@202.XXX.60.XXX;tag=1b0d5617..Call-ID: 83236e2f50004a44@SkFZRVNI..To: sip:6468621545@202.XXX.60.XXX;tag=023 e0170..CSeq: 2 ACK..User-Agent: OpenSer (1.1.0-dev16 -notls (i386/linux))..Content-Length: 0.... # U 202.80.XXX.XXX:1443 -> 202.XXX.60.XXX:5060 SIP/2.0 180 Ringing..Via: SIP/2.0/UDP 202.XXX.60.XXX;branch=z9hG4bK49ec.e5a8534.0..Via: SIP/2.0/UDP 192.168.2.18:8466;recei ved=202.80.XXX.XXX;branch=z9hG4bK-d87543-1b1c6b50b550ef43-1--d87543-;rport=2650..Record-Route: <sip:202.XXX.60.XXX:5060;lr;n at=yes;ftag=1b0d5617>..Contact: sip:6468621545@192.168.2.18:8469..To: sip:6468621545@202.XXX.60.XXX;tag=f6570b78..From: "jayesh"sip:6468621547@202.XXX.60.XXX;tag=1b0d5617..Call-ID: 83236e2f50004a44@SkFZRVNI..CSeq: 3 INVITE..User-Agent: eyeB eam release 3010n stamp 19039..Content-Length: 0.... # U 202.XXX.60.XXX:5060 -> 202.80.XXX.XXX:2650 SIP/2.0 180 Ringing..Via: SIP/2.0/UDP 192.168.2.18:8466;received=202.80.XXX.XXX;branch=z9hG4bK-d87543-1b1c6b50b550ef43-1-- d87543-;rport=2650..Record-Route: sip:202.XXX.60.XXX:5060;lr;nat=yes;ftag=1b0d5617..Contact: <sip:6468621545@202.80.61.25 4:1443>..To: sip:6468621545@202.XXX.60.XXX;tag=f6570b78..From: "jayesh"sip:6468621547@202.XXX.60.XXX;tag=1b0d5617..Call-I D: 83236e2f50004a44@SkFZRVNI..CSeq: 3 INVITE..User-Agent: eyeBeam release 3010n stamp 19039..Content-Length: 0....

The one that I have made bold is the forwarded number. It recognises but it somehow again asks for proxy authentication after the call is forwarded. User 6468621545 has forwarded the call on no answer to 00919833171405.

Please help me in this regard as many must have used that script.

w/regards, jayesh.

--------------------------------- Jiyo cricket on Yahoo! India cricket Yahoo! Messenger Mobile Stay in touch with your buddies all the time. --------------------------------- Jiyo cricket on Yahoo! India cricket Yahoo! Messenger Mobile Stay in touch with your buddies all the time.