Mailing List CGatePro@mail.stalker.com Message #106168
From: Roberto Michelena <rmichelena@mac.com>
Subject: Re: PBX
Date: Sun, 04 Sep 2016 23:54:26 -0500
To: CommuniGate Pro Discussions <CGatePro@mail.stalker.com>
X-Mailer: Apple Mail (2.3124)
I made a lot of tests - on a separate email will report the results of using browsers as VoIP Pronto clients, which I guess is not a priority for most users of CGPro’s VoIP functionality.

I managed to get audio in the calls by removing the WAN IP from CGPro’s config.
Which shouldn’t be the case and surely will bring some trouble on other fronts.
Details below, please what am I doing wrong?

Now I do have audio between two Cisco phones, between a GoIP device and a Cisco phone, and between an iOS Pronto client and a Cisco phone. The only thing I had to do was remove the “WAN IP” from CGPro’s settings. So, question is then, why did I have to do that?

My network configs are as follows:
- One CGPro server with two ethernet interfaces: one to a switch that manages the data network (email, etc.) and one to a PoE switch that handles the VoIP network (a few Cisco phones, one GoIP GSM Gateway, one Grandstream PSTN gateway)
- each switch is also connected to each port of a Mikrotik router that NATs the internet
- two network address ranges: 10.10.10.x (data) and 192.168.15.x (VoIP) ; for each network there is a server address and a gateway address.
- so the CGPro server has one address on each interfase, belonging to each network. It has 10.10.10.5 and 192.168.15.5 ; and each also has it’s associated DNS and Gateway address, which in fact point to the same router which has an address on each port.

In the Network configs of CGPro webadmin, under settings->network->LAN IP both ranges have been included; they’ve also been included in the Client IPs tab although supposedly the “Process LAN IP Addresses as Clients” tab should handle that.
And the WAN IP was filled with the actual public (internet) IP of which the router sends everything to the CGPro server (a DMZ).
And “server LAN IP Address” popup is set to “Disabled"

SO HERE COMES THE WEIRD THING
- as long as there’s a WAN address, CGPro seems to tell the SIP clients to go send their audio packets there; calls connect but no audio.
- if I remove the WAN address, suddenly it all works
- if I change the “server LAN IP Address” popup to the server’s address on the VoIP network, calls don’t even connect.

So why does CGPro, when the WAN IP address is filled, sends the SIP clients on a wild goose chase pointing them to the internet? both ends of the call have registered from local addresses, with account and password… and yes, those addresses are NATed whenever a call comes from/to the internet, but not when calling each other within the local network…

the relevant portion of the logs, where it’s telling the clients to send the audio to the WAN, seems to be here:

20:42:50.248 2 MEDIAPROXY-000014 created for DIALOG-000009
20:42:50.248 2 UDPPROXY-000028 created (port=60000/2) for MEDIAPROXY-000014
20:42:50.248 2 UDPPROXY-000028 processing started
20:42:50.248 2 MEDIAPROXY-000014 audio: UDPPROXY-000028 created
20:42:50.248 2 UDPPROXY-000028 [192.168.15.248]:24156:24157 by SDP <-> [0.0.0.0]:0:0(flex)
20:42:50.248 2 DIALOG-000009 MEDIAPROXY-000014 created (NAT) initial
20:42:50.248 2 UDPPROXY-000028 60000: started(high pty)
20:42:50.248 2 SIPC-000082 request SDP (initial offer) modified
20:42:50.248 2 UDPPROXY-000028 60001: started

* so what was that line above about NAT? and offer modified? and in this next lines below, the WAN address (190.117.85.50) is suddenly involved

20:42:50.248 2 SIPDATA-004380 out: req [190.117.85.50]:5060 -> udp[192.168.15.227]:5060 INVITE(1354 bytes) sip:118@192.168.15.227:5060;user=phone;transport=udp
20:42:50.248 2 SIPC-000082 SIPDATA-004380 INVITE sip:118@192.168.15.227:5060;user=phone;transport=udp sent [190.117.85.50]:5060 -> udp[192.168.15.227]:5060

Roberto

(commented log of the whole transaction below)

**USER ACTION: ext 119 (ip 192.168.15.248) dials ext 118 (ip 192.168.15.227)

20:42:50.035 2 SIPDATA-004374 inp: req [0.0.0.0]:5060 <- udp[192.168.15.248]:50493 INVITE(968 bytes) sip:118@pbx.infinitek.com.pe;user=phone
20:42:50.035 2 SIPDATA-004374 created SIPS-004258
20:42:50.035 2 SIPS-004258 SIPDATA-004374 INVITE sip:118@pbx.infinitek.com.pe;user=phone from udp[192.168.15.248]:50493
20:42:50.036 2 SIPDATA-004375 out: rsp [0.0.0.0]:5060 -> udp[192.168.15.248]:5060 100-INVITE(345 bytes)
20:42:50.036 2 SIPS-004258 SIPDATA-004375 100-INVITE(trying) sent [0.0.0.0]:5060 -> udp[192.168.15.248]:5060
20:42:50.036 2 SIPS-004258 SIGNAL-004224 created
20:42:50.036 2 SIGNAL-004224 SIPS-004258: INVITE(101) sip:118@pbx.infinitek.com.pe;user=phone
20:42:50.036 3 SIGNAL-004224 rejecting INVITE from roberto@infinitek.com.pe w/o authentication
20:42:50.036 2 SIGNAL-004224 401 generated
20:42:50.036 2 SIGNAL-004224 401-INVITE reporting
20:42:50.036 2 SIGNAL-004224 releasing
20:42:50.036 2 SIPDATA-004376 out: rsp [0.0.0.0]:5060 -> udp[192.168.15.248]:5060 401-INVITE(494 bytes)
20:42:50.036 2 SIPS-004258 SIPDATA-004376 401-INVITE(final) sent [0.0.0.0]:5060 -> udp[192.168.15.248]:5060
20:42:50.174 2 SIPDATA-004377 inp: req [0.0.0.0]:5060 <- udp[192.168.15.248]:50524 ACK(357 bytes) sip:118@pbx.infinitek.com.pe;user=phone
20:42:50.174 2 SIPDATA-004377 sent to SIPS-004258
20:42:50.174 2 SIPS-004258 SIPDATA-004377 ACK suppl-request
20:42:50.174 2 SIPS-004258 SIPDATA-004377 confirmed: ACK received
20:42:50.243 2 SIPDATA-004378 inp: req [0.0.0.0]:5060 <- udp[192.168.15.248]:50493 INVITE(1238 bytes) sip:118@pbx.infinitek.com.pe;user=phone
20:42:50.243 2 SIPDATA-004378 created SIPS-004260
20:42:50.243 2 SIPS-004260 SIPDATA-004378 INVITE sip:118@pbx.infinitek.com.pe;user=phone from udp[192.168.15.248]:50493
20:42:50.243 2 SIPDATA-004379 out: rsp [0.0.0.0]:5060 -> udp[192.168.15.248]:5060 100-INVITE(345 bytes)
20:42:50.243 2 SIPS-004260 SIPDATA-004379 100-INVITE(trying) sent [0.0.0.0]:5060 -> udp[192.168.15.248]:5060
20:42:50.243 2 SIPS-004260 SIGNAL-004226 created
20:42:50.243 2 SIGNAL-004226 SIPS-004260: INVITE(102) sip:118@pbx.infinitek.com.pe;user=phone
20:42:50.243 2 DIALOG-000009 created for SIGNAL-004226:[192.168.15.248]
20:42:50.243 2 SIGNAL-004226 DIALOG-000009 created
20:42:50.244 2 SIGNAL-004226 INVITE sip:118@pbx.infinitek.com.pe;user=phone via sip:118@pbx.infinitek.com.pe;user=phone
20:42:50.248 2 SIGNAL-004226 leandro@infinitek.com.pe has 1 registration(s)
20:42:50.248 2 SIGNAL-004226 SIPS-004260: {1/1} sent to SIPC-000082: INVITE sip:118@192.168.15.227:5060;user=phone;transport=udp
20:42:50.248 2 SIPC-000082 SIGNAL-004226 INVITE sip:118@192.168.15.227:5060;user=phone;transport=udp
20:42:50.248 2 MEDIAPROXY-000014 created for DIALOG-000009
20:42:50.248 2 UDPPROXY-000028 created (port=60000/2) for MEDIAPROXY-000014
20:42:50.248 2 UDPPROXY-000028 processing started
20:42:50.248 2 MEDIAPROXY-000014 audio: UDPPROXY-000028 created
20:42:50.248 2 UDPPROXY-000028 [192.168.15.248]:24156:24157 by SDP <-> [0.0.0.0]:0:0(flex)
20:42:50.248 2 DIALOG-000009 MEDIAPROXY-000014 created (NAT) initial
20:42:50.248 2 UDPPROXY-000028 60000: started(high pty)
20:42:50.248 2 SIPC-000082 request SDP (initial offer) modified
20:42:50.248 2 UDPPROXY-000028 60001: started

      * so what was that line above about NAT? and offer modified? and in this next line below, the WAN address (190.117.85.50) is suddenly involved

20:42:50.248 2 SIPDATA-004380 out: req [190.117.85.50]:5060 -> udp[192.168.15.227]:5060 INVITE(1354 bytes) sip:118@192.168.15.227:5060;user=phone;transport=udp
20:42:50.248 2 SIPC-000082 SIPDATA-004380 INVITE sip:118@192.168.15.227:5060;user=phone;transport=udp sent [190.117.85.50]:5060 -> udp[192.168.15.227]:5060
20:42:50.412 2 SIPDATA-004381 inp: rsp [0.0.0.0]:5060 <- udp[192.168.15.227]:50062 100-INVITE(621 bytes)
20:42:50.412 2 SIPDATA-004381 sent to SIPC-000082
20:42:50.412 2 SIPC-000082 SIPDATA-004381 100-INVITE received
20:42:50.412 3 SIPC-000082 2 Record-Route field(s) in non-starting response, clearing
20:42:50.544 2 SIPDATA-004382 inp: rsp [0.0.0.0]:5060 <- udp[192.168.15.227]:50062 180-INVITE(660 bytes)
20:42:50.544 2 SIPDATA-004382 sent to SIPC-000082
20:42:50.544 2 SIPC-000082 SIPDATA-004382 180-INVITE received
20:42:50.544 2 DIALOG-000009 provisioned
20:42:50.548 2 SIPDATA-004383 out: rsp [0.0.0.0]:5060 -> udp[192.168.15.248]:5060 180-INVITE(595 bytes)
20:42:50.548 2 SIPS-004260 SIPDATA-004383 180-INVITE(provisioning) sent [0.0.0.0]:5060 -> udp[192.168.15.248]:5060



**USER ACTION: ext 118 picks up - call is supposedly established, but NO AUDIO

20:43:12.177 2 SIPDATA-004384 inp: rsp [0.0.0.0]:5060 <- udp[192.168.15.227]:50062 200-INVITE(982 bytes)
20:43:12.177 2 SIPDATA-004384 sent to SIPC-000082
20:43:12.177 2 SIPC-000082 SIPDATA-004384 200-INVITE received
20:43:12.177 2 DIALOG-000009 CALLEE(0012dadbe040000c3f436fc1-2421ca3f) media set:[192.168.15.227]
20:43:12.177 2 UDPPROXY-000028 [192.168.15.248]:24156:24157 <-> [192.168.15.227]:26284:26285 by SDP
20:43:12.177 2 DIALOG-000009 CALLEE(0012dadbe040000c3f436fc1-2421ca3f) MEDIAPROXY-000014 modified <- initial answer SDP for [192.168.15.248]
20:43:12.177 2 SIPC-000082 response SDP (initial answer) modified
20:43:12.177 2 DIALOG-000009 CALLEE(0012dadbe040000c3f436fc1-2421ca3f) connected
20:43:12.177 2 ACCOUNT(roberto) out call connected. alerting=22 sec
20:43:12.177 2 ACCOUNT(leandro) inp call connected. alerting=22 sec
20:43:12.181 2 SIGNAL-004226 200-INVITE reporting
20:43:12.181 2 SIGNAL-004226 releasing
20:43:12.181 2 SIPDATA-004385 out: rsp [0.0.0.0]:5060 -> udp[192.168.15.248]:5060 200-INVITE(996 bytes)
20:43:12.181 2 SIPS-004260 SIPDATA-004385 200-INVITE(final) sent [0.0.0.0]:5060 -> udp[192.168.15.248]:5060
20:43:12.375 2 SIPDATA-004386 inp: req [0.0.0.0]:5060 <- udp[192.168.15.248]:50525 ACK(780 bytes) sip:118@192.168.15.227:5060;user=phone;transport=udp
20:43:12.375 2 SIPDATA-004386 created SIPS-004262
20:43:12.375 2 SIPS-004262 SIPDATA-004386 ACK sip:118@192.168.15.227:5060;user=phone;transport=udp from udp[192.168.15.248]:50525
20:43:12.375 2 SIPS-004262 SIGNAL-004228 created
20:43:12.375 2 SIGNAL-004228 SIPS-004262:downstreaming ACK(102) sip:118@192.168.15.227:5060;user=phone;transport=udp
20:43:12.375 2 SIGNAL-004228 SIPS-004262 downstreamed to SIPC-000084: ACK sip:118@192.168.15.227:5060;user=phone;transport=udp
20:43:12.375 2 SIPC-000084 SIGNAL-004228 downstreaming ACK sip:118@192.168.15.227:5060;user=phone;transport=udp
20:43:12.375 2 SIGNAL-004228 releasing
20:43:12.375 2 SIPDATA-004387 out: req [190.117.85.50]:5060 -> udp[192.168.15.227]:5060 ACK(557 bytes) sip:118@192.168.15.227:5060;user=phone;transport=udp
20:43:12.375 2 SIPC-000084 SIPDATA-004387 ACK sip:118@192.168.15.227:5060;user=phone;transport=udp sent [190.117.85.50]:5060 -> udp[192.168.15.227]:5060


**USER ACTION: ext 119 hangs up ending the call

20:44:04.135 2 SIPDATA-004388 inp: req [0.0.0.0]:5060 <- udp[192.168.15.248]:50526 BYE(793 bytes) sip:118@192.168.15.227:5060;user=phone;transport=udp
20:44:04.138 2 SIPDATA-004388 created SIPS-004264
20:44:04.138 2 SIPS-004264 SIPDATA-004388 BYE sip:118@192.168.15.227:5060;user=phone;transport=udp from udp[192.168.15.248]:50526
20:44:04.138 2 SIPS-004264 SIGNAL-004230 created
20:44:04.138 2 SIGNAL-004230 SIPS-004264: BYE(103) sip:118@192.168.15.227:5060;user=phone;transport=udp
20:44:04.139 2 SIGNAL-004230 BYE sip:118@192.168.15.227:5060;user=phone;transport=udp via sip:118@192.168.15.227:5060;user=phone;transport=udp
20:44:04.139 2 SIGNAL-004230 SIPS-004264: {1/1} sent to SIPC-000086: BYE sip:118@192.168.15.227:5060;transport=udp;maddr=192.168.15.227;user=phone via <sip:192.168.15.227:5060;transport=udp;maddr=192.168.15.227;user=phone;routeonly>
20:44:04.139 2 SIPC-000086 SIGNAL-004230 BYE sip:118@192.168.15.227:5060;transport=udp;maddr=192.168.15.227;user=phone
20:44:04.139 2 SIPDATA-004389 out: req [190.117.85.50]:5060 -> udp[192.168.15.227]:5060 BYE(578 bytes) sip:118@192.168.15.227:5060;transport=udp;maddr=192.168.15.227;user=phone
20:44:04.139 2 SIPC-000086 SIPDATA-004389 BYE sip:118@192.168.15.227:5060;transport=udp;maddr=192.168.15.227;user=phone sent [190.117.85.50]:5060 -> udp[192.168.15.227]:5060
20:44:04.225 2 SIPDATA-004390 inp: rsp [0.0.0.0]:5060 <- udp[192.168.15.227]:50062 200-BYE(448 bytes)
20:44:04.225 2 SIPDATA-004390 sent to SIPC-000086
20:44:04.225 2 SIPC-000086 SIPDATA-004390 200-BYE received
20:44:04.225 2 ACCOUNT(roberto) out call completed(118@pbx.infinitek.com.pe). duration=52 sec
20:44:04.230 2 ACCOUNT(leandro) inp call completed(119@pbx.infinitek.com.pe). duration=52 sec
20:44:04.232 2 DIALOG-000009 dequeued(disconnected)
20:44:04.232 2 MEDIAPROXY-000014 UDPPROXY-000028 removed
20:44:04.233 2 UDPPROXY-000028 60001: finished
20:44:04.338 2 UDPPROXY-000028 60000: finished
20:44:04.443 2 UDPPROXY-000028 released. 0(0) <-> 0(0) sent in 74 seconds
20:44:04.443 2 MEDIAPROXY-000014 released
20:44:04.443 2 SIGNAL-004230 200-BYE reporting
20:44:04.443 2 SIGNAL-004230 releasing
20:44:04.444 2 SIPDATA-004391 out: rsp [0.0.0.0]:5060 -> udp[192.168.15.248]:5060 200-BYE(372 bytes)
20:44:04.444 2 SIPS-004264 SIPDATA-004391 200-BYE(final) sent [0.0.0.0]:5060 -> udp[192.168.15.248]:5060
20:44:25.048 1 ROUTER SYSTEM: 'hudson@infinitek.com.pe' rejected. Error Code=unknown user account
20:44:25.048 1 SMTPI-001166([85.194.93.11]) failed to open ACCOUNT(hudson) for [85.194.93.11]:51480->[10.10.10.5]:25. Error Code=unknown user account
20:44:36.004 2 DIALOG-000009 released

END





Subscribe (FEED) Subscribe (DIGEST) Subscribe (INDEX) Unsubscribe Mail to Listmaster