[Spce-user] IM support?

[Andreas Granig]

Hi,

You need version 2.6 installed, and there it's currently configured in a
way that the sender needs to be authorized (via XCAP) by the receiver in
order to be able to deliver MESSAGE requests. If you don't like this, cp
/etc/ngcp-config/templates/etc/kamailio/proxy/impresence.cfg.tt2 to
/etc/ngcp-config/templates/etc/kamailio/proxy/impresence.cfg.customtt.tt2 and
comment the authorization part around line 111. Execute "ngcpcfg apply"
afterwards and you're done.

Andreas.

On 08/31/2012 06:15 PM, Jirka Jirout wrote:
> Hello,
> 
> one step further with deployment, I am now trying to get instant messaging working. My client sends a message over TLS and LB fowards it to Proxy like this:
> 
>> ##
>> U 2012/08/31 17:57:19.403749 127.0.0.1:5888 -> 127.0.0.1:5062
>> MESSAGE sip:1004 at crypto.erika-as.cz SIP/2.0'
>> Record-Route: <sip:127.0.0.1:5888;lr;r2=on;ngcplb=yes>,<sip:PUBLIC_IP:5889;lr;r2=on;transport=tls>'
>> Via: SIP/2.0/UDP PUBLIC_IP:5888;branch=z9hG4bK4a95.89cf41963c5b3e46b3dae06eb362d50d.0;i=e74'
>> Via: SIP/2.0/TLS 192.168.178.23:57546;received=83.161.151.39;rport;branch=z9hG4bK1303890321;rport=57546'
>> From: <sip:1001 at crypto.PROVIDER.cz>;tag=429836876'
>> To: <sip:1004 at crypto.PROVIDER.cz>'
>> Call-ID: 1710aaeb-fb9f-2602-9433-03a1c82332ee'
>> CSeq: 1848943311 MESSAGE'
>> Content-Length: 6'
>> Max-Forwards: 69'
>> Accept-Contact: *;+g.oma.sip-im'
>> Accept-Contact: *;language="en,fr"'
>> Route: <sip:crypto.PROVIDER.cz:5889;lr;transport=tls>'
>> Content-Type: text/plain'
>> Allow: INVITE, ACK, CANCEL, BYE, MESSAGE, OPTIONS, NOTIFY, PRACK, UPDATE, REFER'
>> Privacy: none'
>> P-Access-Network-Info: ADSL;utran-cell-id-3gpp=00000000'
>> User-Agent: IM-client/OMA1.0 ios-ngn-stack/v00 (SecTalk 1 r000)'
>> P-Preferred-Identity: <sip:1001 at crypto.PROVIDER.cz>'
>> P-NGCP-Src-Ip: 83.161.151.39'
>> P-NGCP-Src-Port: 57546'
>> P-NGCP-Src-Proto: tls'
>> P-NGCP-Src-Af: 4'
>> '
>> TEXT A
> 
> The proxy responds by 100 - Trying, followed almost immediately by:
> 
>> #
>> U 2012/08/31 17:57:19.404044 127.0.0.1:5062 -> 127.0.0.1:5888
>> SIP/2.0 403 Request not supported here'
>> Via: SIP/2.0/UDP PUBLIC_IP:5888;branch=z9hG4bK4a95.89cf41963c5b3e46b3dae06eb362d50d.0;i=e74;rport=5888;received=127.0.0.1'
>> Via: SIP/2.0/TLS 192.168.178.23:57546;received=83.161.151.39;rport;branch=z9hG4bK1303890321;rport=57546'
>> From: <sip:1001 at crypto.PROVIDER.cz>;tag=429836876'
>> To: <sip:1004 at crypto.PROVIDER.cz>;tag=1d24a28a0bded6c40d31e6db8aab9ac6.455b'
>> Call-ID: 1710aaeb-fb9f-2602-9433-03a1c82332ee'
>> CSeq: 1848943311 MESSAGE'
>> Server: Sipwise NGCP Proxy 2.X'
>> Content-Length: 0'
> 
> As far as I can tell, the MESSAGE has all the fields necessary - and more. Is it possible that these extra fields cause the delivery to fail?
> 
> regards, jj
> 
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> http://lists.sipwise.com/listinfo/spce-user
> 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 897 bytes
Desc: OpenPGP digital signature
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20120831/31431e4d/attachment-0001.asc>