Chan_sip -> Pjsip – Address Binding

Home » Asterisk Users » Chan_sip -> Pjsip – Address Binding
Asterisk Users 2 Comments

hi,

i want gradually migrate to pjsip

i have 2 network interfaces with a lot of endpoints on both (both UDP)
eth0 1.1.1.1
eth1 2.2.2.2

i want start migrate endpoints to pjsip on 2.2.2.2:5070

but configuration like this is not possible

sip.conf

[general]
bindaddr = 0.0.0.0
bindport = 5060

pjsip.conf
[udp]
type = transport bind = 2.2.2.2:5070
protocol = udp

[Nov 25 14:44:18] ERROR[3442]: res_pjsip/config_transport.c:664
transport_apply: Transport ‘udp’ could not be started: Cannot assign requested address

[Nov 25 14:44:18] ERROR[3442]: res_sorcery_config.c:420
sorcery_config_internal_load: Could not create an object of type
‘transport’ with id ‘udp’ from configuration file

is there some other way?

thanks

Marek

—

2 thoughts on - Chan_sip -> Pjsip – Address Binding

  • tried chan_sip/udp + pjsip/tcp

    but the same problem

    sip.conf

    [general]
    udpbindport=5060
    udpbindaddr=0.0.0.0
    tcpenable=no tlsenable=no

    pjsip.conf
    [transport-tcp]
    type = transport bind = 2.2.2.2:5070
    protocol = tcp

     Loading res_pjsip.so.
    [Nov 25 16:21:04] ERROR[5528]: res_pjsip/config_transport.c:664
    transport_apply: Transport ‘transport-tcp’ could not be started: Cannot assign requested address
    [Nov 25 16:21:04] ERROR[5528]: res_sorcery_config.c:420
    sorcery_config_internal_load: Could not create an object of type
    ‘transport’ with id ‘transport-tcp’ from  configuration file ‘pjsip.conf’

    anybody know if its possible preload pjsip before chan_sip? (tried preload=  but its complicated. a lot of dependecies)

    its Asterisk 13 current

    Marek

    Dne 25/11/2020 v 14:55 marek napsal(a):

    —

  • You’re assuming that the problem is an interaction between chan_sip and chan_pjsip. If you don’t load chan_sip at all, does the problem still occur? If so then chan_sip isn’t the problem but something most likely system level – since the system stated that PJSIP could not use the configured address.