T22P 2 account VPN and not

[s.pisani]

It's a shame. It's seems not too hard to use the outgoing interface IP instead of VPN one in the SIP message.

192.168.203.22 is the IP from VPN

Code:

INVITE sip:902@192.168.4.24:6565 SIP/2.0
Via: SIP/2.0/UDP 192.168.203.22:5063;branch=z9hG4bK3156869259
From: "100" <sip:100@192.168.4.24:6565>;tag=2372591398
To: <sip:902@192.168.4.24:6565>
Call-ID: 849277460@192.168.203.22
CSeq: 2 INVITE
Contact: <sip:100@192.168.203.22:5063>
Authorization: Digest username="100", realm="asterisk", nonce="4b0fcec0", uri="sip:902@192.168.4.24:6565", response="dd0515a91d885dbf67b600452764fd6e", algorithm=MD5
Content-Type: application/sdp
Allow: INVITE, INFO, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, REFER, PUBLISH, UPDATE, MESSAGE
Max-Forwards: 70
User-Agent: Yealink SIP-T22P 7.73.0.40
Supported: replaces
Allow-Events: talk,hold,conference,refer,check-sync
Content-Length: 239

v=0
o=- 20006 20006 IN IP4 192.168.203.22
s=SDP data
c=IN IP4 192.168.203.22
t=0 0
m=audio 11788 RTP/AVP 0 8 101
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=fmtp:101 0-15
a=rtpmap:101 telephone-event/8000
a=ptime:20
a=sendrecv