Hello,
Just wondering whether HMP will be able to handle RE-INVITE with no SDP?
At the moment it seems the application send back "488 Not Acceptable Here", i was thinking it is about codec mismatch.
I still don't understand why Avaya SIP Enable Service (SES) sending SIP RE-INVITE without SDP.
The first INVITE that get accepted by the application shown below (i bold and italics the changed):
=======
INVITE sip:33002@192.168.17.98:5060 SIP/2.0
Call-ID: 808e6f5f4e4cde1e24a2220d100
CSeq: 1 INVITE
From: "33003" <sip:33003@192.168.17.130>;tag=808e6f5f4e4cde1d24a2220d100
Record-Route: <sip:192.168.17.130:5060;lr>,<sip:192.168.17.129:5061;lr;transport=tls>
To: "33002" <sip:33002@sessim.avaya.com>
Via: SIP/2.0/UDP 192.168.17.130:5060;branch=z9hG4bK8383830303038383834846.0,SIP/2.0/TLS 192.168.17.129;psrrposn=2;received=192.168.17.129;branch=z9hG4bK808e6f5f4e4cde1f24a2220d100,SIP/2.0/UDP 192.168.17.156:7318;psrrposn=1;received=192.168.17.156;branch=z9hG4bK-d8754z-3c51a73c06005e0c-1---d8754z-;rport=7318
Content-Length: 162
Content-Type: application/sdp
Contact: "33003" <sip:33003@192.168.17.129:5061;transport=tls>
Max-Forwards: 67
User-Agent: Avaya CM/R015x.01.0.414.0
Allow: INVITE,CANCEL,BYE,ACK,PRACK,SUBSCRIBE,NOTIFY,REFER,OPTIONS,INFO,PUBLISH
Accept-Contact: *;+avaya-cm-line=1
Supported: 100rel,timer,replaces,join,histinfo
Alert-Info: <cid:external@sessim.avaya.com>;avaya-cm-alert-type=external
Min-SE: 1200
Session-Expires: 1200;refresher=uac
History-Info: <sip:33002@sessim.avaya.com>;index=1,"33002" <sip:33002@sessim.avaya.com>;index=1.1
v=0
o=- 1 1 IN IP4 192.168.17.129
s=-
c=IN IP4 127.0.0.2
b=AS:64
t=0 0
m=audio 2376 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
======
and the second INVITE has no SDP:
======
INVITE sip:33002@192.168.17.98:5060 SIP/2.0
Call-ID: 808e6f5f4e4cde1e24a2220d100
CSeq: 2 INVITE
From: "33003" <sip:33003@192.168.17.130>;tag=808e6f5f4e4cde1d24a2220d100
To: "33002" <sip:33002@sessim.avaya.com>;tag=ab08090-0-13c4-50022-30f776-8e76635-30f776
Via: SIP/2.0/UDP 192.168.17.130:5060;branch=z9hG4bK838383030303838383704d.0,SIP/2.0/TLS 192.168.17.129;psrrposn=1;received=192.168.17.129;branch=z9hG4bK808e6f5f4e4cde11424a2220d100
Content-Length: 0
Contact: "33003" <sip:33003@192.168.17.129:5061;transport=tls>
Max-Forwards: 69
User-Agent: Avaya CM/R015x.01.0.414.0
Allow: INVITE,CANCEL,BYE,ACK,PRACK,SUBSCRIBE,NOTIFY,REFER,OPTIONS,INFO,PUBLISH
Supported: 100rel,timer,replaces,join,histinfo
Min-SE: 1200
Session-Expires: 1200;refresher=uac
Record-Route: <sip:192.168.17.130:5060;lr>
======
I tried to look at rtf log (attached) but could not find anything. Any help regarding this would be much appreciated.
Network topology:
- HMP Application : ext 33002 : 192.168.17.98
- SIP PROXY - Avaya SES - 192.168.17.130
- Caller Extension using X-Lite application: ext 33003: 192.168.17.156
the scenario is 33003 calling 33002.
Thank you very much.
Best Regards,
Budi