Re: [Sofia-sip-devel] Problem in using sofia-sip libraries

2010-08-16 Thread Pekka Pessi
Hi Amir,

2010/8/14 Amir Khezrian amir.khezr...@gmail.com:
 From the errors, It seems that compiler can't find sofia-sip/msg_types.h and
 sofia-sip/msg_mime.h
 Have i missed something that is necessary to be installed before using
 sofia-sip?

You should -I the directory where the inlude files has been installed,
not the sofia-sip source tree. By default the include path is
/usr/local/include/sofia-sip .

-- 
Pekka.Pessi mail at nokia.com

--
This SF.net email is sponsored by 

Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev 
___
Sofia-sip-devel mailing list
Sofia-sip-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel


Re: [Sofia-sip-devel] forking calls and overlapping

2010-08-16 Thread Pekka Pessi
2010/8/12 Михаил Кривушин krivushi...@gmail.com:
 Hello!
 We use FreeSWITCH and OpenSIPS, and have problem - when we try use forking
 calls, it seems that sofia nta/nta.c doesnt distinct INVITE-s by Via
 headers, and its branches.
 Is it right, or I need more code reading?

By default, the server side on nta.c detects the branched INVITEs (and
responds with 482 Request Merged to them).

On client side, the same client side transaction can be used to
receive all the responses. It is also possible to create a
fork-specific client-side transaction with nta_outgoing_tagged().

The nua call model does not support forking, and the sdp processing
and media handling gets outright confused on multiple forks.

-- 
Pekka.Pessi mail at nokia.com

--
This SF.net email is sponsored by 

Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev 
___
Sofia-sip-devel mailing list
Sofia-sip-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel


Re: [Sofia-sip-devel] Internal error at nua_stack.c:2388 on SUBSCRIBE

2010-08-16 Thread Pekka Pessi
Hi Philippe,

2010/8/13 Philippe Maymat pmay...@keyyo.com
with the latest git repo, I now have the following error in return of 
nua_subscribe:

 Internal error at nua_client.c:550

 It's due to the ';', with any other char, it works.

Could you show us your code? How do you initialize nh? Which other
tags you include with nua_handle() and nua_subscribe() besides
NUTAG_URL?

--
Pekka.Pessi mail at nokia.com

--
This SF.net email is sponsored by 

Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev 
___
Sofia-sip-devel mailing list
Sofia-sip-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel


[Sofia-sip-devel] Sofia sip RFC2543

2010-08-16 Thread Tech Micron
Hi everyone,

I have a SIP device that is working with RFC 2543. I  am trying to send call 
using Sofia-SIP (via FreeSwitch), but none of my calls are going  through.
I have traced the debug on SOFIA and it returned an error as below. Can anyone 
help me to solve the problem? any hints?


recv 660 bytes from udp/[66.220.15.230]:5060 at 18:45:21.239029:
   
   INVITE sip:1...@66.220.15.234 SIP/2.0
   v: SIP/2.0/UDP 66.220.15.230
   To: sip:1...@66.220.15.234 sip:1...@66.220.15.234
   From: john odu 
sip:26679...@66.220.15.230;tag=4c5c58410003ac2076f6302c11fc3b7b
   i: 41585c4c2ba3030035e697f0a586d...@66.220.15.230
   CSeq: 1  INVITE
   m: john odu sip:26679...@66.220.15.230
   Supported: com.lilo.conferencing, com.lilo.mux
   User-Agent: liloSipMCU/3.1.6.200801281402
   c: application/sdp
   l: 212
   
   v=0
   o=mcu 0 0 IN IP4 66.220.15.230
   s=sip:26679...@66.220.15.230
   c=IN IP4 66.220.15.230
   t=0 0
   m=audio 2006 RTP/AVP 0 111
   a=ptime:20
   a=rtpmap:0 PCMU/8000
   a=rtpmap:111 telephone-event/8000
   a=xlilossrc:8
   
tport_deliver(0x97a1fb0): msg 0xb762bef8 (660 bytes) from 
udp/66.220.15.230:5060/sip next=(nil)
nta: received INVITE sip:1...@66.220.15.234 SIP/2.0 (CSeq 1)
nta: INVITE has bad To  header
nta: INVITE (1) is Bad To Header
tport_tsend(0x97a1fb0) tpn = UDP/66.220.15.230:5060
tport_resolve addrinfo = 66.220.15.230:5060
tport_by_addrinfo(0x97a1fb0): not found by name UDP/66.220.15.230:5060
tport_vsend(0x97a1fb0): 239 bytes of 239 to udp/66.220.15.230:5060
tport_vsend returned 239
send 239 bytes to udp/[66.220.15.230]:5060 at 18:45:21.239369:
   
   SIP/2.0 400 Bad To Header
   Via: SIP/2.0/UDP 66.220.15.230
   From: john odu 
sip:26679...@66.220.15.230;tag=4c5c58410003ac2076f6302c11fc3b7b
   Call-ID: 41585c4c2ba3030035e697f0a586d...@66.220.15.230
   CSeq: 1 INVITE
   Content-Length: 0



  --
This SF.net email is sponsored by 

Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev ___
Sofia-sip-devel mailing list
Sofia-sip-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel


Re: [Sofia-sip-devel] Sofia sip RFC2543

2010-08-16 Thread Fabio Margarido
On Mon, Aug 16, 2010 at 13:45, Tech Micron techmicron...@yahoo.com wrote:
 I have traced the debug on SOFIA and it returned an error as below. Can 
 anyone help me to solve the problem? any hints?

Hi there,
If I remember correctly, '@' and ':' are not valid character in the
display-name portion of the header. Change it to something like To:
Name sip:1...@66.220.15.234 and it should work.
Regards.

--
This SF.net email is sponsored by 

Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev 
___
Sofia-sip-devel mailing list
Sofia-sip-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel


Re: [Sofia-sip-devel] Sofia sip RFC2543

2010-08-16 Thread Michael Jerris
Looks like this is due to missing quotes around the display name.

Mike

On Aug 16, 2010, at 12:45 PM, Tech Micron wrote:

 Hi everyone,
 
 I have a SIP device that is working with RFC 2543. I am trying to send call 
 using Sofia-SIP (via FreeSwitch), but none of my calls are going through.
 I have traced the debug on SOFIA and it returned an error as below. Can 
 anyone help me to solve the problem? any hints?
 
 
 recv 660 bytes from udp/[66.220.15.230]:5060 at 18:45:21.239029:

INVITE sip:1...@66.220.15.234 SIP/2.0
v: SIP/2.0/UDP 66.220.15.230
To: sip:1...@66.220.15.234 sip:1...@66.220.15.234
From: john odu 
 sip:26679...@66.220.15.230;tag=4c5c58410003ac2076f6302c11fc3b7b
i: 41585c4c2ba3030035e697f0a586d...@66.220.15.230
CSeq: 1 INVITE
m: john odu sip:26679...@66.220.15.230
Supported: com.lilo.conferencing, com.lilo.mux
User-Agent: liloSipMCU/3.1.6.200801281402
c: application/sdp
l: 212

v=0
o=mcu 0 0 IN IP4 66.220.15.230
s=sip:26679...@66.220.15.230
c=IN IP4 66.220.15.230
t=0 0
m=audio 2006 RTP/AVP 0 111
a=ptime:20
a=rtpmap:0 PCMU/8000
a=rtpmap:111 telephone-event/8000
a=xlilossrc:8

 tport_deliver(0x97a1fb0): msg 0xb762bef8 (660 bytes) from 
 udp/66.220.15.230:5060/sip next=(nil)
 nta: received INVITE sip:1...@66.220.15.234 SIP/2.0 (CSeq 1)
 nta: INVITE has bad To header
 nta: INVITE (1) is Bad To Header
 tport_tsend(0x97a1fb0) tpn = UDP/66.220.15.230:5060
 tport_resolve addrinfo = 66.220.15.230:5060
 tport_by_addrinfo(0x97a1fb0): not found by name UDP/66.220.15.230:5060
 tport_vsend(0x97a1fb0): 239 bytes of 239 to udp/66.220.15.230:5060
 tport_vsend returned 239
 send 239 bytes to udp/[66.220.15.230]:5060 at 18:45:21.239369:

SIP/2.0 400 Bad To Header
Via: SIP/2.0/UDP 66.220.15.230
From: john odu 
 sip:26679...@66.220.15.230;tag=4c5c58410003ac2076f6302c11fc3b7b
Call-ID: 41585c4c2ba3030035e697f0a586d...@66.220.15.230
CSeq: 1 INVITE
Content-Length: 0
--
This SF.net email is sponsored by 

Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev ___
Sofia-sip-devel mailing list
Sofia-sip-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel