You're showing our internal IP on the INVITE, net2phone can't contact that. Kinda stupid that the devconnect example uses settings if you have an external IP on the IP Office.
Under LAN1 -> Network Topology change firewall to "Blocking firewall" or "Static port block" and put your external IP in "Public IP Adress", that should do it.
When doing a monitor trace check that it's showing the external IP in the INVITE.
3001761mS SIP Call Tx: 17
INVITE sip:9548460000@byod1.net2phone.com: SIP/2.0
Via: SIP/2.0/UDP 192.168.2.10:5060;rport;branch=z9hG4bKc2fed1e9b4bc42602c94c25e575c4550
From: "Agent1" <sip:12422258775@byod1.net2phone.com>;tag=27f29a0fedf27ea4
To: <sip:9548460000@byod1.net2phone.com:>
Call-ID: 58d2512f00ea5b64638353010ba122e3@192.168.2.10
CSeq: 1510524972 INVITE
Contact: "Agent1" <sip:12422258775@192.168.2.10:5060;transport=udp>
Max-Forwards: 70
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, INFO, UPDATE
Content-Type: application/sdp
Supported: timer
P-Asserted-Identity: "Agent1" <sip:12422258775@192.168.2.10:5060>
Content-Length: 251
v=0
o=UserA 1700007074 1324303714 IN IP4 192.168.2.10
s=Session SDP
c=IN IP4 192.168.2.10
t=0 0
m=audio 49152 RTP/AVP 0 18 101
a=rtpmap:0 PCMU/8000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
"Trying is the first step to failure..." - Homer