[Spce-user] Incoming calls forbidden - prefix or domain problem?
ptakjura at gmail.com
Thu Oct 8 08:13:21 EDT 2020
I managed to remove country code with rewrite rules, but there are
still problems with probably wrong TO domain.
I have Sipwise server, where is trunk. And this trunk is used in
second Sipwise as a peering server. It looks like first Sipwise is
doing something wrong with TO header in trunk, he gives here his own
domain, instead of DEST domain.
čt 8. 10. 2020 v 9:44 odesílatel Jiri Ptacnik <ptakjura at gmail.com> napsal:
> Hi all,
> SPCE 8.5.1
> outgoing calls works fine.
> But incoming not. In subscriber we have
> SIP URI like this 111222333 at phone.dest.st
> In ngrep-sip on destination server we can see this:
> U 2020/10/08 09:30:05.255854 220.127.116.11:5060 -> 18.104.22.168:5060 #16
> SIP/2.0 403 Forbidden'
> Via: SIP/2.0/UDP
> Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKdrq93atR;rport=5080'
> From: <sip:421888888888 at sip.source.st>;tag=05C56D6A-5F7EBFEC000C8E16-9F8E7700'
> To: <sip:421111222333 at sip.source.st>;tag=95c37a12bff1a2c36d72bf8333176544.78550000'
> CSeq: 10 INVITE'
> Call-ID: 05e801494863fe8e599e45bf3ef491a7 at 22.214.171.124:5060_b2b-1'
> Server: Sipwise NGCP Proxy 8.X'
> Content-Length: 0'
> There are two mysterious things:
> In TO section, there is country code in this example 421, but defined
> SIP URI in subscriber is without country code.
> Is it problem?
> Or weird is, in TO sections is after @ sign source domain, not
> destination domain?
> What should be wrong?
> Thanks, George
More information about the Spce-user