[Spce-user] Ris: connect 2 sipwise as trunk

stefanormc stefanormc at gmail.com
Thu Nov 30 06:48:54 EST 2017


Instead of deleting and recreating the rule I moved it to the other peer.
Could that be the problem?


On 30 November 2017 at 12:42:46, stefanormc (stefanormc at gmail.com) wrote:

It doesn’t seem to effect the rules

I’m on 5.4.1


On 30 November 2017 at 12:37:19, Daniel Grotti (dgrotti at sipwise.com) wrote:

Try to run:

ngcp-sercmd proxy  lcr.reload

and then again:

ngcp-sercmd proxy lcr.dump_rules

--
Daniel Grotti
Head of Customer Support
Sipwise GmbH, Campus 21/Europaring F15
AT-2345 Brunn am Gebirge

Office: +43(0)130120332
Email: dgrotti at sipwise.com
Website: https://www.sipwise.com

On 11/30/2017 12:32 PM, stefanormc wrote:

There is no rule in ngcp-sercmd proxy lcr.dump_rules

Last login: Thu Nov 30 12:04:19 2017 from 93-57-17-112.ip162.fastwebnet.it

centrale:~# ngcp-sercmd proxy lcr.dump_rules

{

lcr_id: 1

rule_id: 9

prefix:

from_uri: @digi.voceblu.it

request_uri:

stopper: 0

}

{

gw_index: 3

priority: 1

weight: 1

}

{

lcr_id: 1

rule_id: 7

prefix:

from_uri: @voceblu.it

request_uri:

stopper: 0

}

{

gw_index: 1

priority: 2

weight: 1

}

{

lcr_id: 1

rule_id: 6

prefix:

from_uri: old at d.voceblu.it

request_uri:

stopper: 0

}

{

gw_index: 4

priority: 1

weight: 1

}

{

lcr_id: 1

rule_id: 4

prefix:

from_uri: @geva.voceblu.it

request_uri:

stopper: 0

}

{

gw_index: 1

priority: 2

weight: 1

}

0

centrale:~#


But there is in web interface:

# Prefix Caller Pattern State Description Peer Group Peer Name Peer Host Peer
IP Peer State Priority Weight
4
@geva.voceblu.it 1
TWT TWT voce.voipeople.it 77.239.128.7 1 2 1
6
^d\.voceblu\.it$ 1 seleziona numeri digitel centrale03 centrale03
94.125.235.56 1 1 1
7
@voceblu.it 1
TWT TWT voce.voipeople.it 77.239.128.7 1 2 1
8
@v.voceblu.it 1
centrale03 centrale03
94.125.235.56 1 1 1
9
@digi.voceblu.it 1 seleziona tutti quelli diretti digitel Digitel
diretto Digitel
diretto voip.digitelitalia.it 109.238.17.166 1 1 1


On 30 November 2017 at 11:59:24, Daniel Grotti (dgrotti at sipwise.com) wrote:

it seems you do not have it.
Please try to re-save the rule, and also do:

ngcp-sercmd proxy lcr.dump_gws
ngcp-sercmd proxy lcr.dump_rules


Do you see your peer there and the rule?

--
Daniel Grotti
Head of Customer Support
Sipwise GmbH, Campus 21/Europaring F15
AT-2345 Brunn am Gebirge

Office: +43(0)130120332
Email: dgrotti at sipwise.com
Website: https://www.sipwise.com

On 11/30/2017 11:54 AM, stefanormc at gmail.com wrote:

There is a rule catching all d.voceblu.it


-------- Messaggio originale --------
Oggetto: Re: [Spce-user] connect 2 sipwise as trunk
Da: Daniel Grotti
A: stefanormc ,spce-user at lists.sipwise.com
CC:


Hi,
problem is that you do not have a peering rule matching the called (anc
callind) part, see below.
Please check your peering rules in your peerin server. Have you at least
created the "catch-all" rule?

--
Daniel Grotti
Head of Customer Support
Sipwise GmbH, Campus 21/Europaring F15
AT-2345 Brunn am Gebirge

Office: +43(0)130120332
Email: dgrotti at sipwise.com
Website: https://www.sipwise.com

On 11/30/2017 11:29 AM, stefanormc wrote:

Load gws matching calling part 'sip:390118118673 at d.voceblu.it' and called
user '3355416588' and called part 'sip:3355416588 at d.voceblu.it;user=phone'
- R=sip:3355416588 at d.voceblu.it;user=phone
ID=3c4632c304e2-1vukdq0ac0ql at snom190 UA='snom190/3.60x'
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20171130/121820f3/attachment-0001.html>


More information about the Spce-user mailing list