search for: sip_regist

...8.100.129> > > When I'm using the TCP line instead of the other, I've got : > [May 26 17:58:42] NOTICE[2859]: chan_sip.c:20169 sip_parse_host: '/' is not > a valid port number on line 25 of sip.conf. using default. > [May 26 17:58:42] WARNING[2859]: chan_sip.c:6560 sip_register: Format for > registration is > [transport://]user[:secret[:authuser]]@domain[:port][/extension][~expiry] at > line 25 > > > Is this "register=>tcp://trunk4ipbx:password at 192.168.100.129<trunk4ipbx%3Apassword at 192.168.100.129>" > statement correct ? &gt...

...lass codec 5 session protocol sipv2 session target ipv4:192.168.10.103 <--- this is the asterisk's ip dtmf-relay rtp-nte Using asterisk v1.0 i can receive calls perfectly, after i upgraded to asterisk v1.2.4 i receive the following error Feb 28 16:49:34 WARNING[11142]: chan_sip.c:3207 sip_register: Format for registration is user[:secret[:authuser]]@host[:port][/contact] at line 154 Of course, i cant receive incoming call anymore, reading the error i undestand that im missing the username in the register => line in sip.conf , as you can see, there is not username parameter in the c...

...pbx%3Apassword at 192.168.100.129> When I'm using the TCP line instead of the other, I've got : [May 26 17:58:42] NOTICE[2859]: chan_sip.c:20169 sip_parse_host: '/' is not a valid port number on line 25 of sip.conf. using default. [May 26 17:58:42] WARNING[2859]: chan_sip.c:6560 sip_register: Format for registration is [transport://]user[:secret[:authuser]]@domain[:port][/extension][~expiry] at line 25 Is this "register=>tcp://trunk4ipbx:password at 192.168.100.129<trunk4ipbx%3Apassword at 192.168.100.129>" statement correct ? Regards -------------- next part --...

Where in the code does something like: register => user[:secret[:authuser]]@host[:port][/extension] from sip.conf 1) get parsed 2) actually register. I tried looking in channels/chan_sip.c and don't see where that happens. Can someone point me the right file and or function. Thanks, Jerry

...might cause another server to forget the registration previously made there. In such a scenario, registering to all the servers would be a waste of time. I'm leaning toward attempting to register with each server in sequence until we are successful. In reading chan_sip.c, I found the function sip_register(..) which reads register=> lines from sip.conf and copies settings from there to a sip_registry struct. The function does a gethostbyname() to look up the hostname immediately. The IP returned, as well as the hostname, are stored in the struct. Later on, in transmit_register(..), is where the...

...annels/SIP/sip_one_legged_transfer_v6 --- SKIPPED --> Dependency: twisted -- Met: True --> Dependency: starpy -- Met: True --> Dependency: pjsua -- Met: True --> Dependency: ipv6 -- Met: True --> Dependency: pjsuav6 -- Met: True --> tests/channels/SIP/sip_register --- PASSED --> tests/channels/SIP/sip_register_domain_acl --- PASSED --> tests/channels/SIP/sip_channel_params --- PASSED --> tests/channels/SIP/sip_tls_call --- FAILED --> tests/channels/SIP/sip_tls_register --- PASSED --> tests/channels/SIP/sip_srtp --- SKIPPED --> Depen...