[Spce-user] No ACK from Sipwise after 200 OK
Abel Alejandro
aalejandro at alliedtechnologygrouppr.com
Thu Jun 30 03:47:46 EDT 2016
I just did a brand new installation of debian 8 + mr4.4.1 on a different
physical server, restored from backup and still same issue.
If anyone has any tips or idea how to troubleshoot this further that would
be appreciated.
Thanks.
On Tue, Jun 28, 2016 at 4:01 PM, sebastian rojo <arpagon+sipwise at gmail.com>
wrote:
> This is my case.
>
> Huawei SoftX3000 (Peer) (extra_socket and extra & rtp_extra ) ----> SPCE
> -----> Asterisk 11 (Suscriber)
>
> Asterisk Drop the call in 8 seconds too
>
>
>
> On Fri, Jun 24, 2016 at 5:37 PM Abel Alejandro <
> aalejandro at alliedtechnologygrouppr.com> wrote:
>
>> Sebastian,
>>
>> Does this causes intermittent issues for you? Like dropped calls within 8
>> seconds, if yes did you have a workaround?
>>
>> I getting headaches with a Cisco-SIPGateway/IOS-12.x and sometimes it
>> drops the call and the only thing weird I can find is those delayed ACK's.
>>
>>
>>
>> On Thu, Jun 23, 2016 at 2:18 PM, sebastian rojo <
>> arpagon+sipwise at gmail.com> wrote:
>>
>>> Hello,
>>>
>>> I see the same issue in my SPCE.
>>>
>>> Version: System installed. NGCP version mr4.4.1 on 2016-06-21 21:22:58
>>>
>>>
>>> I take captures. in this mode.
>>>
>>> eth1 (peer): tcpdump -i eth1 -s0 -w sip_20160623_1466702965_une.cap
>>> eth0 (suscriber): sudo tcpdump -i eth0 -s0 -w
>>> sip_20160623_1466702973_lan.cap
>>> and (endpoint): sip_20160623_1466702995_cliente.cap
>>>
>>> And Merge all to see the problem.
>>>
>>> This the result.
>>>
>>> [image: Wireshark · Call Flow · compare_481.png]
>>>
>>>
>>>
>>> On Thu, Jun 23, 2016 at 12:01 PM, Abel Alejandro <
>>> aalejandro at alliedtechnologygrouppr.com> wrote:
>>>
>>>> Hello,
>>>>
>>>> I took the capture using the following command, let me know if this is
>>>> enough:
>>>>
>>>> tcpdump -i any port 5060 or port 5080 or port 5061 or port 5062 -w
>>>> test2.pcap
>>>>
>>>> I sent you the pcap privately to you since it has other calls and I do
>>>> not know how to filter them.
>>>>
>>>>
>>>>
>>>>
>>>> On Thu, Jun 23, 2016 at 10:05 AM, Daniel Grotti <dgrotti at sipwise.com>
>>>> wrote:
>>>>
>>>>> capture would help yes.
>>>>> * Daniel Grotti *
>>>>> Head of Customer Support
>>>>>
>>>>> Sipwise GmbH <http://www.sipwise.com> , Campus 21/Europaring F15
>>>>> AT-2345 Brunn am Gebirge
>>>>>
>>>>> Phone: +43(0)1 301 2032 <callto:+4313012032>
>>>>> Email: dgrotti at sipwise.com
>>>>> Website: www.sipwise.com
>>>>>
>>>>> Particulars according Austrian Companies Code paragraph 14
>>>>> "Sipwise GmbH" - Europaring F15 - 2345 Brunn am Gebirge
>>>>> FN:305595f, Commercial Court Vienna, ATU64002206
>>>>> On 06/23/2016 03:59 PM, Abel Alejandro wrote:
>>>>>
>>>>> Hello!
>>>>>
>>>>> I am searching using "zgrep C5A0749D at 10.246.9.8
>>>>> kamailio-proxy.log-20160622.gz" if there is a better way please let me
>>>>> know.
>>>>>
>>>>> Heres what I got around that time. I think there is a missed OK
>>>>> reaching the PROXY from the LB. However this is only accurate to the
>>>>> second, does this help? If not I will see if I can take a capture of the LB
>>>>> <> PROXY traffic and get milisecond timestamps.
>>>>>
>>>>>
>>>>> Jun 22 18:20:05 sip proxy[3785]: NOTICE: <script>: Appending P-D-URI
>>>>> 'sip:127.0.0.1:5060;lr' - R=sip:17877050555 at 196.12.166.251:5060 ID=
>>>>> C5A0749D at 10.246.9.8 UA='<null>'
>>>>> Jun 22 18:20:05 sip proxy[3785]: NOTICE: <script>: Forcing request via
>>>>> B2BUA 'sip:127.0.0.1:5080' - R=sip:17877050555 at 196.12.166.251:5060 ID=
>>>>> C5A0749D at 10.246.9.8 UA='<null>'
>>>>> Jun 22 18:20:05 sip proxy[3785]: NOTICE: <script>: Request leaving
>>>>> server, D-URI='sip:127.0.0.1:5080' - R=
>>>>> sip:17877050555 at 196.12.166.251:5060 ID=C5A0749D at 10.246.9.8 UA='<null>'
>>>>> Jun 22 18:20:05 sip proxy[3777]: NOTICE: <script>: NAT-Reply - S=100 -
>>>>> Connecting M=INVITE IP=196.12.170.244:5060 (127.0.0.1:5080) ID=
>>>>> C5A0749D at 10.246.9.8 UA='<null>'
>>>>> Jun 22 18:20:06 sip proxy[3797]: NOTICE: <script>: NAT-Reply - S=200 -
>>>>> OK M=INVITE IP=196.12.170.244:5060 (127.0.0.1:5080) ID=
>>>>> C5A0749D at 10.246.9.8 UA='<null>'
>>>>> Jun 22 18:20:06 sip proxy[3788]: NOTICE: <script>: New request on
>>>>> proxy - M=ACK R=sip:127.0.0.1:5080;prxroute=1 F=
>>>>> <http://sip:7875868313@196.12.170.244:5060>
>>>>> sip:7875868313 at 196.12.170.244:5060 T=
>>>>> sip:7877050555 at 192.254.110.41:5060 IP=196.12.170.244:5060 (
>>>>> 127.0.0.1:5060) ID=C5A0749D at 10.246.9.8 UA='<null>'
>>>>> Jun 22 18:20:06 sip proxy[3779]: NOTICE: <script>: NAT-Reply - S=200 -
>>>>> OK M=INVITE IP=196.12.170.244:5060 (127.0.0.1:5080) ID=
>>>>> C5A0749D at 10.246.9.8 UA='<null>'
>>>>> Jun 22 18:20:06 sip proxy[3794]: NOTICE: <script>: New request on
>>>>> proxy - M=ACK R=sip:127.0.0.1:5080;prxroute=1 F=
>>>>> <http://sip:7875868313@196.12.170.244:5060>
>>>>> sip:7875868313 at 196.12.170.244:5060 T=
>>>>> sip:7877050555 at 192.254.110.41:5060 IP=196.12.170.244:5060 (
>>>>> 127.0.0.1:5060) ID=C5A0749D at 10.246.9.8 UA='<null>'
>>>>> Jun 22 18:20:12 sip proxy[3788]: NOTICE: <script>: New request on
>>>>> proxy - M=BYE R=sip:127.0.0.1:5080;prxroute=1 F=
>>>>> <http://sip:7875868313@196.12.170.244:5060>
>>>>> sip:7875868313 at 196.12.170.244:5060 T=
>>>>> sip:7877050555 at 192.254.110.41:5060 IP=196.12.170.244:5060 (
>>>>> 127.0.0.1:5060) ID=C5A0749D at 10.246.9.8 UA='<null>'
>>>>> Jun 22 18:20:12 sip proxy[3779]: NOTICE: <script>: NAT-Reply - S=200 -
>>>>> OK M=BYE IP=196.12.170.244:5060 (127.0.0.1:5080) ID=
>>>>> C5A0749D at 10.246.9.8 UA='<null>'
>>>>> root at sip:/var/log/ngcp/old#
>>>>>
>>>>> On Thu, Jun 23, 2016 at 9:46 AM, Daniel Grotti <dgrotti at sipwise.com>
>>>>> wrote:
>>>>>
>>>>>> Wait a minute,
>>>>>> the problem is the 200 OK in delay then.
>>>>>> Sorry, but I cannot see the full proxy.log.
>>>>>> In LB log I see the 200 OK forwarded to sems following Via header:
>>>>>>
>>>>>> Jun 22 18:20:06 sip lb[2909]: NOTICE: <script>: Reply from Outbound -
>>>>>> S=200 - OK M=INVITE IP=udp:196.12.166.251:5060
>>>>>> ID=C5A0749D at 10.246.9.8_b2b-1 UA='<null>'
>>>>>> Jun 22 18:20:06 sip lb[2909]: NOTICE: <script>: Sending reply,
>>>>>> fs='udp:127.0.0.1:5060' - ID=C5A0749D at 10.246.9.8_b2b-1 UA='<null>'
>>>>>>
>>>>>> BUt then not reply from Inbound from proxy 5062:
>>>>>>
>>>>>> Jun 22 18:20:06 sip lb[2907]: NOTICE: <script>: Reply from Outbound -
>>>>>> S=200 - OK M=INVITE IP=udp:196.12.166.251:5060
>>>>>> ID=C5A0749D at 10.246.9.8_b2b-1 UA='<null>'
>>>>>> Jun 22 18:20:06 sip lb[2907]: NOTICE: <script>: Sending reply,
>>>>>> fs='udp:127.0.0.1:5060' - ID=C5A0749D at 10.246.9.8_b2b-1 UA='<null>'
>>>>>>
>>>>>> The same here, no reply back from proxy:
>>>>>>
>>>>>>
>>>>>> Jun 22 18:20:06 sip lb[2912]: NOTICE: <script>: Reply from Outbound -
>>>>>> S=200 - OK M=INVITE IP=udp:196.12.166.251:5060
>>>>>> ID=C5A0749D at 10.246.9.8_b2b-1 UA='<null>'
>>>>>> Jun 22 18:20:06 sip lb[2912]: NOTICE: <script>: Sending reply,
>>>>>> fs='udp:127.0.0.1:5060' - ID=C5A0749D at 10.246.9.8_b2b-1 UA='<null>'
>>>>>> Jun 22 18:20:06 sip lb[2920]: NOTICE: <script>: Reply from Inbound -
>>>>>> S=200 - OK M=INVITE IP=udp:127.0.0.1:5062 ID= <C5A0749D at 10.246.9.8>
>>>>>> C5A0749D at 10.246.9.8 UA='<null>'
>>>>>>
>>>>>> Here I see "Reply from Inbound".
>>>>>> Please check the full proxy log and the 200OK there.
>>>>>>
>>>>>>
>>>>>>
>>>>>> * Daniel Grotti *
>>>>>> Head of Customer Support
>>>>>>
>>>>>> Sipwise GmbH <http://www.sipwise.com> , Campus 21/Europaring F15
>>>>>> AT-2345 Brunn am Gebirge
>>>>>>
>>>>>> Phone: +43(0)1 301 2032 <callto:+4313012032>
>>>>>> Email: dgrotti at sipwise.com
>>>>>> Website: www.sipwise.com
>>>>>>
>>>>>> Particulars according Austrian Companies Code paragraph 14
>>>>>> "Sipwise GmbH" - Europaring F15 - 2345 Brunn am Gebirge
>>>>>> FN:305595f, Commercial Court Vienna, ATU64002206
>>>>>> On 06/23/2016 03:09 PM, Abel Alejandro wrote:
>>>>>>
>>>>>> Daniel,
>>>>>>
>>>>>> I have checked 4 endpoints so far, different from 196.12.166.251, and
>>>>>> same issue.
>>>>>>
>>>>>> The ack you see on the logs being generated, is actually almost half
>>>>>> a second late, I am not a sip expert but I think maybe its hitting some
>>>>>> kind of timeout sometimes.
>>>>>>
>>>>>> If I do a capture on the server (sipwise) itself, I see the same
>>>>>> thing, ACK being generated almost 500 ms later.
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Thu, Jun 23, 2016 at 8:49 AM, Daniel Grotti <
>>>>>> <dgrotti at sipwise.com>dgrotti at sipwise.com> wrote:
>>>>>>
>>>>>>> Hi,
>>>>>>> it's not normal to receive multiple 200 OK.
>>>>>>> Looks like for some reason the ACK didn't receive the callee at
>>>>>>> <sip:17877050555 at 196.12.166.251:5060>
>>>>>>> sip:17877050555 at 196.12.166.251:5060
>>>>>>>
>>>>>>> Question is: are you sure that you can reach IP 196.12.166.251:5060
>>>>>>> <sip:17877050555 at 196.12.166.251:5060> from the socket
>>>>>>> udp:192.254.110.41:5060 (the one you are using to send out the ACK)
>>>>>>> ?
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Relaying request, du='<null>', fs='udp:192.254.110.41:5060' - R=
>>>>>>> sip:17877050555 at 196.12.166.251:5060 ID=C5A0749D at 10.246.9.8_b2b-1
>>>>>>> UA='<null>'
>>>>>>>
>>>>>>>
>>>>>>> Maybe this is why ACK cannot reach the callee.
>>>>>>>
>>>>>>>
>>>>>>> * Daniel Grotti *
>>>>>>> Head of Customer Support
>>>>>>>
>>>>>>> Sipwise GmbH <http://www.sipwise.com> , Campus 21/Europaring F15
>>>>>>> AT-2345 Brunn am Gebirge
>>>>>>>
>>>>>>> Phone: +43(0)1 301 2032 <callto:+4313012032>
>>>>>>> Email: dgrotti at sipwise.com
>>>>>>> Website: www.sipwise.com
>>>>>>>
>>>>>>> Particulars according Austrian Companies Code paragraph 14
>>>>>>> "Sipwise GmbH" - Europaring F15 - 2345 Brunn am Gebirge
>>>>>>> FN:305595f, Commercial Court Vienna, ATU64002206
>>>>>>> On 06/23/2016 02:46 PM, Abel Alejandro wrote:
>>>>>>>
>>>>>>> Hey Daniel,
>>>>>>>
>>>>>>> So its normal to have those 3 OK at first without an ACK missing and
>>>>>>> the sipwise just takes a little while to reply back? Maybe I closed the
>>>>>>> other call too fast and thats why I didnt see it. (the voipmonitor is
>>>>>>> running on the sipwise itself)
>>>>>>> Those are this one right?
>>>>>>>
>>>>>>> Jun 22 18:20:05 sip lb[2907]: NOTICE: <script>: Reply from Outbound
>>>>>>> - S=100 - Trying M=INVITE IP=udp:196.12.166.251:5060
>>>>>>> <ID=C5A0749D at 10.246.9.8_b2b-1>ID=C5A0749D at 10.246.9.8_b2b-1
>>>>>>> UA='<null>'
>>>>>>> Jun 22 18:20:05 sip lb[2907]: NOTICE: <script>: Sending reply,
>>>>>>> fs='udp:127.0.0.1:5060' - ID=C5A0749D at 10.246.9.8_b2b-1 UA='<null>'
>>>>>>> Jun 22 18:20:06 sip lb[2909]: NOTICE: <script>: Reply from Outbound
>>>>>>> - S=200 - OK M=INVITE IP=udp:196.12.166.251:5060
>>>>>>> <ID=C5A0749D at 10.246.9.8_b2b-1>ID=C5A0749D at 10.246.9.8_b2b-1
>>>>>>> UA='<null>'
>>>>>>> Jun 22 18:20:06 sip lb[2909]: NOTICE: <script>: Sending reply,
>>>>>>> fs='udp:127.0.0.1:5060' - ID=C5A0749D at 10.246.9.8_b2b-1 UA='<null>'
>>>>>>> Jun 22 18:20:06 sip lb[2907]: NOTICE: <script>: Reply from Outbound
>>>>>>> - S=200 - OK M=INVITE IP=udp:196.12.166.251:5060
>>>>>>> <ID=C5A0749D at 10.246.9.8_b2b-1>ID=C5A0749D at 10.246.9.8_b2b-1
>>>>>>> UA='<null>'
>>>>>>> Jun 22 18:20:06 sip lb[2907]: NOTICE: <script>: Sending reply,
>>>>>>> fs='udp:127.0.0.1:5060' - ID=C5A0749D at 10.246.9.8_b2b-1 UA='<null>'
>>>>>>> Jun 22 18:20:06 sip lb[2912]: NOTICE: <script>: Reply from Outbound
>>>>>>> - S=200 - OK M=INVITE IP=udp:196.12.166.251:5060
>>>>>>> <ID=C5A0749D at 10.246.9.8_b2b-1>ID=C5A0749D at 10.246.9.8_b2b-1
>>>>>>> UA='<null>'
>>>>>>> Jun 22 18:20:06 sip lb[2912]: NOTICE: <script>: Sending reply,
>>>>>>> fs='udp:127.0.0.1:5060' - ID=C5A0749D at 10.246.9.8_b2b-1 UA='<null>'
>>>>>>>
>>>>>>>
>>>>>>> I just made another call and the left it running for a few more
>>>>>>> seconds and I see the OK, it just takes a bit, it happens on every call it
>>>>>>> seems. Heres the picture:
>>>>>>>
>>>>>>> https://dl.dropboxusercontent.com/u/41014173/anothercall.PNG
>>>>>>>
>>>>>>> So in conclusion, all is normal and ok?
>>>>>>>
>>>>>>> Thanks!
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Thu, Jun 23, 2016 at 8:20 AM, Daniel Grotti <
>>>>>>> <dgrotti at sipwise.com>dgrotti at sipwise.com> wrote:
>>>>>>>
>>>>>>>> The ACK looks ok, and it is sent out here:
>>>>>>>>
>>>>>>>> Jun 22 18:20:06 sip lb[2922]: NOTICE: <script>: New request on lb -
>>>>>>>> M=ACK R= <sip:17877050555 at 196.12.166.251:5060>
>>>>>>>> sip:17877050555 at 196.12.166.251:5060 F=
>>>>>>>> sip:17875868313 at sip.fusetelecom.com T=
>>>>>>>> sip:17877050555 at sip.fusetelecom.com IP=udp:127.0.0.1:5080
>>>>>>>> ID=C5A0749D at 10.246.9.8_b2b-1 UA='<null>'
>>>>>>>> Jun 22 18:20:06 sip lb[2922]: NOTICE: <script>: Relaying request,
>>>>>>>> du='<null>', fs='udp:192.254.110.41:5060' - R=
>>>>>>>> sip:17877050555 at 196.12.166.251:5060 ID=C5A0749D at 10.246.9.8_b2b-1
>>>>>>>> UA='<null>'
>>>>>>>>
>>>>>>>>
>>>>>>>> so should go to <sip:17877050555 at 196.12.166.251:5060>
>>>>>>>> sip:17877050555 at 196.12.166.251:5060.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> * Daniel Grotti *
>>>>>>>> Head of Customer Support
>>>>>>>>
>>>>>>>> Sipwise GmbH <http://www.sipwise.com> , Campus 21/Europaring F15
>>>>>>>> AT-2345 Brunn am Gebirge
>>>>>>>>
>>>>>>>> Phone: +43(0)1 301 2032 <callto:+4313012032>
>>>>>>>> Email: <dgrotti at sipwise.com>dgrotti at sipwise.com
>>>>>>>> Website: <http://www.sipwise.com>www.sipwise.com
>>>>>>>>
>>>>>>>> Particulars according Austrian Companies Code paragraph 14
>>>>>>>> "Sipwise GmbH" - Europaring F15 - 2345 Brunn am Gebirge
>>>>>>>> FN:305595f, Commercial Court Vienna, ATU64002206
>>>>>>>> On 06/23/2016 02:00 PM, Abel Alejandro wrote:
>>>>>>>>
>>>>>>>> Hello,
>>>>>>>>
>>>>>>>> This is the 200 OK sent from sipwise to one leg
>>>>>>>>
>>>>>>>> SIP/2.0 200 OK
>>>>>>>> Record-Route: <sip:127.0.0.1:5062
>>>>>>>> ;lr=on;ftag=10.246.9.8+1+4e9d19+990c8790;did=dce.2ea;ice_caller=strip;ice_callee=strip;aset=50;rtpprx=yes;vsf=cmVrY3ZlX1B+RDpvbXsmFyMHHWomPikxNCEOAyQfbHo6Jjg->
>>>>>>>> Record-Route:
>>>>>>>> <sip:127.0.0.1;r2=on;lr=on;ftag=10.246.9.8+1+4e9d19+990c8790;ngcplb=yes;socket=udp:
>>>>>>>> 192.254.110.41:5060>
>>>>>>>> Record-Route:
>>>>>>>> <sip:192.254.110.41;r2=on;lr=on;ftag=10.246.9.8+1+4e9d19+990c8790;ngcplb=yes;socket=udp:
>>>>>>>> 192.254.110.41:5060>
>>>>>>>> Via: SIP/2.0/UDP 196.12.170.244:5060
>>>>>>>> ;rport=5060;branch=z9hG4bKqlj2ve20bgda0vnsfjg0.1
>>>>>>>> Call-ID: <C5A0749D at 10.246.9.8>C5A0749D at 10.246.9.8
>>>>>>>> From: < <http://sip:7875868313@196.12.170.244:5060>
>>>>>>>> sip:7875868313 at 196.12.170.244:5060
>>>>>>>> >;tag=10.246.9.8+1+4e9d19+990c8790;isup-oli=62
>>>>>>>> To: < <http://sip:7877050555@192.254.110.41:5060>
>>>>>>>> sip:7877050555 at 192.254.110.41:5060
>>>>>>>> >;tag=15F8E190-576B0F15000899A3-8F0C5700
>>>>>>>> CSeq: 579051710 INVITE
>>>>>>>> Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, SUBSCRIBE, NOTIFY,
>>>>>>>> PUBLISH, MESSAGE
>>>>>>>> Supported: replaces
>>>>>>>> Content-Type: application/sdp
>>>>>>>> Content-Length: 285
>>>>>>>> Contact:
>>>>>>>> <sip:ngcp-lb at 192.254.110.41:5060;ngcpct=7369703a3132372e302e302e313a353038303b707278726f7574653d31>
>>>>>>>> <sip:ngcp-lb at 192.254.110.41:5060;ngcpct=7369703a3132372e302e302e313a353038303b707278726f7574653d31>
>>>>>>>> <sip:ngcp-lb at 192.254.110.41:5060;ngcpct=7369703a3132372e302e302e313a353038303b707278726f7574653d31>
>>>>>>>>
>>>>>>>> v=0
>>>>>>>> o=root 223199344 223199344 IN IP4 192.254.110.41
>>>>>>>> s=Asterisk PBX 13.8.0
>>>>>>>> c=IN IP4 192.254.110.41
>>>>>>>> t=0 0
>>>>>>>> m=audio 30768 RTP/AVP 0 101
>>>>>>>> a=rtpmap:0 PCMU/8000
>>>>>>>> a=rtpmap:101 telephone-event/8000
>>>>>>>> a=fmtp:101 0-16
>>>>>>>> a=ptime:20
>>>>>>>> a=maxptime:150
>>>>>>>> a=direction:both
>>>>>>>> a=sendrecv
>>>>>>>> a=rtcp:30769
>>>>>>>>
>>>>>>>>
>>>>>>>> And this is the ACK from the leg to the sipwise
>>>>>>>>
>>>>>>>>
>>>>>>>> ACK
>>>>>>>> <sip:ngcp-lb at 192.254.110.41:5060;ngcpct=7369703a3132372e302e302e313a353038303b707278726f7574653d31>
>>>>>>>> sip:ngcp-lb at 192.254.110.41:5060;ngcpct=7369703a3132372e302e302e313a353038303b707278726f7574653d31
>>>>>>>> SIP/2.0
>>>>>>>> Via: SIP/2.0/UDP 196.12.170.244:5060
>>>>>>>> ;branch=z9hG4bKnujd48008gpka18537c0.1
>>>>>>>> Allow-Events: message-summary, refer, dialog, line-seize, presence,
>>>>>>>> call-info, as-feature-event, calling-name
>>>>>>>> Max-Forwards: 69
>>>>>>>> Call-ID: <C5A0749D at 10.246.9.8>C5A0749D at 10.246.9.8
>>>>>>>> From: < <http://sip:7875868313@196.12.170.244:5060>
>>>>>>>> sip:7875868313 at 196.12.170.244:5060
>>>>>>>> >;tag=10.246.9.8+1+4e9d19+990c8790;isup-oli=62
>>>>>>>> To: < <http://sip:7877050555@192.254.110.41:5060>
>>>>>>>> sip:7877050555 at 192.254.110.41:5060
>>>>>>>> >;tag=15F8E190-576B0F15000899A3-8F0C5700
>>>>>>>> CSeq: 579051710 ACK
>>>>>>>> Contact: <sip:7875868313 at 196.12.170.244:5060;transport=udp>
>>>>>>>> <sip:7875868313 at 196.12.170.244:5060;transport=udp>
>>>>>>>> <sip:7875868313 at 196.12.170.244:5060;transport=udp>;isup-oli=62
>>>>>>>> Organization: MetaSwitch
>>>>>>>> Content-Length: 0
>>>>>>>> Route:
>>>>>>>> <sip:192.254.110.41;r2=on;lr=on;ftag=10.246.9.8+1+4e9d19+990c8790;ngcplb=yes;socket=udp:
>>>>>>>> 192.254.110.41:5060>
>>>>>>>> Route:
>>>>>>>> <sip:127.0.0.1;r2=on;lr=on;ftag=10.246.9.8+1+4e9d19+990c8790;ngcplb=yes;socket=udp:
>>>>>>>> 192.254.110.41:5060>
>>>>>>>> Route: <sip:127.0.0.1:5062
>>>>>>>> ;lr=on;ftag=10.246.9.8+1+4e9d19+990c8790;did=dce.2ea;ice_caller=strip;ice_callee=strip;aset=50;rtpprx=yes;vsf=cmVrY3ZlX1B+RDpvbXsmFyMHHWomPikxNCEOAyQfbHo6Jjg->
>>>>>>>>
>>>>>>>> On Thu, Jun 23, 2016 at 3:21 AM, Daniel Grotti <
>>>>>>>> <dgrotti at sipwise.com>dgrotti at sipwise.com> wrote:
>>>>>>>>
>>>>>>>>> Hi Alejandro,
>>>>>>>>> how the ACK looks like ?
>>>>>>>>> Maybe some missing Route headers ?
>>>>>>>>>
>>>>>>>>> Can you share the ACK received by LB ?
>>>>>>>>>
>>>>>>>>> Regards,
>>>>>>>>> * Daniel Grotti *
>>>>>>>>> Head of Customer Support
>>>>>>>>>
>>>>>>>>> Sipwise GmbH <http://www.sipwise.com> , Campus 21/Europaring F15
>>>>>>>>> AT-2345 Brunn am Gebirge
>>>>>>>>>
>>>>>>>>> Phone: +43(0)1 301 2032 <callto:+4313012032>
>>>>>>>>> Email: <dgrotti at sipwise.com> <dgrotti at sipwise.com>
>>>>>>>>> dgrotti at sipwise.com
>>>>>>>>> Website: <http://www.sipwise.com> <http://www.sipwise.com>
>>>>>>>>> www.sipwise.com
>>>>>>>>>
>>>>>>>>> Particulars according Austrian Companies Code paragraph 14
>>>>>>>>> "Sipwise GmbH" - Europaring F15 - 2345 Brunn am Gebirge
>>>>>>>>> FN:305595f, Commercial Court Vienna, ATU64002206
>>>>>>>>> On 06/23/2016 12:43 AM, Abel Alejandro wrote:
>>>>>>>>>
>>>>>>>>> The subject and the first line of the message are a bit different,
>>>>>>>>> let me rephrase. The problem is it seems the one leg sends a ACK in
>>>>>>>>> response to a 200 OK to the sipwise, but the sipwise never sends the ACK to
>>>>>>>>> the other leg, therefore the other leg keeps retrying sending the 200 OK.
>>>>>>>>>
>>>>>>>>> Thanks!
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Wed, Jun 22, 2016 at 6:34 PM, Abel Alejandro <
>>>>>>>>> <aalejandro at alliedtechnologygrouppr.com>
>>>>>>>>> aalejandro at alliedtechnologygrouppr.com> wrote:
>>>>>>>>>
>>>>>>>>>> Hello,
>>>>>>>>>>
>>>>>>>>>> My calls are working however I just want to clarify something.
>>>>>>>>>> When a call comes thru, after the endpoint sends a 200 OK to sipwise
>>>>>>>>>> (192.254.110.41), it seems sipwise doesnt forward this to the other leg of
>>>>>>>>>> the call, is this normal?
>>>>>>>>>>
>>>>>>>>>> Pictures of both legs:
>>>>>>>>>>
>>>>>>>>>> <https://dl.dropboxusercontent.com/u/41014173/lega.PNG>
>>>>>>>>>> https://dl.dropboxusercontent.com/u/41014173/lega.PNG
>>>>>>>>>> <https://dl.dropboxusercontent.com/u/41014173/legb.png>
>>>>>>>>>> https://dl.dropboxusercontent.com/u/41014173/legb.png
>>>>>>>>>>
>>>>>>>>>> SIPWise info:
>>>>>>>>>>
>>>>>>>>>> root at sip:/var/log/ngcp# cat /etc/sipwise_ngcp_version
>>>>>>>>>> System installed. NGCP version mr3.4.2 on 2014-11-20 02:35:58
>>>>>>>>>> System installed. NGCP version mr3.5.1 - upgraded on 2014-11-20
>>>>>>>>>> 03:26:29
>>>>>>>>>> System installed. NGCP version mr3.6.1 - upgraded on 2014-11-20
>>>>>>>>>> 03:42:49
>>>>>>>>>> System installed. NGCP version mr3.7.1 - upgraded on 2015-02-01
>>>>>>>>>> 11:38:34
>>>>>>>>>> System installed. NGCP version mr3.8.2 - upgraded on 2015-07-27
>>>>>>>>>> 01:06:25
>>>>>>>>>> System installed. NGCP version mr3.8.3 - upgraded on 2015-10-06
>>>>>>>>>> 23:44:13
>>>>>>>>>> System installed. NGCP version mr4.0.1 - upgraded on 2015-10-07
>>>>>>>>>> 00:12:10
>>>>>>>>>> System installed. NGCP version mr4.1.1 - upgraded on 2015-11-20
>>>>>>>>>> 00:25:40
>>>>>>>>>> System installed. NGCP version mr4.1.2 - upgraded on 2016-06-12
>>>>>>>>>> 02:16:40
>>>>>>>>>> System installed. NGCP version mr4.2.1 - upgraded on 2016-06-12
>>>>>>>>>> 05:47:53
>>>>>>>>>> System installed. NGCP version mr4.2.2 - upgraded on 2016-06-22
>>>>>>>>>> 01:53:41
>>>>>>>>>> System installed. NGCP version mr4.3.1 - upgraded on 2016-06-22
>>>>>>>>>> 02:38:38
>>>>>>>>>> System installed. NGCP version mr4.4.1 - upgraded on 2016-06-22
>>>>>>>>>> 02:59:33
>>>>>>>>>>
>>>>>>>>>> root at sip:/var/log/ngcp# grep <C5A0749D at 10.246.9.8>
>>>>>>>>>> C5A0749D at 10.246.9.8 kamailio-lb.log
>>>>>>>>>> Jun 22 18:20:05 sip lb[2914]: NOTICE: <script>: New request on lb
>>>>>>>>>> - M=INVITE R=sip:7877050555 at 192.254.110.41:5060;transport=udp F=
>>>>>>>>>> <sip:7875868313 at 196.12.170.244:5060>
>>>>>>>>>> sip:7875868313 at 196.12.170.244:5060 T=
>>>>>>>>>> <sip:7877050555 at 192.254.110.41:5060>
>>>>>>>>>> sip:7877050555 at 192.254.110.41:5060 IP=udp:196.12.170.244:5060 ID=
>>>>>>>>>> <C5A0749D at 10.246.9.8>C5A0749D at 10.246.9.8 UA='<null>'
>>>>>>>>>> Jun 22 18:20:05 sip lb[2914]: NOTICE: <script>: Relaying request,
>>>>>>>>>> du='sip:127.0.0.1:5062', fs='udp:127.0.0.1:5060' - R=sip:
>>>>>>>>>> 7877050555 at 192.254.110.41:5060;transport=udp ID=
>>>>>>>>>> <C5A0749D at 10.246.9.8>C5A0749D at 10.246.9.8 UA='<null>'
>>>>>>>>>> Jun 22 18:20:05 sip lb[2922]: NOTICE: <script>: Reply from
>>>>>>>>>> Inbound - S=100 - Trying M=INVITE IP=udp:127.0.0.1:5062 ID=
>>>>>>>>>> <C5A0749D at 10.246.9.8>C5A0749D at 10.246.9.8 UA='<null>'
>>>>>>>>>> Jun 22 18:20:05 sip lb[2922]: NOTICE: <script>: Sending reply,
>>>>>>>>>> fs='udp:192.254.110.41:5060' - ID= <C5A0749D at 10.246.9.8>
>>>>>>>>>> C5A0749D at 10.246.9.8 UA='<null>'
>>>>>>>>>> Jun 22 18:20:05 sip lb[2919]: NOTICE: <script>: New request on lb
>>>>>>>>>> - M=INVITE R= <sip:17877050555 at 196.12.166.251:5060>
>>>>>>>>>> sip:17877050555 at 196.12.166.251:5060 F=
>>>>>>>>>> <sip:17875868313 at sip.fusetelecom.com>
>>>>>>>>>> sip:17875868313 at sip.fusetelecom.com T=
>>>>>>>>>> <sip:17877050555 at sip.fusetelecom.com>
>>>>>>>>>> sip:17877050555 at sip.fusetelecom.com IP=udp:127.0.0.1:5080
>>>>>>>>>> <ID=C5A0749D at 10.246.9.8_b2b-1>ID=C5A0749D at 10.246.9.8_b2b-1
>>>>>>>>>> UA='<null>'
>>>>>>>>>> Jun 22 18:20:05 sip lb[2919]: NOTICE: <script>: Relaying request,
>>>>>>>>>> du='<null>', fs='udp:192.254.110.41:5060' - R=
>>>>>>>>>> <sip:17877050555 at 196.12.166.251:5060>
>>>>>>>>>> sip:17877050555 at 196.12.166.251:5060
>>>>>>>>>> <ID=C5A0749D at 10.246.9.8_b2b-1>ID=C5A0749D at 10.246.9.8_b2b-1
>>>>>>>>>> UA='<null>'
>>>>>>>>>> Jun 22 18:20:05 sip lb[2907]: NOTICE: <script>: Reply from
>>>>>>>>>> Outbound - S=100 - Trying M=INVITE IP=udp:196.12.166.251:5060
>>>>>>>>>> <ID=C5A0749D at 10.246.9.8_b2b-1>ID=C5A0749D at 10.246.9.8_b2b-1
>>>>>>>>>> UA='<null>'
>>>>>>>>>> Jun 22 18:20:05 sip lb[2907]: NOTICE: <script>: Sending reply,
>>>>>>>>>> fs='udp:127.0.0.1:5060' - <ID=C5A0749D at 10.246.9.8_b2b-1>
>>>>>>>>>> ID=C5A0749D at 10.246.9.8_b2b-1 UA='<null>'
>>>>>>>>>> Jun 22 18:20:06 sip lb[2909]: NOTICE: <script>: Reply from
>>>>>>>>>> Outbound - S=200 - OK M=INVITE IP=udp:196.12.166.251:5060
>>>>>>>>>> <ID=C5A0749D at 10.246.9.8_b2b-1>ID=C5A0749D at 10.246.9.8_b2b-1
>>>>>>>>>> UA='<null>'
>>>>>>>>>> Jun 22 18:20:06 sip lb[2909]: NOTICE: <script>: Sending reply,
>>>>>>>>>> fs='udp:127.0.0.1:5060' - <ID=C5A0749D at 10.246.9.8_b2b-1>
>>>>>>>>>> ID=C5A0749D at 10.246.9.8_b2b-1 UA='<null>'
>>>>>>>>>> Jun 22 18:20:06 sip lb[2907]: NOTICE: <script>: Reply from
>>>>>>>>>> Outbound - S=200 - OK M=INVITE IP=udp:196.12.166.251:5060
>>>>>>>>>> <ID=C5A0749D at 10.246.9.8_b2b-1>ID=C5A0749D at 10.246.9.8_b2b-1
>>>>>>>>>> UA='<null>'
>>>>>>>>>> Jun 22 18:20:06 sip lb[2907]: NOTICE: <script>: Sending reply,
>>>>>>>>>> fs='udp:127.0.0.1:5060' - <ID=C5A0749D at 10.246.9.8_b2b-1>
>>>>>>>>>> ID=C5A0749D at 10.246.9.8_b2b-1 UA='<null>'
>>>>>>>>>> Jun 22 18:20:06 sip lb[2912]: NOTICE: <script>: Reply from
>>>>>>>>>> Outbound - S=200 - OK M=INVITE IP=udp:196.12.166.251:5060
>>>>>>>>>> <ID=C5A0749D at 10.246.9.8_b2b-1>ID=C5A0749D at 10.246.9.8_b2b-1
>>>>>>>>>> UA='<null>'
>>>>>>>>>> Jun 22 18:20:06 sip lb[2912]: NOTICE: <script>: Sending reply,
>>>>>>>>>> fs='udp:127.0.0.1:5060' - <ID=C5A0749D at 10.246.9.8_b2b-1>
>>>>>>>>>> ID=C5A0749D at 10.246.9.8_b2b-1 UA='<null>'
>>>>>>>>>> Jun 22 18:20:06 sip lb[2920]: NOTICE: <script>: Reply from
>>>>>>>>>> Inbound - S=200 - OK M=INVITE IP=udp:127.0.0.1:5062 ID=
>>>>>>>>>> <C5A0749D at 10.246.9.8>C5A0749D at 10.246.9.8 UA='<null>'
>>>>>>>>>> Jun 22 18:20:06 sip lb[2920]: NOTICE: <script>: Sending reply,
>>>>>>>>>> fs='udp:192.254.110.41:5060' - ID= <C5A0749D at 10.246.9.8>
>>>>>>>>>> C5A0749D at 10.246.9.8 UA='<null>'
>>>>>>>>>> Jun 22 18:20:06 sip lb[2910]: NOTICE: <script>: New request on lb
>>>>>>>>>> - M=ACK
>>>>>>>>>> <R=sip:ngcp-lb at 192.254.110.41:5060;ngcpct=7369703a3132372e302e302e313a353038303b707278726f7574653d31>
>>>>>>>>>> R=sip:ngcp-lb at 192.254.110.41:5060;ngcpct=7369703a3132372e302e302e313a353038303b707278726f7574653d31
>>>>>>>>>> F= <sip:7875868313 at 196.12.170.244:5060>
>>>>>>>>>> sip:7875868313 at 196.12.170.244:5060 T=
>>>>>>>>>> <sip:7877050555 at 192.254.110.41:5060>
>>>>>>>>>> sip:7877050555 at 192.254.110.41:5060 IP=udp:196.12.170.244:5060 ID=
>>>>>>>>>> <C5A0749D at 10.246.9.8>C5A0749D at 10.246.9.8 UA='<null>'
>>>>>>>>>> Jun 22 18:20:06 sip lb[2910]: NOTICE: <script>: Relaying request,
>>>>>>>>>> du='sip:127.0.0.1:5062;lr=on;ftag=10.246.9.8+1+4e9d19+990c8790;did=dce.2ea;ice_caller=strip;ice_callee=strip;aset=50;rtpprx=yes;vsf=cmVrY3ZlX1B+RDpvbXsmFyMHHWomPikxNCEOAyQfbHo6Jjg-',
>>>>>>>>>> fs='udp:127.0.0.1:5060' - R=sip:127.0.0.1:5080;prxroute=1 ID=
>>>>>>>>>> <C5A0749D at 10.246.9.8>C5A0749D at 10.246.9.8 UA='<null>'
>>>>>>>>>> Jun 22 18:20:06 sip lb[2922]: NOTICE: <script>: New request on lb
>>>>>>>>>> - M=ACK R= <sip:17877050555 at 196.12.166.251:5060>
>>>>>>>>>> sip:17877050555 at 196.12.166.251:5060 F=
>>>>>>>>>> <sip:17875868313 at sip.fusetelecom.com>
>>>>>>>>>> sip:17875868313 at sip.fusetelecom.com T=
>>>>>>>>>> <sip:17877050555 at sip.fusetelecom.com>
>>>>>>>>>> sip:17877050555 at sip.fusetelecom.com IP=udp:127.0.0.1:5080
>>>>>>>>>> <ID=C5A0749D at 10.246.9.8_b2b-1>ID=C5A0749D at 10.246.9.8_b2b-1
>>>>>>>>>> UA='<null>'
>>>>>>>>>> Jun 22 18:20:06 sip lb[2922]: NOTICE: <script>: Relaying request,
>>>>>>>>>> du='<null>', fs='udp:192.254.110.41:5060' - R=
>>>>>>>>>> <sip:17877050555 at 196.12.166.251:5060>
>>>>>>>>>> sip:17877050555 at 196.12.166.251:5060
>>>>>>>>>> <ID=C5A0749D at 10.246.9.8_b2b-1>ID=C5A0749D at 10.246.9.8_b2b-1
>>>>>>>>>> UA='<null>'
>>>>>>>>>> Jun 22 18:20:06 sip lb[2919]: NOTICE: <script>: Reply from
>>>>>>>>>> Inbound - S=200 - OK M=INVITE IP=udp:127.0.0.1:5062 ID=
>>>>>>>>>> <C5A0749D at 10.246.9.8>C5A0749D at 10.246.9.8 UA='<null>'
>>>>>>>>>> Jun 22 18:20:06 sip lb[2919]: NOTICE: <script>: Sending reply,
>>>>>>>>>> fs='udp:192.254.110.41:5060' - ID= <C5A0749D at 10.246.9.8>
>>>>>>>>>> C5A0749D at 10.246.9.8 UA='<null>'
>>>>>>>>>> Jun 22 18:20:06 sip lb[2908]: NOTICE: <script>: New request on lb
>>>>>>>>>> - M=ACK
>>>>>>>>>> <R=sip:ngcp-lb at 192.254.110.41:5060;ngcpct=7369703a3132372e302e302e313a353038303b707278726f7574653d31>
>>>>>>>>>> R=sip:ngcp-lb at 192.254.110.41:5060;ngcpct=7369703a3132372e302e302e313a353038303b707278726f7574653d31
>>>>>>>>>> F= <sip:7875868313 at 196.12.170.244:5060>
>>>>>>>>>> sip:7875868313 at 196.12.170.244:5060 T=
>>>>>>>>>> <sip:7877050555 at 192.254.110.41:5060>
>>>>>>>>>> sip:7877050555 at 192.254.110.41:5060 IP=udp:196.12.170.244:5060 ID=
>>>>>>>>>> <C5A0749D at 10.246.9.8>C5A0749D at 10.246.9.8 UA='<null>'
>>>>>>>>>> Jun 22 18:20:06 sip lb[2908]: NOTICE: <script>: Relaying request,
>>>>>>>>>> du='sip:127.0.0.1:5062;lr=on;ftag=10.246.9.8+1+4e9d19+990c8790;did=dce.2ea;ice_caller=strip;ice_callee=strip;aset=50;rtpprx=yes;vsf=cmVrY3ZlX1B+RDpvbXsmFyMHHWomPikxNCEOAyQfbHo6Jjg-',
>>>>>>>>>> fs='udp:127.0.0.1:5060' - R=sip:127.0.0.1:5080;prxroute=1 ID=
>>>>>>>>>> <C5A0749D at 10.246.9.8>C5A0749D at 10.246.9.8 UA='<null>'
>>>>>>>>>> Jun 22 18:20:12 sip lb[2912]: NOTICE: <script>: New request on lb
>>>>>>>>>> - M=BYE
>>>>>>>>>> <R=sip:ngcp-lb at 192.254.110.41:5060;ngcpct=7369703a3132372e302e302e313a353038303b707278726f7574653d31>
>>>>>>>>>> R=sip:ngcp-lb at 192.254.110.41:5060;ngcpct=7369703a3132372e302e302e313a353038303b707278726f7574653d31
>>>>>>>>>> F= <sip:7875868313 at 196.12.170.244:5060>
>>>>>>>>>> sip:7875868313 at 196.12.170.244:5060 T=
>>>>>>>>>> <sip:7877050555 at 192.254.110.41:5060>
>>>>>>>>>> sip:7877050555 at 192.254.110.41:5060 IP=udp:196.12.170.244:5060 ID=
>>>>>>>>>> <C5A0749D at 10.246.9.8>C5A0749D at 10.246.9.8 UA='<null>'
>>>>>>>>>> Jun 22 18:20:12 sip lb[2912]: NOTICE: <script>: Relaying request,
>>>>>>>>>> du='sip:127.0.0.1:5062;lr=on;ftag=10.246.9.8+1+4e9d19+990c8790;did=dce.2ea;ice_caller=strip;ice_callee=strip;aset=50;rtpprx=yes;vsf=cmVrY3ZlX1B+RDpvbXsmFyMHHWomPikxNCEOAyQfbHo6Jjg-',
>>>>>>>>>> fs='udp:127.0.0.1:5060' - R=sip:127.0.0.1:5080;prxroute=1 ID=
>>>>>>>>>> <C5A0749D at 10.246.9.8>C5A0749D at 10.246.9.8 UA='<null>'
>>>>>>>>>> Jun 22 18:20:12 sip lb[2921]: NOTICE: <script>: Reply from
>>>>>>>>>> Inbound - S=100 - Trying M=BYE IP=udp:127.0.0.1:5062 ID=
>>>>>>>>>> <C5A0749D at 10.246.9.8>C5A0749D at 10.246.9.8 UA='<null>'
>>>>>>>>>> Jun 22 18:20:12 sip lb[2921]: NOTICE: <script>: Sending reply,
>>>>>>>>>> fs='udp:192.254.110.41:5060' - ID= <C5A0749D at 10.246.9.8>
>>>>>>>>>> C5A0749D at 10.246.9.8 UA='<null>'
>>>>>>>>>> Jun 22 18:20:12 sip lb[2915]: NOTICE: <script>: New request on lb
>>>>>>>>>> - M=BYE R= <sip:17877050555 at 196.12.166.251:5060>
>>>>>>>>>> sip:17877050555 at 196.12.166.251:5060 F=
>>>>>>>>>> <sip:17875868313 at sip.fusetelecom.com>
>>>>>>>>>> sip:17875868313 at sip.fusetelecom.com T=
>>>>>>>>>> <sip:17877050555 at sip.fusetelecom.com>
>>>>>>>>>> sip:17877050555 at sip.fusetelecom.com IP=udp:127.0.0.1:5080
>>>>>>>>>> <ID=C5A0749D at 10.246.9.8_b2b-1>ID=C5A0749D at 10.246.9.8_b2b-1
>>>>>>>>>> UA='<null>'
>>>>>>>>>> Jun 22 18:20:12 sip lb[2915]: NOTICE: <script>: Relaying request,
>>>>>>>>>> du='<null>', fs='udp:192.254.110.41:5060' - R=
>>>>>>>>>> <sip:17877050555 at 196.12.166.251:5060>
>>>>>>>>>> sip:17877050555 at 196.12.166.251:5060
>>>>>>>>>> <ID=C5A0749D at 10.246.9.8_b2b-1>ID=C5A0749D at 10.246.9.8_b2b-1
>>>>>>>>>> UA='<null>'
>>>>>>>>>> Jun 22 18:20:12 sip lb[2910]: NOTICE: <script>: Reply from
>>>>>>>>>> Outbound - S=200 - OK M=BYE IP=udp:196.12.166.251:5060
>>>>>>>>>> <ID=C5A0749D at 10.246.9.8_b2b-1>ID=C5A0749D at 10.246.9.8_b2b-1
>>>>>>>>>> UA='<null>'
>>>>>>>>>> Jun 22 18:20:12 sip lb[2910]: NOTICE: <script>: Sending reply,
>>>>>>>>>> fs='udp:127.0.0.1:5060' - <ID=C5A0749D at 10.246.9.8_b2b-1>
>>>>>>>>>> ID=C5A0749D at 10.246.9.8_b2b-1 UA='<null>'
>>>>>>>>>> Jun 22 18:20:12 sip lb[2918]: NOTICE: <script>: Reply from
>>>>>>>>>> Inbound - S=200 - OK M=BYE IP=udp:127.0.0.1:5062 ID=
>>>>>>>>>> <C5A0749D at 10.246.9.8>C5A0749D at 10.246.9.8 UA='<null>'
>>>>>>>>>> Jun 22 18:20:12 sip lb[2918]: NOTICE: <script>: Sending reply,
>>>>>>>>>> fs='udp:192.254.110.41:5060' - ID= <C5A0749D at 10.246.9.8>
>>>>>>>>>> C5A0749D at 10.246.9.8 UA='<null>'
>>>>>>>>>> root at sip:/var/log/ngcp#
>>>>>>>>>>
>>>>>>>>>> root at sip:/var/log/ngcp# grep <C5A0749D at 10.246.9.8>
>>>>>>>>>> C5A0749D at 10.246.9.8 kamailio-proxy.log
>>>>>>>>>> Jun 22 18:20:05 sip proxy[3785]: NOTICE: <script>: New request on
>>>>>>>>>> proxy - M=INVITE R=sip:7877050555 at 192.254.110.41:5060;transport=udp
>>>>>>>>>> F= <sip:7875868313 at 196.12.170.244:5060>
>>>>>>>>>> sip:7875868313 at 196.12.170.244:5060 T=
>>>>>>>>>> <sip:7877050555 at 192.254.110.41:5060>
>>>>>>>>>> sip:7877050555 at 192.254.110.41:5060 IP=196.12.170.244:5060 (
>>>>>>>>>> 127.0.0.1:5060) ID= <C5A0749D at 10.246.9.8>C5A0749D at 10.246.9.8
>>>>>>>>>> UA='<null>'
>>>>>>>>>> Jun 22 18:20:05 sip proxy[3785]: NOTICE: <script>: Call from PSTN
>>>>>>>>>> - R=sip:7877050555 at 192.254.110.41:5060;transport=udp ID=
>>>>>>>>>> <C5A0749D at 10.246.9.8>
>>>>>>>>>>
>>>>>>>>>
--
*Abel Alejandro*
787 586 8313 | 787 705 0555
<joquendo at alliedtechnologygrouppr.com>
400 Calle Calaf 477
San Juan, PR 00918
aalejandro at alliedtechnologygrouppr.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20160630/3f150aaa/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Wireshark ? Call Flow ? compare_481.png
Type: image/png
Size: 274039 bytes
Desc: not available
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20160630/3f150aaa/attachment-0001.png>
More information about the Spce-user
mailing list