[Spce-user] Rewrite Rule for SIP Peering

[Matthias Hohl]

Hello,

here the logfile you want:

This is the call from external to the sipeer that doesn't work:

Jan 14 19:51:12 spce proxy[7566]: NOTICE: <script>: New request on proxy -
M=INVITE R=sip:43720371290 at 78.142.184.11 F=sip:06767788111 at 79.170.208.11
T=sip:43720371290 at 78.142.184.11 IP=79.170.208.11:5060 (127.0.0.1:5060)
ID=2291e5af6f96b447260df9d31057daeb at 79.170.208.11
Jan 14 19:51:12 spce proxy[7566]: INFO: <script>: Load domain preferences
for callee - R=sip:43720371290 at 78.142.184.11
ID=2291e5af6f96b447260df9d31057daeb at 79.170.208.11
Jan 14 19:51:12 spce proxy[7566]: INFO: <script>: Clean domain preferences
for callee - R=sip:43720371290 at 78.142.184.11
ID=2291e5af6f96b447260df9d31057daeb at 79.170.208.11
Jan 14 19:51:12 spce proxy[7566]: NOTICE: <script>: Authentication failed,
no credentials - R=sip:43720371290 at 78.142.184.11
ID=2291e5af6f96b447260df9d31057daeb at 79.170.208.11

If i compare this with a sipcall over the other trunk the only differnce
is this:

Sip Peering it works: F=sip:436767788111@ Sip Peering doesn't work:
F=sip:06767788111@

So i believe i must rewrite the 0676 to 43676 to get it to work, but i
don't know how i do this :/

-----Ursprüngliche Nachricht-----
Von: Andrew Pogrebennyk [mailto:apogrebennyk at sipwise.com]
Gesendet: Mittwoch, 14. Jänner 2015 16:08
An: Matthias Hohl; spce-user at lists.sipwise.com
Betreff: Re: [Spce-user] Rewrite Rule for SIP Peering

Hi,

On 01/14/2015 02:35 PM, Matthias Hohl wrote:
> So I believe the problem is the Rewrite Rule for this SIP Peering. I
> tried now some times but i can’t find the right rewrite rule to set
> this number to 436767788111

Please check if the both peering servers have the same configuration:
Peering server preferences -> Number Manipulations -> rewrite_rule_set

if you have not configured or have configured the same rules for both of
them then I see no reason why it would send different number format to two
peers.

Please also provide grep
5f34a351247f83992dc7552e57f2a82f at 79.170.208.11
/var/log/ngcp/kamailio-proxy.log, this should explain it but you need
debug level 2:
ngcp-kamctl proxy fifo debug 2

Hope this helps.
Andrew