Problem with pjsua in MIPS architecture

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello,

I successufully "auto" configured & compiled all pjsip 1.4.5 for MIPS
big endian architecure (using gcc 3.3.3)

./configure --host=mips-linux
make dep
make

Some tools are working OK like siprtp but now I'm using the pjsua
application and I get errors when manually adding SIP accounts (I have
tested the same accounts in a i386 linux version and it works OK).

This is the error presented after creating a SIP account (please notice
some (null) in the SIP URL).

16:09:39.340    pjsua_acc.c  Account sip:2 at 192.168.2.3 added with id 2
16:09:39.343      sip_reg.c  Invalid Contact:
"(null)<sip:2 at 192.168.2.3:5060(null)>(null)"
16:09:39.344    pjsua_acc.c  Client registration initialization error:
Invalid URI (PJSIP_EINVALIDURI) [status=171039]
16:09:39.345    pjsua_acc.c  Unable to create registration: Invalid URI
(PJSIP_EINVALIDURI) [status=171039]
>>>


This is the full log presented in console:

# ./ua
 16:09:03.050 os_core_unix.c  pjlib 1.4.5 for POSIX initialized
 16:09:03.091 sip_endpoint.c  Creating endpoint instance...
 16:09:03.103          pjlib  select() I/O Queue created (0x1003fc28)
 16:09:03.105 sip_endpoint.c  Module "mod-msg-print" registered
 16:09:03.107 sip_transport.  Transport manager created.
 16:09:03.111 sip_endpoint.c  Module "mod-pjsua-log" registered
 16:09:03.113 sip_endpoint.c  Module "mod-tsx-layer" registered
 16:09:03.114 sip_endpoint.c  Module "mod-stateful-util" registered
 16:09:03.116 sip_endpoint.c  Module "mod-ua" registered
 16:09:03.118 sip_endpoint.c  Module "mod-100rel" registered
 16:09:03.120 sip_endpoint.c  Module "mod-pjsua" registered
 16:09:03.122 sip_endpoint.c  Module "mod-invite" registered
 16:09:03.142       pa_dev.c  PortAudio sound library initialized,
status=0
 16:09:03.143       pa_dev.c  PortAudio host api count=1
 16:09:03.144       pa_dev.c  Sound device count=0
 16:09:03.149          pjlib  select() I/O Queue created (0x10045f6c)
 16:09:03.696 sip_endpoint.c  Module "mod-evsub" registered
 16:09:03.698 sip_endpoint.c  Module "mod-presence" registered
 16:09:03.700 sip_endpoint.c  Module "mod-refer" registered
 16:09:03.702 sip_endpoint.c  Module "mod-pjsua-pres" registered
 16:09:03.708 sip_endpoint.c  Module "mod-pjsua-im" registered
 16:09:03.710 sip_endpoint.c  Module "mod-pjsua-options" registered
 16:09:03.712   pjsua_core.c  1 SIP worker threads created
 16:09:03.712   pjsua_core.c  pjsua version 1.4.5 for
mips-unknown-linux-gnu initialized
 16:09:03.714 sip_endpoint.c  Module "mod-default-handler" registered
 16:09:03.781   pjsua_core.c  SIP UDP socket reachable at
192.168.2.3:5060
 16:09:03.785  udp0x10057cc0  SIP UDP transport started, published
address is 192.168.2.3:5060
 16:09:03.788    pjsua_acc.c  Account <sip:192.168.2.3:5060> added with
id 0
 16:09:04.090    tcplis:5060  SIP TCP listener ready for incoming
connections at 192.168.2.3:5060
 16:09:04.092    pjsua_acc.c  Account
<sip:192.168.2.3:5060;transport=TCP> added with id 1
 16:09:04.121  pjsua_media.c  RTP socket reachable at 192.168.2.3:4000
 16:09:04.123  pjsua_media.c  RTCP socket reachable at 192.168.2.3:4001
 16:09:04.141  pjsua_media.c  RTP socket reachable at 192.168.2.3:4002
 16:09:04.143  pjsua_media.c  RTCP socket reachable at 192.168.2.3:4003
 16:09:04.160  pjsua_media.c  RTP socket reachable at 192.168.2.3:4004
 16:09:04.162  pjsua_media.c  RTCP socket reachable at 192.168.2.3:4005
 16:09:04.179  pjsua_media.c  RTP socket reachable at 192.168.2.3:4006
 16:09:04.182  pjsua_media.c  RTCP socket reachable at 192.168.2.3:4007
>>>>
Account list:
  [ 0] <sip:192.168.2.3:5060>: does not register
       Online status: Online
 *[ 1] <sip:192.168.2.3:5060;transport=TCP>: does not register
       Online status: Online
Buddy list:
 -none-

+=============================================================================+
|       Call Commands:         |   Buddy, IM & Presence:  |     Account:
|
|                              |                          |
|
|  m  Make new call            | +b  Add new buddy       .| +a  Add new
accnt |
|  M  Make multiple calls      | -b  Delete buddy         | -a  Delete
accnt. |
|  a  Answer call              |  i  Send IM              | !a  Modify
accnt. |
|  h  Hangup call  (ha=all)    |  s  Subscribe presence   | rr
(Re-)register |
|  H  Hold call                |  u  Unsubscribe presence | ru
Unregister    |
|  v  re-inVite (release hold) |  t  ToGgle Online status |  >  Cycle
next ac.|
|  U  send UPDATE              |  T  Set online status    |  <  Cycle
prev ac.|
| ],[ Select next/prev call
+--------------------------+-------------------+
|  x  Xfer call                |      Media Commands:     |  Status &
Config: |
|  X  Xfer with Replaces       |                          |
|
|  #  Send RFC 2833 DTMF       | cl  List ports           |  d  Dump
status   |
|  *  Send DTMF with INFO      | cc  Connect port         | dd  Dump
detailed |
| dq  Dump curr. call quality  | cd  Disconnect port      | dc  Dump
config   |
|                              |  V  Adjust audio Volume  |  f  Save
config   |
|  S  Send arbitrary REQUEST   | Cp  Codec priorities     |  f  Save
config   |
+------------------------------+--------------------------+-------------------+
|  q  QUIT   L  ReLoad   sleep MS   echo [0|1|txt]     n: detect NAT
type     |
+=============================================================================+
You have 0 active call
>>> +a
Your SIP URL: (empty to cancel): sip:2 at 192.168.2.3
URL of the registrar: (empty to cancel): sip:172.17.211.2
Auth Realm: (empty to cancel): *
Auth Username: (empty to cancel): 2
Auth Password: (empty to cancel): xxx
 16:09:39.340    pjsua_acc.c  Account sip:2 at 192.168.2.3 added with id 2
 16:09:39.343      sip_reg.c  Invalid Contact:
"(null)<sip:2 at 192.168.2.3:5060(null)>(null)"
 16:09:39.344    pjsua_acc.c  Client registration initialization error:
Invalid URI (PJSIP_EINVALIDURI) [status=171039]
 16:09:39.345    pjsua_acc.c  Unable to create registration: Invalid URI
(PJSIP_EINVALIDURI) [status=171039]
>>>

Is this a known bug?
Is it related to the architecture? (as this doesn't happens in
i386-linux)

FYI --> this is running in a MIPS-BE linux 2.4.27 and the libc is
uClibc-0.9.26

Thank you for any hint!!!
Regards
Antonio




[Index of Archives]     [Asterisk Users]     [Asterisk App Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [Linux API]
  Powered by Linux