Allow alphanumeric DIDs to support sipgate

Sipgate is using as default an alphanumeric SIP-ID. To match this SIP-ID in an incoming route, the FreePBX form should allow alphanumeric DIDs (1234567*e0*).

Currently it is only able to use alphanumeric DIDs in Incoming Routes by SQL query.

INVITE sip:1234567e0@69.123.456.78:5060;line=silglkk SIP/2.0
Record-Route: <sip:217.10.79.9;lr;ftag=as3713d7d5>
Record-Route: <sip:172.20.40.5;lr>
Record-Route: <sip:217.10.68.137;lr;ftag=as3713d7d5>
Via: SIP/2.0/UDP 217.10.79.9;branch=z9hG4bKed6a.a05fdcfc3de278f5a0360bf8ce963cdf.0
Via: SIP/2.0/UDP 172.20.40.5;branch=z9hG4bKed6a.bc0c7e2256d587682a7414ba8e2c55cd.0
Via: SIP/2.0/UDP 217.10.68.137;branch=z9hG4bKed6a.063b8d49ce39ac019b150f3c54f5f72c.0
Via: SIP/2.0/UDP 212.9.14.143:5060;branch=z9hG4bK28c4b233
Max-Forwards: 67
From: "01234567890" <sip:01234567890@sipgate.de>;tag=as3713d7d5
To: <sip:1234567e0@sipgate.de>
Contact: <sip:01234567890@212.9.14.143:5060>
Call-ID: 4aefd1180a10205331757ba84a0a3646@sipgate.de
CSeq: 103 INVITE
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces
Content-Type: application/sdp
Content-Length: 399