Wayke91 Posts: 13
4/6/2017
|
When adding a new trunk, I was unable to get the FQDN of the registrar in the SIP Registrar field, it seems there is a character limit on that field. I was able to use one of their IP Addresses as a work around.
I don't think I need any support on this issue really, but more of just notifying everyone of this. Thanks! edited by Wayke91 on 4/6/2017
|
|
0
link
|
mkeys Posts: 6
5/11/2017
|
Wayke91 wrote:
When adding a new trunk, I was unable to get the FQDN of the registrar in the SIP Registrar field, it seems there is a character limit on that field. I was able to use one of their IP Addresses as a work around.
I don't think I need any support on this issue really, but more of just notifying everyone of this. Thanks! edited by Wayke91 on 4/6/2017
I ran into this also. The character limitation also exists in the outbound proxy field but there doesn't seem to be one in the "server" field. I also wanted to point out that it states in the informational section "Specify either IP Address:Port or Domain name", but you must specify IP:port to apply. It will not accept a domain name (server field seems to accept domain.name:port though). Does this mean DNS SRV lookup doesn't work?
|
|
0
link
|
bloxsupport1 Posts: 232
5/15/2017
|
could you please tell us the version of blox you are using ?
|
|
0
link
|
Wayke91 Posts: 13
5/15/2017
|
I'm running 1.0.4-8.
|
|
0
link
|
volga629 Posts: 15
3/3/2018
|
Same think blox-1-0-6-stable
|
|
0
link
|
bloxsupport1 Posts: 232
3/4/2018
|
Please let us the knows the output of the command "rpm -qa | grep blox" volga629 wrote:
Same think blox-1-0-6-stable
|
|
0
link
|
volga629 Posts: 15
3/6/2018
|
[root@casbc00 ~]# rpm -qa | grep blox freeblox-1.0.6-19.x86_64 blox_rtppinhole-1.0.6-19.x86_64 blox_security-1.0.6-19.x86_64 blox_core-1.0.6-19.x86_64 blox_rtpengine-1.0.6-19.x86_64 blox_opensips-1.0.6-19.x86_64 blox-rpm-keys-1.0.6-19.x86_64 blox_ministun_client-1.0.6-19.x86_64
bloxsupport1 wrote:
Please let us the knows the output of the command "rpm -qa | grep blox" volga629 wrote:
Same think blox-1-0-6-stable
|
|
0
link
|
bloxsupport1 Posts: 232
3/6/2018
|
Send us the screen shot of the error you are getting. Please send to support@blox.org
Thanks Blox Support Team.
volga629 wrote:
[root@casbc00 ~]# rpm -qa | grep blox freeblox-1.0.6-19.x86_64 blox_rtppinhole-1.0.6-19.x86_64 blox_security-1.0.6-19.x86_64 blox_core-1.0.6-19.x86_64 blox_rtpengine-1.0.6-19.x86_64 blox_opensips-1.0.6-19.x86_64 blox-rpm-keys-1.0.6-19.x86_64 blox_ministun_client-1.0.6-19.x86_64
bloxsupport1 wrote:
Please let us the knows the output of the command "rpm -qa | grep blox" volga629 wrote:
Same think blox-1-0-6-stable edited by bloxsupport1 on 3/6/2018
|
|
0
link
|
volga629 Posts: 15
3/8/2018
|
I sent screenshot to support email.
bloxsupport1 wrote:
Send us the screen shot of the error you are getting. Please send to support@blox.org
Thanks Blox Support Team.
volga629 wrote:
[root@casbc00 ~]# rpm -qa | grep blox freeblox-1.0.6-19.x86_64 blox_rtppinhole-1.0.6-19.x86_64 blox_security-1.0.6-19.x86_64 blox_core-1.0.6-19.x86_64 blox_rtpengine-1.0.6-19.x86_64 blox_opensips-1.0.6-19.x86_64 blox-rpm-keys-1.0.6-19.x86_64 blox_ministun_client-1.0.6-19.x86_64
bloxsupport1 wrote:
Please let us the knows the output of the command "rpm -qa | grep blox" volga629 wrote:
Same think blox-1-0-6-stable edited by bloxsupport1 on 3/6/2018
|
|
0
link
|
bloxsupport1 Posts: 232
3/15/2018
|
You need to specify domain:port
|
|
0
link
|