outbound ip questions. signaling IP, Media (RTP)IP

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

 



Well a little digging reveals this options coding for pjsua.exe ip-addr option:
         case OPT_IP_ADDR: /* ip-addr */
             cfg->udp_cfg.public_addr = pj_str(pj_optarg);
             cfg->rtp_cfg.public_addr = pj_str(pj_optarg);
             break;

I think the solution is for a new option rtp_ip= to be used for 
cfg->rtp_cfg.public_addr

David Clark



At 01:44 PM 11/21/2008, David Clark wrote:
>Getting back into PJSIP having looked last at version 0.5.8.  I am 
>now on version 1.0-rc1.  I am ready to test and I want to test with SIP
>provider to see how an actually installation works versus pjsip to 
>pjsip for example.
>
>Well they finally have something setup to test with but they come 
>back with this:
>signal ip address: xxx.xxx.xxx.xxx
>Media (RTP) ip address: yyy.yyy.yyy.yyy
>
>Normally I would make my outbound_ip=xxx.xxx.xxx.xxx and
>my software would dial <sip:9166629999 at xxx.xxx.xxx.xxx> for example 
>to reach 9166629999.
>
>But I have no clue what to do with the Media (RTP) ip address being different.
>
>Can pjsip support this...or do I tell them...reconfigure???
>
>Thanks,
>David Clark
>
>
>_______________________________________________
>Visit our blog: http://blog.pjsip.org
>
>pjsip mailing list
>pjsip at lists.pjsip.org
>http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org




[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