- Joined
- Jul 1, 2008
- Messages
- 56
- Reaction score
- 0
I have learnt a little more now....
I am setting up a voip gateway!!
In anycase below are the result from the server status menu in the server software.
12:35:29.553 StunClient:rocess [CM506003]: Resolved SIP external IPort has changed to (60.241.164.205:9167) on Transport 192.168.43.222:5060
12:35:29.288 StunClient:nInitTests [CM506001]: STUN request to resolve SIP external IPort mapping is sent to STUN server 75.101.138.128:3478 over Transport 192.168.43.222:5060
12:15:29.257 StunClient:rocess [CM506003]: Resolved SIP external IPort has changed to (60.241.164.205:8241) on Transport 192.168.43.222:5060
12:15:28.991 StunClient:nInitTests [CM506001]: STUN request to resolve SIP external IPort mapping is sent to STUN server 75.101.138.128:3478 over Transport 192.168.43.222:5060
Is this good?
is the pstn line setup correctly?
How can i test this?
Ilan
I am setting up a voip gateway!!
In anycase below are the result from the server status menu in the server software.
12:35:29.553 StunClient:rocess [CM506003]: Resolved SIP external IPort has changed to (60.241.164.205:9167) on Transport 192.168.43.222:5060
12:35:29.288 StunClient:nInitTests [CM506001]: STUN request to resolve SIP external IPort mapping is sent to STUN server 75.101.138.128:3478 over Transport 192.168.43.222:5060
12:15:29.257 StunClient:rocess [CM506003]: Resolved SIP external IPort has changed to (60.241.164.205:8241) on Transport 192.168.43.222:5060
12:15:28.991 StunClient:nInitTests [CM506001]: STUN request to resolve SIP external IPort mapping is sent to STUN server 75.101.138.128:3478 over Transport 192.168.43.222:5060
Is this good?
is the pstn line setup correctly?
How can i test this?
Ilan