Thank you very much david,
you have cleared my confusion of direct INVITE and Headers manipulation. I have noticed that during normal dial (Dial(SIP/XYZ) when connection is established between both ends, there is a SUBSCRIBE request generated and then comes NOTIFY. these requests are not generated when i dial via IP:Port. do you think this could be the problem. and any direct reference to how can i solve this problem. it’s almos 2 weeks and i am stuck in it.
i will appreciate if you could help.
below is debug trace after remote end picks up .
-- Call on SIP/XYZ-00794e30 left from hold
-- SIP/XYZ-00794e30 answered SIP/caller-9fd06cc0
hammer*CLI>
<— SIP read from 117.58.x.x:28614 —>
<------------->
— (0 headers 1 lines) —
hammer*CLI>
<— SIP read from 117.58.x.x:28614 —>
SUBSCRIBE sip:XYZ@asterisk.server.com:5678 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.12:28614;branch=z9hG4bK-d8754z-7039d4338568107f-1—d8754z-;rport
Max-Forwards: 70
Contact: sip:XYZ@117.58.x.x:28614
To: "XYZ"sip:XYZ@asterisk.server.com:5678
From: "XYZ"sip:XYZ@asterisk.server.com:5678;tag=5d297f22
Call-ID: MTE5N2M4ZDY1OWRjOGQwMjgyOWEzZjkzYjA3Y2RkYWY.
CSeq: 1 SUBSCRIBE
Expires: 300
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO
User-Agent: X-Lite release 1104o stamp 56125
Event: message-summary
Content-Length: 0
<------------->
— (13 headers 0 lines) —
Creating new subscription
Sending to 117.58.x.x : 28614 (NAT)
Found peer 'XYZ’
Looking for XYZ in outbound_dial (domain asterisk.server.com)
hammer*CLI>
<— Transmitting (NAT) to 117.58.x.x:28614 —>
SIP/2.0 404 Not Found
Via: SIP/2.0/UDP 192.168.0.12:28614;branch=z9hG4bK-d8754z-7039d4338568107f-1—d8754z-;received=117.58.x.x;rport=28614
From: "XYZ"sip:XYZ@asterisk.server.com:5678;tag=5d297f22
To: "XYZ"sip:XYZ@asterisk.server.com:5678;tag=as724c598c
Call-ID: MTE5N2M4ZDY1OWRjOGQwMjgyOWEzZjkzYjA3Y2RkYWY.
CSeq: 1 SUBSCRIBE
User-Agent: Asterisk PBX
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
Supported: replaces
Content-Length: 0
<------------>
Really destroying SIP dialog ‘MTE5N2M4ZDY1OWRjOGQwMjgyOWEzZjkzYjA3Y2RkYWY.’ Method: SUBSCRIBE
Reliably Transmitting (NAT) to 117.58.x.x:28614:
OPTIONS sip:XYZ@117.58.x.x:28614;rinstance=0266b8b94f488588 SIP/2.0
Via: SIP/2.0/UDP 70.118.x.x:5678;branch=z9hG4bK42fde971;rport
From: “asterisk” sip:asterisk@70.118.x.x:5678;tag=as223ef4a7
To: sip:XYZ@117.58.x.x:28614;rinstance=0266b8b94f488588
Contact: sip:asterisk@70.118.x.x:5678
Call-ID: 5c66fbdf4234deca50d5c44a18641582@70.118.x.x
CSeq: 102 OPTIONS
User-Agent: Asterisk PBX
Max-Forwards: 70
Date: Wed, 21 Jul 2010 15:07:07 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
Supported: replaces
Content-Length: 0
hammer*CLI>
<— SIP read from 117.58.x.x:28614 —>
SIP/2.0 200 OK
Via: SIP/2.0/UDP 70.118.x.x:5678;branch=z9hG4bK42fde971;rport=5678
Contact: sip:192.168.0.12:28614
To: sip:XYZ@117.58.x.x:28614;rinstance=0266b8b94f488588;tag=15133f38
From: "asterisk"sip:asterisk@70.118.x.x:5678;tag=as223ef4a7
Call-ID: 5c66fbdf4234deca50d5c44a18641582@70.118.x.x
CSeq: 102 OPTIONS
Accept: application/sdp
Accept-Language: en
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO
User-Agent: X-Lite release 1104o stamp 56125
Content-Length: 0
<------------->
— (12 headers 0 lines) —
Really destroying SIP dialog '5c66fbdf4234deca50d5c44a18641582@70.118.x.x’ Method: OPTIONS
hammer*CLI>
<------------>
Scheduling destruction of SIP dialog '6514fece69f1718e5cefe72632909c0e@70.118.x.x’ in 23936 ms (Method: NOTIFY)
Reliably Transmitting (NAT) to 117.58.x.x:28614:
NOTIFY sip:XYZ@117.58.x.x:28614;rinstance=0266b8b94f488588 SIP/2.0
Via: SIP/2.0/UDP 70.118.x.x:5678;branch=z9hG4bK218cf73a;rport
From: “asterisk” sip:asterisk@70.118.x.x:5678;tag=as756cae64
To: sip:XYZ@117.58.x.x:28614;rinstance=0266b8b94f488588
Contact: sip:asterisk@70.118.x.x:5678
Call-ID: 6514fece69f1718e5cefe72632909c0e@70.118.x.x
CSeq: 102 NOTIFY
User-Agent: Asterisk PBX
Max-Forwards: 70
Event: message-summary
Content-Type: application/simple-message-summary
Content-Length: 92
Messages-Waiting: no
Message-Account: sip:asterisk@70.118.x.x
Voice-Message: 0/0 (0/0)
hammer*CLI>
<— SIP read from 117.58.x.x:28614 —>
SIP/2.0 200 OK
Via: SIP/2.0/UDP 70.118.x.x:5678;branch=z9hG4bK218cf73a;rport=5678
Contact: sip:192.168.0.12:28614
To: sip:XYZ@117.58.x.x:28614;rinstance=0266b8b94f488588;tag=b9541904
From: "asterisk"sip:asterisk@70.118.x.x:5678;tag=as756cae64
Call-ID: 6514fece69f1718e5cefe72632909c0e@70.118.x.x
CSeq: 102 NOTIFY
User-Agent: X-Lite release 1104o stamp 56125
Content-Length: 0
<------------->
— (9 headers 0 lines) —
Really destroying SIP dialog '6514fece69f1718e5cefe72632909c0e@70.118.x.x’ Method: NOTIFY
[Jul 21 11:07:15] DEBUG[23749]: chan_sip.c:3074 update_call_counter: Call to peer ‘XYZ’ removed from call limit 2
Scheduling destruction of SIP dialog '25a6e3604896da0e5482a7565560ce3b@70.118.x.x’ in 18624 ms (Method: INVITE)
[Jul 21 11:07:15] DEBUG[23749]: chan_sip.c:5695 reqprep: Strict routing enforced for session 25a6e3604896da0e5482a7565560ce3b@70.118.x.x
set_destination: Parsing sip:XYZ@117.58.x.x:28614;rinstance=0266b8b94f488588 for address/port to send to
set_destination: set destination to 117.58.x.x, port 28614
Reliably Transmitting (NAT) to 117.58.x.x:28614:
BYE sip:XYZ@117.58.x.x:28614;rinstance=0266b8b94f488588 SIP/2.0
Via: SIP/2.0/UDP 70.118.x.x:5678;branch=z9hG4bK05cc42e6;rport
From: “caller coke” sip:17142545542@70.118.x.x:5678;tag=as12245807
To: sip:XYZ@117.58.x.x:28614;rinstance=0266b8b94f488588;tag=bd6f2350
Call-ID: 25a6e3604896da0e5482a7565560ce3b@70.118.x.x
CSeq: 103 BYE
User-Agent: Asterisk PBX
Max-Forwards: 70
Content-Length: 0