[SIP Beyond VoIP] MSRPRelay on TCP

Mihai Richard mihai.richard at softvision.ro
Wed Dec 14 14:49:34 CET 2011


Hello,

We want to set MSRPRelay - and sipsimpleclients to use TCP instead of
TLS, but we receive the following error: SIP session rejected by user
(488 Not Acceptable Here)
Can you give a hint where is the problem?

Thanks,
Mihai

PS.

Our configuration:
1. Two clients with sipsimpleclient command line, making register and
sip-session, then /chat ...
2. MSRPRelay installed with the following settings:

certificate = tls/msrprelay.crt
key = tls/msrprelay.key
address = x.x.x.x:2855
debug_notls = Yes
backend = database

[Database]
uri = mysql://root:xxx@localhost/opensips
cleartext_passwords = No
subscriber_table = subscriber
username_col = username
domain_col = domain
password_col = ha1
ha1_col = ha1


And a tcp dump looks like:
2011-12-14 15:06:20.976370 [sip-session 5870]: RECEIVED: Packet 5,
+0:00:24.791404
80.97.161.39:5060 -(SIP over UDP)-> 192.168.4.48:49484
INVITE sip:ybodrtmq at 192.168.4.48:49484 SIP/2.0
Record-Route: <sip:80.97.161.39;lr=on>
Via: SIP/2.0/UDP 80.97.161.39;branch=z9hG4bK942d.4de60901.0
Via: SIP/2.0/UDP 
184.173.248.18:58426;received=184.173.248.18;rport=58426;branch=z9hG4bKPjiFg
I-2I1ojhYwYvQTUlSweroEM5IFoG-
Max-Forwards: 69
From: <sip:te at 80.97.161.39>;tag=BmsBDOXh38itfhpwwYYc52XBIYV5-Oq3
To: <sip:mr at 80.97.161.39>
Contact: <sip:tfkoyrng at 184.173.248.18:58426>
Call-ID: ZUZctxUE0rd1ixIycChxPU1Oyuuvc9P0
CSeq: 5598 INVITE
Allow: SUBSCRIBE, NOTIFY, PRACK, INVITE, ACK, BYE, CANCEL, UPDATE,
MESSAGE, REFER
Supported: 100rel, replaces, norefersub
User-Agent: sipsimple 0.19.0
Content-Type: application/sdp
Content-Length:   302

v=0
o=- 3532856777 3532856777 IN IP4 184.173.248.18
s=sipsimple 0.19.0
c=IN IP4 184.173.248.18
t=0 0
m=message 2855 TCP/MSRP *
a=path:msrp://184.173.248.18:2855/57c17b25076f20e98666;tcp
a=accept-types:message/cpim text/* application/im-iscomposing+xml
a=accept-wrapped-types:*
a=setup:active

--
2011-12-14 15:06:20.979775 [sip-session 5870]: SENDING: Packet 6,
+0:00:24.794809
192.168.4.48:49484 -(SIP over UDP)-> 80.97.161.39:5060
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 
80.97.161.39;received=80.97.161.39;branch=z9hG4bK942d.4de60901.0
Via: SIP/2.0/UDP 
184.173.248.18:58426;rport=58426;received=184.173.248.18;branch=z9hG4bKPjiFg
I-2I1ojhYwYvQTUlSweroEM5IFoG-
Record-Route: <sip:80.97.161.39;lr>
Call-ID: ZUZctxUE0rd1ixIycChxPU1Oyuuvc9P0
From: <sip:te at 80.97.161.39>;tag=BmsBDOXh38itfhpwwYYc52XBIYV5-Oq3
To: <sip:mr at 80.97.161.39>
CSeq: 5598 INVITE
Server: sipsimple 0.19.0
Content-Length:  0


--
2011-12-14 15:06:20.980140 [sip-session 5870]: SENDING: Packet 7,
+0:00:24.795174
192.168.4.48:49484 -(SIP over UDP)-> 80.97.161.39:5060
SIP/2.0 488 Not Acceptable Here
Via: SIP/2.0/UDP 
80.97.161.39;received=80.97.161.39;branch=z9hG4bK942d.4de60901.0
Via: SIP/2.0/UDP 
184.173.248.18:58426;rport=58426;received=184.173.248.18;branch=z9hG4bKPjiFg
I-2I1ojhYwYvQTUlSweroEM5IFoG-
Record-Route: <sip:80.97.161.39;lr>
Call-ID: ZUZctxUE0rd1ixIycChxPU1Oyuuvc9P0
From: <sip:te at 80.97.161.39>;tag=BmsBDOXh38itfhpwwYYc52XBIYV5-Oq3
To: <sip:mr at 80.97.161.39>;tag=3kJfx6lS7sZm06KTrqNTIoMJD-zfwno-
CSeq: 5598 INVITE
Server: sipsimple 0.19.0
Content-Length:  0


--
2011-12-14 15:06:20.981206 [sip-session 5870]: RECEIVED: Packet 8,
+0:00:24.796240
80.97.161.39:5060 -(SIP over UDP)-> 192.168.4.48:49484
ACK sip:ybodrtmq at 192.168.4.48:49484 SIP/2.0
Via: SIP/2.0/UDP 80.97.161.39;branch=z9hG4bK942d.4de60901.0
From: <sip:te at 80.97.161.39>;tag=BmsBDOXh38itfhpwwYYc52XBIYV5-Oq3
Call-ID: ZUZctxUE0rd1ixIycChxPU1Oyuuvc9P0
To: <sip:mr at 80.97.161.39>;tag=3kJfx6lS7sZm06KTrqNTIoMJD-zfwno-
CSeq: 5598 ACK
Max-Forwards: 70
User-Agent: OpenSIPS (1.6.4-2-notls (i386/linux))
Content-Length: 0




More information about the SIPBeyondVoIP mailing list