[Linphone-users] Still cannot make calls with 1.4.1 (from ARM)!

[Salvador Gianluca]

Hi Simon and all the list!
Sorry for my insistence, but i need to have linphonec-1.4.1 working on my ARM embedded platform...
The only (only?) problem is that i cannot make calls from the board: only receive.
Otherwise linphonec 1.3.5 can both make and receive. This is very strange because the environment conditions are the same:
same platform, same IP and SIP number, same internal-lan and host called.
Only the linphonec version is different between the two cases.
So i have studied a little bit the output of the two versions about same commands: first a call from host to the board (that have succeeded in both cases) and after a call from board to host (that works only for 1.3.5).

0498592086 is the host SIP number
0498592085 is the board SIP number

When the board's 1.3.5 make a call, the SIP messages are:

Message sent: INVITE sip:address@hidden SIP/2.0 [...]
Received message: SIP/2.0 407 Proxy Authentication Required [...]

Message sent: ACK sip:address@hidden SIP/2.0
Via: SIP/2.0/UDP 192.168.1.92:5060;rport;branch=z9hG4bK1629424698
From: <sip:address@hidden>;tag=1260354505
To: <sip:address@hidden>;tag=88f80658fec2aee552096ea46e92568d.85f3
Call-ID: address@hidden
CSeq: 20 ACK
Content-Length: 0

 (len=16 sizeof(addr)=128 28)

| INFO1 | <jcallback.c: 1442> cb_rcv4xx (id=7)
| INFO1 | <jcallback.c: 520> cb_sndack (id=7)
| INFO1 | <eXosip.c: 333> eXosip: Reseting timer to 15s before waking up!
| INFO1 | <eXutils.c: 416> Outgoing interface to reach voip.eutelia.it is 192.168.1.92.
| INFO2 | <eXosip.c: 2157> INFO: authinfo: "voip.eutelia.it" "voip.eutelia.it"
| INFO1 | <eXosip.c: 2278> authinfo: 0498592085
| INFO1 | <eXutils.c: 416> Outgoing interface to reach voip.eutelia.it is 192.168.1.92.
| INFO2 | <osip_transaction.c: 131> allocating transaction ressource 8 70931680
| INFO2 | <ict.c: 34> allocating ICT context
| INFO2 | <eXutils.c: 511> Not an IPv4 or IPv6 address: voip.eutelia.it
| INFO2 | <eXutils.c: 541> DNS resolution with voip.eutelia.it:5060
| INFO1 | <jcallback.c:148>

Message sent: INVITE sip:address@hidden SIP/2.0 [...]
Received message: SIP/2.0 100 trying -- your call is important to us [...]
Received message: SIP/2.0 183 Session Progress [...]
Received message: SIP/2.0 200 OK [...]

and so the commnunication is established.




Instead when the board's 1.4.1 make a call, the SIP messages are:

Message sent: INVITE sip:address@hidden SIP/2.0 [...]
Received message: SIP/2.0 407 Proxy Authentication Required [...]

Message sent: ACK sip:address@hidden SIP/2.0
Via: SIP/2.0/UDP 192.168.1.92:5060;rport;branch=z9hG4bK290640814
From: <sip:address@hidden>;tag=1664892464
To: <sip:address@hidden>;tag=88f80658fec2aee552096ea46e92568d.ed30
Call-ID: address@hidden
CSeq: 20 ACK
Content-Length: 0

 (len=16 sizeof(addr)=128 28)
| INFO1 | <jcallback.c: 1442> cb_rcv4xx (id=7)
| INFO1 | <jcallback.c: 520> cb_sndack (id=7)
| INFO1 | <eXosip.c: 333> eXosip: Reseting timer to 15s before waking up!
ortp-message-CALL_REQUESTFAILURE or GLOBALFAILURE or SERVERFAILURE

| INFO2 | <eXosip.c: 2158> INFO: authinfo: "voip.eutelia.it" "voip.eutelia.it"
| INFO1 | <eXosip.c: 2279> authinfo: 0498592085
| INFO2 | <osip_transaction.c: 131> allocating transaction ressource 8 395057138
| INFO2 | <ict.c: 34> allocating ICT context
| INFO2 | <eXutils.c: 535> Not an IPv4 or IPv6 address: voip.eutelia.it
| INFO2 | <eXutils.c: 565> DNS resolution with voip.eutelia.it:5060
| INFO1 | <jcallback.c: 148>

Message sent: INVITE sip:address@hidden SIP/2.0 [...]
Received message: SIP/2.0 407 Proxy Authentication Required [...]

Message sent: ACK sip:address@hidden SIP/2.0
Via: SIP/2.0/UDP 192.168.1.92:5060;rport;branch=z9hG4bK1477614817
From: <sip:address@hidden>;tag=1664892464
To: <sip:address@hidden>;tag=88f80658fec2aee552096ea46e92568d.4568
Call-ID: address@hidden
CSeq: 21 ACK
Content-Length: 0

 (len=16 sizeof(addr)=128 28)
| INFO1 | <jcallback.c: 1442> cb_rcv4xx (id=8)
| INFO1 | <jcallback.c: 520> cb_sndack (id=8)
| INFO1 | <eXosip.c: 333> eXosip: Reseting timer to 15s before waking up!
ortp-message-CALL_REQUESTFAILURE or GLOBALFAILURE or SERVERFAILURE

| INFO2 | <eXosip.c: 2158> INFO: authinfo: "voip.eutelia.it" "voip.eutelia.it"
| INFO1 | <eXosip.c: 2279> authinfo: 0498592085
| INFO2 | <osip_transaction.c: 131> allocating transaction ressource 9 395057138
| INFO2 | <ict.c: 34> allocating ICT context
| INFO2 | <eXutils.c: 535> Not an IPv4 or IPv6 address: voip.eutelia.it
| INFO2 | <eXutils.c: 565> DNS resolution with voip.eutelia.it:5060
| INFO1 | <jcallback.c: 148>

Message sent: INVITE sip:address@hidden SIP/2.0 [...]
Received message: SIP/2.0 407 Proxy Authentication Required [...]

Message sent: ACK sip:address@hidden SIP/2.0
Via: SIP/2.0/UDP 192.168.1.92:5060;rport;branch=z9hG4bK1063424944
From: <sip:address@hidden>;tag=1664892464
To: <sip:address@hidden>;tag=88f80658fec2aee552096ea46e92568d.d145
Call-ID: address@hidden
CSeq: 22 ACK
Content-Length: 0

 (len=16 sizeof(addr)=128 28)
| INFO1 | <jcallback.c: 1442> cb_rcv4xx (id=9)
| INFO1 | <jcallback.c: 520> cb_sndack (id=9)
| INFO1 | <eXosip.c: 333> eXosip: Reseting timer to 15s before waking up!
ortp-message-CALL_REQUESTFAILURE or GLOBALFAILURE or SERVERFAILURE

| INFO2 | <eXosip.c: 2158> INFO: authinfo: "voip.eutelia.it" "voip.eutelia.it"
| INFO1 | <eXosip.c: 2279> authinfo: 0498592085
| INFO2 | <osip_transaction.c: 131> allocating transaction ressource 10 395057138
| INFO2 | <ict.c: 34> allocating ICT context
| INFO2 | <eXutils.c: 535> Not an IPv4 or IPv6 address: voip.eutelia.it
| INFO2 | <eXutils.c: 565> DNS resolution with voip.eutelia.it:5060
| INFO1 | <jcallback.c: 148>

Message sent: INVITE sip:address@hidden SIP/2.0 [...]
Message sent: INVITE sip:address@hidden SIP/2.0 [...]
Message sent: INVITE sip:address@hidden SIP/2.0 [...]

and after give in console the message: linphonec> Could not reach destination

The only difference between the two outputs is the red line that i have evidenced!
Where the 1.3.5 tells "Outgoing interface to reach voip.eutelia.it is 192.168.1.92"
the 1.4.1 tells "ortp-message-CALLREQUESTFAILURE or GLOBALFAILURE orSERVERFAILURE"

Could it be the nutshell of the problem?
Does this tell you something new about the solution?
Thanks for your patience,
Gian