MCPcopy Create free account
hub / github.com/RangeNetworks/openbts / parseURI

Function parseURI

SIP/SIPParse.cpp:299–308  ·  view source on GitHub ↗

We are not currently using this because we dont care about them. The uri-parameters appear within the and are: transport,user,moethod,ttl,lr. The headers appear after '&' with the In To: and From: there are generic-parameters after the URI outside the <>, including tag.

Source from the content-addressed store, hash-verified

297// The headers appear after '&' with the <uri>
298// In To: and From: there are generic-parameters after the URI outside the <>, including tag.
299string parseURI(const char *buffer, SipParamList &uriparams, SipParamList &headers)
300{
301 try {
302 SipParseLine parser(buffer);
303 return parser.parseLineURI(uriparams,headers);
304 } catch (...) {
305 LOG(DEBUG) << "Caught SIP Parse error";
306 return "";
307 }
308}
309
310// Extract a SIP parameter from a string containing a list of parameters. They look like ;param1=value;param2=value ...
311// The input string need not start exactly at the beginning of the list.

Callers

nothing calls this directly

Calls 1

parseLineURIMethod · 0.80

Tested by

no test coverage detected