brekeke re-transmit INVITE after getting 180 and 200
Moderator: Brekeke Support Team
brekeke re-transmit INVITE after getting 180 and 200
1. Brekeke Product Name and version:
2.4.8.6
2. Java version:
1.6.0_18
3. OS type and the version:
Linux debian 6
4. UA (phone), gateway or other hardware/software involved:
PBX and xlite
5. Select your network pattern from http://www.brekeke-sip.com/bbs/network/ ... terns.html :
pattern 9
6. Your problem:
A is calling B
INVITE from A to Brekeke SIP Server.
Brekeke SIP Server forward the INVITE to PBX.
PBX return INVITE to Brekeke SIP Server.
Brekeke SIP Server send INVITE to B.
B reply with 180 and later with 200, however, Brekeke SIP Server is doesn't stop sending INVITE.
notes - doing the call without going to the PBX is ok, but I must have the PBX because it has all the contacts.
I have a wireshark trace if needed.
looking forward for your help.
2.4.8.6
2. Java version:
1.6.0_18
3. OS type and the version:
Linux debian 6
4. UA (phone), gateway or other hardware/software involved:
PBX and xlite
5. Select your network pattern from http://www.brekeke-sip.com/bbs/network/ ... terns.html :
pattern 9
6. Your problem:
A is calling B
INVITE from A to Brekeke SIP Server.
Brekeke SIP Server forward the INVITE to PBX.
PBX return INVITE to Brekeke SIP Server.
Brekeke SIP Server send INVITE to B.
B reply with 180 and later with 200, however, Brekeke SIP Server is doesn't stop sending INVITE.
notes - doing the call without going to the PBX is ok, but I must have the PBX because it has all the contacts.
I have a wireshark trace if needed.
looking forward for your help.
here is the print of the INVITE
Request-Line: INVITE sip:6868456@62.x.x.x:5060;rinstance=b769be10c08da7ab SIP/2.0
Message Header
Via: SIP/2.0/UDP 184.x.x.x:5060;rport;branch=z9hG4bK13110541c601a14383f799-a48da33f-4323a0d4
To: <sip:6868456@184.x.x.x:5060>
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO
Call-ID: fa610794-e3f491e6-28775069-94f1ea1e@184.x.x.x
User-Agent: X-Lite 4 release 4.1 stamp 63214
Max-Forwards: 67
From: 7675351 <sip:7675351@184.x.x.x>;tag=96044cd9
Contact: <sip:7675351@184.x.x.x:5060>
CSeq: 1 INVITE
Supported: replaces
P-Asserted-Identity: 7675351 <sip:7675351@184.x.x.x>
Content-Type: application/sdp
Content-Length: 234
and of the 180
Status-Line: SIP/2.0 180 Ringing
Message Header
Via: SIP/2.0/UDP 184.x.x.x:5060;rport=5060;branch=z9hG4bK13110541c601a14383f799-a48da33f-4323a0d4
Contact: <sip:6868456@62.x.x.x:5060;rinstance=b769be10c08da7ab>
To: <sip:6868456@184.x.x.x:5060>;tag=a02f576e
From: "7675351"<sip:7675351@184.x.x.x>;tag=96044cd9
Call-ID: fa610794-e3f491e6-28775069-94f1ea1e@184.x.x.x
CSeq: 1 INVITE
User-Agent: X-Lite release 1104o stamp 56125
Content-Length: 0
Request-Line: INVITE sip:6868456@62.x.x.x:5060;rinstance=b769be10c08da7ab SIP/2.0
Message Header
Via: SIP/2.0/UDP 184.x.x.x:5060;rport;branch=z9hG4bK13110541c601a14383f799-a48da33f-4323a0d4
To: <sip:6868456@184.x.x.x:5060>
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO
Call-ID: fa610794-e3f491e6-28775069-94f1ea1e@184.x.x.x
User-Agent: X-Lite 4 release 4.1 stamp 63214
Max-Forwards: 67
From: 7675351 <sip:7675351@184.x.x.x>;tag=96044cd9
Contact: <sip:7675351@184.x.x.x:5060>
CSeq: 1 INVITE
Supported: replaces
P-Asserted-Identity: 7675351 <sip:7675351@184.x.x.x>
Content-Type: application/sdp
Content-Length: 234
and of the 180
Status-Line: SIP/2.0 180 Ringing
Message Header
Via: SIP/2.0/UDP 184.x.x.x:5060;rport=5060;branch=z9hG4bK13110541c601a14383f799-a48da33f-4323a0d4
Contact: <sip:6868456@62.x.x.x:5060;rinstance=b769be10c08da7ab>
To: <sip:6868456@184.x.x.x:5060>;tag=a02f576e
From: "7675351"<sip:7675351@184.x.x.x>;tag=96044cd9
Call-ID: fa610794-e3f491e6-28775069-94f1ea1e@184.x.x.x
CSeq: 1 INVITE
User-Agent: X-Lite release 1104o stamp 56125
Content-Length: 0