[Spce-user] sip registration stuck 3.5.16
Daniel Grotti
dgrotti at sipwise.com
Fri Nov 14 06:30:36 EST 2014
Please,
provide:
grep "3a004a4f642983335856b04f0b207fda at 117.152.246.21"
/var/log/ngcp/kamailio-proxy.log
and
grep "3aeb016a20d3b9aa7640366d3b190643 at 117.152.246.21"
/var/log/ngcp/kamailio-proxy.log
Daniel
On 11/13/2014 06:43 PM, Aziz Palmer wrote:
> ------------Output after clearing all registration--------------
>
> date
> ^Croot at tx-portal-2:~# ngrep-sip r
> interface: any
> filter: (ip or ip6) and ( port 5060 )
> match: (^|CSeq:\s?\d* )(REGISTER)
>
> U 2014/11/13 11:26:43.015168 117.152.246.21:5060 -> 117.152.244.201:5060
> REGISTER sip:edge.xyz-co.com SIP/2.0'
> Via: SIP/2.0/UDP 117.152.246.21:5060;branch=z9hG4bK6a44b7a5'
> Max-Forwards: 70'
> From: <sip:master.sample.edge at edge.xyz-co.com>;tag=as4304f0a0'
> To: <sip:master.sample.edge at edge.xyz-co.com>'
> Call-ID: 3aeb016a20d3b9aa7640366d3b190643 at 117.152.246.21'
> CSeq: 102 REGISTER'
> User-Agent: FPBX-2.11.0(11.7.0)'
> Expires: 120'
> Contact: <sip:master.sample.edge at 117.152.246.21:5060>'
> Content-Length: 0'
> '
>
>
> U 2014/11/13 11:26:43.015489 127.0.0.1:5060 -> 127.0.0.1:5062
> REGISTER sip:edge.xyz-co.com SIP/2.0'
> Via: SIP/2.0/UDP
> 127.0.0.1;branch=z9hG4bK1d23.988c32e163d6b80891604e92e0bfe7c7.0'
> Via: SIP/2.0/UDP 117.152.246.21:5060;rport=5060;branch=z9hG4bK6a44b7a5'
> Max-Forwards: 69'
> From: <sip:master.sample.edge at edge.xyz-co.com>;tag=as4304f0a0'
> To: <sip:master.sample.edge at edge.xyz-co.com>'
> Call-ID: 3aeb016a20d3b9aa7640366d3b190643 at 117.152.246.21'
> CSeq: 102 REGISTER'
> User-Agent: FPBX-2.11.0(11.7.0)'
> Expires: 120'
> Contact: <sip:master.sample.edge at 117.152.246.21:5060>'
> Content-Length: 0'
> P-NGCP-Src-Ip: 117.152.246.21'
> P-NGCP-Src-Port: 5060'
> P-NGCP-Src-Proto: udp'
> P-NGCP-Src-Af: 4'
> P-Sock-Info: udp:117.152.244.201:5060'
> Path: <sip:lb at 127.0.0.1;lr;socket=sip:117.152.244.201:5060>'
> '
>
>
> U 2014/11/13 11:26:43.015689 127.0.0.1:5062 -> 127.0.0.1:5060
> SIP/2.0 100 Trying'
> Via: SIP/2.0/UDP
> 127.0.0.1;branch=z9hG4bK1d23.988c32e163d6b80891604e92e0bfe7c7.0'
> Via: SIP/2.0/UDP 117.152.246.21:5060;rport=5060;branch=z9hG4bK6a44b7a5'
> From: <sip:master.sample.edge at edge.xyz-co.com>;tag=as4304f0a0'
> To: <sip:master.sample.edge at edge.xyz-co.com>'
> Call-ID: 3aeb016a20d3b9aa7640366d3b190643 at 117.152.246.21'
> CSeq: 102 REGISTER'
> P-Out-Socket: udp:117.152.244.201:5060'
> P-NGCP-Auth-IP: 117.152.246.21'
> P-NGCP-Auth-UA: FPBX-2.11.0(11.7.0)'
> Server: Sipwise NGCP Proxy 3.X'
> Content-Length: 0'
> '
>
>
> U 2014/11/13 11:26:43.015884 127.0.0.1:5062 -> 127.0.0.1:5060
> SIP/2.0 401 Unauthorized'
> Via: SIP/2.0/UDP
> 127.0.0.1;branch=z9hG4bK1d23.988c32e163d6b80891604e92e0bfe7c7.0;rport=5060'
> Via: SIP/2.0/UDP 117.152.246.21:5060;rport=5060;branch=z9hG4bK6a44b7a5'
> From: <sip:master.sample.edge at edge.xyz-co.com>;tag=as4304f0a0'
> To:
> <sip:master.sample.edge at edge.xyz-co.com>;tag=1d24a28a0bded6c40d31e6db8aab9ac6.80d1'
> Call-ID: 3aeb016a20d3b9aa7640366d3b190643 at 117.152.246.21'
> CSeq: 102 REGISTER'
> P-Out-Socket: udp:117.152.244.201:5060'
> P-NGCP-Auth-IP: 117.152.246.21'
> P-NGCP-Auth-UA: FPBX-2.11.0(11.7.0)'
> WWW-Authenticate: Digest realm="edge.xyz-co.com",
> nonce="VGTq/1Rk6dMgBWHAG2VtGtcfG2FNnmog"'
> Server: Sipwise NGCP Proxy 3.X'
> Content-Length: 0'
> '
>
>
> U 2014/11/13 11:26:43.015929 117.152.244.201:5060 -> 117.152.246.21:5060
> SIP/2.0 100 Trying'
> Via: SIP/2.0/UDP 117.152.246.21:5060;rport=5060;branch=z9hG4bK6a44b7a5'
> From: <sip:master.sample.edge at edge.xyz-co.com>;tag=as4304f0a0'
> To: <sip:master.sample.edge at edge.xyz-co.com>'
> Call-ID: 3aeb016a20d3b9aa7640366d3b190643 at 117.152.246.21'
> CSeq: 102 REGISTER'
> Server: Sipwise NGCP Proxy 3.X'
> Content-Length: 0'
> '
>
>
> U 2014/11/13 11:26:43.016056 117.152.244.201:5060 -> 117.152.246.21:5060
> SIP/2.0 401 Unauthorized'
> Via: SIP/2.0/UDP 117.152.246.21:5060;rport=5060;branch=z9hG4bK6a44b7a5'
> From: <sip:master.sample.edge at edge.xyz-co.com>;tag=as4304f0a0'
> To:
> <sip:master.sample.edge at edge.xyz-co.com>;tag=1d24a28a0bded6c40d31e6db8aab9ac6.80d1'
> Call-ID: 3aeb016a20d3b9aa7640366d3b190643 at 117.152.246.21'
> CSeq: 102 REGISTER'
> WWW-Authenticate: Digest realm="edge.xyz-co.com",
> nonce="VGTq/1Rk6dMgBWHAG2VtGtcfG2FNnmog"'
> Server: Sipwise NGCP Proxy 3.X'
> Content-Length: 0'
> '
>
>
> U 2014/11/13 11:26:43.111885 117.152.246.21:5060 -> 117.152.244.201:5060
> REGISTER sip:edge.xyz-co.com SIP/2.0'
> Via: SIP/2.0/UDP 117.152.246.21:5060;branch=z9hG4bK5b250768'
> Max-Forwards: 70'
> From: <sip:master.sample.edge at edge.xyz-co.com>;tag=as6746818c'
> To: <sip:master.sample.edge at edge.xyz-co.com>'
> Call-ID: 3aeb016a20d3b9aa7640366d3b190643 at 117.152.246.21'
> CSeq: 103 REGISTER'
> User-Agent: FPBX-2.11.0(11.7.0)'
> Authorization: Digest username="master.sample.edge",
> realm="edge.xyz-co.com", algorithm=MD5, uri="sip:edge.xyz-co.com",
> nonce="VGTq/1Rk6dMgBWHAG2VtGtcfG2FNnmog",
> response="86439eabcad60d3287c4ae1f15542c52"'
> Expires: 120'
> Contact: <sip:master.sample.edge at 117.152.246.21:5060>'
> Content-Length: 0'
> '
>
>
> U 2014/11/13 11:26:43.112182 127.0.0.1:5060 -> 127.0.0.1:5062
> REGISTER sip:edge.xyz-co.com SIP/2.0'
> Via: SIP/2.0/UDP
> 127.0.0.1;branch=z9hG4bK2d23.27f8347c509a51f053d4ba79309f5e5f.0'
> Via: SIP/2.0/UDP 117.152.246.21:5060;rport=5060;branch=z9hG4bK5b250768'
> Max-Forwards: 69'
> From: <sip:master.sample.edge at edge.xyz-co.com>;tag=as6746818c'
> To: <sip:master.sample.edge at edge.xyz-co.com>'
> Call-ID: 3aeb016a20d3b9aa7640366d3b190643 at 117.152.246.21'
> CSeq: 103 REGISTER'
> User-Agent: FPBX-2.11.0(11.7.0)'
> Authorization: Digest username="master.sample.edge",
> realm="edge.xyz-co.com", algorithm=MD5, uri="sip:edge.xyz-co.com",
> nonce="VGTq/1Rk6dMgBWHAG2VtGtcfG2FNnmog",
> response="86439eabcad60d3287c4ae1f15542c52"'
> Expires: 120'
> Contact: <sip:master.sample.edge at 117.152.246.21:5060>'
> Content-Length: 0'
> P-NGCP-Src-Ip: 117.152.246.21'
> P-NGCP-Src-Port: 5060'
> P-NGCP-Src-Proto: udp'
> P-NGCP-Src-Af: 4'
> P-Sock-Info: udp:117.152.244.201:5060'
> Path: <sip:lb at 127.0.0.1;lr;socket=sip:117.152.244.201:5060>'
> '
>
>
> U 2014/11/13 11:26:43.112389 127.0.0.1:5062 -> 127.0.0.1:5060
> SIP/2.0 100 Trying'
> Via: SIP/2.0/UDP
> 127.0.0.1;branch=z9hG4bK2d23.27f8347c509a51f053d4ba79309f5e5f.0'
> Via: SIP/2.0/UDP 117.152.246.21:5060;rport=5060;branch=z9hG4bK5b250768'
> From: <sip:master.sample.edge at edge.xyz-co.com>;tag=as6746818c'
> To: <sip:master.sample.edge at edge.xyz-co.com>'
> Call-ID: 3aeb016a20d3b9aa7640366d3b190643 at 117.152.246.21'
> CSeq: 103 REGISTER'
> P-Out-Socket: udp:117.152.244.201:5060'
> P-NGCP-Auth-IP: 117.152.246.21'
> P-NGCP-Auth-UA: FPBX-2.11.0(11.7.0)'
> Server: Sipwise NGCP Proxy 3.X'
> Content-Length: 0'
> '
>
>
> U 2014/11/13 11:26:43.112625 117.152.244.201:5060 -> 117.152.246.21:5060
> SIP/2.0 100 Trying'
> Via: SIP/2.0/UDP 117.152.246.21:5060;rport=5060;branch=z9hG4bK5b250768'
> From: <sip:master.sample.edge at edge.xyz-co.com>;tag=as6746818c'
> To: <sip:master.sample.edge at edge.xyz-co.com>'
> Call-ID: 3aeb016a20d3b9aa7640366d3b190643 at 117.152.246.21'
> CSeq: 103 REGISTER'
> Server: Sipwise NGCP Proxy 3.X'
> Content-Length: 0'
> '
>
>
> U 2014/11/13 11:26:43.120431 127.0.0.1:5062 -> 127.0.0.1:5060
> SIP/2.0 200 OK'
> Via: SIP/2.0/UDP
> 127.0.0.1;branch=z9hG4bK2d23.27f8347c509a51f053d4ba79309f5e5f.0;rport=5060'
> Via: SIP/2.0/UDP 117.152.246.21:5060;rport=5060;branch=z9hG4bK5b250768'
> From: <sip:master.sample.edge at edge.xyz-co.com>;tag=as6746818c'
> To:
> <sip:master.sample.edge at edge.xyz-co.com>;tag=1d24a28a0bded6c40d31e6db8aab9ac6.1a50'
> Call-ID: 3aeb016a20d3b9aa7640366d3b190643 at 117.152.246.21'
> CSeq: 103 REGISTER'
> P-Out-Socket: udp:117.152.244.201:5060'
> P-NGCP-Auth-IP: 117.152.246.21'
> P-NGCP-Auth-UA: FPBX-2.11.0(11.7.0)'
> P-NGCP-Authorization: master.sample.edge'
> P-NGCP-Authorized: 1'
> P-Caller-UUID: e8093f41-b154-4d8b-b14f-2c861c2b50da'
> Contact: <sip:master.sample.edge at 117.152.246.21:5060>;expires=120'
> Server: Sipwise NGCP Proxy 3.X'
> Content-Length: 0'
> '
>
>
> U 2014/11/13 11:26:43.120747 117.152.244.201:5060 -> 117.152.246.21:5060
> SIP/2.0 200 OK'
> Via: SIP/2.0/UDP 117.152.246.21:5060;rport=5060;branch=z9hG4bK5b250768'
> From: <sip:master.sample.edge at edge.xyz-co.com>;tag=as6746818c'
> To:
> <sip:master.sample.edge at edge.xyz-co.com>;tag=1d24a28a0bded6c40d31e6db8aab9ac6.1a50'
> Call-ID: 3aeb016a20d3b9aa7640366d3b190643 at 117.152.246.21'
> CSeq: 103 REGISTER'
> Contact: <sip:master.sample.edge at 117.152.246.21:5060>;expires=120'
> Server: Sipwise NGCP Proxy 3.X'
> Content-Length: 0'
> '
>
>
>
> *************************** 1. row ***************************
> id: 4
> username: master.sample.edge
> domain: NULL
> contact: sip:master.sample.edge at 117.152.246.21:5060
> received: NULL
> path: <sip:lb at 127.0.0.1;lr;socket=sip:117.152.244.201:5060>
> expires: 2014-11-13 11:30:28
> q: -1.00
> callid: 3aeb016a20d3b9aa7640366d3b190643 at 117.152.246.21
> cseq: 104
> last_modified: 2014-11-13 11:28:28
> flags: 0
> cflags: 0
> user_agent: FPBX-2.11.0(11.7.0)
> socket: udp:127.0.0.1:5062
> methods: NULL
> ruid: uloc-5464e835-7cf0-1
> reg_id: 0
> instance: NULL
>
>
> -------------------------------------------------------------------------------------
> Output after going back into Asterisk and RE-Registering the sip trunk
> ---------------------------------------------------------
>
> as you can see it stops updating the registration in the sipwise DB
>
>
> U 2014/11/13 11:31:07.925577 117.152.246.21:5060 -> 117.152.244.201:5060
> REGISTER sip:edge.xyz-co.com SIP/2.0'
> Via: SIP/2.0/UDP 117.152.246.21:5060;branch=z9hG4bK7b075b0e'
> Max-Forwards: 70'
> From: <sip:master.sample.edge at edge.xyz-co.com>;tag=as3e0f1112'
> To: <sip:master.sample.edge at edge.xyz-co.com>'
> Call-ID: 3a004a4f642983335856b04f0b207fda at 117.152.246.21'
> CSeq: 102 REGISTER'
> User-Agent: FPBX-2.11.0(11.7.0)'
> Expires: 120'
> Contact: <sip:master.sample.edge at 117.152.246.21:5060>'
> Content-Length: 0'
> '
>
>
> U 2014/11/13 11:31:07.925833 127.0.0.1:5060 -> 127.0.0.1:5062
> REGISTER sip:edge.xyz-co.com SIP/2.0'
> Via: SIP/2.0/UDP
> 127.0.0.1;branch=z9hG4bK37bc.df000db46f012802ae57b58a06581831.0'
> Via: SIP/2.0/UDP 117.152.246.21:5060;rport=5060;branch=z9hG4bK7b075b0e'
> Max-Forwards: 69'
> From: <sip:master.sample.edge at edge.xyz-co.com>;tag=as3e0f1112'
> To: <sip:master.sample.edge at edge.xyz-co.com>'
> Call-ID: 3a004a4f642983335856b04f0b207fda at 117.152.246.21'
> CSeq: 102 REGISTER'
> User-Agent: FPBX-2.11.0(11.7.0)'
> Expires: 120'
> Contact: <sip:master.sample.edge at 117.152.246.21:5060>'
> Content-Length: 0'
> P-NGCP-Src-Ip: 117.152.246.21'
> P-NGCP-Src-Port: 5060'
> P-NGCP-Src-Proto: udp'
> P-NGCP-Src-Af: 4'
> P-Sock-Info: udp:117.152.244.201:5060'
> Path: <sip:lb at 127.0.0.1;lr;socket=sip:117.152.244.201:5060>'
> '
>
>
> U 2014/11/13 11:31:07.926105 127.0.0.1:5062 -> 127.0.0.1:5060
> SIP/2.0 100 Trying'
> Via: SIP/2.0/UDP
> 127.0.0.1;branch=z9hG4bK37bc.df000db46f012802ae57b58a06581831.0'
> Via: SIP/2.0/UDP 117.152.246.21:5060;rport=5060;branch=z9hG4bK7b075b0e'
> From: <sip:master.sample.edge at edge.xyz-co.com>;tag=as3e0f1112'
> To: <sip:master.sample.edge at edge.xyz-co.com>'
> Call-ID: 3a004a4f642983335856b04f0b207fda at 117.152.246.21'
> CSeq: 102 REGISTER'
> P-Out-Socket: udp:117.152.244.201:5060'
> P-NGCP-Auth-IP: 117.152.246.21'
> P-NGCP-Auth-UA: FPBX-2.11.0(11.7.0)'
> Server: Sipwise NGCP Proxy 3.X'
> Content-Length: 0'
> '
>
>
> U 2014/11/13 11:31:07.926275 127.0.0.1:5062 -> 127.0.0.1:5060
> SIP/2.0 401 Unauthorized'
> Via: SIP/2.0/UDP
> 127.0.0.1;branch=z9hG4bK37bc.df000db46f012802ae57b58a06581831.0;rport=5060'
> Via: SIP/2.0/UDP 117.152.246.21:5060;rport=5060;branch=z9hG4bK7b075b0e'
> From: <sip:master.sample.edge at edge.xyz-co.com>;tag=as3e0f1112'
> To:
> <sip:master.sample.edge at edge.xyz-co.com>;tag=1d24a28a0bded6c40d31e6db8aab9ac6.20cf'
> Call-ID: 3a004a4f642983335856b04f0b207fda at 117.152.246.21'
> CSeq: 102 REGISTER'
> P-Out-Socket: udp:117.152.244.201:5060'
> P-NGCP-Auth-IP: 117.152.246.21'
> P-NGCP-Auth-UA: FPBX-2.11.0(11.7.0)'
> WWW-Authenticate: Digest realm="edge.xyz-co.com",
> nonce="VGTsB1Rk6tsPFr2TXEJLtoaFKOllrlF9"'
> Server: Sipwise NGCP Proxy 3.X'
> Content-Length: 0'
> '
>
>
> U 2014/11/13 11:31:07.926403 117.152.244.201:5060 -> 117.152.246.21:5060
> SIP/2.0 100 Trying'
> Via: SIP/2.0/UDP 117.152.246.21:5060;rport=5060;branch=z9hG4bK7b075b0e'
> From: <sip:master.sample.edge at edge.xyz-co.com>;tag=as3e0f1112'
> To: <sip:master.sample.edge at edge.xyz-co.com>'
> Call-ID: 3a004a4f642983335856b04f0b207fda at 117.152.246.21'
> CSeq: 102 REGISTER'
> Server: Sipwise NGCP Proxy 3.X'
> Content-Length: 0'
> '
>
>
> U 2014/11/13 11:31:07.926448 117.152.244.201:5060 -> 117.152.246.21:5060
> SIP/2.0 401 Unauthorized'
> Via: SIP/2.0/UDP 117.152.246.21:5060;rport=5060;branch=z9hG4bK7b075b0e'
> From: <sip:master.sample.edge at edge.xyz-co.com>;tag=as3e0f1112'
> To:
> <sip:master.sample.edge at edge.xyz-co.com>;tag=1d24a28a0bded6c40d31e6db8aab9ac6.20cf'
> Call-ID: 3a004a4f642983335856b04f0b207fda at 117.152.246.21'
> CSeq: 102 REGISTER'
> WWW-Authenticate: Digest realm="edge.xyz-co.com",
> nonce="VGTsB1Rk6tsPFr2TXEJLtoaFKOllrlF9"'
> Server: Sipwise NGCP Proxy 3.X'
> Content-Length: 0'
> '
>
>
> U 2014/11/13 11:31:08.021363 117.152.246.21:5060 -> 117.152.244.201:5060
> REGISTER sip:edge.xyz-co.com SIP/2.0'
> Via: SIP/2.0/UDP 117.152.246.21:5060;branch=z9hG4bK30605341'
> Max-Forwards: 70'
> From: <sip:master.sample.edge at edge.xyz-co.com>;tag=as7247830f'
> To: <sip:master.sample.edge at edge.xyz-co.com>'
> Call-ID: 3a004a4f642983335856b04f0b207fda at 117.152.246.21'
> CSeq: 103 REGISTER'
> User-Agent: FPBX-2.11.0(11.7.0)'
> Authorization: Digest username="master.sample.edge",
> realm="edge.xyz-co.com", algorithm=MD5, uri="sip:edge.xyz-co.com",
> nonce="VGTsB1Rk6tsPFr2TXEJLtoaFKOllrlF9",
> response="ad4f421a2734de6fea2fe3f3c26b049d"'
> Expires: 120'
> Contact: <sip:master.sample.edge at 117.152.246.21:5060>'
> Content-Length: 0'
> '
>
>
> U 2014/11/13 11:31:08.021686 127.0.0.1:5060 -> 127.0.0.1:5062
> REGISTER sip:edge.xyz-co.com SIP/2.0'
> Via: SIP/2.0/UDP
> 127.0.0.1;branch=z9hG4bK47bc.1cdf78be45dd9f905d8eb2bd0e1c1d1d.0'
> Via: SIP/2.0/UDP 117.152.246.21:5060;rport=5060;branch=z9hG4bK30605341'
> Max-Forwards: 69'
> From: <sip:master.sample.edge at edge.xyz-co.com>;tag=as7247830f'
> To: <sip:master.sample.edge at edge.xyz-co.com>'
> Call-ID: 3a004a4f642983335856b04f0b207fda at 117.152.246.21'
> CSeq: 103 REGISTER'
> User-Agent: FPBX-2.11.0(11.7.0)'
> Authorization: Digest username="master.sample.edge",
> realm="edge.xyz-co.com", algorithm=MD5, uri="sip:edge.xyz-co.com",
> nonce="VGTsB1Rk6tsPFr2TXEJLtoaFKOllrlF9",
> response="ad4f421a2734de6fea2fe3f3c26b049d"'
> Expires: 120'
> Contact: <sip:master.sample.edge at 117.152.246.21:5060>'
> Content-Length: 0'
> P-NGCP-Src-Ip: 117.152.246.21'
> P-NGCP-Src-Port: 5060'
> P-NGCP-Src-Proto: udp'
> P-NGCP-Src-Af: 4'
> P-Sock-Info: udp:117.152.244.201:5060'
> Path: <sip:lb at 127.0.0.1;lr;socket=sip:117.152.244.201:5060>'
> '
>
>
> U 2014/11/13 11:31:08.022006 127.0.0.1:5062 -> 127.0.0.1:5060
> SIP/2.0 100 Trying'
> Via: SIP/2.0/UDP
> 127.0.0.1;branch=z9hG4bK47bc.1cdf78be45dd9f905d8eb2bd0e1c1d1d.0'
> Via: SIP/2.0/UDP 117.152.246.21:5060;rport=5060;branch=z9hG4bK30605341'
> From: <sip:master.sample.edge at edge.xyz-co.com>;tag=as7247830f'
> To: <sip:master.sample.edge at edge.xyz-co.com>'
> Call-ID: 3a004a4f642983335856b04f0b207fda at 117.152.246.21'
> CSeq: 103 REGISTER'
> P-Out-Socket: udp:117.152.244.201:5060'
> P-NGCP-Auth-IP: 117.152.246.21'
> P-NGCP-Auth-UA: FPBX-2.11.0(11.7.0)'
> Server: Sipwise NGCP Proxy 3.X'
> Content-Length: 0'
> '
>
>
> U 2014/11/13 11:31:08.022280 117.152.244.201:5060 -> 117.152.246.21:5060
> SIP/2.0 100 Trying'
> Via: SIP/2.0/UDP 117.152.246.21:5060;rport=5060;branch=z9hG4bK30605341'
> From: <sip:master.sample.edge at edge.xyz-co.com>;tag=as7247830f'
> To: <sip:master.sample.edge at edge.xyz-co.com>'
> Call-ID: 3a004a4f642983335856b04f0b207fda at 117.152.246.21'
> CSeq: 103 REGISTER'
> Server: Sipwise NGCP Proxy 3.X'
> Content-Length: 0'
> '
>
>
> U 2014/11/13 11:31:08.027495 127.0.0.1:5062 -> 127.0.0.1:5060
> SIP/2.0 200 OK'
> Via: SIP/2.0/UDP
> 127.0.0.1;branch=z9hG4bK47bc.1cdf78be45dd9f905d8eb2bd0e1c1d1d.0;rport=5060'
> Via: SIP/2.0/UDP 117.152.246.21:5060;rport=5060;branch=z9hG4bK30605341'
> From: <sip:master.sample.edge at edge.xyz-co.com>;tag=as7247830f'
> To:
> <sip:master.sample.edge at edge.xyz-co.com>;tag=1d24a28a0bded6c40d31e6db8aab9ac6.2bd1'
> Call-ID: 3a004a4f642983335856b04f0b207fda at 117.152.246.21'
> CSeq: 103 REGISTER'
> P-Out-Socket: udp:117.152.244.201:5060'
> P-NGCP-Auth-IP: 117.152.246.21'
> P-NGCP-Auth-UA: FPBX-2.11.0(11.7.0)'
> P-NGCP-Authorization: master.sample.edge'
> P-NGCP-Authorized: 1'
> P-Caller-UUID: e8093f41-b154-4d8b-b14f-2c861c2b50da'
> Contact: <sip:master.sample.edge at 117.152.246.21:5060>;expires=120'
> Server: Sipwise NGCP Proxy 3.X'
> Content-Length: 0'
> '
>
>
> U 2014/11/13 11:31:08.027760 117.152.244.201:5060 -> 117.152.246.21:5060
> SIP/2.0 200 OK'
> Via: SIP/2.0/UDP 117.152.246.21:5060;rport=5060;branch=z9hG4bK30605341'
> From: <sip:master.sample.edge at edge.xyz-co.com>;tag=as7247830f'
> To:
> <sip:master.sample.edge at edge.xyz-co.com>;tag=1d24a28a0bded6c40d31e6db8aab9ac6.2bd1'
> Call-ID: 3a004a4f642983335856b04f0b207fda at 117.152.246.21'
> CSeq: 103 REGISTER'
> Contact: <sip:master.sample.edge at 117.152.246.21:5060>;expires=120'
> Server: Sipwise NGCP Proxy 3.X'
> Content-Length: 0'
> '
>
> root at tx-portal-2:/etc/nginx/sites-enabled# date
> Thu Nov 13 11:40:36 CST 2014
> root at tx-portal-2:/etc/nginx/sites-enabled# mysql -e "select * from
> kamailio.location\G"
> *************************** 1. row ***************************
> id: 4
> username: master.sample.edge
> domain: NULL
> contact: sip:master.sample.edge at 104.152.246.21:5060
> received: NULL
> path: <sip:lb at 127.0.0.1;lr;socket=sip:104.152.244.201:5060>
> expires: 2014-11-13 11:32:13
> q: -1.00
> callid: 3aeb016a20d3b9aa7640366d3b190643 at 104.152.246.21
> cseq: 105
> last_modified: 2014-11-13 11:30:13
> flags: 0
> cflags: 0
> user_agent: FPBX-2.11.0(11.7.0)
> socket: udp:127.0.0.1:5062
> methods: NULL
> ruid: uloc-5464e835-7cf0-1
> reg_id: 0
> instance: NULL
>
>
>
>
>
> ------------------------------------------------------------------------
> *From:* Spce-user [spce-user-bounces at lists.sipwise.com] on behalf of
> Daniel Grotti [dgrotti at sipwise.com]
> *Sent:* Thursday, November 13, 2014 8:34 AM
> *To:* spce-user at lists.sipwise.com
> *Subject:* Re: [Spce-user] sip registration stuck 3.5.16
>
> Hi,
> I don't think this is related to the stale nonce issue.
> Stale nonce issue just stop Asterisk to send subsequent REGISTER
> messages, because it receives a 403.
>
> Please do the following steps:
>
>
> 1. ngrep-sip r (logging REGISTER sessions)
> 2. register your Asterisk first time
> 3. check mysql -e "select * from kamailio.location\G"
>
> 4. Reproduce the the second REGISTER from asterisk
> 5. check mysql -e "select * from kamailio.location\G" - you should see
> 2 entries here.
>
>
> Please share information about REGISTER sessions on point 2 and 4 as
> well as the output of 3 and 5.
>
>
> Daniel
>
>
> P.S.: This is a best-effert mailing list (as all the mailing list), we
> do not provide professional consultancy here. If you are interest to a
> professional solution + support, please consider to buy a Sip:Provider
> PRO. You can contact our sales team any time.
>
>
>
>
>
> On 11/13/2014 04:30 PM, Aziz Palmer wrote:
>> SPCE TEAM - It's still not working - and i need to put this into
>> production very very soon
>>
>> I made the following changes
>> /etc/ngcp-config/templates/etc/kamailio/lb/kamailio.cfg.tt2
>> #!ifdef ENABLE_AUTHCHECK
>> if((status == "401" || status == "407") &&
>> is_present_hf("P-NGCP-Authorization") && !is_present_hf("P-NGCP-Stale"))
>>
>> vim /etc/ngcp-config/templates/etc/kamailio/proxy/kamailio.cfg.tt2
>> case -4:
>> xlog("L_NOTICE", "Authentication
>> failed, stale nonce - [% logreq -%]\n");
>> append_to_reply("P-NGCP-Stale: yes\r\n");
>> break;
>>
>> ------------------------------------------------------------------------
>> *From:* Spce-user [spce-user-bounces at lists.sipwise.com] on behalf of
>> Jeremy Ward [jward01 at gmail.com]
>> *Sent:* Thursday, November 13, 2014 6:08 AM
>> *To:* Theo
>> *Cc:* Spce-user
>> *Subject:* Re: [Spce-user] sip registration stuck 3.5.16
>>
>> I also saw this on 4PSA VoipNOW -- Asterisk 11/12 issue AFAIK.
>>
>> Jeremy D. Ward, CWNE
>> (954) 661-4965
>>
>> On Nov 13, 2014 9:02 AM, "Theo" <axessofficetheo at gmail.com
>> <mailto:axessofficetheo at gmail.com>> wrote:
>>
>> Hi
>>
>> Assuming the stale nonce issue is the problem, I gave the answer
>> to the fix already
>> earlier: http://lists.sipwise.com/pipermail/spce-user/2014-January/005712.html
>>
>> On Thu, Nov 13, 2014 at 3:51 PM, Martin Stix <ms at pluteus.at
>> <mailto:ms at pluteus.at>> wrote:
>>
>> Hi!
>>
>>
>>
>> Also had this issue with older 3CX Version, it was not an
>> issue of spce.
>>
>>
>>
>> regards
>>
>>
>>
>>
>>
>> mit freundlichen Grüßen
>> best regards
>>
>> *Martin Stix*
>>
>> CEO
>> pluteus communication solutions
>> ms at pluteus.at <mailto:ms at pluteus.at>
>>
>> Dampfsägestraße 17
>> 3300 Amstetten
>> Austria
>> tel.: +43 7472 28165 20
>> fax.: +43 7472 28165 22
>>
>>
>>
>> *Von:*Aziz Palmer [mailto:Aziz.Palmer at AirFIBER.com
>> <mailto:Aziz.Palmer at AirFIBER.com>]
>> *Gesendet:* Donnerstag, 13. November 2014 14:39
>> *An:* Theo
>> *Cc:* spce-user at lists.sipwise.com
>> <mailto:spce-user at lists.sipwise.com>
>> *Betreff:* Re: [Spce-user] sip registration stuck 3.5.16
>>
>>
>>
>> Thank you Theo!
>>
>>
>>
>> but what i don't understand if this is the case why wasn't
>> fixed ?
>>
>>
>>
>> what should i be doing instead when having users register to
>> avoid this issue?
>>
>>
>>
>> Is this happening to you also? if so what did you do to fix
>> it? (follow the steps below?)
>>
>>
>>
>> Thank you!
>>
>>
>>
>>
>>
>> ------------------------------------------------------------------------
>>
>> *From:*Theo [axessofficetheo at gmail.com
>> <mailto:axessofficetheo at gmail.com>]
>> *Sent:* Thursday, November 13, 2014 5:30 AM
>> *To:* Aziz Palmer
>> *Cc:* Andreas Granig; spce-user at lists.sipwise.com
>> <mailto:spce-user at lists.sipwise.com>
>> *Subject:* Re: [Spce-user] sip registration stuck 3.5.16
>>
>> Sorry I accidentally replied just to you rather than to the
>> list.:
>>
>>
>>
>> Hi
>>
>>
>>
>> This looks like the stale nonce issue which is an asterisk
>> problem. The workaround has been posted a few times - search
>> for stale nonce and I am sure you'll find it easily
>>
>>
>>
>> Good luck
>>
>> https://ssl.gstatic.com/ui/v1/icons/mail/images/cleardot.gif
>>
>>
>>
>>
>>
>>
>> https://mail.google.com/mail/u/0/images/cleardot.gif
>>
>>
>>
>>
>> https://mail.google.com/mail/u/0/images/cleardot.gif
>>
>> https://mail.google.com/mail/u/0/images/cleardot.gif
>>
>> to Aziz
>>
>> https://mail.google.com/mail/u/0/images/cleardot.gif
>>
>> It would be this one:
>>
>>
>>
>> http://lists.sipwise.com/pipermail/spce-user/2014-January/005712.html
>>
>>
>>
>> On Thu, Nov 13, 2014 at 3:00 PM, Aziz Palmer
>> <Aziz.Palmer at airfiber.com <mailto:Aziz.Palmer at airfiber.com>>
>> wrote:
>>
>> kamailio.location
>> what command do I need to execute to provide this
>> information?
>>
>>
>> kamailio-proxy.log
>>
>> Nov 13 06:49:36 tx-portal-2 proxy[22474]: NOTICE:
>> <script>: Authentication failed, stale nonce -
>> R=sip:sipwise.xyz..com
>> ID=7233034d51f47c1a7ca56eb2353030ae at 104.34.42.10
>> <mailto:7233034d51f47c1a7ca56eb2353030ae at 104.34.42.10>
>> Nov 13 06:49:36 tx-portal-2 proxy[22473]: NOTICE:
>> <script>: New request on proxy - M=REGISTER
>> R=sip:sipwise.xyz..com
>> F=sip:master.sample.edge at sipwise.xyz..com
>> T=sip:master.sample.edge at sipwise.xyz..com
>> IP=104.34.42.10:5060
>> <http://104.34.42.10:5060>(127.0.0.1:5060
>> <http://127.0.0.1:5060>)
>> ID=7233034d51f47c1a7ca56eb2353030ae at 104.34.42.10
>> <mailto:7233034d51f47c1a7ca56eb2353030ae at 104.34.42.10>
>> Nov 13 06:49:36 tx-portal-2 proxy[22473]: WARNING:
>> app_lua [app_lua_sr.c:100]: lua_sr_log(): lost database
>> connection. Reconnecting
>> Nov 13 06:49:36 tx-portal-2 proxy[22473]: NOTICE:
>> <script>: Contacts successfully updated, expires in 120s
>> - R=sip:sipwise.xyz..com
>> ID=7233034d51f47c1a7ca56eb2353030ae at 104.34.42.10
>> <mailto:7233034d51f47c1a7ca56eb2353030ae at 104.34.42.10>
>> Nov 13 06:51:21 tx-portal-2 proxy[22480]: NOTICE:
>> <script>: New request on proxy - M=REGISTER
>> R=sip:sipwise.xyz..com
>> F=sip:master.sample.edge at sipwise.xyz..com
>> T=sip:master.sample.edge at sipwise.xyz..com
>> IP=104.34.42.10:5060
>> <http://104.34.42.10:5060>(127.0.0.1:5060
>> <http://127.0.0.1:5060>)
>> ID=7233034d51f47c1a7ca56eb2353030ae at 104.34.42.10
>> <mailto:7233034d51f47c1a7ca56eb2353030ae at 104.34.42.10>
>> Nov 13 06:51:21 tx-portal-2 proxy[22480]: WARNING:
>> app_lua [app_lua_sr.c:100]: lua_sr_log(): lost database
>> connection. Reconnecting
>> Nov 13 06:51:21 tx-portal-2 proxy[22480]: NOTICE:
>> <script>: Contacts successfully updated, expires in 120s
>> - R=sip:sipwise.xyz..com
>> ID=7233034d51f47c1a7ca56eb2353030ae at 104.34.42.10
>> <mailto:7233034d51f47c1a7ca56eb2353030ae at 104.34.42.10>
>> Nov 13 06:53:06 tx-portal-2 proxy[22475]: NOTICE:
>> <script>: New request on proxy - M=REGISTER
>> R=sip:sipwise.xyz..com
>> F=sip:master.sample.edge at sipwise.xyz..com
>> T=sip:master.sample.edge at sipwise.xyz..com
>> IP=104.34.42.10:5060
>> <http://104.34.42.10:5060>(127.0.0.1:5060
>> <http://127.0.0.1:5060>)
>> ID=7233034d51f47c1a7ca56eb2353030ae at 104.34.42.10
>> <mailto:7233034d51f47c1a7ca56eb2353030ae at 104.34.42.10>
>> Nov 13 06:53:06 tx-portal-2 proxy[22475]: WARNING:
>> app_lua [app_lua_sr.c:100]: lua_sr_log(): lost database
>> connection. Reconnecting
>> Nov 13 06:53:06 tx-portal-2 proxy[22475]: NOTICE:
>> <script>: Contacts successfully updated, expires in 120s
>> - R=sip:sipwise.xyz..com
>> ID=7233034d51f47c1a7ca56eb2353030ae at 104.34.42.10
>> <mailto:7233034d51f47c1a7ca56eb2353030ae at 104.34.42.10>
>>
>>
>>
>>
>> what does this mean "WARNING: app_lua [app_lua_sr.c:100]:
>> lua_sr_log(): lost database connection. Reconnecting"?
>>
>>
>>
>> ________________________________________
>> From: Spce-user [spce-user-bounces at lists.sipwise.com
>> <mailto:spce-user-bounces at lists.sipwise.com>] on behalf
>> of Andreas Granig [agranig at sipwise.com
>> <mailto:agranig at sipwise.com>]
>> Sent: Thursday, November 13, 2014 1:26 AM
>> To: spce-user at lists.sipwise.com
>> <mailto:spce-user at lists.sipwise.com>
>> Subject: Re: [Spce-user] sip registration stuck 3.5.16
>>
>>
>> Hi,
>>
>> It's most likely not a bug of the system, rather than a
>> problem with
>> your clients registering on said system. I risk to say
>> that because the
>> registrar is based on Kamailio, which is serving dozens
>> of millions of
>> SIP devices out there, so it would be a huge surprise for
>> it not to work
>> correctly.
>>
>> The only way to find out what the REAL issue is for you
>> to send an
>> example entry in the kamailio.location table of the DB,
>> along with a
>> full network trace of this client trying to register on
>> the system, and
>> also the kamailio-proxy.log file.
>>
>> Andreas
>>
>> On 11/13/2014 06:47 AM, Aziz Palmer wrote:
>> > thats not the issue - the problem is when you
>> RE-register a sip trunk it
>> > will stop updating sipwise. in order to fix that you
>> need to manually go
>> > into the subscriber and delete the registration. it
>> will not delete but
>> > instead a new registration will appear.
>> >
>> >
>> > SPCE - are you aware of this bug (its a serous issue -
>> since it gives
>> > the admins a lot of manual work/tech support calls) I
>> would like to put
>> > this this into partial production but can't - please help?
>> >
>> > Thanks!
>> >
>> ------------------------------------------------------------------------
>> > *From:* Raúl Alexis Betancor Santana
>> [rabs at dimension-virtual.com
>> <mailto:rabs at dimension-virtual.com>]
>> > *Sent:* Wednesday, November 12, 2014 1:54 PM
>> > *To:* Aziz Palmer
>> > *Subject:* Re: sip registration stuck 3.5.16
>> >
>> > 3600 secs ... 1 h ... it's default time on the config.xml
>> > kamailio.proxy.default_expire option ... you could
>> change it ... or set
>> > it on the web interface at domain-level or user-level
>> if you prefer, and
>> > as far as you don't touched the .cfg's ... they expire.
>> >
>> >
>> ------------------------------------------------------------------------
>> > *De: *"Aziz Palmer" <Aziz.Palmer at AirFIBER.com
>> <mailto:Aziz.Palmer at AirFIBER.com>>
>> > *Para: *"Raúl Alexis Betancor Santana"
>> <rabs at dimension-virtual.com
>> <mailto:rabs at dimension-virtual.com>>,
>> > spce-user at lists.sipwise.com
>> <mailto:spce-user at lists.sipwise.com>
>> > *Enviados: *Miércoles, 12 de Noviembre 2014 21:17:53
>> > *Asunto: *RE: sip registration stuck 3.5.16
>> >
>> > they are not auto-expiring (I wish they were)
>> >
>> > if they are - taking a extremely long time
>> >
>> ------------------------------------------------------------------------
>> > *From:* Spce-user [spce-user-bounces at lists.sipwise.com
>> <mailto:spce-user-bounces at lists.sipwise.com>] on behalf of
>> > Raúl Alexis Betancor Santana
>> [rabs at dimension-virtual.com
>> <mailto:rabs at dimension-virtual.com>]
>> > *Sent:* Wednesday, November 12, 2014 1:04 PM
>> > *To:* spce-user at lists.sipwise.com
>> <mailto:spce-user at lists.sipwise.com>
>> > *Subject:* Re: [Spce-user] sip registration stuck 3.5.16
>> >
>> >
>> > Why did you whant to remove the old register? ...
>> location entries
>> > auto-expire, so you don't have to worry about them.
>> >
>> >
>> ------------------------------------------------------------------------
>> > *De: *"Aziz Palmer" <Aziz.Palmer at AirFIBER.com
>> <mailto:Aziz.Palmer at AirFIBER.com>>
>> > *Para: *spce-user at lists.sipwise.com
>> <mailto:spce-user at lists.sipwise.com>
>> > *Enviados: *Miércoles, 12 de Noviembre 2014 20:47:13
>> > *Asunto: *[Spce-user] sip registration stuck 3.5.16
>> >
>> > I hate to ask again but this is turning into a real
>> issue - the
>> > "registered devices" are not automatically being
>> removed and when trying
>> > to manually delete them, nothing happens.
>> >
>> > Can i set a timer on how long these orphan registered
>> devices stay part
>> > of sipwise?
>> >
>> > how can i delete these devices without having to issue
>> the below command
>> > - I would like to delete specific devices and not all
>> of them
>> >
>> > mysql kamailio -e "delete from location"
>> > /etc/init.d/kamailio-proxy restart
>> >
>> >
>> > Thanks again,
>> > Aziz
>> >
>> >
>> ------------------------------------------------------------------------
>> > *From:* Spce-user [spce-user-bounces at lists.sipwise.com
>> <mailto:spce-user-bounces at lists.sipwise.com>] on behalf of
>> > Aziz Palmer [Aziz.Palmer at AirFIBER.com]
>> > *Sent:* Tuesday, November 11, 2014 12:15 PM
>> > *To:* spce-user at lists.sipwise.com
>> <mailto:spce-user at lists.sipwise.com>
>> > *Subject:* [Spce-user] sip registration stuck 5.3.16
>> >
>> > Hello SPCE Team,
>> > here is what appears to be a bug
>> >
>> > I enter sip registration settings into asterisk,
>> registers fine with
>> > sipwise. Then I make a change within the sip trunk
>> settings of asterisk
>> > and apply the new settings. Then previous sip
>> registration gets stuck;
>> > meaning within sipwise 2 registrations appear (old &
>> new). When i try to
>> > delete the old one, it stays stuck. The only way i
>> discovered to be able
>> > to remove the old registration is by issuing this
>> command, then i can
>> > delete the registration.
>> >
>> > /etc/init.d/kamailio-proxy restart
>> >
>> > what additional information can i provide to have your
>> team troubleshoot
>> > this issue?
>> >
>> > Thank you,
>> > Anees
>> >
>> > _______________________________________________
>> > Spce-user mailing list
>> > Spce-user at lists.sipwise.com
>> <mailto:Spce-user at lists.sipwise.com>
>> > https://lists.sipwise.com/listinfo/spce-user
>> >
>> >
>> >
>> >
>> > _______________________________________________
>> > Spce-user mailing list
>> > Spce-user at lists.sipwise.com
>> <mailto:Spce-user at lists.sipwise.com>
>> > https://lists.sipwise.com/listinfo/spce-user
>> >
>> _______________________________________________
>> Spce-user mailing list
>> Spce-user at lists.sipwise.com
>> <mailto:Spce-user at lists.sipwise.com>
>> https://lists.sipwise.com/listinfo/spce-user
>> _______________________________________________
>> Spce-user mailing list
>> Spce-user at lists.sipwise.com
>> <mailto:Spce-user at lists.sipwise.com>
>> https://lists.sipwise.com/listinfo/spce-user
>>
>>
>>
>>
>>
>> _______________________________________________
>> Spce-user mailing list
>> Spce-user at lists.sipwise.com <mailto:Spce-user at lists.sipwise.com>
>> https://lists.sipwise.com/listinfo/spce-user
>>
>>
>>
>> _______________________________________________
>> Spce-user mailing list
>> Spce-user at lists.sipwise.com
>> https://lists.sipwise.com/listinfo/spce-user
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20141114/433ad4fe/attachment.html>
More information about the Spce-user
mailing list